- From: Ben Francis <ben@krellian.com>
- Date: Thu, 2 Oct 2025 13:27:28 +0100
- To: member-wot-wg@w3.org, member-wot-ig <member-wot-ig@w3.org>, public-web-of-things@w3.org
- Cc: Public Web of Things WG <public-wot-wg@w3.org>, public-wot-ig <public-wot-ig@w3.org>
- Message-ID: <CAMpSprkF-Ti=dHLiciJUwhcD4fHSppeW0m0--GKB8g4YE5w67Q@mail.gmail.com>
Dear WoT Working Group, Interest Group and Community Group members, The Profiles task force of the WoT Working Group are now collecting use cases & requirements for WoT Profiles 2.0, with a view to writing a first draft of a Use Cases & Requirements document by the end of this month (31st October), which can then be refined over the following months. As a reminder, the current definition of a Profile in WoT Profiles 1.0 <https://w3c.github.io/wot-profile> is "A technical specification which provides a set of assertions such that any Consumer which conforms with the those assertions is out-of-the-box interoperable with any Thing which also conforms with those assertions." We hope to refine this definition for Profiles 2.0, and take a more structured approach <https://github.com/w3c/wot-profile/issues/285> to defining what Profiles can and can't constrain. In order to propose a use case or requirement, please navigate to https://github.com/w3c/wot-profile/issues and click "New issue", then choose either "Use Case" or "Requirement". *Use Cases* Use cases should take the form of a user story... *As a [type of user] I want to [goal] so that [reason]* A use case is a concrete use that you have for Profiles as a developer or end user of the Web of Things, which may be specific to a particular application domain. You may want to add additional context or background information underneath the structured user story sentence to explain why the use case is important to you and what considerations need to be taken into account. *Requirement* Requirements should take the form... The specification shall/shall not... (if the requirement applies to the WoT Profiles specification itself) or Profiles shall/shall not... (if the requirement applies to individual Profiles) Requirements are specific and testable technical requirements you think the Profile specification should fulfil, or you think should be explicitly out of scope. Requirements should be derived from use cases. --- To kick off the process I have filed issues <https://github.com/w3c/wot-profile/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22use%20case%22%2C%22requirement%22%20author%3Abenfrancis> for an initial set of proposed use cases & requirements <https://github.com/w3c/wot-profile/pull/417> based on my own implementation experience, business needs, strawman proposal <https://lists.w3.org/Archives/Public/public-wot-wg/2024Feb/0000.html> for Profiles 2.0, and the task force discussion so far. However, it is very important that we hear from a diverse set of stakeholders from a range of different application domains in order to make the WoT Profiles 2.0 specification as widely useful as it can be. Thank you in advance for your contributions! Kind regards Ben -- Ben Francis Co-moderator, Profiles Task Force Web of Things Working Group
Received on Thursday, 2 October 2025 12:27:45 UTC