W3C

– DRAFT –
WoT Discovery

06 November 2023

Attendees

Present
Kaz_Ashimura, Michael_McCool Kunihiko_Toumura, Tomoaki_Mizushima
Regrets
-
Chair
McCool
Scribe
kaz

Meeting minutes

Minutes

Oct-30

McCool: (goes through the minutes)
… any objections?

(approved, and will be published)

Logistics

McCool: will change the time for the Discovery call two hours earlier from the next week
… that will be one hour later than the Scripting call
… anything else?

(none)

Quick updates

McCool: IEEE P2874 - HSML/Digital Twins/Verses.ai, Draft 3
… let's talk about this during the Chairs call tomorrow

Use Cases and Requirements

PR 231

<McCool_> w3c/wot-usecases#231 wot-usecases PR 231 - Capture Discovery Requirements

<McCool_> (merged 2 weeks ago)

Issue 236

wot-usecases Issue 236 - Associate Discovery Requirement with Use Cases

McCool: would create another issue to move the Discovery Requirements under "Functional Requirements"

wot-usecases Issue 237 - Move Discovery Requirements under Functional Requirements

Kaz: regarding the structure of the "Use Cases and Requirements document", any structure is fine as a tentative structure for brainstorming. However, as the final structure, I think it should have the Use Cases section followed by the Requirements section which lists "Related WoT specs" later
… it would be better to have that kind of basic structure than having detailed sub categories based on the specifications including several use cases and requirements

McCool: (creates yet another issue on categorize status of Discovery Requirements)

wot-usecases Issue 238 - Categorize Status of Discovery Requirements

<McCool_> wot-usecases Issue 239 - Review Discovery Requirements

McCool: (created another bigger issue about Discovery Requirements review)
… need to think about the order to handle those issues

<McCool_> order: 236 and 238 in parallel, then 239. 237 can happen any time, but needs to be coordinated with other TFs

Kaz: issues on structure and issues on the content itself should be handled separately

wot-usecases Issues with "Discovery" label

Publication

McCool: status?

Kaz: Discovery should be OK
… On the other hand, most of the PRs for figure fix have been merged
… there is one remaining to be reviewed during the main call
… regarding the WoT resources, still waiting for the response from PLH
… and regarding the Press Release, the MarComm Team is proposing we ask the W3C Members for review and Testimonials for 2 weeks

Discovery Issues/PRs

PR 514

PR 514 - Initial survey of other discovery mechanisms

McCool: Toumura-san?

toumrua: have not finished it
… if you have any comments, please let me know

McCool: support for wide-range of introduction

Toumura: would be enough to list the mechanisms for WoT Discovery

McCool: is the one from OASIS already a standard?
… maybe we can start with this
… also could look into the "Home Assistant"

Kaz: I think asking Toumura-san to work on everything is too much
… so would suggest we merge this initial list itself right away with a title of "Draft Survey"
… and ask all the WoT participants to share the detailed survey
… maybe we need to ask the related liaison organizations as well for help

McCool: kind of agree
… what do you think, Toumura-san?

Toumura: agree we merge this PR right away with a title of "Draft Survey"

McCool: (changes the title of the MD, and adds a comment)

McCool's comment

(merged)

McCool: now we have a document at https://github.com/w3c/wot-discovery/blob/main/proposals/other_mechs.md
… would change the name to "introductions.md"
… (renames it)

introductions.md (which was "other_mechs.md")

(now, the main introductions.md file has a list of introduction mechanism components first, then Other SDO's discovery mechanisms including MQTT and OPC UA)

wot-discovery/proposals/introductions.md

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).