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

The symbolic name of each Nodedefined in this specificationis 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 specification, the symbolic name is unique.

The NamespaceUrifor all NodeIdsdefined in this document is defined in Annex A. The NamespaceIndexfor this NamespaceUriis vendor-specific and depends on the position of the NamespaceUriin 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 AutoID Devicerepresented by the Server. 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.