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 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 that this document not only defines concrete Nodes, but also requires that some Nodesshall be generated, for example one for each Sessionrunning on the Server. The NodeIdsof those Nodesare Server-specific, including the namespace. But the NamespaceIndexof those Nodescannot be the NamespaceIndexused for the Nodesdefined in this document, because they are not defined by this document but generated by the Server.
For InstanceDeclarationsof NodeClass Objectand Variablethat are placeholders (OptionalPlaceholderand MandatoryPlaceholder ModellingRule), the BrowseNameand the DisplayNameare enclosed in angle brackets (<>) as recommended in OPC 10000-3.If the BrowseNameis 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 Propertyof another specification is overwritten or used in the OPC UA types defined in this document. Table 94provides a list of namespaces and their indexes as used in this document.