TASE2BilateralTable
This class describe the sending (providing) side in a bilateral ICCP data exchange. Hence the ICCP bilateral (table) descriptions are created by exchanging ICCP Provider data between the parties.
Type |
Class |
|---|---|
URI |
|
CIM standard (perspective) |
IEC61970 (Grid) |
Slots
| Name | Cardinality | Type | Description |
|---|---|---|---|
1 |
Dataset containing the data objects. |
||
1 |
Provider of information to a remote peer. |
||
0..1 |
Specifies the version of the Bilateral Table configuration that is being exchanged. |
||
0..1 |
The Version attribute identifies a unique version of the Bilateral Table. If any changes are made to a Bilateral Table, then a new unique value for this attribute shall be generated. |
||
0..1 |
Specifies the version of the TASE.2 that is needed to access the Bilateral Table information via TASE.2. In order for a link to be established, both sides must have the same value. |
||
0..* |
Informational message to be included in a Bilateral Table agreement. |
||
0..1 |
Subscriber of information from a remote peer. |
||
0..1 |
The single CIM data object in the appropriate dataset context. |
||
0..1 |
The aliasName is free text human readable name of the object alternative to IdentifiedObject.name. It may be non unique and may not correlate to a naming hierarchy. The attribute aliasName is retained because of backwards compatibility between CIM relases. It is however recommended to replace aliasName with the Name class as aliasName is planned for retirement at a future time. |
||
0..1 |
The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy. |
||
0..1 |
Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. |
||
0..1 |
The name is any free human readable and possibly non unique text naming the object. |
||
0..* |
The diagram objects that are associated with the domain object. |
||
0..* |
All names of this identified object. |
||
0..* |
Data objects registered. |
aliasName
The aliasName is free text human readable name of the object alternative to IdentifiedObject.name. It may be non unique and may not correlate to a naming hierarchy. The attribute aliasName is retained because of backwards compatibility between CIM relases. It is however recommended to replace aliasName with the Name class as aliasName is planned for retirement at a future time.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
bilateralTableID
Specifies the version of the Bilateral Table configuration that is being exchanged.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
bilateralTableVersion
The Version attribute identifies a unique version of the Bilateral Table. If any changes are made to a Bilateral Table, then a new unique value for this attribute shall be generated.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
Consumer
Subscriber of information from a remote peer.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
description
The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
DiagramObjects
The diagram objects that are associated with the domain object.
URI |
|
|---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
ICCPInformationMessage
Informational message to be included in a Bilateral Table agreement.
URI |
|
|---|---|
Cardinality |
0..* |
Type |
InstanceSet
Dataset containing the data objects.
URI |
|
|---|---|
Cardinality |
1 |
Type |
|
Inherited from |
mRID
Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
name
The name is any free human readable and possibly non unique text naming the object.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
Names
All names of this identified object.
URI |
|
|---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
PropertiesCIMDataObject
The single CIM data object in the appropriate dataset context.
URI |
|
|---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
Provider
Provider of information to a remote peer.
URI |
|
|---|---|
Cardinality |
1 |
Type |
|
Inherited from |
TargetingCIMDataObject
Data objects registered.
URI |
|
|---|---|
Cardinality |
0..* |
Type |
|
Inherited from |