3.3 Conventions used in this document
3.3.1 Usage of Other column in type definitions
In all type definitions, the “Other” column defines additional characteristics of the Node. Examples of characteristics that can appear in this column are shown in Table 1.
| Name | Short Name | Description |
| Mandatory | M | The Node has the Mandatory ModellingRule. |
| Optional | O | The Node has the Optional ModellingRule. |
| MandatoryPlaceholder | MP | The Node has the MandatoryPlaceholder ModellingRule. |
| OptionalPlaceholder | OP | The Node has the OptionalPlaceholder ModellingRule. |
| ReadOnly | RO | The Node AccessLevel Attribute has the CurrentRead bit set but not the CurrentWrite bit. |
| ReadWrite | RW | The Node AccessLevel Attribute has the CurrentRead and CurrentWrite bits set. |
| WriteOnly | WO | The Node AccessLevel Attribute has the CurrentWrite bit set but not the CurrentRead bit. |
If multiple characteristics are defined, they are separated by commas. Throughout this document, the short name is used.
3.3.2 Usage of Asset and FunctionalEntity
Clause 6.3 defines an Asset as an Object either derived from FxAssetType or an Object of any type that implements the required Interfaces. Asset (plural Assets) is used throughout this document to designate an instance of such an Object, regardless of whether derived from the type or implementing the Interfaces.
Clause 6.4 defines a FunctionalEntity as an Object either derived from FunctionalEntityType or an Object of any type that implements the required Interface. FunctionalEntity (plural FunctionalEntities) is used throughout this document to designate an instance of such an Object, regardless of whether derived from the type or implementing the Interfaces.
3.3.3 Usage of Instance of a type
In this document, the name of a type without the addition of “Type” is used to indicate an instance of the type. For example, the following phrase, “an instance of ConnectionConfigurationSetType,” can be replaced with “a ConnectionConfigurationSet”. The phrase “instances of ConnectionEndpointType” can be replaced with “ConnectionEndpoints”.
3.3.4 ConformanceUnits and Node definitions
Each Node defined in this document references at least one ConformanceUnit. (defined in OPC 10000-84). If a Server supports the ConformanceUnit, it shall expose the Nodes related to the ConformanceUnit in its AddressSpace. If two Nodes are exposed, all References between the Nodes defined in this document shall be exposed as well.
The relations between Nodes and ConformanceUnits are defined at the end of the tables defining Nodes, one row per ConformanceUnit.