Meeting minutes
new people
Koster: no Guests, New Members and IEs at the moment
Minutes
<kaz> July-9
Koster: let's skim over the minutes
Koster: any remarks?
Koster: minutes are approved
TPAC2025 Planning
Koster: we need to plan the TPAC and Plugfest
Kaz: please provide your availability for plugfest and tpac
Koster: yes please everyone
Sebastian: I have also invited OPC UA Binding WG in OPCF
Sebastian: some can participate. possibly remote
McCool: I would like to invite NGSI-LD as well
Kaz: Basically, all the participants need to pay, so we need to clarify who to participate how
… if their participation is only one-hour or so, maybe we can negotiate, though
Holiday and Unavailabilities
Koster: kaz is not available on july 31. I will cancel the td call
Publication schedule
McCool: I will update the schedule for use cases
New Charter
<kaz> WoT WG Charter
Koster: we need to agree on what to do with the marketing and people who did not join the wg
<kaz> WoT IG Charter
Ege: what would happen with the marketing resources on GitHub?
… technically, we can remove the WoT IG, but don't want to lose any existing resources
Koster: the biggest issue I imagine is some of the IG participants can't join the WG officially
… but we can invite them to the WG calls if needed
… we can simplify our activities, I think
Sebastian: Ege's concern is valid, I think
Sebastian: valid points regarding infrastructure. Is it possible to continue the space?
Sebastian: in my understanding, we can define our own rules for such kind of task forces like marketing and plugfest
Sebastian: we can say that the CG acts like the old IG. Kaz can comment on that. We can have a closer collab with the CG
<kaz> WoT IG's scope
Kaz: probably we need long discussion about this mechanism. We should clarify what we want to work on as a whole ig and wg together
… then we can discuss which group can do which work
McCool: I propose merging the work of IG into the WG space
… and then decide how to split the work where
… to not leave anything hanging
Koster: IG charter has time left
Koster: There will be time in the IG charter which overlaps with WG
Kaz: I will talk with PLH about the concrete process
Koster: should we make a resolution
Kaz: we can agree on the general direction
Daniel: what about moving the IG topics to the CG?
Kaz: both directions can work potentially
McCool: a draft charter can be done
Kaz: I can help the chairs for this one
<mjk> Proposal: We would like to proceed with merging the WoT Interest Group work into the WoT Working Group. Next steps are to coordinate with W3M and create a plan for merging the activities
Sebastian: I am fine with this direction
RESOLUTION: We would like to proceed with merging the WoT Interest Group work into the WoT Working Group. Next steps are to coordinate with W3M and create a plan for merging the activities
Koster: ok we have a resolution for the basic direction
Use Case Discussion
McCool: I need 1 more hour of work on it. Then it will be in a state ready for the note
McCool: the question is about the process
McCool: Current document has too much stuff for someone to find the interesting stuff
… the intention was always to move the interesting parts to the TFs and for this document to act as a public facing summary
… also there are some use cases and stories that do not fit one TF
Kaz: I agree that we need to think about the process
Kaz: which version of the template should be used should be clarified. Also it should be detached from specwork
McCool: there are no different versions
Kaz: can you clarify what to use? Also we should handle (1) the template on GitHub for spec work and (2) the UCR document as a Note separately.
McCool: I will show
<kaz> wot-usecases repo's Issue templates
McCool: (shows the github issues and the templates)
<kaz> WoT Use Cases and Requirements Editor's Draft
McCool: (shows how it looks like in the document)
McCool: here are the definitions we use. different people have different definitions attached to these words
<kaz> wot-usecases/README.md
Kaz: tx for your description. now we're getting information about the templates, and we should think about the process a bit clear. there is some initial proposed process on README.md above, but we still need to clarify the actual process.
McCool: I think we have enough use cases, which are more generic stuff. User stories drive the features as they are written from the point of view of a developer asking for a feature
Kaz: as you know, the TD TF has started to define concrete process for UCR definition on the TF side, so we as the whole group should clarify which parts to be handled by the UC TF and which other parts to be handled by the TD TF.
Koster: adjourning unless there are no other comments
Koster: no call in the next hour
<kaz> [adjourned]