W3C

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

28 August 2025

Attendees

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

Meeting minutes

Agenda

Ege: refactoring and document freeze

Minutes

<EgeKorkan> Aug-21

Ege: (goes through the minutes)

(approved)

Thing Description

PR 2127

TD PR 2127 - Moving Sebastian and McCool to formerEditors

Ege: easy edit to move Sebastian and McCool to the Former Editors
… any comments?
… who to be listed as Editors additionally?

(none)

(merged)

PR 2128

TD PR 2128 - Temporary Context URL

Ege: need to update the @context URL for the examples
… (shows example 1)

Example 1 withing the preview

Cristiano: we're replacing the URL

Kaz: thought we already had discussion about the URL naming policy
… so we should be careful to put our agreed style carefully

Ege: right
… we decide not to use the year number any more
… but still would like to use the version number itself

Kaz: like we did for WoT TD 1.0 Resources, we should clarify the namespace URL scheme, redirection setting, etc., and then can update the example

<EgeKorkan> https://github.com/w3c/wot-resources/tree/main

Kaz: so we should do that again for TD 2.0 on wot-resources

<cris> +1 for td-next

Kaz: for a tentative use, I'm OK with any name like "ns/td" or "ns/td-next"
… but what is more important is we surely update that "tentative" namespace URL later when the actual TD 2.0 namespace is fixed
… so would suggest we put some explicit label to this point
… and/or put an Editor's Note within the spec draft

Ege: ok

Registry

PR 28

Registry PR 28 - Pilot Phase Information

Ege: (describes the changes)

changes

<EgeKorkan> w3c/process#1085

Kaz: this is a common problem around the Registry Track in general. right?

Ege: right
… so I've created an Issur for the Process document

Ege: you can ask PLH for opinions based on the above Process Issue

Kaz: ok

(merged)

PR 27

Registry PR 27 - Adapt documenting to remove s from bindings

Ege: converted "Bindings Registry" to "Binding Registry" based on the discussion yesterday
… after merging this PR, we should change the repository name also

Kaz: will do
… done

Ege: tx!

PR 30

Registry PR 30 - Second intro section refactoring

Daniel: we can look into the CSS to fix the setting

Ege: can anybody do that???

Daniel: it's a problem with not only this document but also any kind of documents

Ege: right

Jan: work around could be changing the CSS setting...
… but maybe a bug with ReSpec?

Ege: the question here is the CSS setting for "rfc2119-assertion"...

Daniel: there is a workaround by Mozilla

light-dark setting

Kaz: so what should be the next step?
… should talk with the ReSpec Team?

Ege: Daniel will create an Issue on the wot-binding-registry repo first
… and then if needed, we can ask the ReSpec Team for help

Kaz: ok

Jan: maybe we could open an Issue on the ReSpec repo as well...

Registry Issue 31 - Assertion Highighting for dark and light mode

Kaz: ok
… so Daniel has created an issue (31) on wot-binding-registry
… and Jan can create another issue on the ReSpec repo referring to Daniel's issue above

Jan: ok

Ege: (goes through the other points within PR 30)
… (e.g., the "Ownership" section)

Kaz: note that it would be nicer to use GitHub Issue mechanism rather than email communication via the public list and/or to the Chairs

Ege: right
… (tries to merge the PR)
… (but some conflicts there...)
… (fixed, and merged)

Thing Description - revisited

PR 2123

TD PR 2123 - Removing HTTP Binding and Adjusting Defaulting Mechanism for all Bindings

Ege: (goes through the changes)

changes

Ege: the actual changes are within index.template.html

diff around index.template.html

Ege: (shows section 5.4)

5.4 Default Value Definitions

Cristiano: changes look good
… but what about the prefix?

TD Issue 2052 - Default Mechanisms for Bindings Vocabularies

Ege: (explains the mechanism using the Thing Description Playground as well)
… need to add a name space URL for HTTP in RDF, etc., for extensions
… all the examples which use "htv:" prefix should have the @context setting correctly
… will apply the changes as well

Kaz: if any more questions, let's create an additional Issue about that
… and discuss it next week

Ege: ok
… will do

TF Resolution for publication

Kaz: it's already 10 mins past the hour
… also some of the key attendees have left
… so if we really need to make a resolution, let's do that via email

Ege: ok
… will do

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 244 (Thu Feb 27 01:23:09 2025 UTC).