The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the actual NodeIds.

The symbolic name of each Node defined in this document is its BrowseName, or, when it is part of another Node, the BrowseName of the other Node, followed by “.” and its own BrowseName. In this case, “part of” means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes which are not part of another Node have a unique name in this document, the symbolic name is unique.

The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri is vendor specific and depends on the position of the NamespaceUri in the server Namespace table.

Note that this document not only defines concrete Nodes, but also requires for some Nodes to be generated; for example, one for each Session running on the Server. The NodeIds of those Nodes are Server specific, including the Namespace. However, the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined in this document, as they are not defined by this document but are generated by the Server.

The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes. The NamespaceUri for all BrowseNames defined in this document is defined in 10.2.

For InstanceDeclarations of NodeClass Objects and Variables that are placeholders (OptionalPlaceholder and MandatoryPlaceholder ModellingRule), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended in OPC 10000-3.

If a BrowseName is not defined by this document, a Namespace index prefix is added to the BrowseName (e.g., prefix '0' leading to ‘0:EngineeringUnits’ or prefix '2' leading to ‘2:DeviceRevision’). This is typically necessary if a Property of another specification is overwritten or used in the OPC UA types defined in this document. Table 146 provides a list of Namespaces and their indexes as used in this document.