You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: