Table 231, Table 232 and Table 233 define the namespace metadata for this document. Table 231 defines DataTypes that are shared between the AutomationComponent and the ConnectionManager. Table 232 defines the namespace associated with an AutomationComponent. Table 233 defines the namespace associated with a ConnectionManager. The Objects are used to provide version information for the namespaces and an indication of 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 an 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 231 – UAFX Common NamespaceMetadata Object
|
Attribute |
Value |
|
|
BrowseName |
||
|
Property |
DataType |
Value |
|
NamespaceUri |
0:String |
|
|
NamespaceVersion |
0:String |
1.00.00 |
|
NamespacePublicationDate |
0:DateTime |
2022-10-15 |
|
IsNamespaceSubset |
0:Boolean |
False |
|
StaticNodeIdTypes |
0:IdType[] |
0 |
|
StaticNumericNodeIdRange |
0:NumericRange[] |
0:15000 |
|
StaticStringNodeIdPattern |
0:String |
|
Table 232 – AutomationComponent NamespaceMetadata Object
|
Attribute |
Value |
|
|
BrowseName |
||
|
Property |
DataType |
Value |
|
NamespaceUri |
0:String |
|
|
NamespaceVersion |
0:String |
1.00.01 |
|
NamespacePublicationDate |
0:DateTime |
2022-12-02 |
|
IsNamespaceSubset |
0:Boolean |
False |
|
StaticNodeIdTypes |
0:IdType[] |
0 |
|
StaticNumericNodeIdRange |
0:NumericRange[] |
0:15000 |
|
StaticStringNodeIdPattern |
0:String |
|
Table 233 – ConnectionManager NamespaceMetadata Object
|
Attribute |
Value |
|
|
BrowseName |
||
|
Property |
DataType |
Value |
|
NamespaceUri |
0:String |
|
|
NamespaceVersion |
0:String |
1.00.00 |
|
NamespacePublicationDate |
0:DateTime |
2022-10-15 |
|
IsNamespaceSubset |
0:Boolean |
False |
|
StaticNodeIdTypes |
0:IdType[] |
0 |
|
StaticNumericNodeIdRange |
0:NumericRange[] |
0:15000 |
|
StaticStringNodeIdPattern |
0:String |
|
OPC UA uses namespaces 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 234 provides a list of mandatory and optional namespaces used in an OPC UA Server supporting OPC UA FX.
Table 234 – Namespaces used in a UAFX Server
|
NamespaceURI |
Description |
Use |
|
|
Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have the namespace index 0. |
Mandatory |
||
|
Local Server URI |
Namespace for nodes defined in the local server. This may include types and instances used in an OPC UA FX application represented by the Server. This namespace shall have namespace index 1. |
Mandatory |
|
|
Namespace for common datatypes that are shared between a ConnectionManager and an AutomationComponent. |
Mandatory |
||
|
Namespace for NodeIds and BrowseNames defined in the AutomationComponent related part of this document. The namespace index is Server specific. A Server shall support either the AutomationComponent or the ConnectionManager to be considered an OPC UA FX Server |
Optional |
||
|
Namespace for NodeIds and BrowseNames defined in the ConnectionManager-related part of this document. The namespace index is Server specific. A Server shall support either the AutomationComponent or the ConnectionManager to be considered an OPC UA FX Server |
Optional |
||
|
Namespace for NodeIds and BrowseNames defined in OPC UA Part 100. 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 document 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 235 provides a list of namespaces and their index used for BrowseNames in this document. The indices stated here are used as abbreviations throughout this document. Since namespace indices are dynamically assigned during the start of a Server, the namespace indexes, for example, for DI, may be different from 5 in a specific Server.
Table 235 – Namespaces used in this Document
|
NamespaceURI |
Namespace Index |
Example |
|
0 |
0:EngineeringUnits |
|
|
2 |
2:FxCommandMask |
|
|
3 |
3:AutomationComponentType |
|
|
4 |
4:ConnectionManagerType |
|
|
5 |
5:DeviceRevision |