Table 81 defines the namespace metadata for this specification. 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 81 – 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-18 |
|
|
HasProperty |
IsNamespaceSubset |
Boolean |
False |
|
|
HasProperty |
StaticNodeIdTypes |
IdType[] |
{Numeric} |
|
|
HasProperty |
StaticNumericNodeIdRange |
NumericRange[] |
Null |
|
|
HasProperty |
StaticStringNodeIdPattern |
String |
Null |
|
This chapter defines the corresponding profiles and conformance units for the OPC UA Information Model for AutoID. Profiles are named groupings of conformance units. Facets are profiles that will be combined with other Profiles to define the complete functionality of an OPC UA Server or Client. The following tables specify the facets available for Servers that implement the AutoID Information Model companion specification.
Table 82 defines a facet for the base functionality necessary for a synchronous scan operation with AutoID Devices by pure Data Access functionality, where the OPC UA Client optional can trigger the scan operation.
Table 82 – Simple Sync AutoID Server Facet Definition
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
AutoID DeviceType |
Supports the base AutoID device type, the device specific type and the mandatory components of the types. |
M |
|
AutoID Simple Sync Access |
Supports the LastScanData Variable for synchronous access to the scan data. |
M |
|
AutoID Simple Sync Access Control |
Supports the ScanActive Variable for starting/stopping the scan. |
O |
|
AutoID Device Parameters |
Supports the optional components for the AutoID device type like device location or the configuration parameters. |
O |
|
Profile |
||
|
ComplexType Server Facet (defined in OPC 10000-7) |
M |
|
|
BaseDevice_Server_Facet (defined in OPC 10000-100) |
M |
|
Table 83 defines a facet for the base functionality necessary for a synchronous scan operation with AutoID Devices where the OPC UA Client triggers the scan operation.
Table 83 – Base Sync AutoID Server Facet Definition
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
AutoID DeviceType |
Supports the base AutoID device type, the device specific type and the mandatory components of the types. |
M |
|
AutoID Sync Access |
Supports the LastScanData Variable and the Scan Method for synchronous access to the scan data. |
M |
|
AutoID Device Parameters |
Supports the optional components for the AutoID device type like device location or the configuration parameters. |
O |
|
Profile |
||
|
ComplexType Server Facet (defined in OPC 10000-7) |
M |
|
|
BaseDevice_Server_Facet (defined in OPC 10000-100) |
M |
|
Table 84 defines a facet for the base functionality necessary for an asynchronous scan operation with AutoID Devices where the device triggers the scan operation.
Table 84 – Base Async AutoID Server Facet Definition
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
AutoID DeviceType |
Supports the base AutoID device type, the device specific type and the mandatory components of the types. |
M |
|
AutoID Async Access |
Supports the AutoIdScanEventType to inform clients about new scan result. |
M |
|
AutoID Async Access Control |
Supports the ScanStart and ScanStop Method for asynchronous access to the scan data. |
O |
|
AutoID Device Parameters |
Supports the optional components for the AutoID device type like device location or the configuration parameters. |
O |
|
Profile |
||
|
ComplexType Server Facet (defined in OPC 10000-7) |
M |
|
|
Standard Event Subscription Server Facet (defined in OPC 10000-7) |
M |
|
|
BaseDevice_Server_Facet (defined in OPC 10000-100) |
M |
|
Table 85 defines a facet that indicates full support for the different scan operation modes defined by this specification.
Table 85 – Full AutoID Server Facet Definition
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
AutoID Device Parameters |
Supports the optional components for the AutoID device type like device location or the configuration parameters. |
M |
|
AutoID Async Access Control |
Supports the ScanStart and ScanStop Method for asynchronous access to the scan data. |
M |
|
Profile |
||
|
ComplexType Server Facet (defined in OPC 10000-7) |
M |
|
|
Standard Event Subscription Server Facet (defined in OPC 10000-7) |
M |
|
|
BaseDevice_Server_Facet (defined in OPC 10000-100) |
M |
|
|
Simple Sync AutoID Server Facet defined in Table 82. |
M |
|
|
Base Sync AutoID Server Facet defined in Table 83. |
M |
|
|
Base Async AutoID Server Facet defined in Table 84. |
M |
|
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 Address Space 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 86 provides a list of mandatory and optional namespaces used in an AutoID OPC UA Server.
Table 86 – Namespaces used in an AutoID 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 OPC 10000-100. The namespace index is server specific. |
Mandatory |
|
|
Namespace for NodeIds and BrowseNames defined 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 RfidReaderDeviceType or OpticalReaderDeviceType or vendor specific instances of devices in a vendor specific namespace. |
Optional |
Table 87 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 87 – Namespaces used in this specification
|
NamespaceURI |
Namespace Index |
Example |
|
0 |
0:EngineeringUnits |
|
|
1 |
1:DeviceRevision |