PROPOSED [name] (Working|Interest) Group Charter
The mission of the [name] (Working|Interest) Group is to [do something cool and specific on the Web].
|Charter Status||See the group status page and detailed change history.|
|Start date||[dd monthname yyyy] (date of the "Call for Participation", when the charter is approved)|
|End date||[dd monthname yyyy] (Start date + 2 years)|
|Chairs||[chair name] (affiliation)|
|Team Contacts||[team contact name] (0.1 FTE)|
Teleconferences: topic-specific calls may be held or somthing else
Face-to-face: we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year.
Note: The W3C Process Document requires “The level of confidentiality of the group's proceedings and deliverables”; however, it does not mandate where this appears. Since all W3C Working Groups should be chartered as public, this notice has been moved from the essentials table to the communication section.
Motivation and Background
Background of landscape, technology, and relationship to the Web, users, developers, implementers, and industry.
What exactly is in scope, and out of scope. For legal review. Be brief.
Out of Scope
The following features are out of scope, and will not be addressed by this (Working|Interest) group.
Updated document status is available on the group publication status page. [or link to a page this group prefers to use]
Draft state indicates the state of the deliverable at the time of the charter approval. Choose one: Expected completion indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state The Working Group intends to publish the latest state of their work as Candidate Recommendation (with Snapshots) and does not intend to advance their documents to Recommendation.
The (Working|Interest) Group will deliver the following W3C normative specifications:
Consider making a second list for existing specifications that the group will maintain.
- Web [spec name]
This specification defines [concrete description].
Draft state: [No draft | Use Cases and Requirements | Editor's Draft | Member Submission | Adopted from WG/CG Foo | Working Draft]
Expected completion: [Q1–4 yyyy]
Per 5.2.6, for every Recommendation Track deliverable that continues work on a Working Draft (WD) published under any other Charter (including a predecessor group of the same name), for which there is an existing Exclusion Draft:
Adopted Draft: The title, stable URL, and publication date of the Adopted Draft which will serve as the basis for work on the deliverable.
Exclusion Draft: The title, stable URL, and publication date of the most recent Exclusion Draft. Exclusion period began; Exclusion period ended. (this charter assistant helps in producing the list. use the proper wgid)
Exclusion Draft Charter: The stable URL of the Working Group charter under which the most recent Exclusion Draft was published.
Other non-normative documents may be created such as:
- Use case and requirement documents;
- Test suite and implementation report for the specification;
- Primer or Best Practice documents to support web developers when designing applications.
Put here a timeline view of all deliverables.
- Month YYYY: First teleconference
- Month YYYY: First face-to-face meeting
- Month YYYY: Requirements and Use Cases for FooML
- Month YYYY: FPWD for FooML
- Month YYYY: Requirements and Use Cases for BarML
- Month YYYY: FPWD FooML Primer
Remove this clause if the Group does not intend to move to REC: In order to advance to Proposed Recommendation, each normative specification is expected to have at least two independent interoperable implementations of every feature defined in the specification, where interoperability can be verified by passing open test suites, and two or more implementations interoperating with each other. In order to advance to Proposed Recommendation, each normative specification must have an open test suite of every feature defined in the specification.
There should be testing plans for each specification, starting from the earliest drafts.
Consider adopting a healthy testing policy, such as: To promote interoperability, all changes made to specifications in Candidate Recommendation or to features that have deployed implementations should have tests. Testing efforts should be conducted via the Web Platform Tests project.
Each specification should contain sections detailing all known security and privacy implications for implementers, Web authors, and end users.
For specifications of technologies that directly impact user experience, such as content technologies, as well as protocols and APIs which impact content: Each specification should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and recommendations for maximising accessibility in implementations.
This (Working|Interest) Group expects to follow the TAG Web Platform Design Principles.
Consider adding this clause if the Group does not intend to move to REC: All new features should have expressions of interest from at least two potential implementors before being incorporated in the specification.
For all specifications, this (Working|Interest) Group will seek horizontal review for accessibility, internationalization, privacy, and security with the relevant Working and Interest Groups, and with the TAG. Invitation for review must be issued during each major standards-track document transition, including FPWD. The (Working|Interest) Group is encouraged to engage collaboratively with the horizontal review groups throughout development of each specification. The (Working|Interest) Group is advised to seek a review at least 3 months before first entering CR and is encouraged to proactively notify the horizontal review groups when major changes occur in a specification following a review.
Additional technical coordination with the following Groups will be made, per the W3C Process Document:
In addition to the above catch-all reference to horizontal review which includes accessibility review, please check with chairs and staff contacts of the Accessible Platform Architectures Working Group to determine if an additional liaison statement with more specific information about concrete review issues is needed in the list below.
- [other name] Working Group
- [specific nature of liaison]
Note: Do not list horizontal groups here, only specific WGs relevant to your work.
Note: Do not bury normative text inside the liaison section. Instead, put it in the scope section.
- [other name] Working Group
- [specific nature of liaison]
To be successful, this (Working|Interest) Group is expected to have 6 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 working day per week towards the (Working|Interest) 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.
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the W3C Patent Policy.
Participants in the group are required (by the W3C Process) to follow the W3C Code of Ethics and Professional Conduct.
Technical discussions for this (Working|Interest) Group are conducted in public: 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 [name] (Working|Interest) Group home page.
Most [name] (Working|Interest) 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 pick one, or both, as appropriate: on the public mailing list public-[email-list]@w3.org (archive) or on GitHub issues. The public is invited to review, discuss and contribute to this work.
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.
This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 5.2.1, 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 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. 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 [pick a duration within:] 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|Interest) 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.
This charter is written in accordance with the W3C Process Document (Section 5.2.3, Deciding by Vote) and includes no voting procedures beyond what the Process Document requires.
[Keep 'Patent Policy' for a Working Group, 'Patent Disclosures' for an Interest Group]
This Working Group operates under the W3C 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.
The Interest Group provides an opportunity to share perspectives on the topic addressed by this charter. W3C reminds Interest Group participants of their obligation to comply with patent disclosure obligations as set out in Section 6 of the W3C Patent Policy. While the Interest Group does not produce Recommendation-track documents, when Interest Group participants review Recommendation-track specifications from Working Groups, the patent disclosure obligations do apply. For more information about disclosure obligations for this group, please see the licensing information.
This (Working|Interest) Group will use the W3C Software and Document license for all its deliverables.
About this Charter
This charter has been created according to section 3.4 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.
Note:Display this table and update it when appropriate. Requirements for charter extension history are documented in the Charter Guidebook (section 4).
The following table lists details of all changes from the initial charter, per the W3C Process Document (section 4.3, Advisory Committee Review of a Charter):
|Charter Period||Start Date||End Date||Changes|
|Initial Charter||[dd monthname yyyy]||[dd monthname yyyy]||none|
|Charter Extension||[dd monthname yyyy]||[dd monthname yyyy]||none|
|Rechartered||[dd monthname yyyy]||[dd monthname yyyy]||
[description of change to charter, with link to new deliverable item in charter] Note: use the class
Changes to this document are documented in this section.