Normative References to W3C Standards

Status: For review by Chairs and Advisory Board. The W3C has invited Chairs and the Advisory Board to review this document. After the review period the staff intends to integrate the material into the W3C site.

Comments:

• Anne van Kesteren: Case of DOM4, not yet a Rec but already more implementable than DOM3 which is a Rec.
• Missing information how to reference stable parts of HTML5; Ian to speak with Philippe about this.
• Marcos Caceres:
  • Further clarify this document is only about refs to W3C materials
  • Suggestion for references to informative materials, say "Indicate that it's a Work in Progress"; Marcos provides an example
  • Clarify US-English
  • Provide links to improved biblio tools
  • Marcos distinguishes "stable" (meaning has bug fixes, etc.) from "static" (unchanging bits)
• Larry: Is there different guidance for different communities based on whether they need unchanging bits, stability in changes to content (only non-technical editorial) or latest version?
• Art: seems like the main point to communicate is that each spec's SotD summarizes the spec's "stability" level and users should consider that status. As such, I would delete the this sentence: "If a W3C document is not a "W3C Recommendation", do not reference it normatively.". Or water it down with some type of "user beware" statement.
• Shawn: The issue is much broader than specs in development. There have been problems with references to W3C docs that are not normative themselves (e.g., WG Notes, WG wiki pages).
• Addison: Like the accessibility folks, I18N frequently authors WG Notes that are useful references but which are not REC-track. Cf. "Working with Time Zones", "Layout Requirements for Japanese" or "Requirements for Bidi in HTML", as well as techniques and best practices documents.
• Glazman: So I think it should be good to have something between "normative" and "informative" meaning "Informative but to become normative". Such references will have an impact of the spec: it will reach REC only if these references also reach REC.

W3C produces different types of materials. Some publications are standards that can be referenced normatively. Some W3C materials are not standards, and should not be referenced normatively.

Normative References

W3C Standards are produced by W3C Working Groups under the W3C Process and the W3C Patent Policy. To learn more, see the value of creating standards at W3C.

Figure 1: Sample W3C Recommendation

Identifying standards: W3C Standards are called "W3C Recommendations", and are listed in a Standards page. W3C Standards have "W3C Recommendation" near the top of the document, as shown in Figure 1.

Only W3C Recommendations should be referenced normatively. If a W3C document is not a "W3C Recommendation", do not reference it normatively.

The information below on URIs, ISO/IEC Standards, languages, and creating a bibliography applies to all references, including normative references.

Non-Normative/Informative W3C Material

W3C also publishes non-normative/informative material, developed under a variety of processes, copyrights, and patent policies. Informative material should not be referenced normatively.

W3C non-normative material includes:

• Material developed by W3C Working Groups:
  • W3C Working Group Notes and Resources that are approved by a Working Group.
  • Draft specifications that are not yet completed or approved W3C Standards.
  • Editors' Drafts that are not yet approved by a Working Group.
• Material on the W3C website not developed by Working Groups:
  • Documents produced by W3C Interest Groups, Community Groups, and Business Groups.
  • Documents created outside of W3C by W3C Members as input to the W3C process (called Member Submissions).
  • Documents created by the W3C staff as a service to the Web community (called Team Submissions).
  • In-progress work in wiki pages, some of which is not reviewed or approved by anyone.

It is important to understand that some of this material is not approved by W3C Working Groups, staff, or Members. When you reference W3C material, make sure you know and communicate its approval status.

When referencing informative material, make sure to clearly indicate that is it not a normative standard.

For additional guidance on using and referencing W3C work, including example attributions, see the W3C Copyright FAQ.

URIs (Links)

W3C Recommendations and other Technical Reports have two types of URIs, in order to meet different needs for stability:

• "This version" or "dated" URI for every publication, including drafts. The content at that URI will not change; future versions will be published at different URIs. Use "This version" URIs only when you want to link to a specific version that will not change, and that is not necessarily the latest version.
• "Latest version" URI always links to the latest version of a document. Use "Latest version" URIs when you want to link to the most recent published version.

Figure 1 above shows these two links.

For information about how W3C uses these URIs as documents evolve, see Version Management in W3C Technical Reports.

ISO/IEC Standards and W3C Recommendations

Some W3C Recommendations are recognized as ISO/IEC Standards. W3C Recommendations that are also ISO/IEC Standards have identical technical content, and thus in some contexts you can refer to either the W3C Recommendation or the ISO/IEC Standard. However, W3C Recommendations are available at no cost, and W3C may have published errata, test suites, techniques documents, and other materials to supplement the Recommendation.

Therefore, when referring to the ISO/IEC standard, also include a reference to the original W3C Recommendation and any related information on the W3C website so that readers can find additional resources.

ISO/IEC standards can include normative references to W3C Recommendations (because of ISO/IEC recognition of W3C). To learn more about ISO/IEC and W3C Recommendations, see the W3C PAS FAQ.

English Language Versions and Translations

The official language of W3C materials is English, and W3C welcomes translations. Most translations are unofficial; some translations are Authorized W3C Translations.

Always reference the English version of a document. If a relevant translation is available, include a link to the translation as well. Authorized Translations can by referenced normatively. If you link to an unofficial translation, make sure to clearly indicate that is unofficial.

Creating a Bibliography Entry for a W3C Recommendation

W3C offers a tool for generating a bibliography of W3C Recommendations, Working Group Notes, and other Technical Reports.