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

Re: [sensors] Does SensorReading always need a timeStamp ?

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Mon, 16 May 2016 20:52:52 +0000
To: public-device-apis@w3.org
Message-ID: <issue_comment.created-219544358-1463431972-sysbot+gh@w3.org>
> We should probably stick to using the timestamps provided by the 
platform (?)

Agreed (though we'll obviously have to convert them to whatever 
baseline we're using).

> not really sure about the use-cases, but may be actually useful for 
measuring how "stale" a particular data is (as was already mentioned 
by tobie@ I think)

Yes. Measuring latency (granted the timestamp is that of the sensor 
reading, and not the Java event) and frequency also come to mind.

> Looks like on Android and Windows there are timestamps provided by 
the platform (although the exact semantics may be different). However 
I am curious as to what will happen if a platform is unable (or 
unwilling ;)) to provide timestamps.

Well, in that case, I guess we'd just use the equivalent of calling 

> or does this never happen?

I think all underlying platforms have at least a timestamp for when 
the reading is communicated to UA (or can generate one pretty easily).

GitHub Notification of comment by tobie
Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/105#issuecomment-219544358 using
 your GitHub account
Received on Monday, 16 May 2016 20:52:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:08 UTC