Erich Barnstedt

Implement ua-metadata messages as defined in 7.2.3.4.2 of the OPC UA spec (see https://reference.opcfoundation.org/v104/Core/docs/Part14/7.2.3/). These should be sent before sending the corresponding ua-data (telemetry) message and sent in regular intervals...

This only entails setting the content type to application/json to allow IoT Hub to interpret the message correctly.

Upgrade to .Net6.0

1

In this change are the following enhancements: 1. Upgrade to .Net6.0. 2. Upgrade NuGets. 3. Removed config files no longer required.

Add Variable node to return the list of WoT protocol bindings a UA server supports

1

This can be implemented as a simple data node returning an enumeration of the supported WoT protocol bindings: Released: https://www.w3.org/TR/wot-binding-templates/#table-existing-protocol-binding-templates All bindings: https://w3c.github.io/wot-binding-templates/#protocol-bindings-table

Define how OPC UA type information is specified in WoT TDs

7

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,...

This is defined in part 20: https://reference.opcfoundation.org/Core/Part20/v105/docs/4

Feature Request: Try to connect to thing/asset once TD is validated

1

For local connections, it would be great to try out the TD on the real thing/asset.

This will keep our DB clean from the recent spambots.