W3C

WoT-IG/WG

14 July 2021

Attendees

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

Meeting minutes

McCool: <Agenda walkthrough>

<kaz> Agenda

Minutes

McCool: let's review last meeting minutes:

<kaz> July-7

McCool: discussion about implementations ...
… ITU-T: there are two workshops: a proposed joint workshop and an ITU-T hosted WS
… can we publish?

- no objections
… kaz, please add a note to the ITU-T workshop plans to avoid confusion

vF2F minutes

McCool: some TFs have reviewed their parts, I hope TD can be reviewed today, use cases and architecture + profiles tomorrow
… we had 5 external presenters, time was a bit short
… some of the slides were provided, can we please add links to them to the minutes?
… Open day minutes were reviewed - no change required
… Day 1: charter discussion etc.
… Note: we cannot do a new WG charter right now, but only close towards the end of the current charter

McCool: Minutes for Day1 and Day 4 were reviewed and approved, others will be reviewed by TFs

IG Rechartering

IG rechartering:

<McCool> https://github.com/w3c/wot/issues/966

McCool: if you have comments, please add them to the issue

Smart Cities Workshop

mmc workshop has happened, Kaz created a draft report

Kaz: workshop went very well, 3 sessions, we identified important stakeholders, govt. agencies, committees, ...
… we updated the smart cities IG charter and will bring to W3M, the notes are under review by the program committee of the workshop

McCool: recordings and slides are available, some will still be uploaded

Testing

McCool: We need to get our testing organised, let's talk about it in the testing call.
… we should also have testing calls in the upcoming weeks. October plugfest will be testing plug fest, no new experimental features before testing is done.

Publication Planning

McCool: we have updates in editors drafts, including discovery - need to do a resolution next week
… editors drafts are available for reviews
… other plans?

Daniel: Scripting will take some more months

McCool: we have a couple of MRs in place for security best practices - they can wait a bit
… any planned updates for the TD spec?

Sebastian: will discuss in today's TD call, some new findings from F2F and issues - ideally before the summer break but not sure.

McCool: I have created some PRs for architecture, hope to get them merged tomorrow
… terminology about hubs and gateway fixes has some implications, hope to get them in tomorrow

Liaisons

ITU-T SG20

McCool: ITU-T got back to us, potentially need to discuss with W3M if they want to have an official joint workshop between ITU-T and W3C, there was a bit of confusion about two workshops, Kaz will sort it out

ECHONET

<Ege> https://github.com/w3c/wot-profile/pull/85 please check this

McCool: Echonet: need clarification on concrete binding - try to do it and identify technical issues

Kaz: expectation of Echonet/Matsuda-san is to start with the examples that were provided in the slides

McCool: if there's a binding for Echonet, it could be reviewed, but an example is not a spec

Ege: In part of the restructuring of the binding specification I'm proposing an Echonet binding. that Matsuda-san is also an author

Kaz: We could start with the example

Lagally: we may be missing important parts of the spec that are not in the example

Matsuda-san: Please start with the example, I personally would like to write a TD to allow W3C WoT to access Echonet server
… you can access the URL with the binding template spec, but personally I think you cannot specify the data format
… if a client reads a property the HTTP return body is different
… key + value pair is returned as a JSON object, format is different

Lagally: please let's discuss in tomorrow's architecture+profile session

Kaz: I suggest we start with the interface discussion
… we should start the official technical discussion with the Echonet steering committee - I will send it

ECLASS and ISO TC184/SC4

McCool: ECLASS and ISO - we look for extension ontologies for both cases
… I think we have some specification gaps, how to get ontologies, ...
… next step for ECLASS to write up some use cases

Sebastian: CDD is a different approach than ECLASS, we also need to clarify what is meant with "ontology"
… commonalities [between ECLASS and ISO] are IEC61360

McCool: if there's common ground, we should share same base ontologies

Kaz: we should handle both organisations in parallel to identify what and how to refer to their ontologies.

McCool: these guys are experts - why don't we start with ECLASS, if we hit another ontology we may be able to adapt

the Other Liaisons

Sebastian: OPC-UA - will be discussed in next UC call.

McCool: DTDL will be difficult

TF reports

Daniel: Scripting: working on finalizing some topic around discovery. We decided for scripting that the review of minutes is happening outside of the call.

McCool: others could follow that model
… tooling: perhaps we could do minutes in github
… Security / Best practices - Some PRs and cleanup are going on, specifically wrt. OAuth. This should be removed from the UC document, will clean it up in the best practices document.

Sebastian: Marketing: content updates for the web page - news on twitter to share info about vF2F
… some discussions about visitor counters, identify room for improvements
… create a youtube channel with WoT based videos
… Ege plans to hire a student to create tutorials

<kaz> [ Please note I gave a comment on that during the Marketing call. ]

Lagally: Use Cases
… had discussion on ECLASS
… expecting further collaboration on how to use their data definition from TD based on some concrete use case

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 136 (Thu May 27 13:50:24 2021 UTC).