Table 175 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 for more details see OPC 10000-5, NamespaceMetadataType definition.
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 Table 175.
The version information is also provided as part of the ModelTableEntry in the UANodeSet XML file. The UANodeSet XML schema is defined in 15.2.
Table 175 – NamespaceMetadata Object for this Document
|
Attribute |
Value |
||
|
BrowseName |
|||
|
Property |
DataType |
Value |
|
|
NamespaceUri |
String |
||
|
NamespaceVersion |
String |
1.3 |
|
|
NamespacePublicationDate |
DateTime |
2023-07-07 |
|
|
IsNamespaceSubset |
Boolean |
False |
|
|
StaticNodeIdTypes |
IdType [] |
0 |
|
|
StaticNumericNodeIdRange |
NumericRange [] |
0:5000 |
|
|
StaticStringNodeIdPattern |
String |
|
|
Note: The IsNamespaceSubset Property is set to False as the UaNodeSet XML file contains the complete Namespace. Servers only exposing a subset of the Namespace need to change the value to True. The StaticNodeIdTypes are numeric (0).
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 specification shall not use the standard namespaces.
Table 176 provides a list of mandatory and optional namespaces used in an MDIS OPC UA Server.
Table 176 – Namespaces used in a MDIS Server
|
NamespaceURI |
Description |
Use |
|
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 an AutoID Device represented by the Server. This namespace shall have namespace index 1. |
Mandatory |
|
Namespace for NodeIds and BrowseNames defined in This specification. The namespace index is Server specific. |
Mandatory |
|
|
Vendor specific types |
A Server may provide vendor-specific types like types derived from ObjectTypes defined in this specification in a vendor-specific namespace. |
Optional |
|
Vendor specific instances |
A Server provides vendor-specific instances of the standard types or vendor-specific instances of vendor-specific types in a vendor-specific namespace. It is recommended to separate vendor specific types and vendor specific instances into two or more namespaces. |
Mandatory |
Table 177 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 177 – Namespaces used in this document
|
NamespaceURI |
Namespace Index |
Example |
|
0 |
0:EngineeringUnits |
|
|
|
|
|