Skip to content

Extend API with semantic capabilities #204

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
danielpeintner opened this issue Feb 21, 2020 · 1 comment
Closed

Extend API with semantic capabilities #204

danielpeintner opened this issue Feb 21, 2020 · 1 comment
Labels
API-improvement Suggestions for changing the API for next iteration Planned or postponed topics for the future propose closing Solutions exists and labelled as to be closed soon use case Describes a scenario that may be useful for technical decisions

Comments

@danielpeintner
Copy link
Contributor

@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
Copy link
Contributor

zolkis commented Feb 21, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API-improvement Suggestions for changing the API for next iteration Planned or postponed topics for the future propose closing Solutions exists and labelled as to be closed soon use case Describes a scenario that may be useful for technical decisions
Projects
None yet
Development

No branches or pull requests

4 participants