Re: [sensors] Sensor discovery

Tying this in to #9. I think it's critical here to have a better 
understanding of how sensors are discovered/report themselves to the 
browser and which information is available about them when navigating 
to a new resource and which information needs to be queried 
asynchronously.

Obviously, sensor unplugging or plugging during page lifetime also 
needs to be handled.

Finally, there remains the issue that a device can misrepresent 
itself, either accidentally or on purpose, and that must be accounted 
for in the APIs.

Proposing that we resolve this issue like so:

There must be a way for developers to find out which sensors are 
available to a resource, which ones become available during the page's
 lifetime, and which ones get disconnected. The precise API by which 
this must be exposed is dependent on the research carried out in #9 to
 determine how sensor register themselves with a browsing context. 
Such an API must be designed to allow developers to gracefully  handle
 sensors misrepresenting themselves either accidentally or on purpose.


-- 
GitHub Notif of comment by tobie
See https://github.com/w3c/sensors/issues/7#issuecomment-100611051

Received on Sunday, 10 May 2015 09:24:18 UTC