@@ -471,26 +471,30 @@ Users of products may interact directly with the operating system, or the operat
## 4.7 Use Cases
_The following use cases are an illustrative subset of all possible use cases. Manufacturers may contribute additional use cases._
**EDITORS NOTE:**The following list of use cases is an illustrative set of possible use cases selected to demonstrate the mechanics of this standard and provide clear guidance for the most common product categories.
***UC-LR** Operating system for learning and research
**EDITORS NOTE:** Considering that Operating Systems provide an essential functionality for all Digital Products, it is not feasible to list in detail either all extant or all potential use cases for operating systems.
**EDITORS NOTE:** We anticipate that future revisions of this document may include additional use cases, such as for the following product scenarios: embedded devides, baseband management controllers, network interface cards, graphics cards, real-time applications, and special purpose operating systems.
### 4.7.1 **UC-LR** Operating system for learning and research
* is not used for any purpose beyond learning and research
* does not store any sensitive or useful data
* security is provided entirely by the environment
* is highly modified by the user
***UC-IoT-1** Non-internet-connected device such as a bluetooth speaker
### 4.7.2 **UC-IoT-1** Non-internet-connected device such as a bluetooth speaker
* does not store any user-specific data
* has no means to connect directly to a public network
* not intended to support hardware, software, or operating system changes
***UC-IoT-2** Internet-enabled power switch
### 4.7.3 **UC-IoT-2** Internet-enabled power switch
* connects to a central service, operated by the device manufacturer, for remote data processing
* stores account information to authenticate to WiFi and to cloud service provider
* has a minimalistic interface, such as a single button for pairing and a reset button