The following table gives an overview of the additional terms that can be used within a WoT Thing Description.

Vocabulary term

Description

Assignment

Type

uav:object

Semantic annotation for @type of the TD root level to express that this TD instance represent a UA Object from the top level.

optional

-

uav:objectType

Semantic annotation for @type at root level to express that this instance represent a UA ObjectType (in TD context, this is called Thing Model (TM))Note: This annotation is only applicable in a Thing Model definition.

optional

-

uav:variable

Semantic annotation for @type of a TD property to associate a UA Variable.

optional

-

uav:variableType

Semantic annotation for @type of a Thing Model property to associate a UA Variable Type.Note: This annotation is only applicable in a Thing Model definition.

optional

-

uav:method

Semantic annotation for @type of a TD action to associate a UA Method.

optional

-

uav:hasComponent

Term to express there is one or more has-child relationship. The value entry is a nodeId of the child node.

Note: uav:hasComponent is equivalent to <Reference ReferenceType="HasComponent" IsForward="true">

optional

Array of String

uav:componentOf

Term to express there is one or more is-child-of relationship. The value entry is a nodeId of the parent node.

Note: uav:componentOf is equivalent to <Reference ReferenceType="HasComponent" IsForward="false">

optional

Array of String

uav:browseName

Provides the origin browse name of the UA node. The uav:browseName can be used at the top level to provide the browse name of the UA Object or UA ObjectType, and within the property or action level to give the browse name of the UA variable or UA method respectively.

optional

String

uav:mapToNodeId

This term can be used within a property definition to express that the associated runtime datapoint can be mapped to a (external) target OPC UA node (e.g. UA variable) with the corresponding NodeId.This term can be not used at the forms level.

See Section 8.2 for example usage.

optional

string

uav:mapToType

This term can be used within a property definition to express that the associated runtime datapoint can be mapped to a (external) target OPC UA type with the corresponding NodeId.This term can be not used at the forms level.

See Section 8.2 for example usage.

optional

string

uav:mapByFieldPath

This term can be only used with the uav:mapToType term. In the case that the target type of uav:mapToType is complex (e.g. based on BaseType 0:Structure), a specific field name can be addressed within this complex type definition to which the runtime data can be mapped to.

See Section 8.2 for example usage.

optional

string