From 489ae09fb8c2f060fbf16c423c7142f65fdf7aab Mon Sep 17 00:00:00 2001 From: Yoav Weiss Date: Mon, 27 Feb 2023 10:48:07 +0100 Subject: [PATCH 01/19] Charter comments --- charter_comments.md | 536 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 536 insertions(+) create mode 100644 charter_comments.md diff --git a/charter_comments.md b/charter_comments.md new file mode 100644 index 00000000..889de341 --- /dev/null +++ b/charter_comments.md @@ -0,0 +1,536 @@ +# W3C Web Performance Working Group + + +# 2023 Charter Comments + +2021 Charter: [https://www.w3.org/2021/02/webperf.html](https://www.w3.org/2021/02/webperf.html) + +Expires: 28 February 2023 + + + +* Scope/Themes + * Measurement + * Proposal to be "Privacy Preserving Measurement" + * Coordinate w/ IETF group similarly-named + * Scheduling + * Adaptation +* Specs Changes + * Resource Hints + * Discontinued (from 2021 charter) + * Moving to HTML + * Repo doesn't mention this [https://w3c.github.io/resource-hints/](https://w3c.github.io/resource-hints/) + * Preload + * Discontinued (from 2021 charter) + * Moved to HTML + * Repo archived + * Spec mentions this + redirects [https://github.com/w3c/preload/](https://github.com/w3c/preload/) + * Page Visibility + * Discontinue (in 2023 charter) + * Moved to HTML + * Repo archived (but doesn't mention why) + * Spec says discontinued [https://github.com/w3c/page-visibility/](https://github.com/w3c/page-visibility/) + * Spec should redirect? + * Beacon + * Don't finalize to Rec, could incorporate Unload/Pending beacon into it + * Cooperative Scheduling of Background Tasks (rIC) + * Don't finalize to Rec, could incorporate Scheduling APIs + * PaintTiming + * EventTiming + * Listed as a repo, but not a deliverable/spec? + * LCP + * Listed as a repo, but not a deliverable/spec? + * Could incorporate ElementTiming? + * Timing Names Entry Registry + * New process for registries from W3C +* Incubations + * ElementTiming [https://github.com/WICG/element-timing](https://github.com/WICG/element-timing) + * Move into LCP? Or at least bring into WG as LCP already is. + * Merge parts into LCP, parts into PaintTiming + * isInputPending [https://github.com/WICG/is-input-pending](https://github.com/WICG/is-input-pending) + * Any recent updates? + * Layout Instability [https://github.com/WICG/layout-instability](https://github.com/WICG/layout-instability) + * Discussion in early 2022 around lessons from implementation + * Barriers to adoption? + * Mozilla: Neutral (implementation, performance concerns) + * Apple: Opposed (circa 2019) (concerns on bookkeeping, cost at runtime, implementation, animations/scrolling not handled well) + * Memory Measurement [https://github.com/WICG/performance-measure-memory](https://github.com/WICG/performance-measure-memory) + * Network Info [https://github.com/WICG/netinfo/](https://github.com/WICG/netinfo/) + * Unload Beacon [https://github.com/WICG/unload-beacon](https://github.com/WICG/unload-beacon) + * Incorporate into Beacon? + * Scheduling APIs [https://github.com/WICG/scheduling-apis](https://github.com/WICG/scheduling-apis) + * Incorporate into Cooperative Scheduling of Background Tasks? + * Consider a move to HTML spec (same as rIC?) + * JS self profiling [https://wicg.github.io/js-self-profiling/](https://wicg.github.io/js-self-profiling/) + * Any recent updates? + * Priority Hints [https://github.com/WICG/priority-hints](https://github.com/WICG/priority-hints) + * Page Lifecycle [https://github.com/WICG/page-lifecycle](https://github.com/WICG/page-lifecycle) + * Intervention/Deprecation/Crash Reporting + * [https://github.com/WICG/deprecation-reporting](https://github.com/WICG/deprecation-reporting) + * [https://github.com/WICG/intervention-reporting](https://github.com/WICG/intervention-reporting) + * [https://github.com/WICG/crash-reporting](https://github.com/WICG/crash-reporting) + + +## TPAC 22 discussions + + + +* “Privacy preserving monitoring” - proposal from AlexC, to be discussed + * Potential collaboration with the IETF PPM WG +* Sustainability - should it be covered in scope? No direct deliverables just yet +* Lab tooling related browser interop - should it go back to being in scope? + + +## Other questions + + + +* HR-Time is not just about high resolution timers, but defines time in general. Should we rename it? +* We should call out[ open privacy issues](https://github.com/w3c/resource-timing/issues?q=is%3Aissue+is%3Aopen+label%3Aprivacy-needs-resolution) and say that we strive to resolve them + + +# CURRENT CHARTER + + +## Scope + +Web developers are building sophisticated applications where application performance is a critical feature. Web developers want the ability to observe the performance characteristics of their applications, and they want the ability to write more efficient applications, using well-defined interoperable methods. Their methods must be both secure and privacy-enabling by design, using well-defined interoperable methods that conform to the current Web browser security model. + +The Web Performance Working Group's scope of work includes user agent features and APIs to observe and improve various aspects of application performance: + + + +* _Measurement \ +_The WG will deliver APIs to measure network and rendering performance, responsiveness and interactivity, memory and CPU use, application failures, and other aspects of the user’s experience, from the perspectives of both application loading and continuous user interaction. In particular, the group will deliver means to measure user experience metrics in popular web architectures, such as single-page apps, as well as means to collect those measurements. +* _Scheduling \ +_The WG will deliver APIs to enable developers to improve scheduling of application work as well as use of network resources, to minimize loading times and ensure ideal user experience. +* _Adaptation \ +_The WG will deliver APIs to enable developers to deliver resources adapted to the user’s device, preferences, conditions, or other circumstances. + +Such deliverables will apply to desktop and mobile browsers and other non-browser environments where appropriate, and will be consistent with Web technologies designed in other working groups including HTML, CSS, Web Application Security, Web Apps, Device and Sensors, and SVG. The Group will strive for its deliverables to be well-integrated with other specifications where appropriate. + +In addition to developing Recommendation Track documents, the Web Performance Working Group may provide review of specifications from other Working Groups. + + +### Out of Scope + +The following features are out of scope, and will not be addressed by this working group. + + + +* performance data analysis techniques or algorithms. + + +### Success Criteria + +In order to advance to [Proposed Recommendation](https://www.w3.org/2020/Process-20200915/#RecsPR), each specification is expected to have at least two independent implementations of each feature defined in the specification. + +Each specification should contain a section detailing any [known security](https://www.w3.org/TR/security-privacy-questionnaire/), fingerprinting, and privacy implications, and suggested [mitigation strategies](https://w3c.github.io/perf-security-privacy/) for implementers, Web authors, and end users. The group should not publish a specification if acceptable mitigation strategies cannot be found. + +Normative specification changes are generally expected to have a corresponding set of tests, either in the form of new tests or modifications to existing tests, or must include the rationale for why test updates are not required for the proposed update. + + +## Deliverables + +Note: Latest milestone and publication schedules for the group's deliverables listed below can be found on the [publication status page](https://docs.google.com/spreadsheets/d/1JIB8c7hfyH_wuxkf6bLgovFekHP1LpTtqBTJGEUIK7E/edit#gid=0) + +_Draft state_ indicates the state of the deliverable at the time of the charter approval. _Next Recommendation expected completion_ indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state. + + +### Normative Specifications + +The working group will deliver incremental revisions of the following W3C normative specifications: + +**[High Resolution Time](https://w3c.github.io/hr-time/)** + +This document defines an API that provides the current time in sub-millisecond resolution such that it is not subject to system clock skew or adjustments. + +**Level 3 Draft state:** [Working Draft](https://www.w3.org/TR/hr-time-3/) + +**Next Recommendation expected completion:** Q2 2021 + +Latest publication: [01 October 2020](https://www.w3.org/TR/2020/WD-hr-time-3-20201001/) + +Patent Review Draft (level 3): [https://www.w3.org/TR/2020/WD-hr-time-3-20201001/](https://www.w3.org/TR/2020/WD-hr-time-3-20201001/) + +Reference Draft (level 2): [https://www.w3.org/TR/2018/CR-hr-time-2-20180301/](https://www.w3.org/TR/2018/CR-hr-time-2-20180301/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2018Mar/0000.html) on 01 March 2018 ended on 30 April 2018 + +Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). + +**[Performance Timeline](https://w3c.github.io/performance-timeline/)** + +This specification defines a unified interface to store and retrieve performance metric data. + +**Draft state:** [Working Draft](https://www.w3.org/TR/performance-timeline/) + +**Next Recommendation expected completion:** Q1 2021 + +Latest publication: [24 October 2019](https://www.w3.org/TR/2019/WD-performance-timeline-2-20191024/) + +Reference Draft: [https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/](https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2016Dec/0001.html) on 08 December 2016 ended on 06 February 2017 + +Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). + +**[Resource Timing](https://w3c.github.io/resource-timing/)** + +An interoperable means for site developers to collect real-world performance information from the user agent while loading resources as specified from the root document of a webpage. The user agent captures the end to end latency associated with loading resources from a web server. This includes the time associated with fetching the resource from the network and the time associated to load the resource within the user agent. This might include: + + + +* timing associated with the network; +* timings associated with loading the resource in the document; +* a resource, such as one of the following elements: iframe, img, script, object, embed and link. + +**Level 1 Draft state:** [Candidate Recommendation](https://www.w3.org/TR/resource-timing-1/) + +**Next Recommendation expected completion:** Q1 2021 + +Latest publication: [30 March 2017](https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/) + +Reference Draft: [https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/](https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Mar/0005.html) on 30 March 2017 ended on 29 May 2017 + +Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). + +**Level 2 Draft state:** [Working Draft](https://www.w3.org/TR/resource-timing-2/) + +**Next Recommendation expected completion:** Living Standard + +Latest publication: [18 February 2020](https://www.w3.org/TR/2020/WD-resource-timing-2-20200218/) + +Reference Draft: [https://www.w3.org/TR/2016/WD-resource-timing-2-20161103/](https://www.w3.org/TR/2016/WD-resource-timing-2-20161103/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2016Nov/0005.html) on 03 November 2016 ended on 02 April 2017 + +Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) + +**[Navigation Timing](https://w3c.github.io/navigation-timing/)** + +An interoperable means for site developers to collect real-world performance information from the user agent while loading the root document of a webpage. The user agent captures the end to end latency associated with loading a webpage from a web server. This includes the time associated with fetching the document from the network to the time associated to load the document within the user agent. + +**Draft state:** [Working Draft](https://www.w3.org/TR/navigation-timing-2/) + +**Next Recommendation expected completion:** Living Standard + +Note: after Level 2 of Navigation Timing is ratified, future development of new Navigation Timing features will be done within Resource Timing; Navigation Timing will be merged with Resource Timing. + +Latest publication: [21 January 2020](https://www.w3.org/TR/2020/WD-navigation-timing-2-20200121/) + +Reference Draft: [https://www.w3.org/TR/2015/WD-navigation-timing-2-20150120/](https://www.w3.org/TR/2015/WD-navigation-timing-2-20150120/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2013Jan/0014.html) on 31 January 2013 ended on 30 June 2013 + +Produced under Working Group Charter: [https://www.w3.org/2013/01/webperf](https://www.w3.org/2013/01/webperf). + +**[User Timing](https://w3c.github.io/user-timing/)** + +An interoperable means for site developers to capture timing information with a developer supplied name. The user agent captures the time stamp at the point and time specified in the code executing in the user agent. + +**Draft state:** [Working Draft](https://www.w3.org/TR/user-timing-3/) + +**Next Recommendation expected completion:** Living Standard + +Latest publication: [26 March 2020](https://www.w3.org/TR/2020/WD-user-timing-3-20200326/) + +Reference Draft: [https://www.w3.org/TR/2019/WD-user-timing-3-20190305/](https://www.w3.org/TR/2019/WD-user-timing-3-20190305/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2019Mar/0000.html) on 05 March 2019 ended on 02 August 2019 + +Produced under Working Group Charter: [https://www.w3.org/2018/09/webperf](https://www.w3.org/2018/09/webperf) + +**[Page Visibility](https://w3c.github.io/page-visibility/)** + +An interoperable means for site developers to programmatically determine the current visibility of a document and be notified of visibility changes. + +**Draft state:** [Proposed Recommendation](https://www.w3.org/TR/page-visibility-2/) + +**Next Recommendation expected completion:** Q1 2021 + +Latest publication: [17 October 2017](https://www.w3.org/TR/2017/PR-page-visibility-2-20171017/) + +Reference Draft: [https://www.w3.org/TR/2017/CR-page-visibility-2-20170328/](https://www.w3.org/TR/2017/CR-page-visibility-2-20170328/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Mar/0003.html) on 29 March 2017 ended on 27 May 2017 + +Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) + +**[Beacon](https://w3c.github.io/beacon/)** + +An interoperable API for site developers to asynchronously transfer data from the user agent to a web server, with a guarantee from the user agent that the data will be eventually sent. + +**Draft state:** [Candidate Recommendation](https://www.w3.org/TR/beacon/) + +**Next Recommendation expected completion:** Q1 2021 + +Latest publication: [13 April 2017](https://www.w3.org/TR/2017/CR-beacon-20170413/) + +Reference Draft: [https://www.w3.org/TR/2017/CR-beacon-20170413/](https://www.w3.org/TR/2017/CR-beacon-20170413/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Apr/0004.html) on 13 April 2017 ended on 12 June 2017 + +Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). + +**[Cooperative Scheduling of Background Tasks](https://w3c.github.io/requestidlecallback/)** + +An API that web page authors can use to cooperatively schedule background tasks such that they do not introduce delays to other high priority tasks that share the same event loop, such as input processing, animations and frame compositing. + +**Draft state:** [Proposed Recommendation](https://www.w3.org/TR/requestidlecallback/) + +**Next Recommendation expected completion:** Q2 2021 + +Latest publication: [10 October 2017](https://www.w3.org/TR/2017/PR-requestidlecallback-20171010/) + +Reference Draft: [https://www.w3.org/TR/2017/CR-requestidlecallback-20170131/](https://www.w3.org/TR/2017/CR-requestidlecallback-20170131/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Feb/0000.html) on 02 February 2017 ended on 01 April 2017 + +Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). + +**[Long Task](https://w3c.github.io/longtasks/)** + +This specification defines an API that web page authors can use to detect presence of "long tasks" that monopolize the UI thread for extended periods of time and block other critical tasks from being executed - e.g. reacting to user input. + +**Draft state:** [Working Draft](https://www.w3.org/TR/longtasks-1/) + +**Next Recommendation expected completion:** Q4 2021 + +Latest publication: [07 September 2017](https://www.w3.org/TR/2017/WD-longtasks-1-20170907/) + +Reference Draft: [https://www.w3.org/TR/2017/WD-longtasks-1-20170907/](https://www.w3.org/TR/2017/WD-longtasks-1-20170907/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Dec/0001.html) on 07 December 2017 ended on 04 February 2018 + +Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). + +**[Paint Timing](https://w3c.github.io/paint-timing/)** + +An interoperable API for site developers to capture the set of key moments during pageload - e.g. first paint and first contentful paint. + +**Draft state:** [Working Draft](https://www.w3.org/TR/paint-timing/) + +**Next Recommendation expected completion:** Q1 2021 + +Latest publication: [07 September 2017](https://www.w3.org/TR/2017/WD-paint-timing-20170907/) + +Reference Draft: [https://www.w3.org/TR/2017/WD-paint-timing-20170907/](https://www.w3.org/TR/2017/WD-paint-timing-20170907/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Dec/0001.html) on 07 December 2017 ended on 04 February 2018 + +Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) + +**[Server Timing](https://w3c.github.io/server-timing/)** + +This specification enables a server to communicate performance metrics about the request-response cycle to the user agent. It also standardizes a JavaScript interface to enable applications to collect, process, and act on these metrics to optimize application delivery. + +**Draft state:** [Working Draft](https://www.w3.org/TR/server-timing/) + +**Next Recommendation expected completion:** Q2 2021 + +Latest publication: [20 January 2020](https://www.w3.org/TR/2020/WD-server-timing-20200120/) + +Reference Draft: [https://www.w3.org/TR/2017/WD-server-timing-20170713/](https://www.w3.org/TR/2017/WD-server-timing-20170713/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Jul/0005.html) on 13 July 2017 ended on 10 December 2017 + +Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) + +**[Device Memory](https://w3c.github.io/device-memory/)** + +This specification defines a JavaScript API and HTTP Client Hint header to surface device capability for memory — i.e. device RAM, in order to enable web apps to customize content depending on device memory constraints. + +**Draft state:** [Working Draft](https://www.w3.org/TR/device-memory/) + +**Next Recommendation expected completion:** Q4 2021 + +Latest publication: [25-Sep-2018](https://www.w3.org/TR/2018/WD-device-memory-1-20180925/) + +Reference Draft: [https://www.w3.org/TR/2018/WD-device-memory-1-20180925/](https://www.w3.org/TR/2018/WD-device-memory-1-20180925/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2018Sep/0003.html) on 25-Sep-2018 ended on 22-Feb-2019 + +Produced under Working Group Charter: [https://www.w3.org/2018/09/webperf/](https://www.w3.org/2018/09/webperf/) + +**[Reporting](https://w3c.github.io/reporting/)** + +This specification defines a generic reporting framework which allows web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner. + +**Draft state:** [Working Draft](https://www.w3.org/TR/reporting-1/) + +**Next Recommendation expected completion:** Q4 2021 + +Latest publication: [25-Sep-2018](https://www.w3.org/TR/2018/WD-reporting-1-20180925/) + +Reference Draft: [https://www.w3.org/TR/2016/WD-reporting-1-20160407/](https://www.w3.org/TR/2016/WD-reporting-1-20160407/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2016Apr/0001.html) on 7 April 2016 ended on 4 September 2016 + +Produced under Working Group Charter: [https://www.w3.org/2015/06/webperf](https://www.w3.org/2015/06/webperf). + +**[Network Error Logging](https://w3c.github.io/network-error-logging)** + +This specification defines a mechanism that enables developers to declare a network error reporting policy for a web application. A user agent can use this policy to report encountered network errors that prevented it from successfully fetching requested resource. + +**Draft state:** [Working Draft](https://www.w3.org/TR/network-error-logging/) + +**Next Recommendation expected completion:** Q4 2021 + +Latest publication: [25-Sep-2018](https://www.w3.org/TR/2018/WD-network-error-logging-1-20180925/) + +Reference Draft: [https://www.w3.org/TR/2014/WD-navigation-error-logging-20140211/](https://www.w3.org/TR/2014/WD-navigation-error-logging-20140211/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2014Feb/0008.html) on 12-Feb-2014 ended on 12-Jul-2014 + +Produced under Working Group Charter: [https://www.w3.org/2013/01/webperf](https://www.w3.org/2013/01/webperf) + + +### Past Deliverables + +The Group plans to transition the contents of the following past-deliverables to the WHATWG and publish them as a Note. + +**[Resource Hints](https://w3c.github.io/resource-hints/)** + +This specification defines the dns-prefetch, preconnect, prefetch, and prerender relationships of the HTML Link Element (<link>). + +**Draft state:** [Working Draft](https://www.w3.org/TR/resource-hints/) + +Latest publication: [02 July 2019](https://www.w3.org/TR/2019/WD-resource-hints-20190702/) + +Reference Draft: [https://www.w3.org/TR/2014/WD-resource-hints-20141021/](https://www.w3.org/TR/2014/WD-resource-hints-20141021/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2014Oct/0006.html) on 23 October 2014 ended on 20 March 2015 + +Produced under Working Group Charter: [https://www.w3.org/2013/01/webperf](https://www.w3.org/2013/01/webperf) + +**[Preload](https://w3c.github.io/preload/)** + +This specification defines the link relation type preload, a declarative fetch primitive that initiates an early fetch and separates fetching from resource execution. + +**Draft state:** [Candidate Recommendation](https://www.w3.org/TR/preload/) + +Latest publication: [26 June 2019](https://www.w3.org/TR/2019/CR-preload-20190626/) + +Reference Draft: [https://www.w3.org/TR/2017/CR-preload-20171026/](https://www.w3.org/TR/2017/CR-preload-20171026/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Oct/0007.html) on 26 October 2017 ended on 25 December 2017 + +Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). + + +### Other Deliverables + +The Group will maintain a [non-normative Primer document](https://w3c.github.io/perf-timing-primer/) to facilitate the understanding of the interrelationships between its deliverables. + +Other non-normative documents may be created such as: + + + +* [Security and Privacy considerations for Performance APIs](https://w3c.github.io/perf-security-privacy/) +* Test suites for each specification; +* Use cases documents to support development and exploration of performance-critical web platform features and APIs; +* Primer or Best Practice documents to support web developers when designing applications with performance in mind; +* Developer and user guides for its normative specifications; +* Best practice document explaining how data is commonly gathered between the client and the server. + + +## Coordination + +For all specifications, this Working Group will seek [horizontal review](https://www.w3.org/Guide/Charter.html#horizontal-review) for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the [TAG](https://www.w3.org/2001/tag/). Invitation for review must be issued during each major standards-track document transition, including [FPWD](https://www.w3.org/2020/Process-20200915/#RecsWD) and [CR](https://www.w3.org/2020/Process-20200915/#RecsCR), and should be issued when major changes occur in a specification. + +Additional technical coordination with the following Groups will be made, per the [W3C Process Document](https://www.w3.org/2020/Process-20200915/#WGCharter): + + +### W3C Groups + +[Technical Architecture Group (TAG)](https://www.w3.org/2001/tag/) + +The WG may ask the Technical Architecture Group to review some of its specifications. + +[Web Applications Working Group](https://www.w3.org/2019/webapps/) + +This Working Group develops APIs for client-side development and for markup vocabularies for describing and controlling client-side application behavior. + +[Web Application Security Working Group](https://www.w3.org/2011/webappsec/) + +This Working Group develops security and policy mechanisms to improve the security of Web Applications, and enable secure cross-site communication. + +[CSS Working Group](https://www.w3.org/Style/CSS/members) + +The group develops and maintains CSS, which is relevant for specifications such as page visibility. + +[Privacy Interest Group](https://www.w3.org/Privacy/IG/) + +This group monitors ongoing privacy issues that affect the Web, investigates potential areas for new privacy work, and provides guidelines and advice for addressing privacy in standards development. + +[Web Platform Incubator Community Group](https://www.w3.org/community/wicg/) + +This group provides a lightweight venue for proposing, incubating and discussing new web platform features. The Web Performance Working group will incubate and review new proposals that are within scope of our charter within the WICG. Once such WICG-incubated proposal is implemented and available in at least one major browser, and has support from one more, it may be adopted by the Web Performance Working group. + + +### External Organizations + +[ECMA Technical Committee 39 (TC39)](https://www.ecma-international.org/memento/tc39.htm) + +This is the group responsible for ECMAScript standardization, and related ECMAScript features like E4X. As the Web Performance Working Group will be developing ECMAScript APIs, it should collaborate with TC39. + +[Internet Engineering Task Force](https://www.ietf.org/) + +The IETF is responsible for defining robust and secure protocols for Internet functionality, in particular HTTP. The Working Group should coordinate protocol-related work (e.g. profiles of hybi or HTTP) with the appropriate IETF WGs. + +[Web Hypertext Application Technology Working Group (WHATWG)](https://whatwg.org/) + +The Web Hypertext Application Technology Working Group (WHATWG) is a community of people interested in evolving the web through standards and tests. + + +## Participation + +To be successful, this Working Group is expected to have 5 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a day per week towards the Working Group. There is no minimum requirement for other Participants. + +The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in [Communication](https://www.w3.org/2021/02/webperf.html#communication). + +The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy/). + +Participants in the group are required (by the [W3C Process](https://www.w3.org/Consortium/Process/#ParticipationCriteria)) to follow the W3C [Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/). + + +## Communication + +Technical discussions for this Working Group are conducted in [public](https://www.w3.org/2020/Process-20200915/#confidentiality-levels). Meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed on a public repository, and may permit direct public contribution requests. + +Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the [Web Performance Working Group home page.](https://www.w3.org/2010/webperf/) + +Most Web Performance Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis. + +This group primarily conducts its technical work in its [public repositories](https://github.com/orgs/w3c/teams/web-performance/repositories). There is also a public mailing list public-web-perf@w3.org ([archive](https://lists.w3.org/Archives/Public/public-web-perf/)). The public is invited to contribute to the github repositories and post messages to the list. Regular activity summaries around the github repositories will be provided. + + +## Decision Policy + +This group will seek to make decisions through consensus and due process, per the [W3C Process Document (section 3.3](https://www.w3.org/2020/Process-20200915/#Consensus)). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required. + +However, if a decision is necessary for timely progress, but consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote, and record a decision along with any objections. + +To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional until 10 working days after the publication of the resolution in draft minutes sent, which will be published within 5 working days of the meeting to the working group's mailing list with a 'call for consensus' in the subject line. If no objections are raised on the mailing list by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group. + +All decisions made by the group should be considered resolved unless and until new information becomes available, or unless reopened at the discretion of the Chairs or the Director. + +This charter is written in accordance with the [W3C Process Document (Section 3.4, Votes)](https://www.w3.org/Consortium/Process/policies#Votes), and includes no voting procedures beyond what the Process Document requires. + + +## Patent Policy + +This Working Group operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20200915/) 15 September 2020. To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis. For more information about disclosure obligations for this group, please see the [W3C Patent Policy Implementation](https://www.w3.org/2004/01/pp-impl/45211/status). + + +## Licensing + +This Working Group will use the [W3C Software and Document license](https://www.w3.org/Consortium/Legal/copyright-software) for all its deliverables. + + +## About this Charter + +This charter has been created according to [section 5.2](https://www.w3.org/Consortium/Process/groups#GAGeneral) of the [Process Document](https://www.w3.org/Consortium/Process). In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence. From a34043818ecde64ec16c1d4fb7bc394c1df50a0c Mon Sep 17 00:00:00 2001 From: Yoav Weiss Date: Fri, 30 Jun 2023 11:31:08 +0200 Subject: [PATCH 02/19] Update the charter draft with the latest in terms of publishing --- charter_comments.md | 131 ++++++++++++++++++++------------------------ 1 file changed, 60 insertions(+), 71 deletions(-) diff --git a/charter_comments.md b/charter_comments.md index 889de341..4cc91af8 100644 --- a/charter_comments.md +++ b/charter_comments.md @@ -132,24 +132,23 @@ Normative specification changes are generally expected to have a corresponding s ## Deliverables -Note: Latest milestone and publication schedules for the group's deliverables listed below can be found on the [publication status page](https://docs.google.com/spreadsheets/d/1JIB8c7hfyH_wuxkf6bLgovFekHP1LpTtqBTJGEUIK7E/edit#gid=0) - -_Draft state_ indicates the state of the deliverable at the time of the charter approval. _Next Recommendation expected completion_ indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state. +The WG expects to gradually move all of its deliverables to a Living Standard CR model. +Beyond that, the WG expects to converge at least some of its deliverables into a smaller number of specifications. ### Normative Specifications The working group will deliver incremental revisions of the following W3C normative specifications: -**[High Resolution Time](https://w3c.github.io/hr-time/)** +#### [High Resolution Time](https://w3c.github.io/hr-time/) This document defines an API that provides the current time in sub-millisecond resolution such that it is not subject to system clock skew or adjustments. -**Level 3 Draft state:** [Working Draft](https://www.w3.org/TR/hr-time-3/) +**Draft state:** [Working Draft](https://www.w3.org/TR/hr-time/) -**Next Recommendation expected completion:** Q2 2021 +**Next Recommendation expected completion:** -Latest publication: [01 October 2020](https://www.w3.org/TR/2020/WD-hr-time-3-20201001/) +Latest publication: [25 April 2023](https://www.w3.org/TR/2023/WD-hr-time-3-20230425/) Patent Review Draft (level 3): [https://www.w3.org/TR/2020/WD-hr-time-3-20201001/](https://www.w3.org/TR/2020/WD-hr-time-3-20201001/) @@ -159,15 +158,15 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). -**[Performance Timeline](https://w3c.github.io/performance-timeline/)** +#### [Performance Timeline](https://w3c.github.io/performance-timeline/) This specification defines a unified interface to store and retrieve performance metric data. -**Draft state:** [Working Draft](https://www.w3.org/TR/performance-timeline/) +**Draft state:** [Candidate Recommendation Draft](https://www.w3.org/TR/performance-timeline/) -**Next Recommendation expected completion:** Q1 2021 +**Next Recommendation expected completion:** Living Standard -Latest publication: [24 October 2019](https://www.w3.org/TR/2019/WD-performance-timeline-2-20191024/) +Latest publication: [15 November 2022](https://www.w3.org/TR/2022/CRD-performance-timeline-20221115/) Reference Draft: [https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/](https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/) @@ -175,20 +174,12 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). -**[Resource Timing](https://w3c.github.io/resource-timing/)** - -An interoperable means for site developers to collect real-world performance information from the user agent while loading resources as specified from the root document of a webpage. The user agent captures the end to end latency associated with loading resources from a web server. This includes the time associated with fetching the resource from the network and the time associated to load the resource within the user agent. This might include: - - +#### [Resource Timing](https://w3c.github.io/resource-timing/) -* timing associated with the network; -* timings associated with loading the resource in the document; -* a resource, such as one of the following elements: iframe, img, script, object, embed and link. +This specification defines an interface for web applications to access the complete timing information for resources in a document or in a worker. **Level 1 Draft state:** [Candidate Recommendation](https://www.w3.org/TR/resource-timing-1/) -**Next Recommendation expected completion:** Q1 2021 - Latest publication: [30 March 2017](https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/) Reference Draft: [https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/](https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/) @@ -197,11 +188,11 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). -**Level 2 Draft state:** [Working Draft](https://www.w3.org/TR/resource-timing-2/) +**Level 2 Draft state:** [Candidate Recommendation Draft](https://www.w3.org/TR/resource-timing/) **Next Recommendation expected completion:** Living Standard -Latest publication: [18 February 2020](https://www.w3.org/TR/2020/WD-resource-timing-2-20200218/) +Latest publication: [11 May 2023](https://www.w3.org/TR/2023/CRD-resource-timing-20230511/) Reference Draft: [https://www.w3.org/TR/2016/WD-resource-timing-2-20161103/](https://www.w3.org/TR/2016/WD-resource-timing-2-20161103/) @@ -209,9 +200,9 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) -**[Navigation Timing](https://w3c.github.io/navigation-timing/)** +#### [Navigation Timing](https://w3c.github.io/navigation-timing/) -An interoperable means for site developers to collect real-world performance information from the user agent while loading the root document of a webpage. The user agent captures the end to end latency associated with loading a webpage from a web server. This includes the time associated with fetching the document from the network to the time associated to load the document within the user agent. +This specification defines an interface for web applications to access the complete timing information for navigation of a document. **Draft state:** [Working Draft](https://www.w3.org/TR/navigation-timing-2/) @@ -219,7 +210,7 @@ An interoperable means for site developers to collect real-world performance inf Note: after Level 2 of Navigation Timing is ratified, future development of new Navigation Timing features will be done within Resource Timing; Navigation Timing will be merged with Resource Timing. -Latest publication: [21 January 2020](https://www.w3.org/TR/2020/WD-navigation-timing-2-20200121/) +Latest publication: [07 June 2023](https://www.w3.org/TR/2023/WD-navigation-timing-2-20230607/) Reference Draft: [https://www.w3.org/TR/2015/WD-navigation-timing-2-20150120/](https://www.w3.org/TR/2015/WD-navigation-timing-2-20150120/) @@ -227,15 +218,15 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2013/01/webperf](https://www.w3.org/2013/01/webperf). -**[User Timing](https://w3c.github.io/user-timing/)** +#### [User Timing](https://w3c.github.io/user-timing/) An interoperable means for site developers to capture timing information with a developer supplied name. The user agent captures the time stamp at the point and time specified in the code executing in the user agent. -**Draft state:** [Working Draft](https://www.w3.org/TR/user-timing-3/) +**Draft state:** [Candidate Recommendation Draft](https://www.w3.org/TR/user-timing/) **Next Recommendation expected completion:** Living Standard -Latest publication: [26 March 2020](https://www.w3.org/TR/2020/WD-user-timing-3-20200326/) +Latest publication: [26 April 2023](https://www.w3.org/TR/2023/CRD-user-timing-20230426/) Reference Draft: [https://www.w3.org/TR/2019/WD-user-timing-3-20190305/](https://www.w3.org/TR/2019/WD-user-timing-3-20190305/) @@ -243,31 +234,15 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2018/09/webperf](https://www.w3.org/2018/09/webperf) -**[Page Visibility](https://w3c.github.io/page-visibility/)** - -An interoperable means for site developers to programmatically determine the current visibility of a document and be notified of visibility changes. - -**Draft state:** [Proposed Recommendation](https://www.w3.org/TR/page-visibility-2/) - -**Next Recommendation expected completion:** Q1 2021 - -Latest publication: [17 October 2017](https://www.w3.org/TR/2017/PR-page-visibility-2-20171017/) - -Reference Draft: [https://www.w3.org/TR/2017/CR-page-visibility-2-20170328/](https://www.w3.org/TR/2017/CR-page-visibility-2-20170328/) - -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Mar/0003.html) on 29 March 2017 ended on 27 May 2017 - -Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) - -**[Beacon](https://w3c.github.io/beacon/)** +#### [Beacon](https://w3c.github.io/beacon/) An interoperable API for site developers to asynchronously transfer data from the user agent to a web server, with a guarantee from the user agent that the data will be eventually sent. -**Draft state:** [Candidate Recommendation](https://www.w3.org/TR/beacon/) +**Draft state:** [Candidate Recommendation Draft](https://www.w3.org/TR/beacon/) -**Next Recommendation expected completion:** Q1 2021 +**Next Recommendation expected completion:** Living Standard -Latest publication: [13 April 2017](https://www.w3.org/TR/2017/CR-beacon-20170413/) +Latest publication: [03 August 2022](https://www.w3.org/TR/2022/CRD-beacon-20220803/) Reference Draft: [https://www.w3.org/TR/2017/CR-beacon-20170413/](https://www.w3.org/TR/2017/CR-beacon-20170413/) @@ -275,15 +250,15 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). -**[Cooperative Scheduling of Background Tasks](https://w3c.github.io/requestidlecallback/)** +#### [Cooperative Scheduling of Background Tasks](https://w3c.github.io/requestidlecallback/) An API that web page authors can use to cooperatively schedule background tasks such that they do not introduce delays to other high priority tasks that share the same event loop, such as input processing, animations and frame compositing. -**Draft state:** [Proposed Recommendation](https://www.w3.org/TR/requestidlecallback/) +**Draft state:** [Working Draft](https://www.w3.org/TR/requestidlecallback/) -**Next Recommendation expected completion:** Q2 2021 +**Next Recommendation expected completion:** Expected to move to Living Standard -Latest publication: [10 October 2017](https://www.w3.org/TR/2017/PR-requestidlecallback-20171010/) +Latest publication: [28 June 2022](https://www.w3.org/TR/2022/WD-requestidlecallback-20220628/) Reference Draft: [https://www.w3.org/TR/2017/CR-requestidlecallback-20170131/](https://www.w3.org/TR/2017/CR-requestidlecallback-20170131/) @@ -291,13 +266,13 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). -**[Long Task](https://w3c.github.io/longtasks/)** +#### [Long Task](https://w3c.github.io/longtasks/) This specification defines an API that web page authors can use to detect presence of "long tasks" that monopolize the UI thread for extended periods of time and block other critical tasks from being executed - e.g. reacting to user input. **Draft state:** [Working Draft](https://www.w3.org/TR/longtasks-1/) -**Next Recommendation expected completion:** Q4 2021 +**Next Recommendation expected completion:** Latest publication: [07 September 2017](https://www.w3.org/TR/2017/WD-longtasks-1-20170907/) @@ -307,13 +282,13 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). -**[Paint Timing](https://w3c.github.io/paint-timing/)** +#### [Paint Timing](https://w3c.github.io/paint-timing/) An interoperable API for site developers to capture the set of key moments during pageload - e.g. first paint and first contentful paint. **Draft state:** [Working Draft](https://www.w3.org/TR/paint-timing/) -**Next Recommendation expected completion:** Q1 2021 +**Next Recommendation expected completion:** Latest publication: [07 September 2017](https://www.w3.org/TR/2017/WD-paint-timing-20170907/) @@ -323,15 +298,15 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) -**[Server Timing](https://w3c.github.io/server-timing/)** +#### [Server Timing](https://w3c.github.io/server-timing/) This specification enables a server to communicate performance metrics about the request-response cycle to the user agent. It also standardizes a JavaScript interface to enable applications to collect, process, and act on these metrics to optimize application delivery. **Draft state:** [Working Draft](https://www.w3.org/TR/server-timing/) -**Next Recommendation expected completion:** Q2 2021 +**Next Recommendation expected completion:** -Latest publication: [20 January 2020](https://www.w3.org/TR/2020/WD-server-timing-20200120/) +Latest publication: [11 April 2023](https://www.w3.org/TR/2023/WD-server-timing-20230411/) Reference Draft: [https://www.w3.org/TR/2017/WD-server-timing-20170713/](https://www.w3.org/TR/2017/WD-server-timing-20170713/) @@ -339,15 +314,15 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) -**[Device Memory](https://w3c.github.io/device-memory/)** +#### [Device Memory](https://w3c.github.io/device-memory/) This specification defines a JavaScript API and HTTP Client Hint header to surface device capability for memory — i.e. device RAM, in order to enable web apps to customize content depending on device memory constraints. **Draft state:** [Working Draft](https://www.w3.org/TR/device-memory/) -**Next Recommendation expected completion:** Q4 2021 +**Next Recommendation expected completion:** -Latest publication: [25-Sep-2018](https://www.w3.org/TR/2018/WD-device-memory-1-20180925/) +Latest publication: [22 July 2022](https://www.w3.org/TR/2022/WD-device-memory-1-20220722/) Reference Draft: [https://www.w3.org/TR/2018/WD-device-memory-1-20180925/](https://www.w3.org/TR/2018/WD-device-memory-1-20180925/) @@ -355,15 +330,15 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2018/09/webperf/](https://www.w3.org/2018/09/webperf/) -**[Reporting](https://w3c.github.io/reporting/)** +#### [Reporting](https://w3c.github.io/reporting/) This specification defines a generic reporting framework which allows web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner. -**Draft state:** [Working Draft](https://www.w3.org/TR/reporting-1/) +**Draft state:** [Working Draft](https://www.w3.org/TR/reporting/) -**Next Recommendation expected completion:** Q4 2021 +**Next Recommendation expected completion:** -Latest publication: [25-Sep-2018](https://www.w3.org/TR/2018/WD-reporting-1-20180925/) +Latest publication: [12 May 2023](https://www.w3.org/TR/2023/WD-reporting-1-20230512/) Reference Draft: [https://www.w3.org/TR/2016/WD-reporting-1-20160407/](https://www.w3.org/TR/2016/WD-reporting-1-20160407/) @@ -371,13 +346,13 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2015/06/webperf](https://www.w3.org/2015/06/webperf). -**[Network Error Logging](https://w3c.github.io/network-error-logging)** +#### [Network Error Logging](https://w3c.github.io/network-error-logging) This specification defines a mechanism that enables developers to declare a network error reporting policy for a web application. A user agent can use this policy to report encountered network errors that prevented it from successfully fetching requested resource. **Draft state:** [Working Draft](https://www.w3.org/TR/network-error-logging/) -**Next Recommendation expected completion:** Q4 2021 +**Next Recommendation expected completion:** Latest publication: [25-Sep-2018](https://www.w3.org/TR/2018/WD-network-error-logging-1-20180925/) @@ -392,7 +367,7 @@ Produced under Working Group Charter: [https://www.w3.org/2013/01/webperf](https The Group plans to transition the contents of the following past-deliverables to the WHATWG and publish them as a Note. -**[Resource Hints](https://w3c.github.io/resource-hints/)** +#### [Resource Hints](https://w3c.github.io/resource-hints/) This specification defines the dns-prefetch, preconnect, prefetch, and prerender relationships of the HTML Link Element (<link>). @@ -406,7 +381,7 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2013/01/webperf](https://www.w3.org/2013/01/webperf) -**[Preload](https://w3c.github.io/preload/)** +#### [Preload](https://w3c.github.io/preload/) This specification defines the link relation type preload, a declarative fetch primitive that initiates an early fetch and separates fetching from resource execution. @@ -420,6 +395,20 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). +#### [Page Visibility](https://w3c.github.io/page-visibility/) + +An interoperable means for site developers to programmatically determine the current visibility of a document and be notified of visibility changes. + +**Draft state:** [Proposed Recommendation](https://www.w3.org/TR/page-visibility-2/) + +Latest publication: [17 October 2017](https://www.w3.org/TR/2017/PR-page-visibility-2-20171017/) + +Reference Draft: [https://www.w3.org/TR/2017/CR-page-visibility-2-20170328/](https://www.w3.org/TR/2017/CR-page-visibility-2-20170328/) + +associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Mar/0003.html) on 29 March 2017 ended on 27 May 2017 + +Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) + ### Other Deliverables From c23c3d3b74db1face13c2db667b038508b561d0f Mon Sep 17 00:00:00 2001 From: Yoav Weiss Date: Fri, 30 Jun 2023 12:12:44 +0200 Subject: [PATCH 03/19] LCP and EventTiming --- charter_comments.md | 29 ++++++++++++++++++++++++++++- 1 file changed, 28 insertions(+), 1 deletion(-) diff --git a/charter_comments.md b/charter_comments.md index 4cc91af8..edafde78 100644 --- a/charter_comments.md +++ b/charter_comments.md @@ -89,7 +89,7 @@ Expires: 28 February 2023 * We should call out[ open privacy issues](https://github.com/w3c/resource-timing/issues?q=is%3Aissue+is%3Aopen+label%3Aprivacy-needs-resolution) and say that we strive to resolve them -# CURRENT CHARTER +# CHARTER DRAFT ## Scope @@ -362,6 +362,33 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2013/01/webperf](https://www.w3.org/2013/01/webperf) +#### [Event Timing](https://www.w3.org/TR/event-timing/) + +This specification defines an API that provides web page authors with insights into the latency of certain events triggered by user interactions. + +**Draft state:** [First Public Working Draft](https://www.w3.org/TR/event-timing/) + +**Next Recommendation expected completion:** + +Latest publication: [24 May 2022](https://www.w3.org/TR/2022/WD-event-timing-20220524/) + +Reference Draft: [https://www.w3.org/TR/2022/WD-event-timing-20220524/](https://www.w3.org/TR/2022/WD-event-timing-20220524/) + +Produced under Working Group Charter: [https://www.w3.org/2021/02/webperf.html](https://www.w3.org/2021/02/webperf.html) + +#### [Largest Contentful Paint](https://www.w3.org/TR/largest-contentful-paint/) + +This specification defines an API that enables monitoring the largest paint an element triggered on screen. + +**Draft state:** [First Public Working Draft](https://www.w3.org/TR/largest-contentful-paint/) + +**Next Recommendation expected completion:** + +Latest publication: [24 May 2022](https://www.w3.org/TR/2022/WD-largest-contentful-paint-20220524/) + +Reference Draft: [https://www.w3.org/TR/2022/WD-event-timing-20220524/)](https://www.w3.org/TR/2022/WD-event-timing-20220524/)) + +Produced under Working Group Charter: [https://www.w3.org/2021/02/webperf.html](https://www.w3.org/2021/02/webperf.html) ### Past Deliverables From 787ce5971c2aa7784b31f94fec4768c3ab7eafc3 Mon Sep 17 00:00:00 2001 From: Yoav Weiss Date: Fri, 30 Jun 2023 15:05:49 +0200 Subject: [PATCH 04/19] Privacy preserving measurement --- charter_comments.md | 36 ++++++++---------------------------- 1 file changed, 8 insertions(+), 28 deletions(-) diff --git a/charter_comments.md b/charter_comments.md index edafde78..04de4d2c 100644 --- a/charter_comments.md +++ b/charter_comments.md @@ -9,22 +9,7 @@ Expires: 28 February 2023 -* Scope/Themes - * Measurement - * Proposal to be "Privacy Preserving Measurement" - * Coordinate w/ IETF group similarly-named - * Scheduling - * Adaptation * Specs Changes - * Resource Hints - * Discontinued (from 2021 charter) - * Moving to HTML - * Repo doesn't mention this [https://w3c.github.io/resource-hints/](https://w3c.github.io/resource-hints/) - * Preload - * Discontinued (from 2021 charter) - * Moved to HTML - * Repo archived - * Spec mentions this + redirects [https://github.com/w3c/preload/](https://github.com/w3c/preload/) * Page Visibility * Discontinue (in 2023 charter) * Moved to HTML @@ -37,9 +22,7 @@ Expires: 28 February 2023 * Don't finalize to Rec, could incorporate Scheduling APIs * PaintTiming * EventTiming - * Listed as a repo, but not a deliverable/spec? * LCP - * Listed as a repo, but not a deliverable/spec? * Could incorporate ElementTiming? * Timing Names Entry Registry * New process for registries from W3C @@ -63,7 +46,6 @@ Expires: 28 February 2023 * Consider a move to HTML spec (same as rIC?) * JS self profiling [https://wicg.github.io/js-self-profiling/](https://wicg.github.io/js-self-profiling/) * Any recent updates? - * Priority Hints [https://github.com/WICG/priority-hints](https://github.com/WICG/priority-hints) * Page Lifecycle [https://github.com/WICG/page-lifecycle](https://github.com/WICG/page-lifecycle) * Intervention/Deprecation/Crash Reporting * [https://github.com/WICG/deprecation-reporting](https://github.com/WICG/deprecation-reporting) @@ -75,8 +57,6 @@ Expires: 28 February 2023 -* “Privacy preserving monitoring” - proposal from AlexC, to be discussed - * Potential collaboration with the IETF PPM WG * Sustainability - should it be covered in scope? No direct deliverables just yet * Lab tooling related browser interop - should it go back to being in scope? @@ -100,16 +80,16 @@ The Web Performance Working Group's scope of work includes user agent features a -* _Measurement \ -_The WG will deliver APIs to measure network and rendering performance, responsiveness and interactivity, memory and CPU use, application failures, and other aspects of the user’s experience, from the perspectives of both application loading and continuous user interaction. In particular, the group will deliver means to measure user experience metrics in popular web architectures, such as single-page apps, as well as means to collect those measurements. -* _Scheduling \ -_The WG will deliver APIs to enable developers to improve scheduling of application work as well as use of network resources, to minimize loading times and ensure ideal user experience. -* _Adaptation \ -_The WG will deliver APIs to enable developers to deliver resources adapted to the user’s device, preferences, conditions, or other circumstances. +* _Measurement_ +The WG will deliver APIs to measure network and rendering performance, responsiveness and interactivity, memory and CPU use, application failures, and other aspects of the user’s experience, from the perspectives of both application loading and continuous user interaction. In particular, the group will deliver means to measure user experience metrics in popular web architectures, such as single-page apps, as well as means to collect those measurements. Where possible, privacy-preserving measurement techniques will be explored. +* _Scheduling_ +The WG will deliver APIs to enable developers to improve scheduling of application work as well as use of network resources, to minimize loading times and ensure ideal user experience. +* _Adaptation_ +The WG will deliver APIs to enable developers to deliver resources adapted to the user’s device, preferences, conditions, or other circumstances. Such deliverables will apply to desktop and mobile browsers and other non-browser environments where appropriate, and will be consistent with Web technologies designed in other working groups including HTML, CSS, Web Application Security, Web Apps, Device and Sensors, and SVG. The Group will strive for its deliverables to be well-integrated with other specifications where appropriate. -In addition to developing Recommendation Track documents, the Web Performance Working Group may provide review of specifications from other Working Groups. +In addition to developing Recommendation Track documents, the Web Performance Working Group may provide specification review to other Groups, and will collaborate with relevant incubations. Such collaboration can include both web platform specifications as well as relevant developer conventions that align with the Working Group's scope and mission. ### Out of Scope @@ -495,7 +475,7 @@ This is the group responsible for ECMAScript standardization, and related ECMASc [Internet Engineering Task Force](https://www.ietf.org/) -The IETF is responsible for defining robust and secure protocols for Internet functionality, in particular HTTP. The Working Group should coordinate protocol-related work (e.g. profiles of hybi or HTTP) with the appropriate IETF WGs. +The IETF is responsible for defining robust and secure protocols for Internet functionality, in particular HTTP. The Working Group should coordinate protocol-related work (e.g. HTTP, Privacy-Preserving Measurement) with the appropriate IETF WGs. [Web Hypertext Application Technology Working Group (WHATWG)](https://whatwg.org/) From 2d17ee364321109b1b82fb680dd940d91096c317 Mon Sep 17 00:00:00 2001 From: Yoav Weiss Date: Fri, 30 Jun 2023 15:14:39 +0200 Subject: [PATCH 05/19] Rename charter draft doc --- charter_comments.md => charter_draft.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename charter_comments.md => charter_draft.md (100%) diff --git a/charter_comments.md b/charter_draft.md similarity index 100% rename from charter_comments.md rename to charter_draft.md From 22551cab75187ceda548ab884e513c605cf39956 Mon Sep 17 00:00:00 2001 From: Yoav Weiss Date: Fri, 30 Jun 2023 15:24:00 +0200 Subject: [PATCH 06/19] Planned work --- charter_draft.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/charter_draft.md b/charter_draft.md index 04de4d2c..b75f0c6b 100644 --- a/charter_draft.md +++ b/charter_draft.md @@ -138,6 +138,8 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). +Planned work: The specification defines time-related concepts beyond just high-resolution timers. It should be renamed to reflect that. + #### [Performance Timeline](https://w3c.github.io/performance-timeline/) This specification defines a unified interface to store and retrieve performance metric data. @@ -198,6 +200,8 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2013/01/webperf](https://www.w3.org/2013/01/webperf). +Planned work: The specification should be folded into the Resource Timing specification, on which it relies. + #### [User Timing](https://w3c.github.io/user-timing/) An interoperable means for site developers to capture timing information with a developer supplied name. The user agent captures the time stamp at the point and time specified in the code executing in the user agent. @@ -246,6 +250,8 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). +Planned work: The specification should be unified with other [Scheduling APIs](https://github.com/wicg/scheduling-apis), once they mature. + #### [Long Task](https://w3c.github.io/longtasks/) This specification defines an API that web page authors can use to detect presence of "long tasks" that monopolize the UI thread for extended periods of time and block other critical tasks from being executed - e.g. reacting to user input. @@ -262,6 +268,8 @@ associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). +Planned work: Expanding the API to include [long animation frames](https://github.com/w3c/longtasks/blob/main/loaf-explainer.md). + #### [Paint Timing](https://w3c.github.io/paint-timing/) An interoperable API for site developers to capture the set of key moments during pageload - e.g. first paint and first contentful paint. @@ -370,6 +378,8 @@ Reference Draft: [https://www.w3.org/TR/2022/WD-event-timing-20220524/)](https:/ Produced under Working Group Charter: [https://www.w3.org/2021/02/webperf.html](https://www.w3.org/2021/02/webperf.html) +Planned work: Should be folded into Paint Timing, alongside [Element Timing](https://wicg.github.io/element-timing/). + ### Past Deliverables The Group plans to transition the contents of the following past-deliverables to the WHATWG and publish them as a Note. From 17bda33070639ce77069f4c5532ceb7ca60a29ed Mon Sep 17 00:00:00 2001 From: Yoav Weiss Date: Fri, 30 Jun 2023 15:33:11 +0200 Subject: [PATCH 07/19] conventions --- charter_draft.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charter_draft.md b/charter_draft.md index b75f0c6b..3deb8dbe 100644 --- a/charter_draft.md +++ b/charter_draft.md @@ -89,7 +89,7 @@ The WG will deliver APIs to enable developers to deliver resources adapted to th Such deliverables will apply to desktop and mobile browsers and other non-browser environments where appropriate, and will be consistent with Web technologies designed in other working groups including HTML, CSS, Web Application Security, Web Apps, Device and Sensors, and SVG. The Group will strive for its deliverables to be well-integrated with other specifications where appropriate. -In addition to developing Recommendation Track documents, the Web Performance Working Group may provide specification review to other Groups, and will collaborate with relevant incubations. Such collaboration can include both web platform specifications as well as relevant developer conventions that align with the Working Group's scope and mission. +In addition to developing Recommendation Track documents, the Web Performance Working Group may provide specification review to other Groups, and will collaborate with relevant incubations. Such collaboration can be around web platform specifications, but can also include relevant developer or industry conventions, potentially applied in non-browser environments, as long as it's aligned with the Working Group's scope and mission. ### Out of Scope From b452d754cfa080d5e0b96742d15e3406c2ef5db5 Mon Sep 17 00:00:00 2001 From: Nic Jansma Date: Mon, 3 Jul 2023 11:05:10 -0400 Subject: [PATCH 08/19] Primer: Note work for 2023+ charter --- charter_draft.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/charter_draft.md b/charter_draft.md index 3deb8dbe..5c51fa82 100644 --- a/charter_draft.md +++ b/charter_draft.md @@ -431,9 +431,9 @@ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https The Group will maintain a [non-normative Primer document](https://w3c.github.io/perf-timing-primer/) to facilitate the understanding of the interrelationships between its deliverables. -Other non-normative documents may be created such as: - +* Planned work for the Primer for 2023+ charter: Updating it to [include new specs](https://github.com/w3c/web-performance/issues/54), remove deprecated ones and more. +Other non-normative documents may be created such as: * [Security and Privacy considerations for Performance APIs](https://w3c.github.io/perf-security-privacy/) * Test suites for each specification; From 7817cf962a59f1dff5ddd64c4ccf4d11ead903e7 Mon Sep 17 00:00:00 2001 From: Nic Jansma Date: Mon, 3 Jul 2023 11:05:39 -0400 Subject: [PATCH 09/19] README: Include all current and past specs, and incubations --- README.md | 30 +++++++++++++++++++++++++++--- 1 file changed, 27 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 5965841a..eceed003 100644 --- a/README.md +++ b/README.md @@ -11,13 +11,37 @@ GitHub repositories are linked from each specification. * https://w3c.github.io/resource-timing/ * https://w3c.github.io/navigation-timing/ * https://w3c.github.io/user-timing/ -* https://w3c.github.io/page-visibility/ * https://w3c.github.io/requestidlecallback/ * https://w3c.github.io/beacon/ -* https://w3c.github.io/resource-hints/ -* https://w3c.github.io/preload/ * https://w3c.github.io/server-timing/ * https://w3c.github.io/longtasks/ +* https://w3c.github.io/paint-timing/ +* https://w3c.github.io/device-memory/ +* https://w3c.github.io/reporting/ +* https://w3c.github.io/network-error-logging +* https://www.w3.org/TR/event-timing/ +* https://www.w3.org/TR/largest-contentful-paint/ + +Past Deliverables: + +* https://w3c.github.io/page-visibility/ +* https://w3c.github.io/resource-hints/ +* https://w3c.github.io/preload/ + +Incubations: + +* https://github.com/WICG/element-timing +* https://github.com/WICG/is-input-pending +* https://github.com/WICG/layout-instability +* https://github.com/WICG/performance-measure-memory +* https://github.com/WICG/netinfo/ +* https://github.com/WICG/unload-beacon +* https://github.com/WICG/scheduling-apis +* https://github.com/WICG/js-self-profiling/ +* https://github.com/WICG/page-lifecycle +* https://github.com/WICG/deprecation-reporting +* https://github.com/WICG/intervention-reporting +* https://github.com/WICG/crash-reporting Web Performance tests can be found in [web-platforms-tests][WPT]. From 331bf104bc589cc2099983c1785e6d7fc9e65a93 Mon Sep 17 00:00:00 2001 From: Nic Jansma Date: Mon, 3 Jul 2023 11:06:31 -0400 Subject: [PATCH 10/19] Charter: Upper-case Associated --- charter_draft.md | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/charter_draft.md b/charter_draft.md index 5c51fa82..afd0d061 100644 --- a/charter_draft.md +++ b/charter_draft.md @@ -134,7 +134,7 @@ Patent Review Draft (level 3): [https://www.w3.org/TR/2020/WD-hr-time-3-20201001 Reference Draft (level 2): [https://www.w3.org/TR/2018/CR-hr-time-2-20180301/](https://www.w3.org/TR/2018/CR-hr-time-2-20180301/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2018Mar/0000.html) on 01 March 2018 ended on 30 April 2018 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2018Mar/0000.html) on 01 March 2018 ended on 30 April 2018 Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). @@ -152,7 +152,7 @@ Latest publication: [15 November 2022](https://www.w3.org/TR/2022/CRD-performanc Reference Draft: [https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/](https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2016Dec/0001.html) on 08 December 2016 ended on 06 February 2017 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2016Dec/0001.html) on 08 December 2016 ended on 06 February 2017 Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). @@ -166,7 +166,7 @@ Latest publication: [30 March 2017](https://www.w3.org/TR/2017/CR-resource-timin Reference Draft: [https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/](https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Mar/0005.html) on 30 March 2017 ended on 29 May 2017 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Mar/0005.html) on 30 March 2017 ended on 29 May 2017 Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). @@ -178,7 +178,7 @@ Latest publication: [11 May 2023](https://www.w3.org/TR/2023/CRD-resource-timing Reference Draft: [https://www.w3.org/TR/2016/WD-resource-timing-2-20161103/](https://www.w3.org/TR/2016/WD-resource-timing-2-20161103/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2016Nov/0005.html) on 03 November 2016 ended on 02 April 2017 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2016Nov/0005.html) on 03 November 2016 ended on 02 April 2017 Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) @@ -196,7 +196,7 @@ Latest publication: [07 June 2023](https://www.w3.org/TR/2023/WD-navigation-timi Reference Draft: [https://www.w3.org/TR/2015/WD-navigation-timing-2-20150120/](https://www.w3.org/TR/2015/WD-navigation-timing-2-20150120/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2013Jan/0014.html) on 31 January 2013 ended on 30 June 2013 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2013Jan/0014.html) on 31 January 2013 ended on 30 June 2013 Produced under Working Group Charter: [https://www.w3.org/2013/01/webperf](https://www.w3.org/2013/01/webperf). @@ -214,7 +214,7 @@ Latest publication: [26 April 2023](https://www.w3.org/TR/2023/CRD-user-timing-2 Reference Draft: [https://www.w3.org/TR/2019/WD-user-timing-3-20190305/](https://www.w3.org/TR/2019/WD-user-timing-3-20190305/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2019Mar/0000.html) on 05 March 2019 ended on 02 August 2019 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2019Mar/0000.html) on 05 March 2019 ended on 02 August 2019 Produced under Working Group Charter: [https://www.w3.org/2018/09/webperf](https://www.w3.org/2018/09/webperf) @@ -230,7 +230,7 @@ Latest publication: [03 August 2022](https://www.w3.org/TR/2022/CRD-beacon-20220 Reference Draft: [https://www.w3.org/TR/2017/CR-beacon-20170413/](https://www.w3.org/TR/2017/CR-beacon-20170413/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Apr/0004.html) on 13 April 2017 ended on 12 June 2017 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Apr/0004.html) on 13 April 2017 ended on 12 June 2017 Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). @@ -246,7 +246,7 @@ Latest publication: [28 June 2022](https://www.w3.org/TR/2022/WD-requestidlecall Reference Draft: [https://www.w3.org/TR/2017/CR-requestidlecallback-20170131/](https://www.w3.org/TR/2017/CR-requestidlecallback-20170131/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Feb/0000.html) on 02 February 2017 ended on 01 April 2017 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Feb/0000.html) on 02 February 2017 ended on 01 April 2017 Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). @@ -264,7 +264,7 @@ Latest publication: [07 September 2017](https://www.w3.org/TR/2017/WD-longtasks- Reference Draft: [https://www.w3.org/TR/2017/WD-longtasks-1-20170907/](https://www.w3.org/TR/2017/WD-longtasks-1-20170907/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Dec/0001.html) on 07 December 2017 ended on 04 February 2018 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Dec/0001.html) on 07 December 2017 ended on 04 February 2018 Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). @@ -282,7 +282,7 @@ Latest publication: [07 September 2017](https://www.w3.org/TR/2017/WD-paint-timi Reference Draft: [https://www.w3.org/TR/2017/WD-paint-timing-20170907/](https://www.w3.org/TR/2017/WD-paint-timing-20170907/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Dec/0001.html) on 07 December 2017 ended on 04 February 2018 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Dec/0001.html) on 07 December 2017 ended on 04 February 2018 Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) @@ -298,7 +298,7 @@ Latest publication: [11 April 2023](https://www.w3.org/TR/2023/WD-server-timing- Reference Draft: [https://www.w3.org/TR/2017/WD-server-timing-20170713/](https://www.w3.org/TR/2017/WD-server-timing-20170713/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Jul/0005.html) on 13 July 2017 ended on 10 December 2017 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Jul/0005.html) on 13 July 2017 ended on 10 December 2017 Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) @@ -314,7 +314,7 @@ Latest publication: [22 July 2022](https://www.w3.org/TR/2022/WD-device-memory-1 Reference Draft: [https://www.w3.org/TR/2018/WD-device-memory-1-20180925/](https://www.w3.org/TR/2018/WD-device-memory-1-20180925/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2018Sep/0003.html) on 25-Sep-2018 ended on 22-Feb-2019 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2018Sep/0003.html) on 25-Sep-2018 ended on 22-Feb-2019 Produced under Working Group Charter: [https://www.w3.org/2018/09/webperf/](https://www.w3.org/2018/09/webperf/) @@ -330,7 +330,7 @@ Latest publication: [12 May 2023](https://www.w3.org/TR/2023/WD-reporting-1-2023 Reference Draft: [https://www.w3.org/TR/2016/WD-reporting-1-20160407/](https://www.w3.org/TR/2016/WD-reporting-1-20160407/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2016Apr/0001.html) on 7 April 2016 ended on 4 September 2016 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2016Apr/0001.html) on 7 April 2016 ended on 4 September 2016 Produced under Working Group Charter: [https://www.w3.org/2015/06/webperf](https://www.w3.org/2015/06/webperf). @@ -346,7 +346,7 @@ Latest publication: [25-Sep-2018](https://www.w3.org/TR/2018/WD-network-error-lo Reference Draft: [https://www.w3.org/TR/2014/WD-navigation-error-logging-20140211/](https://www.w3.org/TR/2014/WD-navigation-error-logging-20140211/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2014Feb/0008.html) on 12-Feb-2014 ended on 12-Jul-2014 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2014Feb/0008.html) on 12-Feb-2014 ended on 12-Jul-2014 Produced under Working Group Charter: [https://www.w3.org/2013/01/webperf](https://www.w3.org/2013/01/webperf) @@ -394,7 +394,7 @@ Latest publication: [02 July 2019](https://www.w3.org/TR/2019/WD-resource-hints- Reference Draft: [https://www.w3.org/TR/2014/WD-resource-hints-20141021/](https://www.w3.org/TR/2014/WD-resource-hints-20141021/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2014Oct/0006.html) on 23 October 2014 ended on 20 March 2015 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2014Oct/0006.html) on 23 October 2014 ended on 20 March 2015 Produced under Working Group Charter: [https://www.w3.org/2013/01/webperf](https://www.w3.org/2013/01/webperf) @@ -408,7 +408,7 @@ Latest publication: [26 June 2019](https://www.w3.org/TR/2019/CR-preload-2019062 Reference Draft: [https://www.w3.org/TR/2017/CR-preload-20171026/](https://www.w3.org/TR/2017/CR-preload-20171026/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Oct/0007.html) on 26 October 2017 ended on 25 December 2017 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Oct/0007.html) on 26 October 2017 ended on 25 December 2017 Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). @@ -422,7 +422,7 @@ Latest publication: [17 October 2017](https://www.w3.org/TR/2017/PR-page-visibil Reference Draft: [https://www.w3.org/TR/2017/CR-page-visibility-2-20170328/](https://www.w3.org/TR/2017/CR-page-visibility-2-20170328/) -associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Mar/0003.html) on 29 March 2017 ended on 27 May 2017 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Mar/0003.html) on 29 March 2017 ended on 27 May 2017 Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) From 96a95bd23f5c62b67bf50cb6f43d401d846e5d61 Mon Sep 17 00:00:00 2001 From: Nic Jansma Date: Mon, 3 Jul 2023 11:07:28 -0400 Subject: [PATCH 11/19] Charter: Note where Past specs have been moved to --- charter_draft.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/charter_draft.md b/charter_draft.md index afd0d061..a9ca2455 100644 --- a/charter_draft.md +++ b/charter_draft.md @@ -398,6 +398,8 @@ Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2013/01/webperf](https://www.w3.org/2013/01/webperf) +Moved to the [HTML spec](https://html.spec.whatwg.org//multipage/links.html#linkTypes). + #### [Preload](https://w3c.github.io/preload/) This specification defines the link relation type preload, a declarative fetch primitive that initiates an early fetch and separates fetching from resource execution. @@ -412,6 +414,8 @@ Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). +Moved to the [HTML spec](https://html.spec.whatwg.org/multipage/links.html#link-type-preload). + #### [Page Visibility](https://w3c.github.io/page-visibility/) An interoperable means for site developers to programmatically determine the current visibility of a document and be notified of visibility changes. @@ -426,6 +430,7 @@ Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) +Moved to the [HTML spec](https://html.spec.whatwg.org/multipage/interaction.html#page-visibility). ### Other Deliverables From ab47d8f68dff3aad1520f97c51fdcdeedb973cc6 Mon Sep 17 00:00:00 2001 From: Yoav Weiss Date: Thu, 6 Jul 2023 15:38:37 +0200 Subject: [PATCH 12/19] Privacy issues --- charter_draft.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/charter_draft.md b/charter_draft.md index a9ca2455..76da884c 100644 --- a/charter_draft.md +++ b/charter_draft.md @@ -508,6 +508,12 @@ The group also welcomes non-Members to contribute technical submissions for cons Participants in the group are required (by the [W3C Process](https://www.w3.org/Consortium/Process/#ParticipationCriteria)) to follow the W3C [Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/). +## Open privacy issues + +The following WG deliverables currently have a few open issues related to privacy - [Resource Timing](https://github.com/w3c/resource-timing/issues?q=is%3Aissue+is%3Aopen+label%3Aprivacy-needs-resolution), [High Resolution time](https://github.com/w3c/hr-time/issues/79), and [Reporting](https://github.com/w3c/reporting/issues?q=is%3Aissue+is%3Aopen+label%3Aprivacy-tracker). + +The WG will work with the relevant stake holders and strive to resolve those issues. + ## Communication Technical discussions for this Working Group are conducted in [public](https://www.w3.org/2020/Process-20200915/#confidentiality-levels). Meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed on a public repository, and may permit direct public contribution requests. From ed5803c84c47d1a38d32d28356b32dac3c3d9b4a Mon Sep 17 00:00:00 2001 From: Nic Jansma Date: Thu, 6 Jul 2023 10:07:37 -0400 Subject: [PATCH 13/19] Charter: Work for the Security and Privacy document --- charter_draft.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/charter_draft.md b/charter_draft.md index a9ca2455..b8623213 100644 --- a/charter_draft.md +++ b/charter_draft.md @@ -432,15 +432,18 @@ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https Moved to the [HTML spec](https://html.spec.whatwg.org/multipage/interaction.html#page-visibility). + ### Other Deliverables -The Group will maintain a [non-normative Primer document](https://w3c.github.io/perf-timing-primer/) to facilitate the understanding of the interrelationships between its deliverables. +The Group maintains two non-normative documents: -* Planned work for the Primer for 2023+ charter: Updating it to [include new specs](https://github.com/w3c/web-performance/issues/54), remove deprecated ones and more. +* A [Primer for Web Performance Timing APIs](https://w3c.github.io/perf-timing-primer/) document to facilitate the understanding of the interrelationships between its deliverables. + * Planned work: Updating it to [include new specs](https://github.com/w3c/web-performance/issues/54), remove deprecated ones and more. +* A [Performance APIs, Security and Privacy](https://w3c.github.io/perf-security-privacy/) document + * Planned work: [Reviewing and updating the content](https://github.com/w3c/web-performance/issues/46), and adding a section on the principals and value of performance measurements. Other non-normative documents may be created such as: -* [Security and Privacy considerations for Performance APIs](https://w3c.github.io/perf-security-privacy/) * Test suites for each specification; * Use cases documents to support development and exploration of performance-critical web platform features and APIs; * Primer or Best Practice documents to support web developers when designing applications with performance in mind; From ec59be5c36068b8339653cb07338785624243c65 Mon Sep 17 00:00:00 2001 From: Yoav Weiss Date: Fri, 7 Jul 2023 15:17:30 +0200 Subject: [PATCH 14/19] HAR --- charter_draft.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/charter_draft.md b/charter_draft.md index 14d5344e..f0618c23 100644 --- a/charter_draft.md +++ b/charter_draft.md @@ -450,6 +450,8 @@ Other non-normative documents may be created such as: * Developer and user guides for its normative specifications; * Best practice document explaining how data is commonly gathered between the client and the server. +The WG will also explore the possibility of renewing work on the [HAR file format](https://w3c.github.io/web-performance/specs/HAR/Overview.html). + ## Coordination From 8dc9f1be3a040ec5cad6f2ac66325024305dbaa7 Mon Sep 17 00:00:00 2001 From: caribouW3 Date: Fri, 7 Jul 2023 16:09:04 +0200 Subject: [PATCH 15/19] Update charter_draft.md --- charter_draft.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/charter_draft.md b/charter_draft.md index f0618c23..63df0787 100644 --- a/charter_draft.md +++ b/charter_draft.md @@ -150,9 +150,9 @@ This specification defines a unified interface to store and retrieve performance Latest publication: [15 November 2022](https://www.w3.org/TR/2022/CRD-performance-timeline-20221115/) -Reference Draft: [https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/](https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/) +Reference Draft: [https://www.w3.org/TR/2021/CR-performance-timeline-20211202/]([https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/](https://www.w3.org/TR/2021/CR-performance-timeline-20211202/)) -Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2016Dec/0001.html) on 08 December 2016 ended on 06 February 2017 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2021Dec/0001.html) on 02 December 2021 ended on 31 January 2022 Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). From 3ee5f7271e30d8411c22333151f02e4c54f14f71 Mon Sep 17 00:00:00 2001 From: caribouW3 Date: Fri, 7 Jul 2023 16:30:34 +0200 Subject: [PATCH 16/19] Update charter_draft.md --- charter_draft.md | 38 ++++++++++++++------------------------ 1 file changed, 14 insertions(+), 24 deletions(-) diff --git a/charter_draft.md b/charter_draft.md index 63df0787..3f720ddf 100644 --- a/charter_draft.md +++ b/charter_draft.md @@ -150,37 +150,27 @@ This specification defines a unified interface to store and retrieve performance Latest publication: [15 November 2022](https://www.w3.org/TR/2022/CRD-performance-timeline-20221115/) -Reference Draft: [https://www.w3.org/TR/2021/CR-performance-timeline-20211202/]([https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/](https://www.w3.org/TR/2021/CR-performance-timeline-20211202/)) +Reference Draft: [https://www.w3.org/TR/2021/CR-performance-timeline-20211202/](https://www.w3.org/TR/2021/CR-performance-timeline-20211202/)) Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2021Dec/0001.html) on 02 December 2021 ended on 31 January 2022 -Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). +Produced under Working Group Charter: [https://www.w3.org/2021/02/webperf.html](https://www.w3.org/2021/02/webperf.html). #### [Resource Timing](https://w3c.github.io/resource-timing/) This specification defines an interface for web applications to access the complete timing information for resources in a document or in a worker. -**Level 1 Draft state:** [Candidate Recommendation](https://www.w3.org/TR/resource-timing-1/) - -Latest publication: [30 March 2017](https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/) - -Reference Draft: [https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/](https://www.w3.org/TR/2017/CR-resource-timing-1-20170330/) - -Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2017Mar/0005.html) on 30 March 2017 ended on 29 May 2017 - -Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf). - -**Level 2 Draft state:** [Candidate Recommendation Draft](https://www.w3.org/TR/resource-timing/) +**Draft state:** [Candidate Recommendation Draft](https://www.w3.org/TR/resource-timing/) **Next Recommendation expected completion:** Living Standard Latest publication: [11 May 2023](https://www.w3.org/TR/2023/CRD-resource-timing-20230511/) -Reference Draft: [https://www.w3.org/TR/2016/WD-resource-timing-2-20161103/](https://www.w3.org/TR/2016/WD-resource-timing-2-20161103/) +Reference Draft: [https://www.w3.org/TR/2022/CR-resource-timing-20221004/](https://www.w3.org/TR/2022/CR-resource-timing-20221004/) -Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2016Nov/0005.html) on 03 November 2016 ended on 02 April 2017 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2022Oct/0000.html) on 04 October 2022 ended on 03 December 2022 -Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https://www.w3.org/2016/07/webperf) +Produced under Working Group Charter: [https://www.w3.org/2021/02/webperf.html](https://www.w3.org/2021/02/webperf.html). #### [Navigation Timing](https://w3c.github.io/navigation-timing/) @@ -212,11 +202,11 @@ An interoperable means for site developers to capture timing information with a Latest publication: [26 April 2023](https://www.w3.org/TR/2023/CRD-user-timing-20230426/) -Reference Draft: [https://www.w3.org/TR/2019/WD-user-timing-3-20190305/](https://www.w3.org/TR/2019/WD-user-timing-3-20190305/) +Reference Draft: [https://www.w3.org/TR/2021/CR-user-timing-20211202/](https://www.w3.org/TR/2021/CR-user-timing-20211202/) -Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2019Mar/0000.html) on 05 March 2019 ended on 02 August 2019 +Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/2021Dec/0000.html) on 02 December 2021 ended on 31 January 2022 -Produced under Working Group Charter: [https://www.w3.org/2018/09/webperf](https://www.w3.org/2018/09/webperf) +Produced under Working Group Charter: [https://www.w3.org/2021/02/webperf.html](https://www.w3.org/2021/02/webperf.html). #### [Beacon](https://w3c.github.io/beacon/) @@ -252,7 +242,7 @@ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https Planned work: The specification should be unified with other [Scheduling APIs](https://github.com/wicg/scheduling-apis), once they mature. -#### [Long Task](https://w3c.github.io/longtasks/) +#### [Long Tasks API](https://w3c.github.io/longtasks/) This specification defines an API that web page authors can use to detect presence of "long tasks" that monopolize the UI thread for extended periods of time and block other critical tasks from being executed - e.g. reacting to user input. @@ -278,7 +268,7 @@ An interoperable API for site developers to capture the set of key moments durin **Next Recommendation expected completion:** -Latest publication: [07 September 2017](https://www.w3.org/TR/2017/WD-paint-timing-20170907/) +Latest publication: [03 July 2023](https://www.w3.org/TR/2023/WD-paint-timing-20230703/) Reference Draft: [https://www.w3.org/TR/2017/WD-paint-timing-20170907/](https://www.w3.org/TR/2017/WD-paint-timing-20170907/) @@ -318,7 +308,7 @@ Associated [Call for Exclusion](https://lists.w3.org/Archives/Member/member-cfe/ Produced under Working Group Charter: [https://www.w3.org/2018/09/webperf/](https://www.w3.org/2018/09/webperf/) -#### [Reporting](https://w3c.github.io/reporting/) +#### [Reporting API](https://w3c.github.io/reporting/) This specification defines a generic reporting framework which allows web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner. @@ -358,7 +348,7 @@ This specification defines an API that provides web page authors with insights i **Next Recommendation expected completion:** -Latest publication: [24 May 2022](https://www.w3.org/TR/2022/WD-event-timing-20220524/) +Latest publication: [03 July 2022](https://www.w3.org/TR/2023/WD-event-timing-20230703/) Reference Draft: [https://www.w3.org/TR/2022/WD-event-timing-20220524/](https://www.w3.org/TR/2022/WD-event-timing-20220524/) @@ -374,7 +364,7 @@ This specification defines an API that enables monitoring the largest paint an e Latest publication: [24 May 2022](https://www.w3.org/TR/2022/WD-largest-contentful-paint-20220524/) -Reference Draft: [https://www.w3.org/TR/2022/WD-event-timing-20220524/)](https://www.w3.org/TR/2022/WD-event-timing-20220524/)) +Reference Draft: [https://www.w3.org/TR/2022/WD-largest-contentful-paint-20220524/)](https://www.w3.org/TR/2022/WD-largest-contentful-paint-20220524/)) Produced under Working Group Charter: [https://www.w3.org/2021/02/webperf.html](https://www.w3.org/2021/02/webperf.html) From abc813c68f83f091e7f167015e567e9e7ec277f4 Mon Sep 17 00:00:00 2001 From: Nic Jansma Date: Sun, 22 Sep 2024 14:56:16 -0400 Subject: [PATCH 17/19] Linted --- .markdownlint.json | 7 ++++++ charter_draft.md | 61 ++++++++++++---------------------------------- 2 files changed, 23 insertions(+), 45 deletions(-) create mode 100644 .markdownlint.json diff --git a/.markdownlint.json b/.markdownlint.json new file mode 100644 index 00000000..39cf660b --- /dev/null +++ b/.markdownlint.json @@ -0,0 +1,7 @@ +{ + "default": true, + "MD007": { "indent": 4 }, + "MD013": false, + "MD025": false, + "MD033": false +} \ No newline at end of file diff --git a/charter_draft.md b/charter_draft.md index 3f720ddf..d48b4cbb 100644 --- a/charter_draft.md +++ b/charter_draft.md @@ -1,20 +1,17 @@ # W3C Web Performance Working Group - # 2023 Charter Comments 2021 Charter: [https://www.w3.org/2021/02/webperf.html](https://www.w3.org/2021/02/webperf.html) Expires: 28 February 2023 - - * Specs Changes * Page Visibility * Discontinue (in 2023 charter) * Moved to HTML * Repo archived (but doesn't mention why) - * Spec says discontinued [https://github.com/w3c/page-visibility/](https://github.com/w3c/page-visibility/) + * Spec says discontinued [https://github.com/w3c/page-visibility/](https://github.com/w3c/page-visibility/) * Spec should redirect? * Beacon * Don't finalize to Rec, could incorporate Unload/Pending beacon into it @@ -27,59 +24,49 @@ Expires: 28 February 2023 * Timing Names Entry Registry * New process for registries from W3C * Incubations - * ElementTiming [https://github.com/WICG/element-timing](https://github.com/WICG/element-timing) + * ElementTiming [https://github.com/WICG/element-timing](https://github.com/WICG/element-timing) * Move into LCP? Or at least bring into WG as LCP already is. * Merge parts into LCP, parts into PaintTiming - * isInputPending [https://github.com/WICG/is-input-pending](https://github.com/WICG/is-input-pending) + * isInputPending [https://github.com/WICG/is-input-pending](https://github.com/WICG/is-input-pending) * Any recent updates? - * Layout Instability [https://github.com/WICG/layout-instability](https://github.com/WICG/layout-instability) + * Layout Instability [https://github.com/WICG/layout-instability](https://github.com/WICG/layout-instability) * Discussion in early 2022 around lessons from implementation * Barriers to adoption? * Mozilla: Neutral (implementation, performance concerns) * Apple: Opposed (circa 2019) (concerns on bookkeeping, cost at runtime, implementation, animations/scrolling not handled well) - * Memory Measurement [https://github.com/WICG/performance-measure-memory](https://github.com/WICG/performance-measure-memory) - * Network Info [https://github.com/WICG/netinfo/](https://github.com/WICG/netinfo/) - * Unload Beacon [https://github.com/WICG/unload-beacon](https://github.com/WICG/unload-beacon) + * Memory Measurement [https://github.com/WICG/performance-measure-memory](https://github.com/WICG/performance-measure-memory) + * Network Info [https://github.com/WICG/netinfo/](https://github.com/WICG/netinfo/) + * Unload Beacon [https://github.com/WICG/unload-beacon](https://github.com/WICG/unload-beacon) * Incorporate into Beacon? - * Scheduling APIs [https://github.com/WICG/scheduling-apis](https://github.com/WICG/scheduling-apis) + * Scheduling APIs [https://github.com/WICG/scheduling-apis](https://github.com/WICG/scheduling-apis) * Incorporate into Cooperative Scheduling of Background Tasks? * Consider a move to HTML spec (same as rIC?) - * JS self profiling [https://wicg.github.io/js-self-profiling/](https://wicg.github.io/js-self-profiling/) + * JS self profiling [https://wicg.github.io/js-self-profiling/](https://wicg.github.io/js-self-profiling/) * Any recent updates? - * Page Lifecycle [https://github.com/WICG/page-lifecycle](https://github.com/WICG/page-lifecycle) + * Page Lifecycle [https://github.com/WICG/page-lifecycle](https://github.com/WICG/page-lifecycle) * Intervention/Deprecation/Crash Reporting * [https://github.com/WICG/deprecation-reporting](https://github.com/WICG/deprecation-reporting) * [https://github.com/WICG/intervention-reporting](https://github.com/WICG/intervention-reporting) - * [https://github.com/WICG/crash-reporting](https://github.com/WICG/crash-reporting) - + * [https://github.com/WICG/crash-reporting](https://github.com/WICG/crash-reporting) ## TPAC 22 discussions - - * Sustainability - should it be covered in scope? No direct deliverables just yet * Lab tooling related browser interop - should it go back to being in scope? - ## Other questions - - * HR-Time is not just about high resolution timers, but defines time in general. Should we rename it? -* We should call out[ open privacy issues](https://github.com/w3c/resource-timing/issues?q=is%3Aissue+is%3Aopen+label%3Aprivacy-needs-resolution) and say that we strive to resolve them - +* We should call out [open privacy issues](https://github.com/w3c/resource-timing/issues?q=is%3Aissue+is%3Aopen+label%3Aprivacy-needs-resolution) and say that we strive to resolve them # CHARTER DRAFT - ## Scope Web developers are building sophisticated applications where application performance is a critical feature. Web developers want the ability to observe the performance characteristics of their applications, and they want the ability to write more efficient applications, using well-defined interoperable methods. Their methods must be both secure and privacy-enabling by design, using well-defined interoperable methods that conform to the current Web browser security model. The Web Performance Working Group's scope of work includes user agent features and APIs to observe and improve various aspects of application performance: - - * _Measurement_ The WG will deliver APIs to measure network and rendering performance, responsiveness and interactivity, memory and CPU use, application failures, and other aspects of the user’s experience, from the perspectives of both application loading and continuous user interaction. In particular, the group will deliver means to measure user experience metrics in popular web architectures, such as single-page apps, as well as means to collect those measurements. Where possible, privacy-preserving measurement techniques will be explored. * _Scheduling_ @@ -91,16 +78,12 @@ Such deliverables will apply to desktop and mobile browsers and other non-browse In addition to developing Recommendation Track documents, the Web Performance Working Group may provide specification review to other Groups, and will collaborate with relevant incubations. Such collaboration can be around web platform specifications, but can also include relevant developer or industry conventions, potentially applied in non-browser environments, as long as it's aligned with the Working Group's scope and mission. - ### Out of Scope The following features are out of scope, and will not be addressed by this working group. - - * performance data analysis techniques or algorithms. - ### Success Criteria In order to advance to [Proposed Recommendation](https://www.w3.org/2020/Process-20200915/#RecsPR), each specification is expected to have at least two independent implementations of each feature defined in the specification. @@ -109,13 +92,11 @@ Each specification should contain a section detailing any [known security](https Normative specification changes are generally expected to have a corresponding set of tests, either in the form of new tests or modifications to existing tests, or must include the rationale for why test updates are not required for the proposed update. - ## Deliverables -The WG expects to gradually move all of its deliverables to a Living Standard CR model. +The WG expects to gradually move all of its deliverables to a Living Standard CR model. Beyond that, the WG expects to converge at least some of its deliverables into a smaller number of specifications. - ### Normative Specifications The working group will deliver incremental revisions of the following W3C normative specifications: @@ -248,7 +229,7 @@ This specification defines an API that web page authors can use to detect presen **Draft state:** [Working Draft](https://www.w3.org/TR/longtasks-1/) -**Next Recommendation expected completion:** +**Next Recommendation expected completion:** Latest publication: [07 September 2017](https://www.w3.org/TR/2017/WD-longtasks-1-20170907/) @@ -282,7 +263,7 @@ This specification enables a server to communicate performance metrics about the **Draft state:** [Working Draft](https://www.w3.org/TR/server-timing/) -**Next Recommendation expected completion:** +**Next Recommendation expected completion:** Latest publication: [11 April 2023](https://www.w3.org/TR/2023/WD-server-timing-20230411/) @@ -422,7 +403,6 @@ Produced under Working Group Charter: [https://www.w3.org/2016/07/webperf](https Moved to the [HTML spec](https://html.spec.whatwg.org/multipage/interaction.html#page-visibility). - ### Other Deliverables The Group maintains two non-normative documents: @@ -442,14 +422,12 @@ Other non-normative documents may be created such as: The WG will also explore the possibility of renewing work on the [HAR file format](https://w3c.github.io/web-performance/specs/HAR/Overview.html). - ## Coordination For all specifications, this Working Group will seek [horizontal review](https://www.w3.org/Guide/Charter.html#horizontal-review) for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the [TAG](https://www.w3.org/2001/tag/). Invitation for review must be issued during each major standards-track document transition, including [FPWD](https://www.w3.org/2020/Process-20200915/#RecsWD) and [CR](https://www.w3.org/2020/Process-20200915/#RecsCR), and should be issued when major changes occur in a specification. Additional technical coordination with the following Groups will be made, per the [W3C Process Document](https://www.w3.org/2020/Process-20200915/#WGCharter): - ### W3C Groups [Technical Architecture Group (TAG)](https://www.w3.org/2001/tag/) @@ -476,7 +454,6 @@ This group monitors ongoing privacy issues that affect the Web, investigates pot This group provides a lightweight venue for proposing, incubating and discussing new web platform features. The Web Performance Working group will incubate and review new proposals that are within scope of our charter within the WICG. Once such WICG-incubated proposal is implemented and available in at least one major browser, and has support from one more, it may be adopted by the Web Performance Working group. - ### External Organizations [ECMA Technical Committee 39 (TC39)](https://www.ecma-international.org/memento/tc39.htm) @@ -491,7 +468,6 @@ The IETF is responsible for defining robust and secure protocols for Internet fu The Web Hypertext Application Technology Working Group (WHATWG) is a community of people interested in evolving the web through standards and tests. - ## Participation To be successful, this Working Group is expected to have 5 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a day per week towards the Working Group. There is no minimum requirement for other Participants. @@ -502,7 +478,6 @@ The group also welcomes non-Members to contribute technical submissions for cons Participants in the group are required (by the [W3C Process](https://www.w3.org/Consortium/Process/#ParticipationCriteria)) to follow the W3C [Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/). - ## Open privacy issues The following WG deliverables currently have a few open issues related to privacy - [Resource Timing](https://github.com/w3c/resource-timing/issues?q=is%3Aissue+is%3Aopen+label%3Aprivacy-needs-resolution), [High Resolution time](https://github.com/w3c/hr-time/issues/79), and [Reporting](https://github.com/w3c/reporting/issues?q=is%3Aissue+is%3Aopen+label%3Aprivacy-tracker). @@ -517,8 +492,7 @@ Information about the group (including details about deliverables, issues, actio Most Web Performance Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis. -This group primarily conducts its technical work in its [public repositories](https://github.com/orgs/w3c/teams/web-performance/repositories). There is also a public mailing list public-web-perf@w3.org ([archive](https://lists.w3.org/Archives/Public/public-web-perf/)). The public is invited to contribute to the github repositories and post messages to the list. Regular activity summaries around the github repositories will be provided. - +This group primarily conducts its technical work in its [public repositories](https://github.com/orgs/w3c/teams/web-performance/repositories). There is also a public mailing list [public-web-perf@w3.org](mailto:public-web-perf@w3.org) ([archive](https://lists.w3.org/Archives/Public/public-web-perf/)). The public is invited to contribute to the github repositories and post messages to the list. Regular activity summaries around the github repositories will be provided. ## Decision Policy @@ -532,17 +506,14 @@ All decisions made by the group should be considered resolved unless and until n This charter is written in accordance with the [W3C Process Document (Section 3.4, Votes)](https://www.w3.org/Consortium/Process/policies#Votes), and includes no voting procedures beyond what the Process Document requires. - ## Patent Policy This Working Group operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20200915/) 15 September 2020. To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis. For more information about disclosure obligations for this group, please see the [W3C Patent Policy Implementation](https://www.w3.org/2004/01/pp-impl/45211/status). - ## Licensing This Working Group will use the [W3C Software and Document license](https://www.w3.org/Consortium/Legal/copyright-software) for all its deliverables. - ## About this Charter This charter has been created according to [section 5.2](https://www.w3.org/Consortium/Process/groups#GAGeneral) of the [Process Document](https://www.w3.org/Consortium/Process). In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence. From f356f998b1f617fc599069379202e6e62ec19433 Mon Sep 17 00:00:00 2001 From: Nic Jansma Date: Sun, 22 Sep 2024 14:58:31 -0400 Subject: [PATCH 18/19] Updated Charter date through 2025-12-01 --- charter_draft.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/charter_draft.md b/charter_draft.md index d48b4cbb..85e44256 100644 --- a/charter_draft.md +++ b/charter_draft.md @@ -2,9 +2,9 @@ # 2023 Charter Comments -2021 Charter: [https://www.w3.org/2021/02/webperf.html](https://www.w3.org/2021/02/webperf.html) +2023 Charter: [https://www.w3.org/2023/11/webperf-charter-2023.html](https://www.w3.org/2023/11/webperf-charter-2023.html) -Expires: 28 February 2023 +Expires: 01 December 2025 * Specs Changes * Page Visibility From 1be33d9f0cd87af69eb98249d4121dee11e8e342 Mon Sep 17 00:00:00 2001 From: Nic Jansma Date: Sun, 22 Sep 2024 15:24:42 -0400 Subject: [PATCH 19/19] Merged in final charter wording --- charter_draft.md => charter.md | 125 ++++++++++----------------------- 1 file changed, 38 insertions(+), 87 deletions(-) rename charter_draft.md => charter.md (76%) diff --git a/charter_draft.md b/charter.md similarity index 76% rename from charter_draft.md rename to charter.md index 85e44256..1813ce6e 100644 --- a/charter_draft.md +++ b/charter.md @@ -1,70 +1,11 @@ -# W3C Web Performance Working Group - -# 2023 Charter Comments - -2023 Charter: [https://www.w3.org/2023/11/webperf-charter-2023.html](https://www.w3.org/2023/11/webperf-charter-2023.html) - -Expires: 01 December 2025 - -* Specs Changes - * Page Visibility - * Discontinue (in 2023 charter) - * Moved to HTML - * Repo archived (but doesn't mention why) - * Spec says discontinued [https://github.com/w3c/page-visibility/](https://github.com/w3c/page-visibility/) - * Spec should redirect? - * Beacon - * Don't finalize to Rec, could incorporate Unload/Pending beacon into it - * Cooperative Scheduling of Background Tasks (rIC) - * Don't finalize to Rec, could incorporate Scheduling APIs - * PaintTiming - * EventTiming - * LCP - * Could incorporate ElementTiming? - * Timing Names Entry Registry - * New process for registries from W3C -* Incubations - * ElementTiming [https://github.com/WICG/element-timing](https://github.com/WICG/element-timing) - * Move into LCP? Or at least bring into WG as LCP already is. - * Merge parts into LCP, parts into PaintTiming - * isInputPending [https://github.com/WICG/is-input-pending](https://github.com/WICG/is-input-pending) - * Any recent updates? - * Layout Instability [https://github.com/WICG/layout-instability](https://github.com/WICG/layout-instability) - * Discussion in early 2022 around lessons from implementation - * Barriers to adoption? - * Mozilla: Neutral (implementation, performance concerns) - * Apple: Opposed (circa 2019) (concerns on bookkeeping, cost at runtime, implementation, animations/scrolling not handled well) - * Memory Measurement [https://github.com/WICG/performance-measure-memory](https://github.com/WICG/performance-measure-memory) - * Network Info [https://github.com/WICG/netinfo/](https://github.com/WICG/netinfo/) - * Unload Beacon [https://github.com/WICG/unload-beacon](https://github.com/WICG/unload-beacon) - * Incorporate into Beacon? - * Scheduling APIs [https://github.com/WICG/scheduling-apis](https://github.com/WICG/scheduling-apis) - * Incorporate into Cooperative Scheduling of Background Tasks? - * Consider a move to HTML spec (same as rIC?) - * JS self profiling [https://wicg.github.io/js-self-profiling/](https://wicg.github.io/js-self-profiling/) - * Any recent updates? - * Page Lifecycle [https://github.com/WICG/page-lifecycle](https://github.com/WICG/page-lifecycle) - * Intervention/Deprecation/Crash Reporting - * [https://github.com/WICG/deprecation-reporting](https://github.com/WICG/deprecation-reporting) - * [https://github.com/WICG/intervention-reporting](https://github.com/WICG/intervention-reporting) - * [https://github.com/WICG/crash-reporting](https://github.com/WICG/crash-reporting) - -## TPAC 22 discussions - -* Sustainability - should it be covered in scope? No direct deliverables just yet -* Lab tooling related browser interop - should it go back to being in scope? - -## Other questions - -* HR-Time is not just about high resolution timers, but defines time in general. Should we rename it? -* We should call out [open privacy issues](https://github.com/w3c/resource-timing/issues?q=is%3Aissue+is%3Aopen+label%3Aprivacy-needs-resolution) and say that we strive to resolve them - -# CHARTER DRAFT +# Web Performance Working Group Charter -## Scope +## Motivation and Background Web developers are building sophisticated applications where application performance is a critical feature. Web developers want the ability to observe the performance characteristics of their applications, and they want the ability to write more efficient applications, using well-defined interoperable methods. Their methods must be both secure and privacy-enabling by design, using well-defined interoperable methods that conform to the current Web browser security model. +## Scope + The Web Performance Working Group's scope of work includes user agent features and APIs to observe and improve various aspects of application performance: * _Measurement_ @@ -84,18 +25,15 @@ The following features are out of scope, and will not be addressed by this worki * performance data analysis techniques or algorithms. -### Success Criteria +## Deliverables -In order to advance to [Proposed Recommendation](https://www.w3.org/2020/Process-20200915/#RecsPR), each specification is expected to have at least two independent implementations of each feature defined in the specification. +Updated document status is available on the [group publication status page](https://www.w3.org/groups/wg/webperf/publications). -Each specification should contain a section detailing any [known security](https://www.w3.org/TR/security-privacy-questionnaire/), fingerprinting, and privacy implications, and suggested [mitigation strategies](https://w3c.github.io/perf-security-privacy/) for implementers, Web authors, and end users. The group should not publish a specification if acceptable mitigation strategies cannot be found. +Draft state indicates the state of the deliverable at the time of the charter approval. -Normative specification changes are generally expected to have a corresponding set of tests, either in the form of new tests or modifications to existing tests, or must include the rationale for why test updates are not required for the proposed update. +The Working Group intends to publish the latest state of their work as Candidate Recommendations, upgrading specifications with Candidate Recommendation Snapshots. Alternatively, ongoing work may be published as Recommendations to be updated further with Candidate Changes. -## Deliverables - -The WG expects to gradually move all of its deliverables to a Living Standard CR model. -Beyond that, the WG expects to converge at least some of its deliverables into a smaller number of specifications. +The Working Group expects to gradually move all of its deliverables to this model. Beyond that, the WG expects to converge at least some of its deliverables into a smaller number of specifications. ### Normative Specifications @@ -414,6 +352,7 @@ The Group maintains two non-normative documents: Other non-normative documents may be created such as: +* [Security and Privacy considerations for Performance APIs](https://w3c.github.io/perf-security-privacy/) * Test suites for each specification; * Use cases documents to support development and exploration of performance-critical web platform features and APIs; * Primer or Best Practice documents to support web developers when designing applications with performance in mind; @@ -422,6 +361,22 @@ Other non-normative documents may be created such as: The WG will also explore the possibility of renewing work on the [HAR file format](https://w3c.github.io/web-performance/specs/HAR/Overview.html). +### Timeline + +* Next meeting: TPAC 2024 in hybrid mode. + +## Success Criteria + +There should be testing plans for each specification, starting from the earliest drafts. + +To promote interoperability, all changes made to specifications in Candidate Recommendation or to features that have deployed implementations should have [tests](https://www.w3.org/2019/02/testing-policy.html). Testing efforts can be conducted via the [Web Platform Tests](https://github.com/web-platform-tests/wpt) project. + +Each specification should contain sections detailing all known security and privacy implications for implementers, Web authors, and end users. + +This Working Group expects to follow the TAG [Web Platform Design Principles](https://www.w3.org/TR/design-principles/). + +All new features should be supported by at least two intents to implement before being incorporated in the specification. + ## Coordination For all specifications, this Working Group will seek [horizontal review](https://www.w3.org/Guide/Charter.html#horizontal-review) for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the [TAG](https://www.w3.org/2001/tag/). Invitation for review must be issued during each major standards-track document transition, including [FPWD](https://www.w3.org/2020/Process-20200915/#RecsWD) and [CR](https://www.w3.org/2020/Process-20200915/#RecsCR), and should be issued when major changes occur in a specification. @@ -478,37 +433,33 @@ The group also welcomes non-Members to contribute technical submissions for cons Participants in the group are required (by the [W3C Process](https://www.w3.org/Consortium/Process/#ParticipationCriteria)) to follow the W3C [Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/). -## Open privacy issues - -The following WG deliverables currently have a few open issues related to privacy - [Resource Timing](https://github.com/w3c/resource-timing/issues?q=is%3Aissue+is%3Aopen+label%3Aprivacy-needs-resolution), [High Resolution time](https://github.com/w3c/hr-time/issues/79), and [Reporting](https://github.com/w3c/reporting/issues?q=is%3Aissue+is%3Aopen+label%3Aprivacy-tracker). - -The WG will work with the relevant stake holders and strive to resolve those issues. - ## Communication -Technical discussions for this Working Group are conducted in [public](https://www.w3.org/2020/Process-20200915/#confidentiality-levels). Meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed on a public repository, and may permit direct public contribution requests. +Technical discussions for this Working Group are conducted in [public](https://www.w3.org/Consortium/Process/#confidentiality-levels): the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests. The meetings themselves are not open to public participation, however. -Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the [Web Performance Working Group home page.](https://www.w3.org/2010/webperf/) +Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the [Web Performance Working Group home page](https://www.w3.org/groups/wg/webperf). Most Web Performance Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis. -This group primarily conducts its technical work in its [public repositories](https://github.com/orgs/w3c/teams/web-performance/repositories). There is also a public mailing list [public-web-perf@w3.org](mailto:public-web-perf@w3.org) ([archive](https://lists.w3.org/Archives/Public/public-web-perf/)). The public is invited to contribute to the github repositories and post messages to the list. Regular activity summaries around the github repositories will be provided. +This group primarily conducts its technical work on [GitHub](https://github.com/w3c/web-performance) in the relevant specifications repositories. The public is invited to review, discuss and contribute to this work. + +The group may use a Member-confidential mailing list for administrative purposes. ## Decision Policy -This group will seek to make decisions through consensus and due process, per the [W3C Process Document (section 3.3](https://www.w3.org/2020/Process-20200915/#Consensus)). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required. +This group will seek to make decisions through consensus and due process, per the [W3C Process Document (section 5.2.1, Consensus)](https://www.w3.org/Consortium/Process/#Consensus). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required. -However, if a decision is necessary for timely progress, but consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote, and record a decision along with any objections. +However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections. -To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional until 10 working days after the publication of the resolution in draft minutes sent, which will be published within 5 working days of the meeting to the working group's mailing list with a 'call for consensus' in the subject line. If no objections are raised on the mailing list by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group. +To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue. If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group. -All decisions made by the group should be considered resolved unless and until new information becomes available, or unless reopened at the discretion of the Chairs or the Director. +All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs. -This charter is written in accordance with the [W3C Process Document (Section 3.4, Votes)](https://www.w3.org/Consortium/Process/policies#Votes), and includes no voting procedures beyond what the Process Document requires. +This charter is written in accordance with the [W3C Process Document (Section 5.2.3, Deciding by Vote)](https://www.w3.org/Consortium/Process/#Votes) and includes no voting procedures beyond what the Process Document requires. ## Patent Policy -This Working Group operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20200915/) 15 September 2020. To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis. For more information about disclosure obligations for this group, please see the [W3C Patent Policy Implementation](https://www.w3.org/2004/01/pp-impl/45211/status). +This Working Group operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy/) (Version of 15 September 2020). To promote the widest adoption of Web standards, W3C seeks to issue Web specifications that can be implemented, according to this policy, on a Royalty-Free basis. For more information about disclosure obligations for this group, please see the [licensing information](https://www.w3.org/groups/wg/webperf/ipr). ## Licensing @@ -516,4 +467,4 @@ This Working Group will use the [W3C Software and Document license](https://www. ## About this Charter -This charter has been created according to [section 5.2](https://www.w3.org/Consortium/Process/groups#GAGeneral) of the [Process Document](https://www.w3.org/Consortium/Process). In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence. +This charter has been created according to [section 3.4](https://www.w3.org/Consortium/Process/#GAGeneral) of the [Process Document](https://www.w3.org/Consortium/Process/). In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.