[WoT UC] Shutter Control

Find attached a use case in the application domain of smart home / shutter control.
There are for sure different means to provide the technical description of the use case. The question is how to describe it in a neutral way, so in later technology landscape discussions it can be mapped to different approaches. Any idea?

BR,
Joerg

---- 8< cut here ----

-------
What is the user motivation for the use case
-------
Jo has motor driven shutters in front of the windows. He wants that the shutter control adapts to the lighting and presence in the house. So he combines the shutter control with other sensor services such as web based information on day light. If he is not present the shutter is closed in the evening and opened in the morning. If he is present he explicit controls it with a switch sensor. In this case closing the shutter result in switching on a minimum lighting. Finally one switch is configured by Jo as emergency opening of the shutters.

-------
How does this translate to a technical Description
--------

The resources of the shutter controller can be discovered by the web browser. The resources can be mashed up with web based information such as daylight information. This mashup can be activated by a resource of the presence sensor.

-------
What application domains are related (e.g. referring to the taxonomy)
-------
main: smart home / home automation / shutter control
related: smart home / home automation / lighting

-------
What interaction pattern with or btw things can be observed
-------
Thing discovery: find things in the local network
Thing resource browsing: to create a mashup the resource of the thing can be browsed
Mashup of Thing resources: thing resources can be mashed up (this might need some further clarification)

-------
Which aspects are not considered
-------
Life cycle of devices, services and applications
Installation process
Dealing with faults
Replacing devices

---- 8< cut here ----