The NodeIdsof all Nodesdescribed in this document are only symbolic names. Annex Adefines the actual NodeIds.

The symbolic name of each Nodedefined in this document is its BrowseName, or, when it is part of another Node, the BrowseNameof the other Node, a “.”, and the BrowseNameof itself. In this case “part of” means that the whole has a HasPropertyor HasComponent Referenceto its part. Since all Nodesnot being part of another Nodehave a unique name in this document, the symbolic name is unique.

The namespace for this specification is defined in Annex A. The NamespaceIndex for all NodeIdsdefined in this specification is server specific and depends on the position of the namespace URI in the server namespace table.

Note: This specification does not only define concrete Nodes, but also requires that some Nodes have to be generated, for example one for each device type available in the frame application. The NodeIdsof those Nodesare server-specific, including the Namespace. But the NamespaceIndex of those Nodescannot be the NamespaceIndex used for the Nodes defined by this specification, because they are not defined by this specification but generated by the Server.

The text part of the BrowseNamesfor all Nodesdefined in this specification is specified in the tables defining the Nodes. The NamespaceIndex for all BrowseNamesdefined in this specification is server specific and depends on the position of the namespace URI defined in this specification in the server namespace table.

If the BrowseName is not defined by this specification, a namespace index prefix like ‘0:EngineeringUnits’ is added to the BrowseName. This is typically necessary if a Property of another specification is overwritten or used in the OPC UA types defined in this specification. Table 39provides a list of namespaces used in this specification.