W3C

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

04 June 2025

Attendees

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

Meeting minutes

Ege: welcome

Agenda

<kaz> Agenda for today

Ege: we have a more discussion oriented session
… if there is time will look into the Github project status
… for tomorrow we are working on the TD toolchain repository
… we are going to have some updates on that

Minutes review

<kaz> May-21

Ege: anything that needs to be updated?

Ege: minutes approved

Binding registry Small Update

Ege: we now have a new repository called wot-bindings-registry
… I can't change the description of the repository

<EgeKorkan> https://w3c.github.io/wot-bindings-registry/

Kaz: you can create an Issue for that, and I can update the description

Ege: the initial document PR has been merged

<EgeKorkan> registry PR 6 - Initial Document

Ege: which means that now we have the first editor draft (see link above)
… we have two small issues to discuss
… is anybody open to volunteer for issue number 7 and 8 ?

<kaz> registry Issue 7 - Writing the Abstract and Informative Introduction

<kaz> registry Issue 8 - Copying over the Requirements.md content to index.html

Daniel: I can volunteer for 8

Ege: I'll take number 7

Daniel: I notice a minor issue in the license file, we speak about test suites, is it correct? I am not sure we'll do actual testing.

Kaz: we should check the license from the TTWG registry, etc.
… I'll check the other registry repos. Also check with PLH.

Kaz: as the starting point, we can remove the last two lines about CLA and BSD license for today.

Cris: you can add your statement in the commit message too.

Kaz: ok

Ege: I hope we don't have the same issue in other places
… I notice we have one in wot-binding-templates repository

TD PRs

data mapping analysis

<kaz> TD PR 2105 - Add HTTP to the data mapping analysis

Ege: What is your opinion about creating user stories?

<kaz> s/analysis|/analysis/

Luca: 90% of the who is always the same
… it was not annoying but redundant

Ege: any other point?

Luca: another point, thinking about URI variables this is a sort of data mapping. We can uniform URI variables with this data mapping work
… we can spin up the work
… and add the relevant user story

Cris: +1 to work on URI variables together with data mapping

Kaz: there is a typo in the title for "analysis"

Ege: the thing code base would not be necessary effected.

Luca: we can even deprecate
… URI Variables

<kaz> TD ED - 6.3.9.1 uriVariables

Ege: ok, +1

Cris: +1

Ege: merged

<kaz> TD Issue 2094 - Collecting Analysis on Data Mapping (Ege's comments based on the discussion today)

Manageable affordances

<kaz> TD PR 2107 - Improve analysis manageable affordances document and add an initial list of user stories.

Cristiano: as Luca said, "Who" part is difficult to describe or it is too obvious
… you are always the TD designer or the person who needs to onboard
… there is a list in the UC TF, we can list there or copy them over here

Cristiano: some feedback would be good on the "why" part as well

Ege: I would mention maybe "so that I can monitor or cancel an invoked action"

Kaz: a requirement should not need a "who" I think. The use case would have a user
… since the TD TF can work on their own for the requirements

Ege: maybe we will see a trend

Cristiano: we can say that in TD TF, the "Who" would have a default answer of "TD designer"
… these were good tests for the template from my point of view

Kaz: as discussed during the main call today, the end of the WoT WG Charter is approaching in 4 months, we should think about how to deal with spec generation schedule and necessary UCR discussion for that purpose.

Cristiano: I have also found other types of affordances (not just actions)

Cristiano: also the preemptible actions keyword were interesting
… in general I have added more linked issues
… then I have added user stories

<kaz> TD PR 2107 - Improve analysis manageable affordances document and add an initial list of user stories. Cristiano's updates on user stories

Cristiano: I am not sure about existing solutions section
… I will increase the section

Ege: Existing solutions section is about other solutions that can describe the user story
… they might be even commercial solutions
… you can put there anything that is not a theory
… and standards
… also previous WoT spec can be listed

<kaz> rendered MD from the PR 2107

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