Table 2 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 2 – NamespaceMetadata Object for this Document
|
Attribute |
Value |
||
|
BrowseName |
http://opcfoundation.org/UA/Mining/DevelopmentSupport/General/ |
||
|
Property |
DataType |
Value |
|
|
NamespaceUri |
String |
http://opcfoundation.org/UA/Mining/DevelopmentSupport/General/ |
|
|
NamespaceVersion |
String |
1.0.0 |
|
|
NamespacePublicationDate |
DateTime |
2022-09-01 |
|
|
IsNamespaceSubset |
Boolean |
False |
|
|
StaticNodeIdTypes |
IdType [] |
System.Int32[] |
|
|
StaticNumericNodeIdRange |
NumericRange [] |
|
|
|
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.
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 3 provides a list of mandatory and optional namespaces used in an OPC 40565-1 OPC UA Server.
Table 3 – Namespaces used in an OPC 40565-1 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 namespace shall have namespace index 1. |
Mandatory |
|
Namespace for NodeIds and BrowseNames defined in OPC 10000-100. The namespace index is Server specific. |
Mandatory |
|
|
Namespace for NodeIds and BrowseNames defined in OPC 40001-1. The namespace index is Server specific. |
Mandatory |
|
|
Namespace for NodeIds and BrowseNames defined in OPC 40560. The namespace index is Server specific. |
Mandatory |
|
|
http://opcfoundation.org/UA/Mining/DevelopmentSupport/General/ |
Namespace for NodeIds and BrowseNames defined in this document. 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 4 provides a list of namespaces and their indices 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 4 – Namespaces used in this document
|
NamespaceURI |
Namespace Index |
Example |
|
0 |
0:EngineeringUnits |
|
|
2 |
2:DeviceRevision |
|
|
3 |
3:MachineComponentsType |
|
|
4 |
4:MiningEquipmentType |
(normative)OPC 40565-1 Namespace and mappings
Namespace and identifiers for OPC 40565-1 Information Model
This appendix defines the numeric identifiers for all of the numeric NodeIds defined in this document. The identifiers are specified in a CSV file with the following syntax:
<SymbolName>, <Identifier>, <NodeClass>
Where the SymbolName is either the BrowseName of a Type Node or the BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId.
The BrowsePath for an Instance Node is constructed by appending the BrowseName of the instance Node to the BrowseName for the containing instance or type. An underscore character is used to separate each BrowseName in the path. Let’s take for example, the MiningEquipmentType ObjectType Node which has the add-in Identification object. The Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification.
The NamespaceUri for all NodeIds defined here is:
The CSV released with this version of the specification can be found here:
NOTE The latest CSV that is compatible with this version of the specification can be found here:
A computer processible version of the complete Information Model defined in this document is also provided. It follows the XML Information Model schema syntax defined in OPC 10000-6.
The Information Model Schema for this version of the specification (including any revisions, amendments or errata) can be found here:
NOTE The latest Information Model schema that is compatible with this version of the document can be found here:
___________