W3C

– DRAFT –
WoT WG/IG

16 November 2022

Attendees

Present
Daniel_Peintner, Ege_Korkan Tetsushi_Matsuda, Kaz_Ashimura, Kunihiko_Toumura, Michael_Koster, Michael_Lagally, Ryuichi_Matsukura, Sebastian_Kaebisch, Tomoaki_Mizushima
Regrets
McCool
Chair
Sebastian
Scribe
kaz

Meeting minutes

Guests

Sebastian: no guests for today

Minutes

Nov-2

Sebastian: (quickly skim them)

approved

Discussion on Profile

Sebastian: unfortunately, no time to discuss Profile topics during the Architecture/Profile call right before this call
… would use 10-15 mins now

Lagally: we have 11 PRs for wot-profile
… Testfest expected in December
… no Architecture/Profile call tomorrow
… would see the PRs now

Pr 324 - December Testfest Preparation - implementation cross reference and xref tool

Lagally: created an additional README for report generation
… also updated the original README with how to provide results for Profile
… also several CSVs: assertion-totals.csv, implementation-xref.csv, template.csv
… and tool for cross-referencing

Ege: PR itself is fine
… but wot-testing repo should be used to get the test results from the implementers, shouldn't it?
… we should clarify our policy which to go
… putting the results on the spec repo
… or wot-testing

Lagally: point taking
… would like to keep things simple
… we can copy the results to the wot-testing area for the Testfest later

Ege: wot-testing repo has sub-directories for data handling already
… so people would be confused by this new proposal

Lagally: this approach itself is simple

Kaz: let's have more discussion during the Testing call later about how to handle the data for testing
… we just have 10 mins for Profile discussion during the main call now

Sebastian: did quick check on the wot-testing repo
… we already have README files there on how to organize the tests
… so not sure why we need to put this information under the wot-profile repo

Lagally: I'm OK with having this information under the wot-testing repo
… but we should have cross-referencing mechanism between the WoT Profile spec and its testing work

Ege: would suggest we not merge this PR and discuss it further during the Testing call

Lagally: would suggest we merge this and have further discussion later during the Testing call

Ege: would object we merge this PR...

Sebastian: also would suggest we discuss this during the Testing call

Daniel: +1

Sebastian: let's stop this discussion, and continue the discussion during the Testing call

Quick updates

IIWOT 23

Sebastian: our proposed invited talk itself is accepted
… but the are only 4 submissions for the workshop
… the question is now whether we really want to join the workshop or not
… would hear from McCool as well

Cancellations

Cancellations

Sebastian: no Architecture/Profile call tomorrow on Nov 17
… also no calls during the weeks of Dec 26 and Jan 2

Publications

Sebastian: got comments from Ralph on the exit criteria
… so have added clarification for TD and Discovery

<sebastian_> https://github.com/w3c/transitions/issues/474

Sebastian: generated a draft Transition Request for Architecture

Lagally: would review it

Sebastian: ok
… Regarding WoT Profile
… planning to have an updated WD by Dec 8 so that we can use it for the Testfest

Societal Impact Questionnaire

Sebastian: McCool is working on that

updated schedule

Sebastian: would publish an updated WD for Profile on Dec 21

WG Charter

Old Issue on WoT WG Charter

Draft WG Charter

Sebastian: confused with how to proceed

Kaz: the above Issue 978 on WoT WG Charter is kind of obsolete
… so we should rather create new Issues and PRs to update the draft Charter
… we should add an explicit label of "WG Charter", etc., for that discussion

Sebastian: good point
… (generates a new label of "WG New Charter Plans 2023")

Liaisons

Sebastian: no specific updates on OPC or DTDL
… would like to consider creating a dedicated TF for the OPC liaison
… but should have discussion during the WG Charter topic
… need to ask Erich about his availability for the next meeting

Collaborations

WoT CG

Ege: Cristiano and I had discussions on "Office Hours"
… around JSON Schema, etc.
… every Thursday
… also confirmed to have meetups
… with Deutsch Telekom on smart homes
… then Netzo
… next week, we'll have concrete link
… planned on Dec 15

Kaz: "Office Hours" is a generic term, but used for a meeting with AC Reps to supplement the discussion on virtual AC meetings. so it might be better to use another term for your event.
… regarding the meetup, we should not advertise non-Members work :)
… should be careful about how to manage the discussion

Ege: understood

Lagally: outreach from the CG?
… potential adapters who would be able to provide use cases

<Ege> +1 this :)

Lagally: hope that the CG would bring new Members for WoT

WoT-JP CG

Mizushima: JP CG is planning to have events on use cases and plugfest/testfest next year

APA

Lagally: asking the APA Chair to review the WoT Profile spec
… from accessibility viewpoints like screen reader

[adjourned; testing call in 8 mins]

Minutes manually created (not a transcript), formatted by scribe.perl version 196 (Thu Oct 27 17:06:44 2022 UTC).