– DRAFT –
WoT Discovery

<kaz> how to do wide review

meeting starts reviewing the PRs

correction, meeting starts reviewing the minutes

minutes

<kaz> Feb-21

since no objections were presented minutes are approved

Wide Review

McCool: I would like to review the wide review process

it is discussed who reviews the different proposals: Accessibility, Architecture, Internationalization, Privacy, Security

discovery needs to work on questionnaire and the short checklist

McCool: some of the FAST Checklist may apply so we need to go through

mccool asks for volunteers for Accesibility and Internationalization

Kaz: 2 comments
… we can look into our previous answers for v 1.0 specs
… also it would make sense to talk about the procedure and tools during the Editors call, e.g., tomorrow

mccool creates an issue in the discovery repo with the report to be filled

the report is going to be filled during this call

<cris_> https://www.w3.org/TR/wot-discovery/#validation

for the first point of the report (if in the spec there is any natural language text besides messages, UI text, json) mccool specifies that the spec contains Error details, mapping from error codes, and others

<kaz> example of Secure Payment Confirmation

<kaz> secure-payment-confirmation issue 93 - Localization topics to address (using i18n-tracker)

McCool: marks point 2 of the report as "Not applicable"

mccool fills section 3 explaining the mechanism to page through TDs

mccool fills section 4 with the different query mechanisms

section 6 is not applicable

section 7 is filled explaining that time is used.

<kaz> (btw, Kaz gave some tutorial on horizontal review tracker 2 years ago: https://www.w3.org/2020/Talks/0814-dashboards-ka/20200814-dashboards-ka.html p8)

<kaz> (see also: https://www.w3.org/PM/horizontal/)

<kaz> (that's why suggesting we look into to the procedure again)

mccool fills section 8, saying that UTF-8 is required

section 10 is filled also specifying that dateTime is used

section 11 is filled, and section 12 is not applicable

mccool creates a new issue for the UTF-8

<kaz> "JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32. " by https://tools.ietf.org/id/draft-ietf-json-rfc4627bis-09.html

<kaz> https://w3c.github.io/wot-thing-description/#dfn-thing-description says "TDs MUST be encoded using UTF-8 [RFC3629]."

this issue will require the discovery spec to specify that text, queries, etc. are always encoded as UTF-8

ISSUE: https://github.com/w3c/wot-discovery/issues/281

<kaz> FYI, document check area for TD: https://github.com/w3c/wot-thing-description/tree/main/publication/ver11/3-wd

<kaz> (to be checked by the Pubrules checker: https://www.w3.org/pubrules)

meeting is running out of time

mccool quickcly checks the PRs

quickly*

<kaz> [adjourend]