W3C

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

11 September 2024

Attendees

Present
Daniel_Peintner, Jan_Romann, Kaz_Ashimura, Luca_Barbato, Mahda_Noura, Michael_Koster, Tomoaki_Mizushima
Regrets
Ege
Chair
Koster
Scribe
dape

Meeting minutes

Minutes Review

-> 4 September 2024

Koster: I don't see any issues..
… any additions/changes?
… none -> minutes are approved

TPAC

<kaz> TPAC 2024 WoT wiki

Koster: Last week we covered the breakouts
… we look at 60 minutes slot for TD and Binding

TPAC 2024 WoT wiki - TD/Binding slot

Koster: We a list to be discussed
… we need to think about priority
… "Binding vs Profile" seems important
… I move it to the top
… Not sure what "Use case extraction" means?
… what should we talk about

Kaz: It is about potential use-case extraction from backlog
… 2 items "use-case" and "backlog" can be merged

Koster: Okay, I see
… is there anything we can de-prioritize?

Kaz: "Binding vs Profile" is important, but depends on Lucas availability
… 90 minute slot seems reasonable

Koster: I see, merging "Profile" and "TD"

Kaz: We should ask Luca about his opinion

Luca: I am not sure if I am available at TPAC
… more important to have Ben. I am just the moderator...

Koster: Is combining TD and Profile okay?

Luca: Seems a good idea
… Profile and Binding is getting closer
… getting Ben in would be the best option
… Ben has a strong opinion

Koster: We try to make offline progress
… we might want to engage Ben
… we also discussed to prepare use-case templates
… putting upfront use-cases makes sense

Mahda: Suggest to have "use cases and requirements" at the beginning .. since it is driving the disusscion
… we also have "JSON schema resources".. not sure why there is specific topic about it

Koster: I think JSON schema topic is resolved.. lets remove it
… we can combine toolchain and resource management

Mahda: Maybe JSON schema points to the work about referencing JSON schema officially

Koster: Probably .. yes.. normative references
… JSON schema folks created own legal entity

Koster: What is "Project/Backlog" ?
… like a review?

Kaz: Yes
… TPAC meeting is special
… priority should be use-case requirements and binding vs. profile
… maybe we can tackle a 3rd topic

Koster: I would say "Registry"

Kaz: There will be breakout sessions about registry ... I think there is at least one from Ege
… could give a short report about breakout session

Mahda: McCool mentioned ontology versioning in main call
… should we talk about it at TPAC

Koster: As part of resource management?

Mahda: I think ontology versioning needs its own slot
… but we don't know what we need to do yet

Koster: Okay, let's keep them separate

Mahda: We also have breakout session for toolchain
… we could have a report for it as well

Kaz: separate breakout report session might make more sense.. since McCool, myself and Koster have their own breakout sessions also

Koster: We could do that

Kaz: BTW, we have "Resources" section also

Koster: I see, move resources topics to this slot

Koster: Let's look at the times
… 30 mins use-case
… 30 profile vs. binding
… 15 breakout reports
… 15 min Project/Backlog
… we can still refine it

Kaz: BTW, I added "smart city report" to the "Slack" section. Report out for TD topics to be done during the TD slot and other reports to be done during the "Slack" slot.

Koster: I think it looks okay so far
… any suggestions?

AOB?

Koster: Not sure if we should open another topic? Suggest to close early today..

Kaz: Agree

Koster: We will not have a "slot 2" meeting tomorrow

<kaz> [adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 229 (Thu Jul 25 08:38:54 2024 UTC).