This page provides the details behind the requirements of the Community and Business Group Process related to deliverables.
Formal Identification
W3C provides a means for each group Chair to publish and thereby designate the group’s Reports (as defined in the CLA and FSA). These reports are listed on the group’s home page.
Final Reports must be published on the W3C Web site. This can be achieved through mechanisms available on GitHub.
Style Sheets
ReSpec is a widely used tool at W3C for creating specifications, and it includes four style sheets (for draft and final reports, both for Community and Business Groups); set specStatus in the configuration accordingly (e.g., specStatus = CG-DRAFT). Several documents using ReSpec are linked from the reports page. Please note that ReSpec is not required, but is a useful option for editors.
Logos
To avoid confusion about standardization status, a Community Group Report must not use a W3C organization logo.
A Community Group Report must use the appropriate W3C Community Group logo (draft or final) in the upper left corner of the document. These logos are included automatically when using ReSpec.
Name and Date
The report must include:
- the name of the Community or Business that published the deliverables and link to a public page about the group.
- a publication date (e.g., “last modified” or a fixed date for a final report).
Relation to Standards Track
The report must not cause confusion about its status, in particular with respect to W3C Technical Reports. For example, reports must not suggest that they are standards or on the standards-track.
Copyright
The copyright statement to include at the top of each report
varies depending on whether the document is a draft or final report. In the boilerplate below please replace YEAR(s) (with a single year or range), the name of the report, the URI to the group’s home page (“groupname”), and the Group Name.
For draft reports, based on the CLA Deed, please use this markup (adjustments for HTML5 ok):
<p>Copyright © YEAR(S) the Contributors to the REPORT NAME/VERSION, published by the <a href="https://www.w3.org/community/grouphome/">Group Name</a> under the <a href="https://www.w3.org/community/about/process/cla/">W3C Community Contributor License Agreement (CLA)</a>. A human-readable <a href="https://www.w3.org/community/about/process/cla-deed/">summary</a> is available. </p>
For final reports, based on the FSA Deed, please use this markup (adjustments for HTML5 ok):
<p>Copyright © YEAR(S) the Contributors to the REPORT NAME/VERSION, published by the <a href="https://www.w3.org/community/grouphome/">Group Name</a> under the <a href="https://www.w3.org/community/about/process/final/">W3C Community Final Specification Agreement (FSA)</a>. A human-readable <a href="https://www.w3.org/community/about/process/fsa-deed/">summary</a> is available. </p>
Boilerplate
In the boilerplate below please replace the URI to the group’s home page (“groupname”), and the Group Name.
The following paragraph appears at the top of each draft report:
<p>This report was published by the <a href="https://www.w3.org/community/grouphome/">Group Name</a>. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the <a href="https://www.w3.org/community/about/process/cla/">W3C Community Contributor License Agreement (CLA)</a> there is a limited opt-out and other conditions apply. Learn more about <a href="https://www.w3.org/community/">W3C Community and Business Groups</a>.</p>
The following paragraph appears at the top of each final report:
<p>This report was published by the <a href="https://www.w3.org/community/grouphome/">Group Name</a>. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the <a href="https://www.w3.org/community/about/process/final/">W3C Community Final Specification Agreement (FSA)</a> other conditions apply. Learn more about <a href="https://www.w3.org/community/">W3C Community and Business Groups</a>.</p>
Patent Licensing Commitments
Readers should be able to find the contribution history easily from the report. Per the Community Group process, the contribution history must be archived permanently on the W3C Web site.
For final reports, W3C maintains information about which participants have signed the Final Specification Agreement and which have not. A final report must refer to the page maintained by W3C.
Privacy Policy
Reports must not violate the W3C Privacy Policy. In practical terms, this means not tracking report users via a third party system.