W3C

– DRAFT –
WoT-IG/WG

15 December 2021

Attendees

Present
Daniel_Peintner, Ege_Korkan, Kaz_Ashimura, Kunihiko_Toumura, Michael_Koster, Michael_Lagally, Michael_McCool, Ryuichi_Matsukura, Sebastian_Kaebisch, Tetsushi_Matsuda, Tomoaki_Mizushima
Regrets
-
Chair
McCool/Sebastian
Scribe
dape

Meeting minutes

Previous minutes

-> Dec-8

McCool: Correction: Farshid works on EdgeX and not for

Kaz: fixed

McCool: Minutes approved

Quick updates

Editors' sync-up call on Tuesday

Lagally: talked about scripting and use-cases
… proposal to call them "Developer use cases"

McCool: use-cases are quite broad
… "Developer examples" ?

Lagally: rather "Deployment"
… w.r.t. Profile
… see PDF
… Dave is one of the authors

<McCool> https://european-iot-pilots.eu/wp-content/uploads/2018/11/D06_02_WP06_H2020_CREATE-IoT_Final.pdf

Lagally: talks about interoperability
… currently profile looks at technical interoperability

Kaz: /* back to use-cases, will talk with PLH */

OPC-UA

Sebastian: We had meeting with Jeff 2-3 weeks ago
… talked about ideas how we can work together
… Jeff was okay with that
… IF we want to have more impact... we should work on a stronger partnership
… I think currently the liaison statement seems enough to me
… IF there is more interest, we can think about new partnership

Kaz: I agree with the reasoning
… we should start with basic discussion
… can also involve OPC-UA people in PlugFest

McCool: At this point we should do our homework

Lagally: industrial use-cases are important
… joint action-plan/vision would be desirable
… should work on requirements and a plan

McCool: We can do it informally
… should do it more structurally
… develop drafts
… joint standard is a next step

Lagally: We need 2 documents
… 1 on OPC side and 1 one our side

McCool: We need to look at the scope also

<mlagally_> ... these documents need to be synchronized, coordinated

Sebastian: Agree with structured overview proposal
… should do that together with OPC-UA
… I will ping OPC again
… show our ideas
… maybe in a joint meeting

McCool: +1

<mlagally_> ml: +1

Kaz: Yes, let's go in this direction

Sebastian: Okay, will do that the next weeks

Updates on the possible new Architecture call slot?

McCool: Conclusion on timeslots?

Lagally: Need to check Doodle
… will look at it in tomorrows Arch call

McCool: Note: we are thinking about 2 slots

WoT Japanese CG updates

Mizushima: The agenda for Kick-off meeting has been decided
… each task force (translation and use-case/outreach/deployment) will be discussed

<kaz> announcement on ML

Kaz: Mizushima-San has sent out email about it

Smart Cities updates

Kaz: will talk to stakeholders in various countries

W3C notes

Daniel: notes are not allowed to have normative statements or conformance section

McCool: Yes, Binding is somewhat in the same situation
… Scripting is special, since we might turn Scripting into REC

Kaz: W3C can have conformance section
… note itself is non-normative
… suggest to remove conformance section

McCool: Need conformance section
… special version

Kaz: several notes which have conformance section usually state they are non-normative
… will talk to PLH

Daniel: 2 points
… 1. non-normative API does not make sense
… 2. Other notes like DID have normative statements also

Lagally: Situation is confusing
… getting rid of MUST etc

Kaz: IF we want to have normative statements, we need to be on REC track

McCool: Should handle it in next charter

Lagally: We have charter
… I would be very concerned if we try to move WG notes to the REC track at the end of the current charter period

McCool: We are talking about "next" charter

Rechartering and Charter Extensions

IG Rechartering

McCool: W3M approved charter
… need 3 months to accommodate the AC Review procedure.
… need announcement soon
… today we send out call for review

WG Charter Extension

McCool: similar problem
… expires end of January
… AC review takes 6 weeks due to holiday
… we *might* have a gap
… Question: 1 announcement or 2 ?
… tight timing

McCool: W3M meet today
… please ping AC reps to approve charters

Lagally: draft extension, what do you mean?

McCool: Yes, this is just the extension

Lagally: Same charter with changed dates?

McCool: Correct, a modification only
… new charter will cover *new* deliverables
… at the moment we collect ideas

Lagally: new charter in Sep 2022?

McCool: Plan for July/August

Kaz: Next charter for 2.0 in August ... we need to finalize charter in April/May *IF* we really want to start our next charter period around July.

McCool: Okay, let's revisit this topic

Discuss decision process

McCool: We need to discuss it in more depth
… once we have more bandwidth

Publications

McCool: Call for Resolution to publish updated WoT Use Cases and Requirements?

Lagally: Yes, we agreed on publication candidate yesterday
… please have a look

McCool: 2 week announcement?
… because of Christmas.. we might do it in January

Lagally: one more use-case call next week

Marketing

WoT CG

McCool: CG is not up-to-date anymore
… need a *new* chair, since Dave is stuff member
… CG useful for OpenDay and public announcement

McCool: Ege volunteered to be CG chair
… need 5 nominations from organization

Lagally: Propose call for chair

McCool: Okay, let's do that
… maybe 2 chairs are even better
… Decision: early next year
… please volunteer

Ege: Fine by me

Wiki page improvements

McCool: will do some wiki clean-up

Testing

McCool: will discuss this the next hour

McCool: TD call today?

Ege: Yes, I will chair

Liaisons

ITU-T SG20

McCool: Joint call now set for Feb 3 at 09:00 EDT / 15:00 CET, for 2h

https://www.itu.int/en/ITU-T/webinars/20220203/Pages/default.aspx

McCool: speakers from W3C WoT (proposing 60m total, McCool (15m), Kaz (15m), Sebastian (30m) to present)

<kaz> [main call adjourned; Plugfest call starts in 10 mins]

Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).