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 3provides a list of mandatory and optional namespaces used in an OPC 40564-1 OPC UAServer.

Table 3– Namespaces used in an OPC 40564-1 Server

NamespaceURI

Description

Use

http://opcfoundation.org/UA/

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 namespace shall have namespace index 1.

Mandatory

http://opcfoundation.org/UA/DI/

Namespace for NodeIdsand BrowseNamesdefined in OPC 10000-100. The namespace index is Serverspecific.

Mandatory

http://opcfoundation.org/UAMachinery/

Namespace for NodeIdsand BrowseNamesdefined in OPC 40001-1. The namespace index is Serverspecific.

Mandatory

http://opcfoundation.org/UA/Mining/General/

Namespace for NodeIdsand BrowseNamesdefined in OPC 40560. The namespace index is Serverspecific.

Mandatory

http://opcfoundation.org/UA/Mining/MineralProcessing/General/

Namespace for NodeIdsand BrowseNamesdefined in this document. The namespace index is Serverspecific.

Mandatory

Vendor specific types

A Servermay provide vendor-specific types like types derived from ObjectTypes defined in this document in a vendor-specific namespace.

Optional

Vendor specific instances

A Serverprovides 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 4provides a list of namespaces and their indices used for BrowseNamesin this document. The default namespace of this document is not listed since all BrowseNameswithout prefix use this default namespace.

Table 4– Namespaces used in this document

NamespaceURI

Namespace Index

Example

http://opcfoundation.org/UA/

0

0:EngineeringUnits

http://opcfoundation.org/UA/DI/

2

2:DeviceRevision

http://opcfoundation.org/UA/Machinery/

3

3:MachineComponentsType

http://opcfoundation.org/UA/Mining/General/

4

4:MiningEquipmentType

(normative)OPC 40563-1 Namespace and mappings

This appendix defines the numeric identifiers for all of the numeric NodeIdsdefined in this document. The identifiers are specified in a CSV file with the following syntax:

<SymbolName>, <Identifier>, <NodeClass>

Where the SymbolNameis either the BrowseNameof a Type Nodeor the BrowsePathfor an Instance Nodethat appears in the specification and the Identifieris the numeric value for the NodeId.

The BrowsePathfor an Instance Nodeis constructed by appending the BrowseNameof the instance Nodeto the BrowseNamefor the containing instance or type. An underscore character is used to separate each BrowseNamein the path. Let’s take for example, the MiningEquipmentType ObjectType Nodewhich has the add-in Identification object. The Namefor the Identification InstanceDeclarationwithin the MiningEquipmentTypedeclaration is: MiningEquipmentType_Identification.

The NamespaceUrifor all NodeIdsdefined 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:

___________