[ResourceTiming] The clock base to use in ResourceTiming is not defined

This is implementor feedback on 
http://www.w3c-test.org/webperf/specs/ResourceTiming/

This document never defines the point that corresponds to time 0. 
Specifically:

1)  http://www.w3c-test.org/webperf/specs/ResourceTiming/#terminology 
never defines "time" (unlike, say the Terminology section of Navigation 
Timing).

2) 
http://www.w3c-test.org/webperf/specs/ResourceTiming/#performanceresourcetiming 
defines all the attributes as returning DOMHighResTimeStamp, but the 
DOMHighResTimeStamp type does not actually define what its 0 point 
represents.

3) 
http://www.w3c-test.org/webperf/specs/ResourceTiming/#processing-model 
keeps talking about recording "the current time", but as I said this 
term is never defined.

4) 
http://www.w3c-test.org/webperf/specs/ResourceTiming/#monotonic-clock 
has wording that is identical to the "Monotonic Clock" section of 
Navigation Timing.

Given item 4 and the lack of anything saying otherwise, the only obvious 
conclusion is that this document is using the same definition of "time" 
as Navigation Timing does: "milliseconds since midnight of January 1, 
1970 (UTC)".

However, I'm pretty sure that my testing of UAs that claim to implement 
this specification showed they are not using that definition of "time". 
  I'd appreciate it if the time base were actually specified here, 
instead of me having to reverse-engineer what those UAs are actually 
doing.  ;)

Thanks,
Boris

P.S. http://w3c-test.org/webperf/specs/NavigationTiming2/ has a similar 
problem.

Received on Saturday, 28 September 2013 02:42:34 UTC