W3C home > Mailing lists > Public > public-device-apis-log@w3.org > December 2016

[sensors] SensorReading.timeStamp could be clarified

From: Mark Foltz via GitHub <sysbot+gh@w3.org>
Date: Mon, 26 Dec 2016 19:27:54 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-197614169-1482780472-sysbot+gh@w3.org>
mfoltzgoogle has just created a new issue for 
https://github.com/w3c/sensors:

== SensorReading.timeStamp could be clarified ==
For sensor fusion applications, it's important that readings from 
different sensors have comparable timestamps.  The spec may want to 
clarify:

- Whether the timeStamp accounts for latency in delivering the reading
 from the sensor to the user agent.  If different sensors have 
different latencies, it will be hard to compare them.
- Whether the timeStamp corresponds to the time at the end of polling 
interval for a given reading.  (Some sensors may accumulate data for 
the entire polling interval and report an average at the end.)
- Whether the precision and accuracy of the timeStamp needs to be 
considered. For example, if the polling interval is 100 Hz, must the 
timeStamps be exactly 10ms apart?




Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/155 using your GitHub account
Received on Monday, 26 December 2016 19:27:55 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 12:18:52 UTC