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

RE: current list of sysinfo issues

From: Nilsson, Claes1 <Claes1.Nilsson@sonyericsson.com>
Date: Thu, 15 Apr 2010 15:49:48 +0200
To: 'Max Froumentin' <maxfro@opera.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <6DFA1B20D858A14488A66D6EEDF26AA3232A1FB3EC@seldmbx03.corpusers.net>
Hi Max,

> * Are we being short-sighted in only listing four orientations? Would
> it make sense to have it be an angle, except that in most cases it would
> only change in 90° increments?

Assuming that the Geo-location WG will specify a "full orientation API" I would say that it is enough with this simple "four orientation" API in the Sys Info spec.

> * Use focal length instead of maxZoomFactor for cameras? And shutter speed/aperture/ISO/sensor type?
>

The "focal length" is not especially usable. It is related to the size of the camera sensor. Keeping "maxZoomFactor" makes more sense. The web application might want to know how much zooming the camera is capable of. 

Furthermore. I don't see any use cases for more camera information such as shutter speed/aperture/ISO/sensor type.
>
>

As I have stated earlier I consider "Training" a common use case that should be supported by web applications. So would it make sense to add the following training related properties to Sensors, section 4.8?

- Heart Rate:
Attributes:
* value represents the measured heart rate in bpm.
* min value represents the minimum heart rate that the heart rate sensor can report, in bpm .
* max value represents the maximum heart rate that the heart rate sensor can report, in bpm.
* normalized value represents the measured heart rate, normalized to a 0 to 1 range.

- Step Counter:
Attributes:
* value represents the measured number of steps.
* min value represents the minimum number of steps that the step counter sensor can report.
* max value represents the maximum number of steps that the step counter sensor can report.
* normalized value represents the measured number of steps, normalized to a 0 to 1 range. (or stated as not applicable for this property)

If these properties are included I suggest that we change the first sentence after the section heading 4.8 to:
" The properties defined below expose the values of external sensors, reflecting the device's environment such as temperature, ambient brightness or ambient sound or the user's condition such as heart rate."

Best regards
  Claes


> -----Original Message-----
> From: public-device-apis-request@w3.org [mailto:public-device-apis-
> request@w3.org] On Behalf Of Max Froumentin
> Sent: onsdag den 14 april 2010 15:33
> To: public-device-apis@w3.org
> Subject: current list of sysinfo issues
> 
> As per my action item of last week, I am gathering all the known issues
> with the sysinfo specification, for further discussion:
> 
> * [Issue-79] System information, including sensor data and network
> connections, may permit obtaining sensitive information about the
> device
> and its user, in particular their location. Access control policies for
> this specification need to be aligned with access to the more sensitive
> information that can be inferred. Furthermore, the principle of
> minimization (the distribution of user data retrieval methods over as
> many interfaces as convenient) should apply as a general design rule
> for
> this specification.
> 
> * Are we being short-sighted in only listing four orientations? Would
> it
> make sense to have it be an angle, except that in most cases it would
> only change in 90° increments?
> 
> * Use focal length instead of maxZoomFactor for cameras? And shutter
> speed/aperture/ISO/sensor type?
> 
> * extensibility of enumerated constants, i.e. forwards compatibility
> with new network beyond WIFI, WIRED and PLMN. New constants? Strings?
> 
> * checking alignment with /proc filesystem in Linux
> 
> * Mapping with DCO (Bryan was tasked to work on that at the f2f)
> 
> That's all I can think of for now.
> 
> Max.

Received on Thursday, 15 April 2010 13:50:26 UTC

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