#818: Web of Things (WoT) Profile - Review Requested

Visit on Github.

Opened Feb 17, 2023

こんにちは TAG-さん!

I'm requesting a TAG review of Web of Things (WoT) Profiles.

The WoT Profile WoT Profile defines a Profiling Mechanism which restricts options and guides best practices to enable out-of-the-box interoperability when using Web of Things for greenfield devices. The current draft defines only profiles for HTTP. Out-of-the-box interoperability implies that devices can be integrated together into various application scenarios without deep level adaptations.

Further details:

  • I have reviewed the TAG's Web Platform Design Principles
  • Relevant time constraints or deadlines: Aiming for CR transition by 2023-03-30
  • The group where the work on this specification is currently being done: Web of Things (WoT) WG
  • The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue):
  • Major unresolved issues with or opposition to this specification: Expect async actions to still be at risk going into CR.
  • This work is being funded by:

You should also know that...

[please tell us anything you think is relevant to this review]

We'd prefer the TAG provide feedback as (please delete all but the desired option):

🐛 open issues in our GitHub repo for each point of feedback


CAREFULLY READ AND DELETE CONTENT BELOW THIS LINE BEFORE SUBMITTING

Please preview the issue and check that the links work before submitting.

In particular, if anything links to a URL which requires authentication (e.g. Google document), please make sure anyone with the link can access the document. We would prefer fully public documents though, since we work in the open.

¹ We require an explainer to give the relevant context for the spec review, even if the spec has some background information. For background, see our explanation of how to write a good explainer. We recommend the explainer to be in Markdown.

² A Security and Privacy questionnaire helps us understand potential security and privacy issues and mitigations for your design, and can save us asking redundant questions. See https://www.w3.org/TR/security-privacy-questionnaire/.

Discussions

2023-05-15

Minutes

Hadley: I see the need for a profile... It could aid adoption - this allows it to be more specific - doesn't have to do as much comfig.

Peter: there is the new "matter" solution for home automation that seems to be gaining traciton.

Dan: some iot vendors have been announcing support for this.. it's not on the web.

Peter: IP based..

https://en.wikipedia.org/wiki/Matter_(standard)

Peter: I think Matter is at a lower level - doesn't require http.. There should be an answer to how it plays with other standards...

Hadley: [leaves comment]

2023-05-22

Minutes

[Hadley: Regrets for this breakout, but we have asked them to join us for a call after 29 May and are awaiting a response.]

2023-07-10

Minutes

Amy: they will be working on it in the next draft charter. They also replied about Matter.

Dan: reached out to Michael via email

2023-07-mos-eisley

Minutes

Profiles no longer a priority but they'd like input for the next charter. Asked if it's useful for one of us to join their meeting at tpac

2023-10-09

Minutes

Amy: Did anyone meet with them at tpac? I completely forgot we said we'd do this, and didn't make it to any of their meetings. Can we punt this? It doesn't feel like a priority, although it's an opportunity to get ahead of the game for their next charter..

Dan: to my knowledge nobody talked to WoT people at TPAC...

Dan: considering how much we have on our plate right now I suggest we apologise and let them know we haven't been able to get to it but they should send us a review request during next charter period...

We're really sorry we didn't manage to arrange a time to meet with you at TPAC. We're going to close this for now, please could you file a new review request at a suitable time during your next charter period? We unfortunately don't have time for an early review of this at the moment, but will do our best to get back to you if we clear our backlog before we hear from you next.