Meeting Minutes
===

:::spoiler Document Usage
This document is used for all minutes of the WoT CG.
After the meeting, the contents will be copied to the GitHub with a PR.

===

###### tags: `Meetup`

:::spoiler Document Usage
This document is used for all minutes of the WoT CG.
After the meeting, the contents will be copied to GitHub with a PR.
For one week, changes can be requested and then the PR will be merged.
After the PR is merged, the content here can be deleted.

Document Access:
- Everyone has read and commenting access
- Cristiano Aguzzi and Ege Korkan can edit the document
- Other people can request write access for a meeting
- The scribe of the meeting will have write access

<!-- Do not change this spoiler container when writing an instance document -->
<!-- See https://github.com/ikatyang/emoji-cheat-sheet for list of emojis -->
:::

:::info

:date: **Date:** 16 October 2025

### :bust_in_silhouette: Participants

<!-- This list will copied over from the meeting tool -->
- Ege Korkan
- Cristiano Aguzzi
-

### :scroll: Agenda

:writing_hand: **Scribe:** Ege

----

### Introduction

Ege: Welcome Everyone! we are at Meetup 29th! All slide are public
Ege: you can find us in different places on the web

### News

Ege:

### Meetup Presentation

Sebastian: OneConnectivity internally and node-wot under Eclipse Foundation implement the OPC UA binding.

Kerem Coban: What is the relationship between AAS and WoT?

Sebastian: There is a specific AAS Submodel called asset

EK: Do you see the willingness from manufacturers to provide their protocols' binding specs?

EB: That would be ideal indeed.

EB: Prosys supports WoT connectivity in their Forge product.

JH: Can I use the AAS Templates AID or AIMC for directly sending opc-ua to mqtt, kafka, etc. ?

EB: Yes you can. The client I have shown can send to mqtt or kafka too

EK: Any features you want to see in the standards?

EB: We will add new affordance types like actions and events. More adoption is needed. More should ask for WoT TD files. I am working on getting people to adopt wot connectivity.

EB: More bindings are needed too. But it is easy to write them yourself.

EB: I needed help with lorawan though. That was a bit tricky with some fields like doing bitmasking and endianness. Also the Matter spec is huge.

Abidoun: Physics student here. As frontend developers are building tools around WoT Thing Descriptions, what are the current limitations or gaps in the TD specification that we should be aware of when designing UIs or developer tools?

SK: You can build UIs based on the different affordances. Like widgets-based. For more advanced UIs, you need to leverage more semantics. Like to build a timeseries graph, you need more information.

Matthias Meier: W3C is working on a profinet binding. Does your LLM also support profinet too?

EB: LLMs we use are generic. If you do prompt engineering, like saying make sure to include this binding. You need to experiment though. OpenAI provides the tools. You need to be specific though.

EB: It would be more interesting to use RAGs together with LLMs. That would be more interesting.

EB: UA Edge Translator can be improved upon. Feel free to add more protocols. You can use a simple interface to add more protocol driver implementations.

## :ballot_box_with_check: Resolutions

## :exclamation: Action Items

## :envelope_with_arrow: Feedbacks

## Presentation Summary

-