W3C home > Mailing lists > Public > public-device-apis@w3.org > January 2010

Re: [sysinfo] SEMC comments (was RE: Publishing System Information API FPWD)

From: Thomas Roessler <tlr@w3.org>
Date: Fri, 29 Jan 2010 15:13:53 +0100
Cc: Thomas Roessler <tlr@w3.org>, 'Max Froumentin' <maxfro@opera.com>, 'Robin Berjon' <robin@robineko.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-Id: <540FDD13-CF94-4FA0-B82C-DA45B0D772ED@w3.org>
To: "Nilsson, Claes1" <Claes1.Nilsson@sonyericsson.com>
On 29 Jan 2010, at 15:08, Nilsson, Claes1 wrote:

> Proximity is tricky. It is probably difficult to achieve: " The distance from the device to the nearest object, as determined by this device's proximity sensors, in meters (m)". An object is always close to the device if we assume that it is not "flying in the air" :-) It is difficult, but might be possible, to differ the user's hand or pocket from any other object. The question is what do we want to achieve? Which are the use cases? There are many parameters to consider.  E.g: Where is the sensor situated? In which direction does the sensor operate? Which type of sensor, granularity of values? Etc. 

Thinking out loud here -- isn't the typical use case of a proximity sensor really to figure out whether a specific display is obscured (and can therefore be turned off) or not?  That would, in particular, imply that it's not a property of just the device.
Received on Friday, 29 January 2010 14:14:04 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:41 UTC