General information about the Web of Things can be found on https://www.w3.org/WoT/.
The WoT Use Case task force is responsible for collecting use cases for WoT and extracting requirements. Use cases can include both specific vertical applications and relevant technologies or other horizontal usage patterns. Guests who are not WoT members but who have an interest in specific vertical application domains, technologies, or usage patterns are explicitly invited to engage with this task force to provide input.
If you would like to participate please contact the TF lead [email protected].
Web conferences and agenda: https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf
All work on the Use Cases document is happening in this repository. It includes various use case proposals and a consolidated document based on those proposals.
Each commit here will sync it to the master, which will expose the content to http://w3c.github.io/wot-usecases/.
Please document new use cases in the USE-CASES directory adopting the template use-case-template.md (Markdown) or use-case-template.html (HTML). The HTML template is the preferred form.
Describe new requirements in the REQUIREMENTS directory using the template requirements-template.md (Markdown) or requirements-template.html (HTML). The HTML template is the preferred form.
Put all other contributions in the CONTRIBUTIONS directory using an open file format, e.g.text, markdown, html, svg.
To make direct changes to the IG document, please provide pull-requests to the html file, see github help.
- You can contribute even if you don't have access by forking this repository and doing a Pull Request from your fork.
- When you are doing a Pull Request, try to make little changes per Pull Request, which makes it easier to review.
In the virtual F2F members of the Architecture WG and Use Case WG assigned the following priorities to the use cases for the 1st round. The list shows the owners for each use case category and expected timeline for a requirement document.
| Category | business critical | business relevant | useful | not interested | Priority | Timeline for requirements document | Owner | Comments |
|---|---|---|---|---|---|---|---|---|
| Retail | 3 | 4 | 5 | 1 | 1 | 2-4 weeks | McCool (+ David ?) | Will be discussed in POC meeting. |
| Audio/Video | 2 | 5 | 6 | 0 | 1 | ? | NHK + Kaz (+Chris Needham?) | |
| Agriculture | 2 | 3 | 7 | 1 | 1 | 2 weeks (greenhouse) | Matsukura-san + Cristiano | Requirement for greenhouse horticulture exists |
| 4 week | ||||||||
| Smart City | 3 | 6 | 4 | 0 | 1 | 2-4 weeks | McCool + Jennifer | Will be discussed in POC meeting. |
| Health | 3 | 5 | 2 | 3 | 2 * | Need expertise - | ||
| Manufacturing | 4 | 5 | 3 | 1 | 1 | ? | Sebastian+Christian | |
| Multi Vendor System Integration | 2 | 9 | 1 | 1 | 1 | 4 weeks | Lagally | horizontal |
| Multimodal System Integration | 2 | 2 | 7 | 2 | 2 | 3-4 weeks | McCool + Kaz + Josh | horizontal |
| Accessibility | 3 | 2 | 6 | 2 | 1 | Josh | Horizontal | |
| Josh: Accessibility is underrepresented, this is a horizontal requirement cross other use cases. We should work together to support accessibility | ||||||||
| Automotive | 2 | 4 | 5 | 2 | 2 * | Kaz + (Urata-san?) | Regulated, Access might be interested, .e.g Urata-san | |
| Energy / Smart Grid | 3 | 6 | 3 | 1 | 1 | ? | Sebastian+Christian | regulated |
| Transportation | 3 | 3 | 6 | 1 | 2 * | ? | Zoltan ? | Use case is very high level |
| Need industry domain experience | ||||||||
| Smart Building | 4 | 6 | 2 | 1 | 1 | 3-4 weeks | Farshid+Sebastian | regulated |
| (+ Andrea) | ||||||||
| Shared Devices and Resources | 4 | 1 | 6 | 2 | 1 | 2 weeks | Ege (+ McCool) | Horizontal |
| Oauth2 Flows | 2 | 6 | 4 | 1 | 1 | 4 weeks | McCool | Horizontal: Technical Feature, not a use case --> Security TF to create a requirement doc |
| Device lifecycle | 3 | 4 | 4 | 3 | 1 | 2-4 weeks | Zoltan + Michael | Horizontal |