W3C

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

26 June 2025

Attendees

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

Meeting minutes

Agenda

Cristiano: Please add manageable action topic on the agenda please

Koster: sure

Minutes

--> 18 June 2025

Koster: Any corrections?
… none -> minutes approved

Summer Schedule

Koster: Any other vacations?
… none

Koster: Deliverable for first WD is important
… what do we do about things that are work in progress
… we decided to publish WD within this charter period

<kaz> TD Issue 2112 - TD 2.0 FPWD Goals

Koster: how much of features in progress do we document

Koster: Binding part of TD might be far along

Koster: I think we need to prioritize this work

Cristiano: A short update about binding registry should be coming
… not the whole mechanism
… just put some text to explain the plan

Koster: Right

Koster: Did we decide on a date?
… mid August / mid September ?

Ege: 2 points
… mechanism included in TD ... editorial work ... needs to be fixes
… this is high priority..
… we also need to mention registry
… w.r.t. dates.. i would say we have deadline a week before charter ends
… latest date possible

Kaz: we made basic resolution
… fpwd ... end of October
… what kind of content to be included
… okay with date
… need to think about content
… there is a possibility we could publish FPWD with content "as is"

Ege: Date is fine
… current ED is not ready to be published... I think

Koster: Fixing description only?

Ege: This is not the only thing...
… we should have hints about new features ..

Kaz: Also fine
… adding basic ideas and editors notes

Ege: Question to Mahda about toolchain...

Koster: Can be decided as we go
… do we depend on toolchain

Daniel: I think the later we change toolchain the more complex it gets

Cristiano: Big impact is initial connection
… this topic is "on discussion"
… there is strong dependency between toolchain and initial connection

Koster: I see

Ege: I don't think it will be ready
… still put it in the spec with the "current" toolchain

Cristiano: Means we need to do the work twice

Ege: Yes

Kaz: In that case we need to identify when to use what

Ege: For now we use "old" toolchain till new toolchain is ready

Koster: We may need some toolchain features for Plugfest

Kaz: okay with using current toolchain
… we need to check which part is correct and synchronized
… among various resources

Ege: Yes

Kaz: Manual checks might be needed

Koster: We need to talk about scheduling
… and look at checklist in w3c/wot-thing-description#2112

Ege: A question to group
… anything needed for other task forces.. like scripting

Cristiano: We tagged issues "wait for TD"

Daniel: topic "async actions" comes to my mind

Koster: relates to manageable actions

Daniel: Yes .. many parts are underspecified

Koster: We need to think prioritizing ...
… we should start prototyping

Ege: Availability of people during summer is important

Koster: we have 2 weeks in July and 2 weeks in August

Daniel: Beginning July to mid of July vacation

Cristiano: 2 weeks in August
… maybe 1 week in July

Koster: leaves 2 weeks in July and 2 weeks in August to work

Mahda: Miss week 21st of July
… Aug 11 also

Mizushima: 1 week end of August

Ege: last 2 weeks in July/August everyone seems available

Koster: w.r.t. data mapping we need to look into requirements
… the rest of the "goals" are fine scoped

Ege: I think we should do the "same" for Binding registry
… there are 2 PRs

Bindings Registry

<kaz> Registry Issue 12 - First Draft Registry Plan

PR 10

<kaz> Registry PR 10 - refactor: initial setup taking over content from MD

Koster: Any objections to merge this PR
… no objections .. merging

PR 11

<kaz> Registry PR 11 - Adding abstract

Koster: is about abstract

Daniel: Yes, abstract was taken from an existing abstract

Koster: Any objections to merge this PR 11

Koster: Merging ...

Thing Description

Manageable Affordances

<kaz> Manageable Affordances Analysis

Cristiano: Look for technologies in area of async actions
… we already have good use-case
… Concepts of invoke, cancel, queuing
… I have a rather long list of technologies
… some technologies support async actions
… and then observing property ...
… I think those are not the right exanples..

Koster: We want to have something that has a better mechanism , right?
… do we have to map to these protocols ?

Cristiano: For now I am focusing on frameworks
… still observing protocols
… in AWS you can have async actions.. mapped to MQTT
… in "Particle" they don't have these concept
… interesting to know.. but I would like to leave those out

Kaz: Discussion is useful
… Manageable affordance might be a bit vague
… based on the issues we can create user stories
… starting with those 4 pain points

Cristiano: We have a bunch of user stories
… and we can move in parallel
… the name "manageable affordances" is very generic, right
… maybe we can rename in future

Kaz: manageable affordance would be broader than TD itself
… management seems to much
… I think we should be careful

Cristiano: Sure, it is a broad scope

Cristiano: For now, I am just focusing on "async actions"
… I hope till next week I have something to present

Koster: Kaz, is it about the name and the implied scope ?

Kaz: Yes

Koster: Pain points might be too broad also?

Kaz: Yes

Koster: I think it is fine to focus on async actions

Koster: we can narrow the scope to things we can tackle
… there are uses besides "async actions" ... and we need to accommodate them also

Cristiano: Creates more verbose TDs
… including them as "bad" example ?

Koster: Yes, maybe

Kaz: Echonet has own version of TD
… has capabilities of grouping of actions and devices
… we can look into their approach

Cristiano: Yes

Kaz: If their approach is good enough, we can import the approach

Koster: Dynamic nature is a breaking point
… that's a fundamental issue

Koster: We should look into prioritizing

Koster: AOB ?
… good discussions today!

Koster: BTW, Ege is on vacation next week
… we start vacation season ;-)

[adjourned]

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