The mission of the Web Performance Working Group, part of the Rich Web Client Activity, is to provide methods to observe and improve aspects of application performance of user agent features and APIs.
|End date||31 May 2016|
|Confidentiality||Proceedings are public|
|Initial Chairs||Ilya Grigorik, Google
Todd Reifsteck, Microsoft
|Initial Team Contacts
(FTE %: 30)
|Philippe Le Hégaret, Xiaoqian Wu|
|Usual Meeting Schedule||Teleconferences: Bi-weekly
Face-to-face: we will meet during the W3C's annual Technical Plenary week (if space available); an additional face-to-face meeting may be scheduled by consent of the participants
IRC channel: #webperf
Web developers are building sophisticated applications where application performance is a critical feature. Web developers need the ability to observe the performance characteristics of their applications, and they need the ability to write more efficient applications, using well-defined interoperable methods.
The Web Performance Working Group's deliverables include user agent features and APIs to observe and improve aspects of application performance. These 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, WebApps, DAP and SVG.
In addition to developing Recommendation Track documents, the Web Performance Working Group may provide review of specifications from other Working Groups.
In order to advance to Proposed Recommendation, each specification is expected to have two independent implementations of each of feature defined in the specification.
The following items are not in scope:
The working group will deliver incremental revisions of the following specifications:
In addition, the Working Group will:
The specifications will include privacy and security considerations.
The Group will produce a non-normative Primer document to facilitate the understanding of the interrelationships between its deliverables.
Other non-normative documents may be created such as:
Current status of each deliverable, including implementation and other dependencies which may block it, is maintained on the Web Performance/Publications page.
The Web Performance Working Group should ensure proper reviews from the Web Applications, Technical Architecture Group, Web Application Security and Privacy groups at the minimum.
To be successful, the Web Performance Working Group is expected to have 5 or more active participants for its duration. The Chairs and specification Editors are expected to contribute one day per week towards the Working Group. There is no minimum requirement for other Participants.
The Web Performance Working Group will also allocate the necessary resources for building Test Suites for each specification.
The group encourages questions and comments on its public mailing lists, as described in Communication.
The group also welcomes non-Members to contribute technical submissions for consideration, with the agreement from each participant to Royalty-Free licensing of those submissions under the W3C Patent Policy.
Most Web Performance Working Group Teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis. Note the Decision Policy below with regards to synchronous meetings.
This group primarily conducts its work in github issues and on the public mailing list firstname.lastname@example.org (archive). 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.
Information about the group (deliverables, participants, teleconferences, etc.) is available from the Web Performance Working Group home page.
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
Information about the group (for example, details about deliverables, issues, actions, status, participants) will be available from the Web Performance Working Group home page.
As explained in the W3C Process Document (section 3.3), this group will seek to make decisions when there is consensus and with due process. The expectation is that 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 should put a question out for voting within the group (allowing for remote asynchronous participation -- using, for example, email and/or web-based survey techniques) and record a decision, along with any objections. The matter should then be considered resolved unless and until new information becomes available.
Any resolution taken in a face-to-face meeting or teleconference is to be considered provisional until 10 working days after the publication of the resolution in draft minutes sent to the working groups mailing list. If no objections are raised on the mailing list within that time, the resolution will be considered to have consensus as a resolution of the Working Group.
This charter is written in accordance with Section 3.4, Votes of the W3C Process Document and includes no voting procedures beyond what the Process Document requires.
This Working Group operates under the W3C Patent Policy (5 February 2004 Version). 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.
This charter for the Web Performance Working Group has been created according to section 6.2 of the Process Document. 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.