Table 77 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 77 – NamespaceMetadata Object for this Specification
|
Attribute |
Value |
|||
|
BrowseName |
||||
|
References |
BrowseName |
DataType |
Value |
|
|
HasProperty |
NamespaceUri |
String |
||
|
HasProperty |
NamespaceVersion |
String |
1.0 |
|
|
HasProperty |
NamespacePublicationDate |
DateTime |
2017-10-11 |
|
|
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 TMC 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 table specify the facets available for Servers that implement the TMC Information Model companion standard.
Table 78 – TMC Server Facet Definition
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
TMC Essential |
Essential server features. See chapter 6.15.2 for more information. |
M |
|
TMC Advanced |
Advanced server features. See chapter 6.15.2 for more information. |
O |
|
Profile |
||
|
Standard UA Server Profile |
M |
|
|
Base Server Behaviour Facet |
M |
|
|
Request State Change Server Facet |
M |
|
|
File Access Server Facet |
M |
|
|
Documentation Server Facet |
O |
|
|
Durable Subscription Server Facet |
O |
|
|
Data Access Server Facet |
M |
|
|
ComplexType Server Facet |
M |
|
|
Standard Event Subscription Server Facet |
M |
|
|
Address Space Notifier Server Facet |
M |
|
|
Method Server Facet |
M |
|
|
Standard Event Subscription Server Facet |
M |
|
|
Historical Raw Data Server Facet |
M |
|
|
HIstorical Data AtTime Server Facet |
M |
|
|
Historical Access Structured Data Server Facet |
O |
|
|
Base Historical Event Server Facet |
M |
|
|
Security Policy [B] - Basic256SHA256 |
M |
|
|
Security User Access Control Full |
M |
|
|
Security Time Synch - NTP/OS based support |
M |
|
|
Best Practice - Time Outs |
M |
|
The following table specify the facets available for Clients that implement the TMC Information Model companion standard.
Table 79 – TMC Client Facet Definition
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
TMC Essential |
Essential client features. See chapter 6.15.2 for more information. |
M |
|
TMC Advanced |
Advanced client features. See chapter 6.15.2 for more information. |
O |
|
Profile |
||
|
Standard UA Client Profile |
M |
|
|
Base Client Behaviour Facet |
M |
|
|
Request State Change Client Facet |
M |
|
|
File Access Client Facet |
M |
|
|
Documentation Client Facet |
O |
|
|
Durable Subscription Client Facet |
O |
|
|
Data Access Client Facet |
M |
|
|
Notifier and Source Hierarchy Client Facet |
M |
|
|
Method Client Facet |
M |
|
|
Base Event Processing Client Facet |
M |
|
|
Historical Access Client Facet |
M |
|
|
HIstorical Data AtTime Client Facet |
M |
|
|
Historical Structured Data Access Client Facet |
O |
|
|
Base Historical Events Client Facet |
M |
|
|
Security Policy [B] - –asic256SHA256 |
M |
|
|
Security User Access Control Full |
M |
|
|
Security Time Synch - –TP/OS based support |
M |
|
|
Best Practice - –ime Outs |
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 80 provides a list of mandatory and optional namespaces used in a TMC OPC UA Server.
Table 80 – Namespaces used in a TMC OPC UA Server
|
http://opcfoundation.org/UA/ |
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 a device represented by the server. This namespace shall have namespace index 1. |
Mandatory |
|
http://opcfoundation.org/UA/DI/ |
Namespace for NodeIds and BrowseNames defined in OPC 10000-100. The namespace index is server specific. |
Mandatory |
|
http://www.euromap.org/euromap77/ |
Namespace for NodeIds and BrowseNames defined in OPC UA Euromap77 Companion Specification RC1.00. The namespace index is server specific. |
Mandatory |
|
http://opcfoundation.org/UA/TMC/ |
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 MachineModuleType or vendor specific instances of devices in a vendor specific namespace. |
Optional |
Table 81 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 81 – Namespaces used in this specification
|
Namespace |
Namespace Index |
Example |
|
http://opcfoundation.org/UA/ |
0 |
0:EngineeringUnits |
|
http://opcfoundation.org/UA/DI/ |
1 |
1:DeviceRevision |
|
http://www.euromap.org/euromap77/ |
2 |
2:ControllerType |