|
| 1 | +## Notes on the items within the Use Case Proposal Template |
| 2 | + |
| 3 | +### Submitter |
| 4 | + |
| 5 | +Put your name here. |
| 6 | + |
| 7 | +### Motivation |
| 8 | + |
| 9 | +Provide a description of the problem that is solved by the use case. Include some reason(s) why this use case is important for the users. |
| 10 | + |
| 11 | +### Description |
| 12 | + |
| 13 | +Provide a description from the user's perspective. |
| 14 | + |
| 15 | +### Expectations for stakeholders and environments |
| 16 | + |
| 17 | +#### Target Users |
| 18 | + |
| 19 | +List all stakeholders that are involved in the use case from the following list: |
| 20 | +- device owner |
| 21 | +- device user |
| 22 | +- cloud provider |
| 23 | +- service provider |
| 24 | +- device manufacturer |
| 25 | +- gateway manufacturer |
| 26 | +- network operator (potentially transparent for WoT use cases) |
| 27 | +- identity provider |
| 28 | +- directory service operator |
| 29 | + |
| 30 | +#### Expected Devices |
| 31 | + |
| 32 | +List the target device(s), e.g., a sensor, a solar panel, an air conditioner. |
| 33 | + |
| 34 | +#### Expected Data |
| 35 | + |
| 36 | +List the type(s) of expected data, e.g., weather and climate data, medical data, machine sensor data, vehicle data. |
| 37 | + |
| 38 | +### Relationships with existing resources and standards |
| 39 | + |
| 40 | +#### Dependencies on WoT- Affected WoT deliverables and/or work items |
| 41 | + |
| 42 | +List any WoT deliverables that will have to be changed to enable this use case. |
| 43 | + |
| 44 | + |
| 45 | +#### Existing standards from other WGs within W3C |
| 46 | + |
| 47 | +Provide links to standards that are relevant to this use case. |
| 48 | + |
| 49 | +#### Existing standards outside W3C |
| 50 | + |
| 51 | +Provide links to standards that are relevant to this use case. |
| 52 | + |
| 53 | +### Clarifications of user's needs (optional, but to be described as specifically as possible, so that precise requirements can be extracted later) |
| 54 | + |
| 55 | +#### Security Considerations |
| 56 | + |
| 57 | +* Describe any issues related to security; if there are none, say "none" and justify. |
| 58 | +* As a guide, see the security part of [security and privacy review](https://github.com/w3c/wot-architecture/blob/main/publication/ver11/security_and_privacy.md). |
| 59 | + |
| 60 | +#### Privacy Considerations |
| 61 | + |
| 62 | +* Describe any issues related to privacy; if there are none, say "none" and justify. |
| 63 | +* As a guide, see the privacy part of [security and privacy review](https://github.com/w3c/wot-architecture/blob/main/publication/ver11/security_and_privacy.md). |
| 64 | + |
| 65 | +#### Accessibility Considerations |
| 66 | + |
| 67 | +* Describe any issues related to accessibility; if there are none, say "none" and justify. |
| 68 | +* As a guide, see [accessibility review](https://github.com/w3c/wot-architecture/blob/main/publication/ver11/accessibility.md). |
| 69 | + |
| 70 | +#### Internationalization (i18n) Considerations |
| 71 | + |
| 72 | +* Describe any issues related to internationalization; if there are none, say "none" and justify. |
| 73 | +* As a guide, see [internationalization review](https://github.com/w3c/wot-architecture/blob/main/publication/ver11/internationalization.md). |
| 74 | + |
| 75 | +### Gaps between the user's need and what's possible today |
| 76 | + |
| 77 | +Describe any gaps that are not addressed by the current WoT standards and building blocks. |
| 78 | + |
| 79 | +## Terminology |
| 80 | + |
| 81 | +We use common terminology across the use cases to make sure |
| 82 | +everybody has the same understanding and the descriptions will match |
| 83 | +when we combine the use cases into a single document. |
| 84 | + |
| 85 | +Please avoid domain-specific terminology, e.g., don't use "MNO" or "telco"; better to use "network operator" or "telephone company" instead. |
| 86 | + |
| 87 | +### Stakeholders and actors |
| 88 | + |
| 89 | +- device owner |
| 90 | +- device user |
| 91 | +- cloud provider |
| 92 | +- service provider |
| 93 | +- device manufacturer |
| 94 | +- gateway manufacturer |
| 95 | +- network operator (potentially transparent for WoT use cases) |
| 96 | +- identity provider |
| 97 | +- directory service operator |
| 98 | + |
| 99 | +### Categories and Domains |
| 100 | + |
| 101 | +#### Retail |
| 102 | +Integrating and interconnecting multiple devices into the common retail workflow. |
| 103 | +[Retail.md](retail.md) |
| 104 | + |
| 105 | +#### Audio/Video |
| 106 | +[Media Use Case Information Bucket](media-information-references.md) |
| 107 | + |
| 108 | +Synchronise Home WoT devices with TV program |
| 109 | +[nhk-device-tv-sync.md](nhk-device-tv-sync.md) |
| 110 | + |
| 111 | +#### Agriculture |
| 112 | +Smart Agriculture (Greenhouse Horticulture) to create an optimal environment for growing plants. |
| 113 | +[smart-agriculture.md](smart-agriculture.md) |
| 114 | + |
| 115 | +#### Smart City |
| 116 | +Managing mobile devices and sensors in a Smart City. |
| 117 | +[smartcity-geolocation.md](smartcity-geolocation.md) |
| 118 | + |
| 119 | +Interactive Public Spaces |
| 120 | +[mmi-3-1_interactive-public-spaces.md](mmi-3-1_interactive-public-spaces.md) |
| 121 | + |
| 122 | +Meeting Room Event Assistance |
| 123 | +[mmi-3-2_meeting-room-event-assistance.md](mmi-3-2_meeting-room-event-assistance.md) |
| 124 | + |
| 125 | +#### Health |
| 126 | +##### Public Health |
| 127 | +Monitor the health of people in public places to |
| 128 | +control the spread of infectious diseases. |
| 129 | +[smartcity-health-monitoring.md](smartcity-health-monitoring.md) |
| 130 | + |
| 131 | +Connected devices in ICUs (Intensive Care Units). |
| 132 | +[MedicalDevices.md](MedicalDevices.md) |
| 133 | + |
| 134 | +##### Private Health |
| 135 | +Health Notifiers. |
| 136 | +[mmi-4-1_health-notifiers.md](mmi-4-1_health-notifiers.md) |
| 137 | + |
| 138 | +#### Manufacturing |
| 139 | +Monitoring production lines and plants and predicting and preventing fault conditions. |
| 140 | + |
| 141 | +Industry 4.0 scenarios which include innteractions to OPC UA endpoints. [use-case-opc-ua-binding.md](use-case-opc-ua-binding.md) |
| 142 | + |
| 143 | +#### Multi-Vendor System Integration |
| 144 | +Out of the box interoperability of devices. |
| 145 | +[wot-profile.md](wot-profile.md) |
| 146 | + |
| 147 | +Digital twin to analyze and troubleshoot physical assets in real time, predict future problems, minimize downtime, and perform simulations. |
| 148 | +[digital-twin.md](digital-twin.md) |
| 149 | + |
| 150 | +Multi vendor and protocol interoperability by communicating across different protocols. |
| 151 | +[X-Protocol-Interworking.md](X-Protocol-Interworking.md) |
| 152 | + |
| 153 | +#### Multimodal System Integration |
| 154 | +Multimodal Recognition Support. |
| 155 | +[mmi-5-1_multimodal-recognition-support.md](mmi-5-1_multimodal-recognition-support.md) |
| 156 | + |
| 157 | +Synergistic Interactions |
| 158 | +[mmi-5-2_enhancement-of-synergistic-interactions.md](mmi-5-2_enhancement-of-synergistic-interactions.md) |
| 159 | + |
| 160 | +#### Accessibility |
| 161 | +Audiovisual Devices Acting as Smartphone Extensions |
| 162 | +[mmi-1-1_audiovisual-devices-as-smartphone-extensions.md](mmi-1-1_audiovisual-devices-as-smartphone-extensions.md) |
| 163 | + |
| 164 | +Unified Smart Home Control and Status |
| 165 | +[mmi-1-2_unified-smart-home-control-and-status.md](mmi-1-2_unified-smart-home-control-and-status.md) |
| 166 | + |
| 167 | +#### Automotive |
| 168 | +Smart Car Configuration Management |
| 169 | +[mmi-2-1_smart-car-configuration-management.md](mmi-2-1_smart-car-configuration-management.md) |
| 170 | + |
| 171 | +#### Energy / Smart Grids |
| 172 | +Integrate all players in the electricity market into one overall system through the interaction of generation, storage, grid management and consumption. |
| 173 | +[smart-grid.md](smart-grid.md) |
| 174 | + |
| 175 | +#### Transportation |
| 176 | +Fleet management, public transport, managing shipping, air cargo, train cargo, last mile transportation. |
| 177 | +[transportation.md](transportation.md) |
| 178 | + |
| 179 | +#### Smart Building |
| 180 | +IoT in (commercial) buildings such as office buildings, hotels, airports, train stations and sport stadiums. |
| 181 | +[smart-building.md](smart-building.md) |
| 182 | + |
| 183 | +Sensor networks for optimizing energy consumption of buildings. |
| 184 | +[connected-building-energy-efficiency.md](connected-building-energy-efficiency.md) |
| 185 | + |
| 186 | +#### Shared Devices and resources |
| 187 | +Standardized use of shared resources. |
| 188 | +[education.md](education.md) |
| 189 | + |
| 190 | +#### Oauth2 Flows |
| 191 | +Use cases for each OAuth2 flow. |
| 192 | +[oauth.md](oauth.md) |
| 193 | + |
| 194 | +#### Device lifecycle |
| 195 | +Common lifecycle model. |
| 196 | +[device-lifecycle.md](device-lifecycle.md) |
0 commit comments