Table 27defines the namespace metadata for this specification. The Objectis 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 Part5 for more details.
The information is provided as Objectof type NamespaceMetadataType. This Objectis a component of the Namespaces Objectthat is part of the Server Object. The NamespaceMetadataType ObjectTypeand its Propertiesare defined in Part5.
The version information is also provided as part of the ModelTableEntry in the UANodeSet XML file. The UANodeSet XML schema is defined in Part 6.
Table 27– NamespaceMetadata Object for this Specification
|
Attribute |
Value |
|||
|
BrowseName |
||||
|
References |
BrowseName |
DataType |
Value |
|
|
HasProperty |
NamespaceUri |
String |
||
|
HasProperty |
NamespaceVersion |
String |
1.01 |
|
|
HasProperty |
NamespacePublicationDate |
DateTime |
2020-06-01 00:00:00 |
|
|
HasProperty |
IsNamespaceSubset |
Boolean |
False |
|
|
HasProperty |
StaticNodeIdTypes |
IdType[] |
{Numeric} |
|
|
HasProperty |
StaticNumericNodeIdRange |
NumericRange[] |
Null |
|
|
HasProperty |
StaticStringNodeIdPattern |
String |
Null |
|
Namespaces are used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeIdand BrowseNameare identifiers. A Nodein the UA AddressSpaceis unambiguously identified using a NodeId. Unlike NodeIds, the BrowseNamecannot be used to unambiguously identify a Node. Different Nodesmay have the same BrowseName. They are used to build a browse path between two Nodesor to define a standard Property.
Serversmay often choose to use the same namespace for the NodeIdand the BrowseName. However, if they want to provide a standard Property, its BrowseNameshall have the namespace of the standards body although the namespace of the NodeIdreflects something else, for example the EngineeringUnits Property. All NodeIdsof Nodesnot defined in this document shall not use the standard namespaces.
Table 28provides a list of mandatory and optional namespaces used in an OPC 40082-1 OPC UAServer.
Table 28– Namespaces used in an OPC 40082-1 Server
|
NamespaceURI |
Description |
Use |
|
Namespace for NodeIdsand BrowseNamesdefined 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 device represented by the server. This namespace shall have namespace index 1. |
Mandatory |
|
Namespace for NodeIdsand BrowseNamesdefined in OPC UA Part 100. The namespace index is server specific. |
Mandatory |
|
|
http://opcfoundation.org/UA/PlasticsRubber/ GeneralTypes/ |
Namespace for NodeIdsand BrowseNamesdefined in OPC 40083. The namespace index is server specific. |
Mandatory |
|
http://opcfoundation.org/UA/PlasticsRubber/ TCD/ |
Namespace for NodeIdsand BrowseNamesdefined 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 MachineTypeor MachineStatusTypeor vendor specific instances of devices in a vendor specific namespace. |
Optional |
Table 29provides a list of namespaces and their index used for BrowseNamesin this specification. The default namespace of this specification is not listed since all BrowseNameswithout prefix use this default namespace.
Table 29– Namespaces used in this specification
|
NamespaceURI |
Namespace Index |
Example |
|
0 |
0:NodeVersion |
|
|
2 |
2:DeviceClass |
|
|
3 |
3:MachineInformationType |