W3C home > Mailing lists > Public > public-web-perf@w3.org > April 2016

Resource Timing Level 1 and beyond

From: Philippe Le Hegaret <plh@w3.org>
Date: Tue, 26 Apr 2016 10:52:53 -0400
To: public-web-perf <public-web-perf@w3.org>
Message-ID: <571F80C5.6000501@w3.org>
Following last week discussion, I added "Level 1" to Resource Timing 
with the following:
[[
This specification is ready for wide review, with the following features 
at risk for the first release:

*    Dependency with Performance Timeline 2, since performance observers 
are lacking implementations;

*    Dependency with High Resolution Time 2 and workers support, 
including workerStart, since we're still refining time origin;

*    nextHopProtocol, transferSize, encodedBodySize, and 
decodedBodySize, since we're currently lacking implementations.
]]

I also labeled the issues with V1 and V2:
  https://github.com/w3c/resource-timing/issues

Imho, the issue that affects the most implementations at the moment is
  https://github.com/w3c/resource-timing/issues/12

I'm proposing that we don't solve it for V1 but keep flagging it as an 
issue in the spec for Web developers to be aware of.

If we're ok with this, plan is to move a Level 1 version of the spec 
without the feature at risk and publish at the same time a Level 2 of 
spec as normal. Level 1 shouldn't impact editors, ongoing issues, or 
pull requests. The branch gh-pages will continue to hold v.next and 
https://www.w3.org/TR/resource-timing will continue to reflect it as a 
Working Draft. In other words, Level 1 is and should remain a side 
artifact. We do however have enough implementations of Level 1 to ship 
to Recommendation within 3/4 months.

Philippe
Received on Tuesday, 26 April 2016 14:52:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 26 April 2016 14:52:56 UTC