W3C

– DRAFT –
WoT Profile

05 April 2023

Attendees

Present
Ege_Korkan, Kaz_Ashimura, Luca_Barbato, Michael_Lagally, Michael_McCool, Ryuichi_Matsukura, Tomoaki_Mizushima
Regrets
-
Chair
Lagally
Scribe
luca_barbato

Meeting minutes

Past Minutes Review

<kaz> Mar-22

Lagally: Consensus?
… published

<kaz> (approved)

Open Issues

#302

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

The issue can be closed

#299

<kaz> Issue 299 - Contradiction with the Arch spec on protocol bindings

Ege: We discussed about it, we need to add something to the profile spec
… a PR is open for it.

#223

<kaz> Issue 223 - Example 46 is not about subscribeallevents

Ege: The example 48 should address it

Lagally: Closed

#213

<kaz> Issue 213 - Wrong place to use HTTP Baseline Profile

Lagally: The linked PR is already a significant improvement

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

Ege: Michael's last review is pending

Lagally: Is everybody happy with merging this PR ?

McCool: Let's merge it

McCool: Merged and Issue closed

#171

<kaz> Issue 171 - Identification of profiles

Lagally: Outdated and to be closed

#299

<kaz> Issue 299 - Contradiction with the Arch spec on protocol bindings

Kaz: I agree with Ben's position
… we need to refactor all the specifications, and we'll do that in the new charter

<mlagally> s/cannot//

Ege: The pr linked is fixing a different problem

#349

<kaz> Issue 349 - Are all TD 1.1 assertions valid in all profiles?

<kaz> related PR 368 - Add TD assertion conformance

Lagally: I support going with that PR

<consensus&PR368 merged>

<kaz> <Issue 349 also closed>

<kaz> security issues

#313

<kaz> Issue 313 - Include the "auto" security scheme to the list of supported schemes

McCool: We'll discuss them in the wot-security

McCool: but it conflicts with the work on wot-discovery that has higher priority

McCool: All the issues are all related and might be addressed in a single PR.

#348

<mlagally> Issue 348 - Create sub-assertions for Keywords in the Links section

McCool: it is related to formatting assertions
… the security issues have priority

McCool: I'll ask to opensource the generator script

Lagally: We'll wait for a response on the request

Lagally: Please expand the information on the issue so other may help

Kaz: is 348 part of the security issues?

Lagally: 348 is not related to security, but needs mm contribution

Kaz: <clarification on the topic at hand>

<kaz> (just removed "Security-labeled issues" from the topic within the minutes)

McCool: Help wanted on addressing the P1 issues still open

New pull requests

#382

<kaz> PR 382 - Draft: initial draft of webhook properties section

Lagally: It is a draft, ege already started reviewing it
… it contains a proposal for the an observe mechanism for properties

Luca: Better to use POST for both subscription and unsubscription

<kaz> preview - 8.4.1.4 unobserveallproperties

Ege: Make sure the refer to properties instead of event

Ege: DELETE would need a identifer for the matching observe

<Ege> see https://stackoverflow.com/questions/299628/is-an-entity-body-allowed-for-an-http-delete-request

McCool: I'll do another iteration

<kaz> [Kaz notes we're out of time and suggests continue the discussion next time]

<kaz> [adjourned]

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