Extend API with semantic capabilities

[danielpeintner]

@mjkoster presented a slideset during the TD call that sketches some ideas with regard to semantic annotations. I think it highly relates to the Scripting API.

I did see 4 areas we might want to look into

1. discover things fullfilling semantic anntations
   • (at the momement we provide a way to pass along a ThingFilter to discover() with a thing fragment)
2. based on a thing select an interaction that fulfills (possibly yet another set of) semantic annotations (e.g., RGB light)
   • (at the moment one needs to know the name of an Interaction. I still propose that selecting an interaction should be a separate helper step saying please provide me the property names that fulfill a given set of semantic annotations. Hence the API can remain the same)
3. interact with a selected interaction (e.g., RGB light) by selecting/filtering based on semantic annotations, e.g. only the "red" light should be set
   • (at the moment one needs to provide the full set, R, G, and B colors and not only R)
4. scale/units conversion

@mjkoster did I miss any points?

Personally, I see it as a layered approach. Keeping the core of the scripting API as is (unless we need more features) but the semantic can be a very nice and handy enhancement on top if it....

[zolkis]

I like the slide set, it's a fresh look at things and is very interesting.

I agree with the layered approach.

It would be nice to discuss it in the Scripting call, which is not at US PST friendly time.
Perhaps we could touch the topic also in the Discovery TF call that is 2 hours after the Scripting call ends.