Define how OPC UA type information is specified in WoT TDs

[barnstee]

A UANodeSet or Namespace of an OPC UA Information Model can optionally be referenced in the WoT TD to define the OPC UA types to be used for the mapping, including structures. This needs to be brought to the W3C WoT working group.

[barnstee]

Current proposal is something like this:
"@context": [
"https://www.w3.org/2022/wot/td/v1.1",
{
"opcua": [
"http://opcfoundation.org/UA/PNEM/"
]
}
],

"properties": {
"VoltageL1-N": {
"type": "number",
"mapping:opcua:nodeId": "s=VoltageL-N",
"mapping:opcua:type": "nsu=http://opcfoundation.org/UA/PNEM/;i=3005",
"mapping:opcua:fieldPath": "A",

[barnstee]

Agreement is to move this to the new OPC UA WoT-binding working group.

[barnstee]

Awaiting kickoff of the new WoT-binding WG within the OPC Foundation.

[barnstee]

WoT-Binding Working Group established and call for participation sent out via email yesterday. For registration please contact Dr Sebastian Käbisch ([[email protected]]).

The Kick-off Meeting is scheduled on July 30th, 2024 as a web conference.
Start Times (duration ca 90 minutes)
6:00 am PST (US West coast)
9:00 am EST (US East coast)
3:00 pm CEST (Germany)
10:00 pm JST (Japan)

[barnstee]

Proposed binding sample is here:

UA-EdgeTranslator/Samples/pac4200.tm.jsonld

Line 28 in c5d2169

"opcua:nodeId": "s=VoltageL-N",

[barnstee]

Also need a way to make this type information available via PubSub metadata messages.

[barnstee]

This is also tracked in Mantis issue: https://mantis.opcfoundation.org/view.php?id=8682