The BrowseName is used as interaction name of a property or action.

It is important to ensure that the interaction names within the properties and actions are unique within the TD.

If the uniqueness is not guaranteed by a given BrowseName (same value is used at a different place in a UA tree), different strategies can be realized. In the following, two strategies are presented; others are also possible as long as uniqueness is guaranteed.

Lets assume, we have following UA tree and both nodes 1:Pressure should be transformed into a WoT TD:

2:Root
|_1:Data1
|_1:Pressure
|_1:Date2
|_1:Pressure

E.g., the interaction name can be augmented with additional characters such as with a separator character (e.g., "_", "-") and an ascending number or alphabet character.

Example: "1:Pressure_1" for "1:Pressure" in "1:Data1". ""1:Pressure_2" for "1:Pressure" in "1:Data2".

Alternatively, the browse path to the UA node can be sketched (e.g., without namespace prefixes) as unique interaction name:

Example: "Root_Data2_Pressure"

In the case the original BrowseName is not used, it is recommended to add the term "uav:browseName" within the interaction affordance to provide the origin browse name.

…

<UAVariable NodeId="ns=1;i=428" BrowseName="1:Pressure" ParentNodeId="ns=1;i=20" DataType="Double">
…

…

"properties": {

"1:Pressure_1":

{

…

Alternative:

…

"properties": {

"Root_Data1_Pressure": {
"uav:browseName":"1:Pressure"

…