12 Namespaces ToC Previous Next

12.2 Handling of OPC UA Namespaces ToC Previous Next

Namespaces are used by OPC UA to create unique identifiers across different naming authorities. The Attribute’s NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId. Unlike NodeIds, the BrowseName cannot be used to unambiguously identify a Node. Different Nodes may have the same BrowseName. They are used to build a browse path between two Nodes or to define a standard Property.

Servers may often choose to use the same namespace for the NodeId and the BrowseName. However, if they want to provide a standard Property, its BrowseName shall have the namespace of the standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property. All NodeIds of Nodes not defined in this specification shall not use the standard namespaces.

Table 68 - Namespaces used in a PA-DIM ServerTable 68 provides a list of mandatory namespaces used in a Process Automation Device OPC UA Server.

Table 68 - Namespaces used in a PA-DIM Server

NamespaceURI Description Use
http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory
Local Server URI Namespace for nodes defined in the local server. This may include types and instances used in a PA-DIM Device represented by the server. This namespace shall have namespace index 1. Mandatory
http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100. The namespace index is server specific. Mandatory
http://opcfoundation.org/UA/Dictionary/IRDI Namespace for NodeIds for IRDIs using HasDictionaryEntry. The namespace index is server specific. Optional
http://opcfoundation.org/UA/PADIM/ Namespace for NodeIds and BrowseNames defined in this specification. The namespace index is server specific. Mandatory
Vendor specific types and instances A server may provide vendor-specific types like types derived from ObjectTypes defined in this specification or vendor-specific instances of those types in a vendor-specific namespace. Mandatory

Table 69 provides a list of namespaces and their index used for BrowseNames in this specification. The default namespace of this specification is not listed since all BrowseNames without prefix use this default namespace.

Table 69 - Namespaces used in this specification

NamespaceURI Namespace Index Example
http://opcfoundation.org/UA/ 0 0:EngineeringUnits
http://opcfoundation.org/UA/DI/ 2 2:DeviceRevision
http://opcfoundation.org/UA/Dictionary/IRDI 3 3:0112/2///61987#ABH526#001

Previous Next