W3C

– DRAFT –
WoT Discovery

03 July 2023

Attendees

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

Meeting minutes

minutes

McCool: there is a typo with extra quotes

<kaz> June-26

McCool: one question here, part of mention about geolocation is missing

<McCool_> change "that's possible" to "geolocation has two parts, metadata and discovery; the second depends on the first"

the typo is with the sentence: around "break "improvements"

that should be "break 'improvements'"

<kaz> (fixed)

minutes are published since there is no objection

detailed planning

<McCool_> wot PR 1094 - Discovery Planning

<kaz> proposed work-items.md within the PR

McCool: the summary is putting planning documents under discovery-planning branch
… in last meetings the working items were prioritized

McCool: adds some points under additional introductions (e.g. discovery in MQTT)

McCool: high priority are things that provide us major functionalities, middle are improvements but are not pillar functionalities, low is questionable/tentative things

McCool: the middle priority is divided into direct and dependency

Kaz: the categorization is nice
… but we need to think about concrete use cases for variable industry adaptions.

McCool: we should look for use cases that want to adopt WoT directly for this

McCool: we could focus on things that are just wot and remove middle having only two categories instead of three

Kaz: we need also to consider existing discovery mechanisms in IoT (that is open question)

mccool captures this comment under "Open Questions"

Kaz: we should confirm and validate the compatibility with these mechanisms in WoT

Luca: onboarding should not be discussed here
… that's part of security

Luca: there are two components one is in charge of discovery items and another mapping the device to a description

McCool: this extends the scope of discovery, the discovery is more restricted. We discovery things that are registered and there is no generation of TDs, these are provided.

mccool adds an item explaining this topic under the Open Questions

McCool: moving to geolocation, maybe what is a bit confusing is that geolocation can be divided into two items: the meta-data part and the discovery using that meta-data

mccool fixes the work items in the document putting moving the bullets under their correct section

McCool: any idea on how to improve the organisation of this section?

Kaz: I'm OK with this discussion itself, but we could use the wot-discovery repository to discuss this around the initial phase of the Discovery TF's work for the next Charter, Couldn't we?

McCool: yes, but the planning discussion should be managed based on the group-wide decision. So I proposed this method during the planning meeting last week and it was approved. Also moving the information from now would be confusing.

mccool merges the PR

Kaz: this discussion is fine as initial brainstorming, but for further discussion, we need to look into concrete use cases for example for smart homes, smart buildings and smart cities, which would require more complicated setting and mechanism for device and user discovery
… and after clarifying those target use cases, we can think about what is needed for WoT Discovery.

McCool: right

<Mizushima> +1 kaz

McCool: but note that I don't want to extend the scope of WoT Discovery drastically

Kaz: agree

McCool: please review the updated work items and give comments

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).