Skip to content
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

[question] Are proprietary search/discovery mechanisms in scope? #25

Open
egekorkan opened this issue Jun 1, 2020 · 0 comments
Open
Labels
Discuss question Further information is requested

Comments

@egekorkan
Copy link
Contributor

I think the task force is focusing on an API for querying TDs and also network level service discovery style discovery. However, some platforms already have search/discovery mechanisms in place for finding platform specific devices. One example is the Philips Hue, where the Hue Bridge can get an HTTP Post request to search for new lights and also a GET request to retrieve the list of found lights. This also applies for sensors that work with Philips Hue (called accessories).

This TD of a Philips Hue Bridge has these two requests as actions. Further information can be also found at https://developers.meethue.com/develop/hue-api/lights-api/ which requires a free account. I am not sure if I am allowed to paste screenshots here.

The question is, how can we properly annotate TDs to allow this interactions to be identified with discovery functionalities? Also, are these really interaction affordances?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discuss question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants