DeviceMotion event vs Accelerometer sensor data

Dear GeoLoc WG,

My name is Jose Cantera and I'm one of the editors of the Sensor API [1]
within the Device APIs WG.The purpose of the Sensor API is to provide
access to the raw data provided by sensors accessible from a device. We
have had within the Working Group different discussions whether the Sensor
API should address Acceleremoter and Gyroscope sensors or not, due to
potential overlapping problems with your DeviceMotion events spec.

DeviceOrientation says "The information provided by the events
is not raw sensor data, but rather high-level data which is agnostic to
the underlying source of information." but our Sensor API is intended to
provide raw sensor data. In theory there is a subtle difference between
the two. The article at [2] gives a good explanation on the difference
between raw sensor data and smoothed data coming from the accelerometer.

Another important point to take into account is that in the Device Motion
event spec there is no way for an author to specify the delivery rate for
sensor data. And that is something well covered by the sensor API.

Thus the question for you is how do you see this problem?

Should the sensor API target Accelerometer and Gyroscope?

How we can coordinate? Can we have different APIs for different use cases
and share data structures for example?

Many thanks, All the best

[1] http://dev.w3.org/2009/dap/system-info/Sensors.html

[2]
http://windowsteamblog.com/windows_phone/b/wpdev/archive/2010/09/08/using-t

he-accelerometer-on-windows-phone-7.aspx





Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

Received on Thursday, 6 October 2011 12:04:19 UTC