Table 11 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 11 - NamespaceMetadata Object for this Specification

Attribute
BrowseName	http://opcfoundation.org/UA/Sercos/
References	BrowseName	DataType	Value
HasProperty	NamespaceUri	String	http://opcfoundation.org/UA/Sercos/
HasProperty	NamespaceVersion	String	1.20
HasProperty	NamespacePublicationDate	DateTime	2017-04-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 Sercos. 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.

Table 12 defines a facet that indicates full support defined by this specification.

Table 12 – Full Sercos Server Facet Defintion

Conformance Unit	Description	Optional/ Mandatory
Sercos DeviceType	Supports the base Sercos device type, the device specific type and the mandatory components of the types.	M
Sercos Device Parameters	Supports the optional components for the Sercos device type like device location or the configuration parameters.	O
Profile
Embedded_DataChange_Subscription_Server_Facet (defined in OPC 10000-7)		M
BaseDevice_Server_Facet (defined in OPC UA DI)		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 13 provides a list of mandatory and optional namespaces used in an Sercos OPC UA Server.

Table 13– Namespaces used in a Sercos Server

Namespace	Description	Use
http://opcfoundation.org/UA/	Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0.	Mandatory
http://sercos.org/UA/	Namespace for NodeIds and BrowseNames defined in Sercos. The namespace index is server specific.	Mandatory
Vendor specific types and instances	A server may provide vendor specific types or vendor specific instances of devices in a vendor specific namespace.	Mandatory