W3C

– DRAFT –
WoT Thing Description

30 October 2025

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan, Kunihiko_Toumura, Luca_Barbato, Mahda_Noura, Michael_Koster, Tomoaki_Mizushima
Regrets
-
Chair
Ege_Korkan, Michael_Koster
Scribe
Ege

Meeting minutes

Ege_Korkan, Kunihiko_Toumura, Mahda_Noura, Luca_Barbato

Minutes

https://www.w3.org/2025/10/23-wot-td-minutes.html

ek: any remarks?

lb: looks good

ek: approved
… I am making a PR for the wot repo with html minutes

Toolchain Updates

mn: they also have a runtime. linkml-runtime generates the linkml documentation. Eat your own dogfood
… now they are working on merging the both repositories
… i.e. linkml and linkml-runtime
… in the meantime, I started learning about their testing runtime
… I talked to a colleague in Siemens, Silvano, who works on this too

additionalProperties modelling

w3c/wot-thing-description-toolchain-tmp#28
… I was doing some post processing to add additionalProperties
… it depends on the linkml-runtime
… this is tracked in linkml/linkml#2940

Multilanguage Support
… this is tracked in linkml/linkml#2896

ek: do we have the same feature in the json-ld context

mn: yes it is in our context as well

<Zakim> dape, you wanted to https://w3c.github.io/wot-thing-description/#example-11

dp: we have titles and title and it looks different to the example in linkml
… who is behaving badly?

https://github.com/w3c/wot-thing-description/blob/main/context/td-context-1.1.jsonld#L1387

mn: the default language in TD terms is english

<dape> https://w3c.github.io/wot-thing-description/#table-vocabulary-terms-in-dataschema-level

dp: is our title going to be object based on this ?

ca: we decided to keep it a string for now
… this way we support json only parsers

<Zakim> dape, you wanted to https://w3c.github.io/wot-thing-description/#example-9

ek: should we add anything to our multilanguage examples? Like in the linkml example?

mn: no since our json-ld context already explains it

PR 2900 in LinkML

mn: this got merged so I get to remove a post processing script
… this is a nice progress I am seeing

our repo

mn: I need to fix the ontology generators
… also I managed to back into the repo
… I did some cleanups
… also the document generation
… I have copied over the index.template.html
… we have the placeholder indicated by %s
… I create jinja template and now focusing on the Thing class
… (shows the local index.html)
… the table section now gets auto generated

https://github.com/w3c/wot-thing-description/blob/main/validation/td-validation.ttl

mn: we need to handle the atrisk stuff too

ek: also we need unique ids for assertions

mn: and I need to go into the shacl shapes too

ek: yes I hate that we need to edit that file at the same time

mn: also the ontology and spec have different values for descriptions

ca: not sure why we have a discrepency but indeed we should not have this

ek: also good to see that the linkml community is active

mn: yes indeed. however, I would need to provide a fix the rdf generator as it doesn't seem to be a high prio for them

mn: we can keep a fork and use that for the spec as well. What do you think?

ek: we should contribute upstream

Charter

Minutes manually created (not a transcript), formatted by scribe.perl version 248 (Mon Oct 27 20:04:16 2025 UTC).

Diagnostics

Maybe present: ca, dp, ek, lb, mn

All speakers: ca, dp, ek, lb, mn

Active on IRC: dape, Ege, luca_barbato, mahda, mjk