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

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

From: Mats Wichmann via GitHub <sysbot+gh@w3.org>
Date: Sat, 14 May 2016 07:48:22 +0000
To: public-device-apis@w3.org
Message-ID: <issue_comment.created-219206651-1463212101-sysbot+gh@w3.org>
This is an interesting problem.  There are all kinds of sensors, and 
thus a number of different reporting styles.  In some cases it's 
important to relate the event to a real time - we want to know that 
this reading was taken at 8:02 AM locally, which means we want to know
 the timezone/DST situation as well.  In some other cases the 
interesting data is the relative time to other captures - here we 
don't want tz/dst, and we don't want to be affected by any possible 
time changes on the device. Think of these as Realtime Clock vs. 
Monitonic Clock.  And I can imagine in some cases, we may not care at 
all about the time - that's the original subject of this issue.  In 
general, the situation is more determined by the sensor in question 
than the application talking to it. Can there be a way to express the 
time in a flexible way such that the sensor can choose any of these 
three as their preferred reporting style?

-- 
GitHub Notification of comment by mwichmann
Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/105#issuecomment-219206651 using
 your GitHub account
Received on Saturday, 14 May 2016 07:48:24 UTC

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