Re: Call for Use Cases & Requirements for WoT Profiles 2.0

Dear WoT Working Group,

Just a heads up that in the Profiles call tomorrow we will review the 6
open PRs
<https://github.com/w3c/wot-profile/pulls?q=is%3Apr+is%3Aopen+draft%3Afalse>
and try to decide which initial set of requirements will go into the first
draft of the WoT Profiles 2.0 Use Cases & Requirements document. You can
find the agenda on the wiki here
<https://www.w3.org/WoT/IG/wiki/WG_WoT_Profile_WebConf#Profiles_-_2025-10-15>
.

Please check the WoT Working Group calendar
<https://www.w3.org/groups/wg/wot/calendar/> for the latest event
information and joining instructions as we are hoping to get a new working
Zoom link for tomorrow (if you subscribe to the calendar in a calendar
application it may take a while to synchronise).

Kind regards

Ben

On Thu, 9 Oct 2025 at 17:40, Ben Francis <ben@krellian.com> wrote:

> Hi,
>
> Thank you everyone for the input so far on Use Cases & Requirements for
> WoT Profiles 2.0.
>
> Just a heads up that there are now 6 open PRs
> <https://github.com/w3c/wot-profile/pulls?q=is%3Apr+is%3Aopen+draft%3Afalse>
> ready for review which propose an initial set of use cases & requirements
> for the Use Cases & Requirements document, based on issues filed
> <https://github.com/w3c/wot-profile/issues?q=is%3Aissue%20state%3Aopen%20label%3Arequirement%2C%22use%20case%22%20label%3AProfile-2.0>
> and feedback received so far, plus some proposed introductory text.
>
> It would be great to get your review on these PRs so that we can determine
> which requirements have broad consensus and which still require further
> discussion.
>
> Also, if you think of other use cases & requirements that aren't yet
> covered then please do file an issue
> <https://github.com/w3c/wot-profile/issues> using the "Use Case" and
> "Requirement" issue templates.
>
> I'm aiming to get an initial Draft Note put together by 29th October,
> which is when I need to file the final report for my fellowship.
> Requirements that come in after that date will not make it into that first
> draft.
>
> My intention is certainly to continue to refine this document in the
> following months in order to eventually publish a final Group Note, but I
> won't have dedicated time to work on it after that date.
>
> Kind regards
>
> Ben
>
> On Thu, 2 Oct 2025 at 13:27, Ben Francis <ben@krellian.com> wrote:
>
>> 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
>>
>