[Directory Use Case] Add non-WoT device to smart home hub

[benfrancis]

As a user I want to add a non-WoT device to my smart home hub so that it can be monitored and controlled through my smart home software as a web thing.

In this scenario the user wants to pair a smart home device using a non-web or non-internet protocol (e.g. Zigbee, Z-Wave or HomeKit) with their smart home hub, which then bridges the device to the Web of Things and serves its Thing Description. The Thing Description is automatically generated by the smart home hub based on an adapter for the specific protocol the device is using. The client doesn't know what the content of the thing description will be when they pair the device. A unique identifier for the device (e.g. a MAC address) may be provided to the hub by the software adapter, but the client adding the device doesn't know or care what ID is assigned. Once added, the device will be enumerated alongside other devices in a WoT directory and may then be monitored, controlled and automated through a smart home dashboard UI and monitored and controlled as a web thing by other WoT clients.

[mmccool]

Not sure in general what we want to do with use cases. They should be documented somewhere, i.e. in the Use Cases and Requirements document. For now I am just using the label Use Case so we can see these are not "problems" we need to resolve in the spec per se.