W3C

– DRAFT –
WoT Use Cases

23 July 2025

Attendees

Present
Ege_Korkan, Michael_McCool, Tomoaki_Mizushima
Regrets
-
Chair
-
Scribe
EgeKorkan

Meeting minutes

Minutes

https://www.w3.org/2025/07/16-wot-uc-minutes.html

McCool: any issues other than typo?

Recap

McCool: we reorganized the intro section
… added definitions etc.
… we need to work on stakeholders
… also formatting to use dfn tags

Mizushima: there are comments by tallted

McCool: let's look at it

Mizushima: PR 371 it is
… one is a typo, the other one I don't get

McCool: we can work on the use case definition

Ege: user story word comes from agile development but just the word

McCool: requirement and user story overlap

Ege: yeah requirement is the feature of the user story sentence

Ege: I would say that the second sentence of use case definition is wrong
… use cases are high level, so they cannot identify gaps

McCool: (edits the definition)

<McCool> https://github.com/w3c/wot-usecases/pull/372

PR 372

McCool: This does a lot of the work around this
… I was careful on authorization and authentication

Ege: these are not feature requests in my opinion

McCool: these are assertions though. For example for rate limiting in the discovery spec.

Ege: these create higher quality standards but not features

McCool: an assertion is a feature though

McCool: (writes the discussion in github comment)

Minutes manually created (not a transcript), formatted by scribe.perl version 196 (Thu Oct 27 17:06:44 2022 UTC).