Meeting minutes
Guests, New Members and IEs
Koster: no new Members
… 2 more IE applications
… Kaz is checking with the Membership Team and PLH
Kaz: right
Minutes
Koster: (goes through the minutes)
… any objections?
(none)
approved
Quick Items
Discovery
Koster: postponed till McCool is back
… any other quick items?
(none)
Notices
TPAC 2025
Kaz: group meetings and breakouts
… TPAC will be held in Kobe on Nov 10-14
… should respond to the GitHub repo
Meetups
WoT CG
Koster: next meetup on June 5
Sebastian: Ege was planning to join this call but seems to be a bit late
Koster: ok
WoT JP CG
Mizushima: no updates
Smart Cities
Koster: there will be a 2.5h workshop by the Nordic Smart City CG
… Kaz and Koster will join it
… they're doing bunch of stuff
… on the other hand, the IG's next call will be held on May 26
… working on collecting resources
Kaz: we'd invite stakeholders to the meetings
… sent invitation to key stakeholders from related SDOs, and have got a response from Mark Fox from ISO, etc.
Cloud-Edge
Koster: any updates?
(none)
Liaisons
ECHONET
Koster: TD TF has related use cases
Kaz: at some point, we can ask them for review about the use cases, e.g., grouping and history
Conexxus
Koster: any updates?
… they're joining the Profile calls
David: actual group has stopped their work, but planning to publish documents by the end of year
… still mean to clarify our needs
Koster: ok
… communication aspects around WoT Profile
David: what kind of Binding would fit together as well
… obviously two potential layers there
Koster: the guidance we have so far is...
… defining Profile as constraint
… then mapping for interoperability by Binding
… we're hoping to get use cases
David: flexibility to define our standards
… right handling of WoT would be useful to refine implementations
Koster: why it's different from Open API, etc., is a good question
… the other important thing is connection to Ontologies
David: Connexus, GS1 and VCWG are working together
Koster: if you use modern Ontology descriptions, ...
David: there was now OWL, etc., in 2002
… while there are various notations now
… our system uses JSON Schema
Koster: would be interesting to have longer discussion about that
… some of the AI systems use good meta data ontologies
… good discussion
… details to be done during the Profile calls, etc.
OPC
Sebastian: can share latest information
… they're now on their review phase
… at least two more meetings to be done
… then they can submit an OPC Binding proposal
Koster: sounds great
Sebastian: we can ask them about implementations too
… if you're interested in joining their meetings, let me know
Koster: liaison with them is really good
Sebastian: node-wot implementation is also updated now
Daniel: correct
Sebastian: you're welcome to try that
… for OPC binding proposal
ETSI
Koster: next meeting will be held on June 2
Kaz: right
… we're collecting resources on use cases from W3C and ETSI
Meetups - revisited
WoT CG - revisited
Ege: next meeting on June 5
… visual programming with WoT
… handling bluetooth, HDI and USB bindings
… non-TCP protocols
… very interesting approach
… so wanted to explicitly mention that here
<EgeKorkan> Calendar
Ege: btw, the CG participants are wondering about the next Plugfest
… any interest in organizing one?
… can we talk about that now?
Kaz: there will be held TPAC 2025, so we should have one there
… for that purpose, we should start discussion about the logistics, etc.
Sebastian: are you thinking about physical one?
Ege: possibly
Sebastian: online version Plugfest would be easier to organize
… but physical one would be better
… would invite TUV, etc., too
… maybe we should put this on the agenda for TPAC
… possibly right before the official TPAC meeting
Kaz: agree
… technically, we can start initial discussion next Wednesday given the Profile call will be bi-weekly
Koster: sounds great
… btw, what about CG's organizing Plugfest?
Kaz: technically, anybody can organize Plugfests :)
… also we can joint their organizing Plugfest as well
… maybe we should be a bit careful about the usage of "WoT Plugfest", though
Koster: good point
Ege: think "Plugfest" is common enough
Kaz: maybe we can simply say "WoT WG/IG Plugfest" and they can say "WoT CG Plugfest"
Koster: yeah, could be able to differentiate it
Ege: so far, CG Plugfests have been very casual
Koster: another point around testing
… we need to handle testing as well for Rec documents
Ege: we should restart the Plugfest/Testing calls
Kaz: I think as a starting point, the Chairs can moderate the call to discuss TPAC prep
… and then at some point, if there is somebody interested in moderating the detailed discussion on Plugfest and Testing, we can ask that person to take over the role
Koster: sounds good
Ben: regarding the slot, it's fine to use the Profile slot bi-weekly
… should be checked on the case-by-case basis
Koster: ok
… let's proceed with that plan
… any other points?
(none)
Schedule
Kaz: Sebastian won't be available on May 21. right?
Koster: ok
… goes through the Cancellations section
… Kaz will be unavailable on June 11-13
Kaz: sorry but there will be a big exhibition event there
Koster: let's cancel the calls on Wed/Thu then
… will be checked during the Chairs call next Monday
Kaz: ok
Policy
Koster: any topics for today?
(none)
TF Leads
Koster: anybody interested in Security, Discovery, Architecture or Testing?
(none for now)
Koster: regarding the UC TF, we've decided to move the UC work to the TD TF
… what is the status and plan for the UC TF itself?
(none)
Mizushima: today's UC call was cancelled due to lack of participation
Koster: should we suspend the UC call?
Mizushima: would like to continue the UC call itself...
Koster: so you mean we're not ready for suspending the call?
Mizushima: right
Ege: just wanted to mention one thing
… need somebody to put UCs on GitHub
Kaz: you and McCool showed the proposed procedure during the main call 2 weeks ago
… then we as the whole group made a resolution to go for generating UCs by the TD TF
… so the details on the procedure to be discussed during the TD TF, e.g., today
[adjourned]