Errata exists for this version of the document.

For the purposes of this document, the terms and definitions given in OPC 10000-1 as well as the following apply.

instance of a DataType Node that is used together with the ValueRank Attribute to define the data type of a Variable

NodeId of a DataType Node

Variables that represent values of Objects, either directly or indirectly for complex Variables, where the Variables are always the TargetNode of a HasComponent Reference

ObjectType Node that represents the type definition of an Event

Reference that is used to construct hierarchies in the AddressSpace

Note 1 to entry: All hierarchical ReferenceTypes are derived from HierarchicalReferences.

Node that is used by a complex TypeDefinitionNode to expose its complex structure

Note 1 to entry: It is an instance used by a type definition.

metadata of an InstanceDeclaration that defines how the InstanceDeclaration will be used for instantiation and also defines subtyping rules for an InstanceDeclaration

Variables that are the TargetNode for a HasProperty Reference

Note 1 to entry: Properties describe the characteristics of a Node.

Node having a Reference to another Node

EXAMPLE: In the Reference “A contains B”, “A” is the SourceNode.

Node that is referenced by another Node

EXAMPLE: In the Reference “A Contains B”, “B” is the TargetNode.

Node that is used to define the type of another Node

Note 1 to entry: ObjectType and VariableType Nodes are TypeDefinitionNodes.

Node that represents the type definition for a Variable

UAUnified Architecture

UMLUnified Modeling Language

URIUniform Resource Identifier

W3CWorld Wide Web Consortium

XMLExtensible Markup Language

Nodes and their References to each other are illustrated using figures. Figure 1 illustrates the conventions used in these figures.

Figure 1 – AddressSpace Node diagrams

In these figures, rectangles represent Nodes. Node rectangles may be titled with one or two lines of text. When two lines are used, the first text line in the rectangle identifies the NodeClass and the second line contains the BrowseName. When one line is used, it contains the BrowseName.

Node rectangles may contain boxes used to define their Attributes and References. Specific names in these boxes identify specific Attributes and References.

Shaded rectangles with rounded corners and with arrows passing through them represent References. The arrow that passes through them begins at the SourceNode and points to the TargetNode. References may also be shown by drawing an arrow that starts at the Reference name in the “References” box and ends at the TargetNode.

Clause 5 defines AddressSpace NodeClasses. Table 1 describes the format of the tables used to define NodeClasses.

Table 1 – NodeClass Table Conventions

Name	Use	Data Type	Description
Attributes
“Attribute name”	“M” or “O”	Data type of the Attribute	Defines the Attribute
References
“Reference name”	“1”, “0..1” or “0..*”	Not used	Describes the use of the Reference by the NodeClass
Standard Properties
“Property name”	“M” or “O”	Data type of the Property	Defines the Property

The Name column contains the name of the Attribute, the name of the ReferenceType used to create a Reference or the name of a Property referenced using the HasProperty Reference.

The Use column defines whether the Attribute or Property is mandatory (M) or optional (O). When mandatory the Attribute or Property shall exist for every Node of the NodeClass. For References it specifies the cardinality. The following values may apply:

• “0..*” identifies that there are no restrictions, that is, the Reference does not have to be provided but there is no limitation how often it can be provided;
• “0..1” identifies that the Reference is provided at most once;
• “1” identifies that the Reference shall be provided exactly once.

The Data Type column contains the name of the DataType of the Attribute or Property. It is not used for References.

The Description column contains the description of the Attribute, the Reference or the Property.

Only this standard may define Attributes. Thus, all Attributes of the NodeClass are specified in the table and can only be extended by other parts of this series of standards.

This standard also defines ReferenceTypes, but ReferenceTypes can also be specified by a Server or by a client using the NodeManagement Services specified in OPC 10000-4. Thus, the NodeClass tables contained in this standard can contain the base ReferenceType called References identifying that any ReferenceType may be used for the NodeClass, including system specific ReferenceTypes. The NodeClass tables only specify how the NodeClasses can be used as SourceNodes of References, not as TargetNodes. If a NodeClass table allows a ReferenceType for its NodeClass to be used as SourceNode, this is also true for subtypes of the ReferenceType. However, subtypes of the ReferenceType may restrict its SourceNodes.

This standard defines Properties, but Properties can be defined by other standard organizations or vendors and Nodes can have Properties that are not standardised. Properties defined in this standard are defined by their name, which is mapped to the BrowseName having the NamespaceIndex 0, which represents the Namespace for OPC UA.

The Use column (optional or mandatory) does not imply a specific ModellingRule for Properties. Different Server implementations will choose to use ModellingRules appropriate for them.