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

Hi Thomas,

Yes, I guess that there are general use cases where the web application wants to detect whether the front on the device is "visible" or whether it is obscured (in pocket, by the ear, etc). Then you can control display light on/off, enable/disable touch etc.  

This can be supported by a simple API giving a Boolean attribute stating whether an object is close to the front of the device or not.

Any more proximity use cases?

Claes
> -----Original Message-----
> From: public-device-apis-request@w3.org [mailto:public-device-apis-
> request@w3.org] On Behalf Of Thomas Roessler
> Sent: fredag den 29 januari 2010 15:14
> To: Nilsson, Claes1
> Cc: Thomas Roessler; 'Max Froumentin'; 'Robin Berjon'; public-device-
> apis@w3.org
> Subject: Re: [sysinfo] SEMC comments (was RE: Publishing System
> Information API FPWD)
> 
> 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 15:30:30 UTC