W3C

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

12 March 2025

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan, Jan_Romann, Kaz_Ashimura, Kunihiko_Toumura, Michael_Koster, Tomoaki_Mizushima
Regrets
-
Chair
Ege, Koster
Scribe
dape

Meeting minutes

Minutes Review

<kaz> Mar-5

Ege: Any remarks?
… none -> minutes are approved

Next week

Ege: Kaz is not available both days Wed/Thu
… changes to agenda
… Wed: Connexus special call
… not a normal taskforce call.. but still relevant for all of us

Kaz: I am sorry I cannot make it
… we can call that "Informal Discussion about Connexxus liaison"

Ege: On Thursday: Informal meeting. Informal means working/refining issues but not merging PRs
… the week after, we cancel call on March 27th

PRs

PR 2086

<EgeKorkan> TD PR 2086 - PR Template: Remove Checkboxes

Ege: Template is now working
… simple fix to show up properly
… editorial vs. normative

<cris> +1

Ege: No concerns, merging

PR 2080

<EgeKorkan> TD PR 2080 - fix: align JSON Schema with JSON-LD @context format

Ege: about not validating TDs with JSON schema
… URI enforcement etc
… tool I shared is not working as expected
… I don't understand the problem
… real problem is minor errata
… prefixItems term is only introduced in newer version of JSON schema
… term "items" should be used instead
… Hence we have a small errata
… changing "prefixItems" with "items" solved this issue
… "contains" no longer needed
… we should add tests in playground

Jan: Do I need to update the PR?

Ege: I did already

Ege: Question allowing old context URL ... comment there

Cristiano: I am not 100% sure why it is there
… I think it is there for backwards compatibility
… I think Ben was also advocating for it

Ege: I hope people are fine with the changes
… I have done tests on playground
… I didn't encounter any issues

<kaz> related playground PR 626 - Update schema to test context urls

Ege: putting it to wot-resources requires resolution

Jan: Minor point. We need to update thing model schema as well

Ege: Right

Cristiano: I am okay moving it to wot-resources
… it is just a corner case

<JKRhb> +1

Cristiano: Some previous TDs can fail now, right?

Ege: Yes, TD could have a number for context and would fail now.

<EgeKorkan> proposal: The changes to the TD and TM JSON Schemas in w3c/wot-thing-description#2080 can be mirrored to wot-resources

Ege: Errata needs to be updated

<cris> +1

Ege: I will send email to ask for a resolution

RESOLUTION: The changes to the TD and TM JSON Schemas in w3c/wot-thing-description#2080 can be mirrored to wot-resources

Ege: closing PR 2088

PR 2081

TD PR 2081 - Make contentType optional in ExpectedResponse and AdditionalExpectedResponse classes

Ege: I think there hasn't been any update
… Ben responded with "not liking global default being removed"
… not an issue with initial connections

Cristiano: contentType is not strictly needed for TD2.0
… 1 step of a more complex solution that is going to come

Binding Registry

PR 420

<kaz> Binding PR 420 - Binding Dependencies

Ege: Replaced *weird* paragraph
… summary document must contain dependencies
… binding shall not be redefined
… dependency must be submitted as a separate entity
… we roughly agreed on last week
… issue 401

<kaz> related Binding Issue 401 - Handling Bindings that depend on other bindings

Jan: Changes look good
… should it be possible to specify version ranges?
… patch releases?
… or is that going to be too complicated

Ege: Yes, seems complicated

Jan: Okay, let's defer this discussion

Ege: I think we can merge PR 420

Issue 400

Binding Issue 400 - Versioning of Registry Entries

Ege: For now, we say version is a string
… we cannot say "semantic versioning"
… we can discuss versioning mechanism
… or submitter uses its own versioning mechanism
… most users unique version should be enough
… so far we do not do any versioning in bindings

Kaz: Maybe we need a mechanism in the end
… but maybe the registry mechanism could handle necessary versioning automatically
… so probably we should think about what kind of semantic versioning is needed for registry entries a bit more based on concrete usage.

Ege: You are saying we should understand first how people use the registry?

Kaz: Yes

Cristiano: For us, it is important to have a defined order between the versions
… like concept of "latest" version
… I think we should enforce that
… otherwise any versioning scheme might work

Ege: I don't see strong opinions
… no concrete proposal yet
… based on CAs proposal, the date seems to be important

[adjourned]

Summary of resolutions

  1. The changes to the TD and TM JSON Schemas in w3c/wot-thing-description#2080 can be mirrored to wot-resources
Minutes manually created (not a transcript), formatted by scribe.perl version 244 (Thu Feb 27 01:23:09 2025 UTC).