This is the checklist used by the W3C Webmaster for maintaining the W3C technical reports index. Editors and Team contacts should consult How to Write a W3C Technical Report for detailed guidance. Publication requests should be sent to webreq@w3.org (archive) and w3t-comm@w3.org (archive). If you want a member-visible archive of your request and its disposition, you may copy w3c-archive.
The Webmaster starts by examining the publication request to find the information that will be used to update the tech reports index:
The shortname determines the identifier of the latest version in a series
of documents as http://www.w3.org/TR/shortname
. The
identifier of the particular publication is determined by the shortname, the
status, and the date:
http://www.w3.org/TR/
YYYY
/
status
-
shortname
-
YYYYMMDD
Upon receiving a request to publish a technical report, the Webmaster shall make a best effort to check these constraints and, provided they are met, publish the document by linking it from the tech reports index and updating the latest version to agree with this version.
The Webmaster has created a Pubrules Checker; we recommend that Working Groups use this tool to check their documents for conform to Publication Rules.
If any constraint is not met, the Webmaster shall decline the publication request, detailing which of the following constraints were not met. See below regarding exceptions to this policy.
Find the date for the title page from the publication request. It must not be in the future; if it is, don't publish it yet. If it's too far in the past then abort and try to get a document with a newer title page date. The editor must not change the document after the title page date.
Editors and Team contacts: if you want to synchronize document's title page date with the actual date the document becomes available in the tech reports index (or with anything else), the editor must negotiate the date with the Communications Team to ensure their schedule permits. Five days advance notice is appreciated; more notice is even better, and experience shows that less than five days is risky.
The form of authorization required varies with the status of the document, etc.:
For information about publications process and requirements based on document type, editors and Team contacts should consult:
Note: in the past, shortnames have been changed between versions, and technical reports have been split and merged between versions. A conservative approach is to treat a merged or split technical report like a first publication.
The Webmaster must have confirmation from the Team contact that:
In particular, the status section must contain a customized paragraph that has not been copied from another document. This section should include the title page date of the document.
Regarding the document as a whole:
(Alternative representations such as plain text, PostScript, etc. are optional.)
<link rel="stylesheet" type="text/css"
href="http://www.w3.org/StyleSheets/TR/W3C-WD" />
<link rel="stylesheet" type="text/css"
href="http://www.w3.org/StyleSheets/TR/W3C-CR" />
<link rel="stylesheet" type="text/css"
href="http://www.w3.org/StyleSheets/TR/W3C-PR" />
<link rel="stylesheet" type="text/css"
href="http://www.w3.org/StyleSheets/TR/W3C-REC" />
<link rel="stylesheet" type="text/css"
href="http://www.w3.org/StyleSheets/TR/W3C-NOTE" />
Regarding the document head, editors and Team contacts please see guidelines on technical reports structure, including templates, sample, etc. In particular:
<div class="head">
<a href="http://www.w3.org/"> <img height="48" width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home" /></a>
title
element and an
h1
element.h2
element as follows. The date must be in
Day Month Year order with the month spelled out in full and the year in
four digits.
<h2>W3C status dd Month yyyy</h2>
for example
<h2>W3C Working Draft 03 March 2000</h2>
http://www.w3.org/TR/
YYYY
/
status
-
shortname
-
YYYYMMDDhttp://www.w3.org/TR/
shortname
For HTML:
<p
class="copyright"><a
href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#Copyright">
Copyright</a> ©2002 <a
href="http://www.w3.org/"><abbr title="World Wide Web
Consortium">W3C</abbr></a><sup>®</sup>
(<a href="http://www.lcs.mit.edu/"><abbr title="Massachusetts
Institute of Technology">MIT</abbr></a>, <a
href="http://www.inria.fr/"><abbr lang="fr" title="Institut
National de Recherche en Informatique et
Automatique">INRIA</abbr></a>, <a
href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved.
W3C <a
href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#Legal_Disclaimer">liability</a>,
<a
href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#W3C_Trademarks">trademark</a>,
<a
href="http://www.w3.org/Consortium/Legal/copyright-documents-19990405">document
use</a> and <a
href="http://www.w3.org/Consortium/Legal/copyright-software-19980720">software
licensing</a> rules apply.</p>
For XHTML:
<p
class="copyright"><a
href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#Copyright">
Copyright</a> ©2002 <a
href="http://www.w3.org/"><abbr title="World Wide Web
Consortium">W3C</abbr></a><sup>®</sup>
(<a href="http://www.lcs.mit.edu/"><abbr title="Massachusetts
Institute of Technology">MIT</abbr></a>, <a
href="http://www.inria.fr/"><abbr xml:lang="fr" lang="fr"
title="Institut National de Recherche en Informatique et
Automatique">INRIA</abbr></a>, <a
href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved.
W3C <a
href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#Legal_Disclaimer">liability</a>,
<a
href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#W3C_Trademarks">trademark</a>,
<a
href="http://www.w3.org/Consortium/Legal/copyright-documents-19990405">document
use</a> and <a
href="http://www.w3.org/Consortium/Legal/copyright-software-19980720">software
licensing</a> rules apply.</p>
</div>
hr
) must follow the
copyright.h2
element.h2
element.This document arose from January 2000 discussion on the Chairs list, after considerable experience and discussion of How to Write a W3C Technical Report.
Exceptions to these rules may be authorized by the Comm Team Lead or the Director.
The key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional in this document are to be interpreted as described in RFC2119.
Related:
20010719: Modified to reflect links to 20010719 version of Process Document.
20020226: Modified to include link to the Pubrules Checker.