WG WoT Profile WebConf
The WoT Profile task force is responsible for interoperability profiles for the Web of Things.
WebConf Information
- #wot-profile IRC channel used for taking minutes and asking questions
- Quick start guide for W3C teleconferences
- Table of all the WoT calls on our Web page
- W3C WG Calendar - Please use this for schedule and call-in logistics.
- Scripting APIs | Security | Discovery | Marketing | Use Cases | PlugFest/Testing | TD | Architecture | Profile
This is a call of the WoT Working Group (WG).
Normative Deliverable
WoT Profiles
"The WoT Profiles specification defines a Profiling Mechanism and a set of Profiles which enable out-of-the-box interoperability between Web Things and their Consumers on the Web of Things.
Being out-of-the-box interoperable means that any Consumer which conforms with a given Profile can interact with any Thing which conforms with the same profile, without additional customization.
A Profile is a technical specification which provides a set of assertions to which conformant Consumers and Things must conform.
The Profiling Mechanism provides a means to denote that a given Thing conforms to one or more Profiles, by referring to the identifiers of those Profiles in the profile member of its Thing Description."
-- WoT Profiles Editor's Draft
People
- Co-moderator: Luca Barbato (Luminem SRLs)
- Co-moderator: Ben Francis (Krellian)
WoT Profile Co-Editors:
- Michael Lagally (Oracle Corp.)
- Ben Francis (Krellian)
- Michael McCool (Intel Corp.)
- Ryuichi Matsukura (Fujitsu Ltd.)
- Sebastian Kaebisch (Siemens AG)
- Tomoaki Mizushima (Internet Research Institute, Inc.)
Agenda
Profiles - 2025-07-09
- Scribe:
- Past scribes: Kazuyuki Ashimura, Michael Koster, Ege, Sebastian, JKRhb, Daniel, Michael Lagally
Review minutes from the last meeting
https://www.w3.org/2025/06/25-wot-profile-minutes.html
Review PRs
Ready for review:
Assign 1.0 issues needing a PR
Re-work HTTP Webhook Profile sectionNew section on Webhook message formatNormative text needs to be outside of examplesIssues with recent webhook subscription mechanism changesReview of HTTP Webhook ProfileRefine example Thing DescriptionStructure of section 8.4 HTTP Webhook Profile Protocol Binding is brokenMultiple subscriptions from the same consumer to the same endpoint?
- CREATE PR to remove accessibility assertions
- CREATE PR to fix conflicting security assertions
- CREATE PR to remove the Default Language section of the Profile specification
- CREATE PR to Clarify the behavior when a response does not have body
- CREATE PR to soften assertions in Privacy Considerations and Security Considerations sections
Re-work links section- CREATE PR with a Note to warn Consumers that Things may not necessarily be compliant just because they say they are
- Make it clearer that Profiles should only progressively enhance a Thing
- Assert that profiles should not diverge from binding template defaults
Discuss 1.0 issues that need discussion
- #347 Clarify OAuth schemes - consider requiring Bearer tokens only
- #313 Include the "auto" security scheme to the list of supported schemes
Profiles - 2025-06-25
- Scribe: Kaz
- Past scribes: Michael Koster, Ege, Sebastian, JKRhb, Kazuyuki Ashimura, Daniel, Michael Lagally
Review minutes from the last meeting
https://www.w3.org/2025/05/28-wot-profile-minutes.html
Review PRs
- PRs
- Ready for review:
- Work in Progress:
- https://github.com/w3c/wot-profile/pull/314 (Michael McCool)
- https://github.com/w3c/wot-profile/pull/334 (Sebastian)
- https://github.com/w3c/wot-profile/pull/417 (Ben, re-visit later)
Triage 1.0 issues proposed for closing
Triage 1.0 issues proposed to defer to 2.0
Assign issues needing a PR
- Re-work HTTP Webhook Profile section
- New section on Webhook message format
- Normative text needs to be outside of examples
- Issues with recent webhook subscription mechanism changes
- Review of HTTP Webhook Profile
- Refine example Thing Description
- Structure of section 8.4 HTTP Webhook Profile Protocol Binding is broken
- Multiple subscriptions from the same consumer to the same endpoint?
- CREATE PR to remove accessibility assertions
- CREATE PR to fix conflicting security assertions
- CREATE PR to remove the Default Language section of the Profile specification
- CREATE PR to Clarify the behavior when a response does not have body
- CREATE PR to soften assertions in Privacy Considerations and Security Considerations sections
- Re-work links section
- CREATE PR with a Note to warn Consumers that Things may not necessarily be compliant just because they say they are
- Make it clearer that Profiles should only progressively enhance a Thing
- Assert that profiles should not diverge from binding template defaults
Triage remaining 1.0 issues
Profiles - May 28th, 2025
- Scribe:
- Past scribes: Ege, Sebastian, JKRhb, Kazuyuki Ashimura, Daniel, Michael Lagally
Past Minutes
https://www.w3.org/2025/05/14-wot-profile-minutes.html
PRs
https://github.com/w3c/wot-profile/pulls
1.0 Issue Triage
Questions for each issue:
- Should this still block 1.0 if published as a Working Group Note?
- Who is responsible for next steps?
Action Items
Over the next two weeks:
- Continue to review existing issues to identify any that should block publication as a Note and ensure they are assigned to someone
- Encourage a full review of the current Profiles specification to identify any other issues which should block publication as a Note
- Start to work on Profile-1.0 issues as assigned
Future Meetings
- Next meeting two weeks from now (11th June)
- Meetings every two weeks
(In the meantime, see you on GitHub and Discord)
Profiles - May 14th, 2025
- Scribe: Ege
- Past scribes: Sebastian, JKRhb, Kazuyuki Ashimura, Daniel, Ege, Michael Lagally
Past Minutes
https://www.w3.org/2025/05/07-wot-profile-minutes.html
Working Group Note Resolution
Resolution from last time:
"The WoT Profiles Task Force will aim to publish WoT Profiles 1.0 as a Working Group Note by July 2025 and write Use Cases & Requirements for WoT Profiles 2.0 by October 2025."
https://lists.w3.org/Archives/Public/public-wot-wg/2025May/0012.html
W3C Working Group Note Publication Process
Summary:
- A Group Note (NOTE) is published to provide a stable reference for a useful document that is not intended to be a formal standard.
- There are few formal requirements to publish a document as a Note or Draft Note, and they have no standing as a recommendation of W3C but are simply documents preserved for historical reference.
- The group:
- MUST record their decision to request publication as a Note or Draft Note, and
- SHOULD publish documentation of significant changes to the technical report since any previous publication.
Question:
- Should we publish a Draft Note before publishing a Note (by July), or is the last Working Draft sufficient?
1.0 Issue Triage
Questions for each issue:
- Should this still block 1.0 if published as a Working Group Note?
- Who is responsible for next steps?
Action Items
Over the next two weeks:
- Continue to review existing issues to identify any that should block publication as a Note and ensure they are assigned to someone
- Encourage a full review of the current Profiles specification to identify any other issues which should block publication as a Note
- Start to work on Profile-1.0 issues as assigned
Future Meetings
- Next meeting two weeks from now (28th May)
- Meetings every two weeks
(In the meantime, see you on GitHub and Discord)
Profiles - May 7th, 2025
- Scribe: Sebastian
- Past scribes: JKRhb, Kazuyuki Ashimura, Daniel, Ege, Michael Lagally
Past Minutes
WoT Profiles 2025 Planning
- Definition of a Profile
- Question
- Profiles 1.0
- Issues with WoT Profiles 1.0
- Profiles 2.0 Strawman Proposal
- Persevere or Pivot?
- Proposed resolution
- Next steps
- Collaborations
Question
Should we:
- Continue to pursue the existing WoT Profiles 1.0 specification along the recommendation track
OR
- Publish WoT Profiles 1.0 as a non-normative Working Group Note and start to work on use cases & requirements for WoT Profiles 2.0 instead?
Profile - Oct 9th, 2024
- Scribe:
- Past scribes: Kazuyuki Ashimura, Daniel, Ege, Michael Lagally
Past minutes
Profiles philosophy
- Protocol Bindings extend the Thing Description, Profiles restrict/constrain it.
Use Case Task Force requests
- Which are the Use Cases for profiles?
Profile - Sep 11th, 2024
- Scribe: Kazuyuki Ashimura
- Past scribes: Daniel, Kazuyuki Ashimura, Ege, Michael Lagally
Past minutes
Profiles as Ecosystem descriptors
- Continue the last meeting discussion
- Profiles were mainly focused on Greenfield implementations, but they have an importance for Brownfield as well.
- An Ecosystem covers more than what a single binding protocol does
- It could include provisions for Discovery, Onboarding, Data Representation
Use Case Task Force requests
- The UC TF asks to use the new form to model our Use Cases
Profile - Jul 31th, 2024
- Scribe: Daniel
- Past scribes: Kazuyuki Ashimura, Ege, Michael Lagally
Past minutes
Profiles as Ecosystem descriptors
- Profiles were mainly focused on Greenfield implementations, but they have an importance for Brownfield as well.
- An Ecosystem covers more than what a single binding protocol does
- It could include provisions for Discovery, Onboarding, Data Representation
PRs
- https://github.com/w3c/wot-profile/pull/417 - A start on use cases and requirements for Profiles 2.0
Profile - Jul 17th, 2024
- Scribe:
- Past scribes: Kazuyuki Ashimura, Ege, Michael Lagally
Profiles as Ecosystem descriptors
- Profiles were mainly focused on Greenfield implementations, but they have an importance for Brownfield as well.
- An Ecosystem covers more than what a single binding protocol does
- It could include provisions for Discovery, Onboarding, Data Representation
out-of-the-box explanation
- Discussion on what can be made clearer
Profile - Jul 2nd, 2024
Cancelled
Profile - Jun 18th, 2024
Cancelled
- Scribe:
- Past scribes: Kazuyuki Ashimura, Ege, Michael Lagally
Past minutes review
out-of-the-box explanation
- Discussion on what can be made clearer.
Profile 1.0 pressing issues
Profile - Jun 11th, 2024
- Scribe: Kazuyuki Ashimura
- Past scribes: Kazuyuki Ashimura, Ege, Michael Lagally
Past minutes review
Project management
- Update Ben's role on github to match his Editor status
- Try to reach the current people listed as Editor.
- Decide on a timeout/deadline to update the list.
Explainer refresh
Profile 1.0 pressing issues
- https://github.com/w3c/wot-profile/issues/402
- https://github.com/w3c/wot-profile/issues/403
- https://github.com/w3c/wot-profile/issues/404
Profile - Jun 4th, 2024
- Scribe: Kazuyuki Ashimura
- Past scribes: Kazuyuki Ashimura, Ege, Michael Lagally
Past minutes review
Explainer refresh
Profile 1.0 pressing issues
- https://github.com/w3c/wot-profile/issues/402
- https://github.com/w3c/wot-profile/issues/403
- https://github.com/w3c/wot-profile/issues/404
Profile - May 28th, 2024
- Scribe: Kazuyuki Ashimura
- Past scribes: Kazuyuki Ashimura, Ege, Michael Lagally
Past minutes review
Asyncronous contribution
- Policy regarding PRs
- Mailing list threads
Pending pull requests
Profile 1.0 pressing issues
- https://github.com/w3c/wot-profile/issues/402
- https://github.com/w3c/wot-profile/issues/403
- https://github.com/w3c/wot-profile/issues/404
Profile - May 21st, 2024
- Scribe: N/A
- Past scribes: Kazuyuki Ashimura, Ege, Michael Lagally
No topics due low attendance
Profile - May 14th, 2024
- Scribe: Kazuyuki Ashimura
- Past scribes: Kazuyuki Ashimura, Ege, Michael Lagally
Housekeeping (5 min)
Approval of the minutes of the previous call.
No other topics due low attendance
Profile - May 7th, 2024
- Scribe: Kazuyuki Ashimura
- Past scribes: Kazuyuki Ashimura, Ege, Michael Lagally
Housekeeping (5 min)
Approval of the minutes of the previous call.
Quick Pull Requests (1 min)
Profile 1.0 pressing issues
As part of the past weeks email exchange
- https://github.com/w3c/wot-profile/issues/402
- https://github.com/w3c/wot-profile/issues/403
- https://github.com/w3c/wot-profile/issues/404
Profile - Apr 23rd, 2024
- Scribe: Ege
- Past scribes: Ege, Michael Lagally, Kazuyuki Ashimura
Housekeeping (5 min)
Approval of the minutes of the previous call.
Asynchronous Actions out of the profile
- Shall we remove the asynchronous action from profiles and defer to TD work on the topic?
- Do we have consensus on publishing as REC or NOTE with that part removed?
Profiles with Ontologies
- Do we have consensus in express a profile as a fixed set of vocabulary terms from well defined ontologies?
Profile - Apr 9nd, 2024
- Cancelled
Profile - Apr 2nd, 2024
Misc
- Scribe: Ege
- Past scribes: Michael Lagally, Kazuyuki Ashimura
Housekeeping (5 min)
Approval of the minutes of the previous call.
Actions in Profile
- https://github.com/w3c/wot-profile/issues/369
- We should come with an agreement in the Main Call regarding TD under-specify action.
Pending Profile 1.0
- Pending Profile-1.0 issues
- Pending PRs
Higher priority issues
Profile - Mar 26th, 2024
cancelled
Profile - Mar 19th, 2024
Misc
- Scribe: Michael Lagally / Kazuyuki Ashimura
Housekeeping (5 min)
Approval of the minutes of the previous call.
Retrospective
- Were are we? - Michael Lagally
- Profile 1.0 remaining work - Michael Lagally
Pending Profile 1.0
- Pending Profile-1.0 issues
- Pending PRs
Higher priority issues
Planning
- Charter document deadlines
- Expected CR Transition: Q2 2024
- Expected PR Transition: Q3 2024
- Expected REC Transition: Q4 2024