Meeting Minutes

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   ::: :::info :date: **Date:** 16 October 2025 ### :bust_in_silhouette: Participants  - Ege Korkan - Cristiano Aguzzi - :writing_hand: **Scribe:** Ege ---- ### Welcome Cris: Welcome Everyone! we are at Meetup 30! All slide are public Cris: you can find us in different places on the web ### News Cris: ### Meetup Presentation EK: project was started by Pedram and now I'm taking over. As first thing I want start from why we are building a device catalog. EK: Adding a new device into as existing system (onboarding), involves different steps which are always quite delicate. EK: different users in popular blogs ask how to configure and interact with new devices. All of them ask for the same thing, easy process to connect. EK: Maybe inside simens is better? We have proofs that the problem is still there. Integration work is still something that is impacting the final user experience. EK: at least in home assistant you have a nice UI, but still you have to grasp all the details. Some goes with other popular tools (HiveMQ and Node-Red) EK: In the end people just one to interact with the devices (building dashboard, record live data, etc.) EK: it happens in many protocols, and impact the final cost of the digital product. EK: but why don't we manually integrate those devices? It is not easy as the device portofolio and singular features are diverse. In the end, it doesn't scale. EK: in the home autumation space there are plenty of platform that use propetary device modelling. EK: WoT can help here. Instead of using manual work you can use TD and TM. EK: today we will focus on the catalog and how to manage a collection of thing models. EK: We have two kind of Thing Models: generic (model a switch) or device specif (model a particular device). ### Thing Model catalog EK: it is first a catalog but also the tooling around this service. All the services are inside wot-oss. EK: thing models are categoriezed by authorships. It should be easy to find a TM in front of you. We should support also offline deployment. It should be easy to work inside the CI/CD Git env. There is also support for federarted deployement. Another important goal is to not centralizing TMs in one place. *shows a basic repository structure* EK: In the end we provide you a cli tool. We that you can manage the whole lifecycle of TM. EK: we provide a nice documentation for simple usage and use cases. EK: we have a web ui work in progress too. EK: to work with the catalog you must add some metadata that is mandatory: author and manufactore. EK: I prepared two demo. *Show CLI RESTAPI and federed demo* EK: with serve you host the tmc as rest api. You can use your preferred openAPI client to interact with the API. EK: you can manage two or more repositories even in different locations. *stop demo* EK: but how to contribute to thing model catalog? you can use ediTDor. There is also some nice validation and verification. *Second demo authoring workflow* EK: you can test a modbus device using a gateway in the ediTDor. *stop demo* EK: In previous meetup we showed how in siemes you can onboard devices. In there we were using the TMC. EK: Since now we have a place to publish and show thing models. We will host a small extra event as CG. Your challenge is to create a set of TM for your favorite devices and we will collect them in a big TMC. *ege shows steps* EK: we are going to announce next week as well. EK: I will design a TM for a new Tado X Thermostat with Matter. EK: that was all. ## Q&A Cris: can you publish generic TMs? Ege: no, only TMs connected to a particular device Cris: It would be cool to have some of those hosted. Daniel: If I publish TM for devices what are the legal implications? Ege: the tooling it self does not take responsability. It happens with some devices that would not allow publication of internal devices. All siemens TMs that are out there uses the apache library. Ege: with DPP we might see more open APIs as the devices manifacturers are forced to publish them by law. Thomas: I think if this might happen also for could APIs (that proxy devices). I worked for a company that uses LORAWan that maybe might be intresting. Ege: yeah but maybe in this case I would see more TDs rather than TMs or discovery tools for TDs. ## :ballot_box_with_check: Resolutions ## :exclamation: Action Items ## :envelope_with_arrow: Feedbacks ## Presentation Summary -