Mission Statement
The working group will be chartered to [...describe the main aspects of the WG's mission...]
Scope and Work Items
Architectural Constraints
[...optional subsections like this might describe context, architectural constraints, etc, on the work items and their scope...]
Technical Items
[...the non-QA technical items associated with the WG's main goals, e.g....]
- [...specification name...] requirements document
- [...specification name...] specification
- Proof of concept implementations of [...specification name...]
Quality Commitments
In its operations, specifications, and test materials the [--WG name--] WG will achieve at least the quality levels:
- Level [--choose one: {A | AA | AAA}--] conformance of its operations to QA Framework: Operational Guidelines.
- Level [--choose one: {A | AA | AAA}--] conformance of [--specification name--] to QA Framework: Specification Guidelines.
- Level [--choose one: {A | AA | AAA}--] conformance of its test materials to QA Framework: Test Guidelines.
[For OpsGL checkpoint CP1.1]
Specific Quality Assurance Items
- [Choose one, this bullet or the next one.] Basic-level [--test materials--] for [--specification name--]. [For OpsGL checkpoint CP1.2]
- [Choose one, this bullet or the preceding one.] Comprehensive, complete [--test materials--] for [--specification name--]. [For OpsGL checkpoint CP1.3]
Tracking and Maintenance Items
- Collect errata and periodically publish new editions of the [...specification name...] incorporating errata
- Gather requirements for any subsequent version of [...specification name...]
- [QA recommended] Monitoring of implementations for conformance to [--specification name--], interoperability and quality. Publication of Implementation Reports.
Success criteria
Production of a stable document collectively addressing each of the Work Items, at Proposed Recommendation status.
Attainment of [--WG name--] WG's quality level goals in its operations, specifications, and test materials. [For OpsGL checkpoint CP1.1 ]
Completion of associated comprehensive [--test materials--] at Proposed Recommendation status of [--specification name--]. [For OpsGL checkpoints CP1.2, CP1.3]
Availability of multiple, independent, interoperable implementations of [...specification name...], and [...], including [...]
Duration
This group will commence in [...start date...] and will terminate in [...end date...].
Deliverables
General Working Group deliverables will include:
- The group will create one or more Working Drafts, [...etc...note QA-related items will be in following QA-deliverables enumeration section].
- The group will produce Proposed Recommendation(s), drawn from stable Working Draft(s).
- Minutes of teleconferences and face to face meetings are also available at the @@WG page@@
- [...etc...]
Specific QA deliverables will include:
- [chose one: {Basic | Complete}] test materials, consisting of [--test materials--]. [For OpsGL checkpoints CP1.2, CP1.3]
- A set of operational, specification and test materials deliverables,
complete for its committed quality levels,
containing at least (common to all quality-level commitments) [For OpsGL checkpoints CP1.1]:
- a QA Process Document (QAPD) for [--WG name--];
- SpecGL ICS reviews of [--specification name--],
- ample use cases and examples for [--specification name--],
- publication of test assertions for [--specification name--].
[For OpsGL checkpoint CP1.4.]
- [QA optional/additional] In addition to the QA deliverables required for its committed quality levels, the [--WG name--] WG intends to produce these additional QA deliverables: [--other QA deliverables--] [For OpsGL checkpoint CP1.4.]
- The [--WG name--] Working Group intends to produce [--test materials--] by [--all intra-WG work | importing external materials | hybrid internal-external | other(specify]. [--discuss further as needed--]. [For OpsGL checkpoint CP2.1.]
Legal Data
The [...WG name...] Working Group will develop [...Royalty Free (RF) | RAND...] specification(s) as defined by the Patent Policy Working Group.
[...etc...]
[QA optional] The planned distribution licenses for [--test materials--] are [--identify licenses--]. [Note. This information is required in the WG's QA Process Document.]
Release policy
[Sample text about general document release policy...] A list of documents actively under consideration by the group, is maintained by [...who...]. [...describe process for adding documents, modifying, etc...]. As documents stabilize, they will be released as W3C Working Drafts. No document may stay on the list of documents actively under consideration by the group for more than [...time...] without [...state any policy...]. Documents may be released sooner if consensus is achieved. If the three month deadline is reached, the current draft will be released (and not a draft from three months earlier). [...any other details of specifications consensus/release process...]
[QA Optional] The release policy for in-progress versions of [--test materials--] is [--state it--].
Relationship to other forums
- QA Working Group [QA recommended]
- The [--WG name--] WG will coordinate its QA work the Quality Assurance Working Group, with an appointed QA moderator as principal point of contact.
- ...other technical WGs...
- The [...WG-name...] WG will coordinate [...etc...].
- W3C Web Accessibility Initiative
- The work of the [...WG-name...] WG will be coordinated with the WAI project to ensure accessibility of [...specification name...].
- Device Independence Activity
- The work of the [...WG-name...] WG will be coordinated with this activity, in particular the Device Independence Working Group, to ensure that [...specification name...] can [...].
- Internationalization Working Group
- The I18N WG will review the [...specification name...] to ensure it is adequately Internationalized.
Milestones
One or more public Working Drafts, plus associated Test Suites and Implementation Reports, will be produced covering each of the Work Items, to the following schedule:
- [Non-QA items, for example...]
- first Working Group meeting: [...time and place...]
- [...specification name...] requirements document: [...date...]
- [...specification name...] Last Call by [...LC-date...]
- [...specification name...] Candidate Recommendation by [...CR-date...]
- [...specification name...] Proposed Recommendation by [...PR-date...]
- [...specification name...] Recommendation by [...Rec-date...]
- By [--maturity-level-milestone--] the group will produce/publish [--test materials | other QA deliverables--]. [For OpsGL checkpoint CP1.5]
- [Example... "By PR entrance (CR completion) the WG will publish a complete test suite."]
[For OpsGL checkpoint CP1.5]
Meetings
[...state meetings policy...]. Meeting details are made available on the W3C Member Calendar and from the [..WG-name..] WG page
Communication Mechanisms
The archived [...member-only | public...] mailing list [...specify and link it...] is the primary means of discussion within the group. [...More about confidentiality, public comment lists, etc...]
There is a public Web page on [...specification name...], at [...specify and link it...]
[QA optional] There is a public mailing list for [--specification name--], dealing with QA topics, announcements, and [--test materials--] feedback, at [--specify and link it--]. [Note. This is required for the QA Process Document (QAPD) of the WG.]
[QA optional] There is a public Web page for [--specification name--], for posting information about QA topics and [--test materials--], at [--specify and link it--]. [Note. This is required for the QA Process Document (QAPD) of the WG.]
Web site
There is a public Web page on [...specification-name...] topics, at [...specify and link it...]
[QA optional] There is a public Web page for [--specification name--], for posting information about QA topics and [--test materials--], at [--specify and link it--]. [Note. This is required for the QA Process document of the WG.]
Phone
[...specify teleconference policy...]
Voting Mechanisms
The Group works by consensus, including the use of straw polls. In the event of failure to achieve consensus, the Group may resort to a vote as described in the Process Document. [...specify further details...]
Participation
[...general participation requirements, including confidentiality, etc...].
by W3C Members
Requirements for meeting attendance and timely response are described in the Process document. Participation (meetings, reviewing and writing drafts) is expected to consume time equal to [...specify...]. [...specify any other member participation details...]
The [--WG name--] Working Group expects that its committed quality levels and QA deliverables production scenario will require [--specify amount--] WG member and staff resources. [--all | some subset(specify)--] WG members are expected to spend a portion of their time equivalent to [--specify amount--] on test materials production and other QA tasks. [For OpsGL checkpoint CP2.2]
by invited experts
[...specify invited experts policies...].
by W3C Team
[...specify W3C Team duties, functions, and any other policies...]