W3C

– DRAFT –
WoT Profile

22 March 2023

Attendees

Present
Ege_Korkan, Kaz_Ashimura, Luca_Barbato, Michael_Lagally, Tomoaki_Mizushima
Regrets
McCool
Chair
Lagally
Scribe
kaz

Meeting minutes

Minutes

Mar-8

Lagally: (goes through the minutes)

approved

Wide reviews

<mlagally> w3c/wot-profile#358

Issue 358 - Wide review

Lagally: got responses from wide review groups

I18n

i18n-activity issue 1664 - [WoT Profile] Unclear character set constraints and non-UTF-8 html

Kaz: any questions about the response?

Lagally: so far the response is clear enough
… why don't we invite them to the Profile call next Thursday?
… how to invite them?

Kaz: you as the Profile TF moderator can send an invitation message to them (Addison an Atsushi) CCing team-wot (including McCool, Sebastian and Kaz)

Lagally: OK. will do

wot-profile issue 373 - Mismatch with MUST clause and examples in default language section

Lagally: kind of long discussion bout default language section
… should update the example

<mlagally> w3c/wot-profile#373

Kaz: so you want to talk about their issue 1664 and our issue 373 next Thursday. Right?

Lagally: yeah

Privacy

<mlagally> PING issue 115 - Web of Things (WoT) Profile 2023-02-16 > 2023-03-20

Lagally: wait until they file a new issue on wot-profile based on this review
… would be a good idea to invite them too

A11y

A11y issue 54 - Web of Things (WoT) Profile 2023-02-16 > 2023-03-20

Kaz: still waiting for the response. Right?

Lagally: right
… we're waiting for Security and TAG as well

Security issue

TAG issue

Issues

Issues to be closed

Issue 34

Issue 34 - Extension vocabulary for protocols

Lagally: can be closed

(closed)

Issue 213

Issue 213 - Wrong place to use HTTP Baseline Profile

Ege: thought there was a related PR

Lagally: ok
… let's close this after handling that

Kaz: Ege, do you have the number of the URL of the related PR handy?

<Ege> PR 297 - Revised Abstract and Introduction - fixes #115

Ege: PR 297 as above

Issue 299

Issue 299 - Contradiction with the Arch spec on protocol bindings

Lagally: what is the actual problem here?

Ege: the problem is clear
… Architecture spec says:

Protocol Bindings MUST be serialized as hypermedia controls to be
self-descriptive on how to activate the Interaction Affordance.

Ege: On the other hand, Profile also defines protocol binding
… should make sure the Protocol Binding part
… also all the examples should have complete description of the forms tag

Lagally: what is need then?
… we need to have concrete examples
… you can create your own examples
… (adds comments to the Issue 299)
… need more discussion and a concrete proposal

Ege: note that Lagally's example for the Testfest didn't have problem

Lagally's example TD for the Testfest

Lagally: should remove the normative language from the Architecture spec
… then add language to require "complete forms"

Kaz: which document?

Lagally: requirements for "complete forms" to be included in the Profile spec

Issue 302 - Clarify the payload formats of read/write property

Issue 302

Lagally: let's keep this open

Contributions

PR 374

PR 374 - Define values of in and name for basic security scheme

Lagally: (goes through the changes and comments)
… I'm OK with this PR

Kaz: +1

(merged)

PR 334

PR 334 - WIP: Provide example in the new introduction section

Lagally: marked as "WIP"
… would like to get feedback from Sebastian
… Ege, can you ping him?

Ege: ok

PR 368

<mlagally__> PR 368 - Add TD assertion conformance

Lagally: myself was thinking about simple editorial changes
… but second point need further discussion
… Ben was raising comments

Ben's comments

Ege: would require big changes, so would suggest we add exceptions

Lagally: wondering about Ben's 2nd point

One slight subtlety here is that in the HTTP SSE Profile we assume the
text/event-stream response type from the subprotocol member of the Form
being set to sse. Given this is fixed in the SSE specification, I think
that's a reasonable assumption.

Lagally: If we work on the exception, we should look into the spec carefully
… and see if there is anything else missing

Kaz: we should add necessary clarification for the Profile spec
… but should think about the detailed analysis on the relationship among related specs separately (if possible)

PR 297

PR 297 - Revised Abstract and Introduction - fixes #115

Lagally: let's revisit this next time

AOB

Profile 1.0 issues

Lagally: please review the remaining issues around Profile 1.0 too

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).