The structure/category of the use case description

[chachamimm]

@k-toumura wrote a comment :

---

How about classifying the use cases as follows and discussing them with different templates in different session or task forces?

1. Use cases to guide what should be standardized:
   • Including specific user stories: these should allow us to understand situation where TD is used, what to describe in it, etc.
   • It enables us to identify functions that are currently lacking in TD, discovery, etc. (= gap analysis)
2. Use cases to explain the applicability of WoT:
   • Clearly explain the benefit of using WoT to those outside the WoT WG, Chapter 4 and 5 of the current Architecture document may correspond to this. (the architecture TF might be a suitable candidate to collect and discuss them)
3. Case studies from implementing IoT solution using WoT:
   • Introduce the experiences of using WoT in specific projects. (the marketing TF or CG might be suitable to collect and discuss them)

---

Please also see "Issues - 257 [Discuss] Focus on Functional Requirements"

We decided to consider this comment separately from Issues #257 at the UC Call on February 7th. So I create a new issue.

If you have opinions and comments, please write comments here.

[egekorkan]

As commented already in #257, I agree with this direction.