W3C

– DRAFT –
WoT Discovery

08 August 2022

Attendees

Present
Andrea_Cimmino, Christian_Glomb, David_Ezell, Farshid_Tavakolizadeh, Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool, Tomoaki_Mizushima
Regrets
-
Chair
McCool
Scribe
FarshidT

Meeting minutes

Minutes

<kaz> Aug-1

McCool: some minor issues
… no objections to publishing

Logistics

McCool: Aug 15th is a public holiday in Germany

Farshid: In some states only

McCool: Any objections to cancelling the next two weeks?
… many people will be on vacation
… Will cancel. No objections.

TAG Review

McCool: I took care of the issue about making sure that assertions are testable.

Wide Review

McCool: Only remaining issues is: Registration information timezone handling (https://github.com/w3c/wot-discovery/issues/321)

McCool: We should use RFC3339 to enforce having the timezone

Farshid: we use dateTime as with TD's created and modified

McCool: TD has an additional assertion saying that RFC3339 should be used: https://w3c.github.io/wot-thing-description/#td-basic-types-mapping

<kaz> related wot-discovery PR 389 - Absolute time in dateTime format

Farshid: However, section 5.3.1.1 points to XML dateTime for created and modified: https://w3c.github.io/wot-thing-description/#thing

McCool: Proposing the addition a similar assertion

Farshid: We need to make sure it is consistent with the ontology

McCool: Updating the assertion in the PR...

Andrea: We can define a new type and add it to the ontology.

McCool: Added an ed-note to try and add this constraint into the ontology instead of the assertion in text.

McCool: Created an issue to resolve this later: https://github.com/w3c/wot-discovery/issues/390

McCool: no objections. PR merged.

<kaz> related issue 321 - Registration information timezone handling

Testing

tdd-notification-data-diff-unsupported should be tested manually

<McCool_> https://w3c.github.io/wot-discovery#tdd-notification-data-diff-unsupported should be handled manually

Farshid: the assertions about unimplemented features are too strict, often requiring additional implementation
… will add a PR to relax the assertions for things that aren't implemented by a server

Next Charter

McCool: We may want a Discovery 1.1 instead of 2.0, depending on backward-compatibility requirements.
… will go through the backlog to try and understand better.
… we also need to be ready for the CR by the end of month and close remaining issues such as relaxing the error responses.

<kaz> [adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).