– DRAFT –
WoT Discovery

Minutes

<kaz> Oct-10

no objections to publishing

Implementation Report Updates

<kaz> PR 427 - Update Oct 2022 impl report

McCool: Did the at-risk markup for CR transition as part of the same PR
… rendered report available at https://cdn.statically.io/gh/w3c/wot-discovery/2c3010dd5aa2d14fa41e8b27c454b47b13997ef8/testing/report.html

McCool: The report has a list of features that are at risk

Andrea: I have submitted new manual results for WoTHive

<kaz> wot-testing PR 452 - update Hitachi's result for Discovery

<kaz> wot-testing PR 453 - Create manual.cs for WoTHive

<kaz> wot-testing PR 454 - Update Discovery manual.csv for dart_wot

McCool: There seem to be multiple naming conventions for node-wot results, adding confusion in the manual/auto merger.

McCool: working on the implementation report...
… pagination is no longer at risk, except for the sorting and collection format

McCool: Thing type identification by discoverer is no longer at risk

I think tdd-notification-data-diff-unsupported (at risk) is covered by tdd-http-unsupported-feature. We can drop it.

McCool: Let's do that in another PR

PR (https://github.com/w3c/wot-discovery/pull/428) updating WoTHive results - has merge conflicts.

PR - Add dns-sd UDP assertions to manuals (https://github.com/w3c/wot-discovery/pull/429) - merged

PR to update the implementation report (https://github.com/w3c/wot-discovery/pull/427) - merged

<McCool_> proposal: request resolution in main call to proceed with CR transition for https://github.com/w3c/wot-discovery/tree/cr-candidate-3 branch of WoT Discovery

RESOLUTION: request resolution in main call to proceed with CR transition for https://github.com/w3c/wot-discovery/tree/cr-candidate-3 branch of WoT Discovery

<kaz> [adjourned]