W3C home > Mailing lists > Public > public-device-apis-log@w3.org > March 2017

Re: [sensors] Sensor discovery

From: Lars Knudsen via GitHub <sysbot+gh@w3.org>
Date: Fri, 31 Mar 2017 14:23:17 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-290725977-1490970195-sysbot+gh@w3.org>
(moved from #178 a case and some concerns related to discovery):

A use case that might very well happen soon:

I am sitting in my house looking at a temperature widget.

1. The web app widget is connected to both my phone temperature sensor and a temperature sensor outside my kitchen window.
2. I walk out to my car, losing connection with the sensor in my house - but keeping connection with the phone's sensor.
3. I start my car and my web app widget discovers the inside and outside temperature sensors in the car and shows them in the widget

now... there are a few issues with the current API for this to happen:

1. to have a new TemperatureSensor() in the first place, the browser needs to know about a 'TemperatureSensor' or it needs to be added with some polyfill (= not very generic)
2. I don't see any mechanism/events for adding/removing sensors
3. I see only a short example of a very specific way of addressing multiple sensors in the tire pressure example ... IMO, we need sensor discovery based on physical properties (e.g. tire pressure sensors can (also) be found by searching for sensors related to 'rotating motion' & 'air pressure' ... )

-- 
GitHub Notification of comment by larsgk
Please view or discuss this issue at https://github.com/w3c/sensors/issues/7#issuecomment-290725977 using your GitHub account
Received on Friday, 31 March 2017 14:23:24 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 12:18:52 UTC