The NodeIdsof all Nodesdescribed in this standard are only symbolic names. OPC 10000-6defines the actual NodeIds.

The symbolic name of each Nodedefined in this standard 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 standard, the symbolic name is unique. For example, the ServerTypedefined in 6.3.1has the symbolic name “ServerType”. One of its InstanceDeclarationswould be identified as “ServerType.ServerCapabilities”. Since this Objectis complex, another InstanceDeclarationof the ServerTypeis “ServerType.ServerCapabilities.MinSupportedSampleRate”. The Server Objectdefined in 8.3.2is based on the ServerType and has the symbolic name “Server”. Therefore, the instance based on the InstanceDeclarationdescribed above has the symbolic name “Server.ServerCapabilities.MinSupportedSampleRate”.

The NamespaceIndex for all NodeIdsdefined in this standard is 0. The namespace for this NamespaceIndex is specified in OPC 10000-3.

Note that this standard not only defines concrete Nodes, but also requires that some Nodes have to be generated, for example one for each Session running on the Server. The NodeIdsof those Nodesare server-specific, including the Namespace. However the NamespaceIndex of those Nodescannot be the NamespaceIndex 0, because they are not defined by the OPC Foundation but generated by the Server.