W3C

– DRAFT –
WoT Discovery

14 February 2022

Attendees

Present
Christian_Glomb, Cristiano_Aguzzi, Farshid_Tavakolizadeh, Jan_Romann, Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool, Tomoaki_Mizushima
Regrets
-
Chair
McCool
Scribe
glomb

Meeting minutes

Minutes

Minutes from last meeting: https://www.w3.org/2022/02/07-wot-discovery-minutes.html

Some corrections, approved.

PR 275

PR 275: Update Problem Details editor notes

Cleans up reference, merged

PRs

PR 264

PR 264: Update Security and Privacy Considerations

Needs wide review

McCool: Separated the PR

Unfinished sections commented out

Added differentations between privacy and security

Resulting in new section ids

Farshid: another issue https://github.com/w3c/wot-discovery/issues/254 should also be included

McCool: will need additional PRs

Farshid: and also consider issue https://github.com/w3c/wot-discovery/issues/185

Will be merged, having the comments in mind

PR 269

PR 269 - Permit use of TD Links for Self-Description of Multiple Endpoints

McCool: Should be closed wo/ merging due to several points mentioned there - however still relevant

McCool: Two additional PRs still need rework, keep PR freeze at 28th of February in mind

PR 273

PR 273 - Things API with optional CRUD

McCool: Let's create issue for last open point and try to merge

Farshid: Renaming of APIs to avoid confusion

Farshid: Should drop "501" http error

Farshid: However, "404" still optional

McCool: Will save the discussion about this in an issue

Farshid: Directories must contain feature subsets such that the implementation makes sense, e.g. "create" wo/ "update" is a bit weired

McCool: Should have categories like "basic", ...

McCool: Should gather feedback on this PR until next week

McCool: Should have a note about "duplicates" and close the corresponding issue

PR 274

PR 274 - Specify Consumer Discovery Process

McCool: Requires lot of review

Scripting API TF already discussed it and want to give feedback

"D-" entities = "Discovery-" entities

McCool: Several implications wrt. fetching external URLs, or downloading all TDs from a TDD

McCool: Propose to introduce new section "Discovering Clients and Consumers" in spec.

McCool: "Read TD from a file" - is that discovery?

Probably not, even if it is a file URL

To allow for different protocols, introduce "configurator" and "executor"

Introduction should deliver unorded set of URLs (if there are multiple TDDs)

What if directories refer to each other? - should detect and limit possible loops.

Farshid: Could detect via unique id

McCool: What about directories inside directories?

Navigate via thing links?

Farshid: Can have TDD that is not hosting its TD but hosts it somewhere else

McCool: everyone, please review and comment

Adjourned

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