- From: Ingar Arntzen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Oct 2015 07:46:41 +0000
- To: public-webtiming@w3.org
Additionally, the interface between TimingProvider and TimingObject needs to be explicit about the time unit. The equation (clock_timing_provider = clock_user_agent + skew) requires that all values are expressed in the same unit. Since clock_timing_provider is likely to be epoch in seconds, it would be sensible that skew is expressed in seconds as well. So, I propose that the timing object spec consistently uses seconds as time unit - for skew, for its internal clock and for the timestamps that are exposed through StateVectors. -- GitHub Notif of comment by ingararntzen See https://github.com/webtiming/timingobject/issues/17#issuecomment-146783339
Received on Friday, 9 October 2015 07:46:44 UTC