– DRAFT –
WoT-WG - TD-TF - Slot 1

Previous minutes review

<kaz> * WoT Thing Description Slot 1: https://www.w3.org/2024/09/18-wot-td-minutes.html

<kaz> * WoT Thing Description Slot 2: https://www.w3.org/2024/09/19-wot-td-minutes.html

Ege: any changes?
… minutes are approved

Ege: minutes from the 19th, any changes?
… minutes from September 19th approved

TPAC summary

Ege: (present and review the TD slides from TPAC)

Ege: notable discussion was the relationship between bindings and profiles

review minutes from TPAC

Ege: any corrections or additions?
… approved

<EgeKorkan> https://docs.google.com/presentation/d/112oOOoIx7prStCR8Bv6wLqUV5fN_At9btWE9_x7Ame0/edit?usp=sharing

report out from other meetings

Ege: linkML toolchain meeting
… attendance was not good, it was early in the morning
… overall good feedback
… other SDO groups are also transitioning to linkML

Ege: registry breakout session report

<kaz> WoT main wiki - F2F section (to be updated with the breakout minutes URLs)

Ege: not large attendance but we connected with other people working on the registry topic
… our feedback is that the process is too open, which is by design
… any comments or questions?

Ege: JSON-LD session report out
… there is a pending update to JSON-LD to include RDF-Star
… CBOR-LD will have a context registry for compression
… YAML-LD is done, no surprises

Cristiano: is there a way to convert YAML comments to $comment in JSON?
… it may not be standardized

<luca_barbato> https://json5.org/

Luca: there is JSON5 which is for configuration

Cristiano: JSON5 may be a better approach

<Cris> https://code.visualstudio.com/docs/languages/json#_json-with-comments (says that is vscode specific)

Luca: YAML is a superset of JSON

<kaz> https://www.w3.org/2024/09/26-wot-minutes.html#t11

Ege: no news on canonicalization

Ege: @type issue of collision with JSON Schema type
… need to clarify what is happening
… normative references to JSON Schema may not be resolved after all

kaz: we should continue to watch the situation with the VC specification

kaz: the question from W3C viewpoint is if the resource is stable
… could talk with Philippe if we want to go this direction
… any other comments?

tooling

Ege: would like to have the meetings every 2 weeks, using the TD zoom link

initial connection

<EgeKorkan> wot-thing-description PR 2040 - Initial/Common Connection Container Proposal

Ege: PR #2040

Ege: there is a proposal and Luca has extended, Ben Francis has commented

Ege: some remaining questions like what is a subprotocol?
… propose to focus on the container architecture and discuss the terminology later

Luca: the problem is from where we want to start. How can we set defaults, and how can we describe protocols with less ambiguity

Ege: the reuse mechanism can be discussed separately

Luca: the proposal allows the consumer to decide on connection reuse, and it is protocol specific
… for example, some protocols like QUIC provide a built-in persistent connection and a client can decide whether to use it or not

Luca: we may need to provide hints

Cristiano: we discussed both protocol description and behavior
… in some cases, the protocol is stateful with reused resources
… sometimes there is an option to close after each transaction
… we need a way to explain this in the description
… if we dramatically change the way we describe protocols, we need to account for this in the container design
… so we probably should discuss the protocol description up front

Ege: tomorrow we could discuss adding security definitions in the container
… in cases like OpenAPI, there is a "component" for everything that is reusable. Should we do something like this?
… it is a common reference mechanism
… any quick remarks?
… adjourned