W3C home > Mailing lists > Public > public-device-apis@w3.org > October 2009

FW: ISSUE-14: Gathering requirements [System Info & Events]

From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Sun, 4 Oct 2009 08:27:31 -0700
To: Max Froumentin <maxfro@opera.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <753F67ADE6F5094C9F1DBA00D1BAA8D312C3A7EF48@orsmsx501.amr.corp.intel.com>
> > Requirements for System Info & Events:
> > -       Power: battery, wall
> > -       Connection: WIFI, LAN, 3G, ..etc
> > -       CPU: type, id#, model, freq, number
> > -       Storage: hard disk, Solid state, read & write attributes
> 
> Also, available space, but then we're entering File I/O territory

The File I/O API does not report information about available space. Nor does it provide information about whether volume is removable. This is an API 'about' the storage capabilities of the device, not an API to store and retrieve information.

> 
> > -       Memory: RAM,
> > -       Display: # of display, color depth, resolution
> > -       Input: mouse, keyboard
> 
> +keypad, voice, stylus

Touch, multi-touch

> 
> > -       Audio: stereo, 5.1, 7.1 channels, microphone (recording)
> > o       Is this audio codec capability?
> > -       Video: Is this video codec capability? What about recording?
> > -       Thermal: internal, external (ambient)
> > -       Ambient Sound
> > -       Ambient Light (screen adjust due to brightness)
> 
> one or several values? (the iPhone has 2 ambient light detectors)

Several values. In the case of Thermal, for example, an In-car device might have two or three thermometers that report values to an application: inside, outside, and engine. 

> 
> > -       Proximity
> 
> to what?

Human

> 
> > -       Movement: gyroscope, accelerometer
> > -       Vibrate device
> > -       Compass
> 
> As in the existence or absence of a Compass device, right? But not
> providing a heading, since that would overlap the geolocation
> specification.
> If that's right, then add: Geolocation device

Providing access to Geolocation information via the System Info & Events API is logical, although it would be duplicitous. I'm not sure the Geolocation API has in mind the use case where orientation info comes from a compass rather than being extrapolated over time from GPS coordinates. If we choose to provide compass data via the Geolocation API, it should have an orientation Use Case and an orientation Requirement added, e.g. requirement 6.2.4 should be modified to read: " The Geolocation API MUST allow an application to register to receive updates when >>either the position or the heading<< of the hosting device changes."
Received on Sunday, 4 October 2009 15:28:07 UTC

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