Table 110 defines the namespace metadata for this document. The Object is used to provide version information for the namespace and an indication about static Nodes. Static Nodes are identical for all Attributes in all Servers, including the Value Attribute. See OPC 10000-5 for more details.
The information is provided as Object of type NamespaceMetadataType. This Object is a component of the Namespaces Object that is part of the Server Object. The NamespaceMetadataType ObjectType and its Properties are defined in OPC 10000-5.
The version information is also provided as part of the ModelTableEntry in the UANodeSet XML file. The UANodeSet XML schema is defined in OPC 10000-6.
Table 110 – NamespaceMetadata Object for this Document
Attribute |
Value |
||
BrowseName |
|||
Property |
DataType |
Value |
|
0:NamespaceUri |
0:String |
||
0:NamespaceVersion |
0:String |
1.05.02 |
|
0:NamespacePublicationDate |
0:DateTime |
2022-10-01 |
|
0:IsNamespaceSubset |
0:Boolean |
False |
|
0:StaticNodeIdTypes |
0:IdType [] |
0 |
|
0:StaticNumericNodeIdRange |
0:NumericRange [] |
|
|
0:StaticStringNodeIdPattern |
0:String |
|
Namespaces are used by OPC UA to create unique identifiers across different naming authorities. The Attributes 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 document shall not use the standard namespaces.
Table 111 provides a list of namespaces and their index used for BrowseNames in this document. The default namespace of this document is not listed since all BrowseNames without prefix use this default namespace.
Table 111 – Namespaces used in this document
NamespaceURI |
Namespace Index |
Example |
0 |
0:EngineeringUnits |
|
2 |
2:ApplicationRecordDataType |