CR Request for Resource Timing -- shortname: resource-timing

[caribouW3]

Document title, URLs, estimated publication date

Resource Timing

(note that it was previously "Resource Timing Level 2", the WG has decided to drop levels (Level 1 was still in CR)
and use the process2020 model. That implies a reuse of the resource-timing shortname.

https://w3c.github.io/resource-timing//?specStatus=CR&crEnd=2021-06-18&previousMaturity=WD&previousPublishDate=2021-04-14&implementationReportURI=https://w3c.github.io/test-results/resource-timing/all.html

Abstract

This specification defines an interface for web applications to access the complete timing information for resources in a document.

Status

This document was published by the Web Performance Working Group as a Candidate Recommendation Snapshot. This document is intended to become a W3C Recommendation.

GitHub Issues are preferred for discussion of this specification. Alternatively, you can send comments to our mailing list. Please send them to public-web-perf@w3.org (subscribe, archives) with [ResourceTiming] at the start of your email's subject.

Publication as a Candidate Recommendation does not imply endorsement by the W3C Membership. A Candidate Recommendation Snapshot has received wide review and is intended to gather implementation experience.

This Candidate Recommendation is not expected to advance to Proposed Recommendation any earlier than 18 June 2021.

This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 15 September 2020 W3C Process Document.

Link to group's decision to request transition

https://lists.w3.org/Archives/Public/public-web-perf/2021May/0002.html

Changes

In comparison to previously published "level 1" (in CR), changes are mainly
the addition of the size attributes, better buffering algorithms and Fetch integration.

Dependencies met (or not)

yes

Wide Review

https://lists.w3.org/Archives/Public/public-review-announce/2017Mar/0009.html

Privacy review issues https://github.com/w3c/resource-timing/issues?q=is%3Aissue+is%3Aopen+label%3Aprivacy-tracker
Fetch integration issues https://github.com/w3c/resource-timing/issues?q=is%3Aissue+is%3Aopen+label%3Afetch-integration

Issues addressed

https://github.com/w3c/resource-timing/issues

Formal Objections

None

Implementation

https://wpt.fyi/results/resource-timing

[swickr]

Thank you for issuing the Call for Wide Review early in the development of this specification. The publication history shows frequent updates since that Call was issued in 2017. Given the time that may have elapsed since reviews, especially the horizontal reviews were completed we have decreasing confidence that those reviews still apply. Our confidence should be less due to changes in the Working Drafts over the intervening time, due to additional understandings in the horizontal review areas, due to side-effects of subsequent work in other area, and possibly other factors.

Therefore, a CR Transition for this specification is not approved until the Working Group re-requests another wide review and requests explicit confirmation of horizontal reviews.

[caribouW3]

Hi. The Wide review has been started a long time ago, apparently it's time to declare a timeout on the security feedback.

[swickr]

PING has three open needs-resolution issues; w3cping/tracking-issues#39. w3cping/tracking-issues#40, w3cping/tracking-issues#41.

I do not see in those threads that the WG has given consideration to those issues. Therefore this transition is not yet approved.

[yoavweiss]

w3cping/tracking-issues#39

w3c/resource-timing#221 raises some valid concerns.
This was discussed on Feb 27 2020, at 2020 TPAC and as recently as April 14 2022.
At the same time, it's true that this was not yet resolved.

w3cping/tracking-issues#40

This was discussed at length in w3c/resource-timing#222
I don't think we can characterize the lack of agreement as a lack of consideration.

w3cping/tracking-issues#41.

w3c/resource-timing#223 is essentially a duplicate of 222, mentioned above.

[yoavweiss]

This was discussed at length in w3c/resource-timing#222 I don't think we can characterize the lack of agreement as a lack of consideration.

It was also discussed at the WG meeting itself.

[swickr]

Thank you @yoavweiss

For all three issues, please add a note referring to the issues in the relevant sections of the spec.

Assuming you are OK doing that, this spec is approved to advance to CR. If the WG has reasons for not adding such notes, please describe.

[yoavweiss]

Thanks @swickr! I'll add related notes (and try to reach conclusions on the parts that IMO should already be closed).

[yoavweiss]

Belatedly addressing this at w3c/resource-timing#339
Apologies for the delay!

[plehegar]

Not sure what's happening on this front but this CR hasn't been published yet: https://www.w3.org/standards/history/resource-timing-2

[caribouW3]

As soon as w3c/resource-timing#339 is closed we can edit the SOTD and publish as CR

[yoavweiss]

And now it's merged. Thanks for the ping (and @caribouW3 for the review)!

[plehegar]

The spec is still being published as WD: https://www.w3.org/TR/2022/WD-resource-timing-2-20220929/

[caribouW3]

The CR snapshot publication request has been sent to the webmaster earlier today (no public link available)

[deniak]

The spec is still being published as WD: https://www.w3.org/TR/2022/WD-resource-timing-2-20220929/

The GH action should probably be updated to publish CRD now that the CR has been published.

[plehegar]

https://www.w3.org/TR/2022/CR-resource-timing-20221004/