W3C

– DRAFT –
WoT Discovery

05 September 2022

Attendees

Present
Andrea_Cimmino, Christian_Glomb, Cristiano_Aguzzi, Farshi_Tavakolizadeh, Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool, Tomoaki_Mizushima
Regrets
-
Chair
McCool
Scribe
cris_, glomb

Meeting minutes

Minutes

<kaz> Aug-29

Minutes from last meeting - approved

PRs

PR 395: Reduce restrictions on error codes for unsupported features

https://github.com/w3c/wot-discovery/pull/395

Farshid will fix collisions

PR 405: Update DNS-SD section

https://github.com/w3c/wot-discovery/pull/405

Suggestions from McCool added

McCool: Both UDP and TCP service names, more work for MDNS discoverer

McCool: What about CoAP over TCP?

Toumura: No implementation available yet

McCool: Should we drop protocol column such that there could be any protocol over TCP/UDP?

McCool: Cannot be tested

Cristiano: How to identify protocol? TLS vs. non-TLS?

mDNS response should clarify it

Cristiano: Should be in the URL -> http / https / coap / coaps

McCool: Or another parameter

Default http - CoAP special case

McCool: Concerns about multiple broadcasts

McCool captures comments in the issue

PR merged, but needs to be updated

PR 406: Refine DID assertions

https://github.com/w3c/wot-discovery/pull/406

McCool: Ambiguous assertions

<cris_> +1 for the changes

McCool: are resolved by this PR

Merged

PR 407: Remove stray mention of geolocation

https://github.com/w3c/wot-discovery/pull/407

Loosens statement about geo-location

Merged

PR 408: editorial: Remove extra word in example

https://github.com/w3c/wot-discovery/pull/408

Editorial fix, merged

https://github.com/w3c/wot-discovery/pull/395 (now fixed by Farshid)

Merged

McCool: Current draft should be CR candidate

<McCool> proposal: put forward the current editor's draft, after proposed improvements to the DNS-SD method in https://github.com/w3c/wot-discovery/pull/405#issuecomment-1237134489, as the CR Candidate for WoT Discovery, and begin the 2wk review process by at the latest Wednesday Sept 7.

<McCool> proposal: put forward the current editor's draft, after proposed improvements to the DNS-SD method in https://github.com/w3c/wot-discovery/pull/405#issuecomment-1237134489 (PR to be prepared by Toumura and reviewed and merged by McCool), as the CR Candidate for WoT Discovery, and begin the 2wk review process by at the latest Wednesday Sept 7.

RESOLUTION: put forward the current editor's draft, after proposed improvements to the DNS-SD method in https://github.com/w3c/wot-discovery/pull/405#issuecomment-1237134489 (PR to be prepared by Toumura and reviewed and merged by McCool), as the CR Candidate for WoT Discovery, and begin the 2wk review process by at the latest Wednesday Sept 7.

Issues

https://github.com/w3c/wot-discovery/issues/ w/ labels "Resolve by CR" and "Discuss"

Issue 165: Add Ability to Retrieve Original TD

https://github.com/w3c/wot-discovery/issues/165

Deferred to 2.0

Resolve TD/Thing ID Semantics (was Reconsider @type ThingID)

https://github.com/w3c/wot-discovery/issues/190

Farshid: Could add an assertion

Deferred to 2.0

Issue 185: OAuth2 and SSE Notificiations

https://github.com/w3c/wot-discovery/issues/185

Farshid: No good solution for this

Could add informative text in post-CR

Marked as "Resolve by PR"

Issue 96: Should security be mandatory on directories for WoT Discovery?

<kaz> https://github.com/w3c/wot-discovery/issues/96

McCool: we went on this long time ago
… I added a security-tracker label
… basically we concluded that there is an unrelated issue
… no time to resolve that by CR
… I don't understand where the issue is coming from. I think it is stale or already fixed
… any objection for closing the issue?
… ok closed

Issue 209: Thing Description Framing

<kaz> https://github.com/w3c/wot-discovery/issues/209

McCool: I can't see how we are going to solve this in the time we have
… we can defer it for 2.0
… is it something we still care about?

Andrea: it was something about the validation/signing of arrays in TDs

Cristiano: it is more a TD issue than discovery

McCool: right, adding a convert to TD label

Issue 157: Better explain HTTP focus

<kaz> https://github.com/w3c/wot-discovery/issues/157

McCool: I established that the issue is resolved.
… any objections ?
… closed

<kaz> Issue 187: Registration of Well-known URI, DNS-SD and DID Service Names, CoRE Resource Type

Issue 187

<kaz> https://github.com/w3c/wot-discovery/issues/187

McCool: we have a Pullrequest inflight, still in progress
… changing the label to resolved by Proposed REC

kaz: the important criteria is whether there are any normative changes which would impact existing implementations.

McCool: go back to resolve by CR label because we need to fix the DNS naming

Issue 148

McCool: it seems that we don't have the related PR

Andrea: just remember to uplaod the new ontology and context file to that namespace

McCool: can we use GitHub ?
… no we can't, but we have to upload the ontology to the new namespace
… We can always use the Github url for testing purposes

Issue 283: Organize Testing

<kaz> https://github.com/w3c/wot-discovery/issues/283

Andrea: I have some issues that I would like to discuss with farshid but I can do it later

Issue 340: Improve TD Server for protocols

<kaz> https://github.com/w3c/wot-discovery/issues/340

McCool: regarding Size2 option in coap
… it is slightly inconsistent but it is too late to fix. It is not a breaking issue

Issue 381: What should the server do if a user submits a Thing Description with POST request on /things which contains an id in the body?

<kaz> https://github.com/w3c/wot-discovery/issues/381

McCool: not understand

Cristiano: it should not be an issue

McCool: I would like to close Propose Close issues
… ping there if you feel otherwise
… closing the meeting

<kaz> [adjourned]

Summary of resolutions

  1. put forward the current editor's draft, after proposed improvements to the DNS-SD method in https://github.com/w3c/wot-discovery/pull/405#issuecomment-1237134489 (PR to be prepared by Toumura and reviewed and merged by McCool), as the CR Candidate for WoT Discovery, and begin the 2wk review process by at the latest Wednesday Sept 7.
Minutes manually created (not a transcript), formatted by scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).