This Guidebook is the collected wisdom of the W3C Group Chairs and other collaborators.
This Guidebook is the collected wisdom of the W3C Group Chairs and other collaborators.
This resource provides three services:
Publication requirements and checker test results are shown below. The requirements and template are not shown in "Checker (Auto)" mode until you have run the checker.
A companion document includes a glossary, roles, and history of this document. A comparison of requirements across all document types is available.
For information about process requirements (how to request a transition, how to request publication, etc.), see How to Organize a Recommendation Track Transition. If you would like to discuss technical report production informally among your peers and get the latest tips and techniques, try the spec-prod mailing list (archive). Document Contacts should consult the W3C Manual of Style for guidance on additional publication topics and conventions.
The Document Contact MUST verify that the requirements in this section (listed in "document order") have been satisfied before requesting publication. How to Organize a Recommendation Track Transition explains the remainder of the publication process.
See the sample below that has been generated by the parameters you have chosen in the form at the top of this document, summarized here:
Highlighted test results appear after each provision. Several resulttypes require attention: Errors, Warnings, and those marked "Please verify." For the latter, some test results include a link to a tool to help verify the requirement has been satisfied.
http://www.w3.org/StyleSheets/TR/W3C-RECInclude this source code:<link rel="stylesheet" type="text/css"
href="http://www.w3.org/StyleSheets/TR/W3C-REC"/>
hr element after the
copyright MAY appear inside
or after the div element.
Editors SHOULD NOT include
other information in this section.title element and in an h1 element.h2 element as follows (see also
date syntax):
<h2>W3C Recommendation 14 August 2007</h2>
If this is a modified Recommendation that was modified in place or is a new edition, the document MUST include both the original publication date and the modification date. For example:
<h2>W3C Recommendation 7 April 2004,
edited in place 19 August2004</h2>dl list,
where each dt element marks up an identifier role ("This Version", "Latest Version", "Previous Version", etc.)
and each dd element includes a link whose link text is the identifier.
<p>Please refer to the <a
href="http://www.w3.org/..."><strong>errata</strong></a>
for this document, which may include some normative
corrections.</p>
The order of the a and strong elements
MAY be reversed.
See also suggestions on errata page
structure in the Manual of Style. Note: Do not
put the errata document in TR space as the expectation is that
we will not modify document in TR space after publication; see the policy for
in-place modification of
W3C Technical Reports.
<p>This document is also available in these
non-normative formats:
<a href="REC-shortname-20020101.html">single HTML
file</a>, <a href="REC-shortname-20020101.tgz">gzipped tar file of
HTML</a>.</p>
<p>See also
<a href="
http://www.w3.org/2003/03/Translations/byTechnology?technology=shortname">
<strong>translations</strong></a>.</p>
See suggestions on translations in the manual of style.
abbr element MAY be used in place of acronym.
Copyright © 2007 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
hr) MUST
follow the copyright.h2 element with content "Abstract" that follows the hr element.h2 element with content "Status of This
Document". The Team maintains the status section of a document.This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent.
Note: Contact the Communications Team for suitable adaptations in the case where a document has been published jointly by more than one group. In the adaptation, be sure that the text for informative-only specs or specs not going to Rec is the same as the standard text.
h2 element with content
"Table of Contents".h1-h6). The
anchor may be specified using an id (or
name if an a element is used)
attribute on any of the following: the heading element
itself, the
parent div element of the heading element (where the
heading element is the first child of the div), a
descendant of the heading element, or an a
immediately preceding the heading element.Given the parameters you have chosen, the head of your document should resemble the instance shown below. Note however that you will still need to provide a custom paragraph in the status section, and you may also have to adjust some of the recommended language according to your publication context. The sample shown does not illustrate all of the requirements of pubrules: it does not illustrate every possible publication context or requirements beyond those of the document head and status section.
The following appear in the head element but are not
shown here:
title element includes document title.<link rel="stylesheet" type="text/css"
href="http://www.w3.org/StyleSheets/TR/W3C-REC" />Please refer to the errata for this document, which may include some normative corrections.
This document is also available in these non-normative formats: ...links to formats here....
See also translations.
Copyright © 2007 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademarkdocument use rules apply.
....abstract text...
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
Please see the Working Group's implementation report (...or a statement that no report was used as part of the Director's decision...).
...Your custom paragraph here; see examples ...
This document was developed by the Sample Working Group. A complete list of changes to this document is available.
Please send comments about this document to public-mailing-list@w3.org (with public archive).
This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent.