This resource describes the internal W3C Technical Report publication processes. A companion document provides more information about roles involved in these processes and interactions with the W3C Communications Team. A comparison of requirements across all document types is available.
W3C follows the steps described below for transition to a First Public Working Group Note. These steps are grouped by theme. They are not strictly ordered; in practice, some steps are completed in parallel. For instance, groups often manage the transition request/meeting steps in parallel with the publication request steps.
The message subject line and body SHOULD identify this as a "transition request"; see above for where to send the request. A First Public Working Group Note transition request MUST include:
The goal of the transition request is to secure an archived record of the Domain Lead(s)' approval of the title, and shortname. In the past, shortnames have been changed between versions, and documents have been split and merged between versions. A conservative approach is to treat a merged or split document like a first publication.
The Team Contact(s) generally present the new draft for the entire W3C Team as soon as possible after the transition request (and possibly before Domain Lead approval). The length of the presentation varies (from "more than a lightning talk" to a Project Review) depending on the technical or political complexity of the specification.
A publication request is an assertion from the Document Contact that the document satisfies the pubrules requirements. The subject line and body SHOULD identify this as a "publication request"; see above for where to send the request. A publication request MUST include the following information.
The Document Contact negotiates a publication date with the Webmaster. Each publication request SHOULD propose a publication date, which SHOULD be at least five days later. The title page date SHOULD be the same as, or shortly before, the proposed publication date. If the request does not include a proposed publication date, the Webmaster MAY consider the title page date as the proposed publication date.
If it becomes apparent that a publication date will be well after a title page date, the Webmaster SHOULD ask the Document Contact to resubmit a revised document with a more current title page date.
When scheduling publication, please note that publishing "blackouts" occur at the end of the calendar year and around certain W3C events such as AC meetings and All-Group meetings. The Communications Team announces these publishing moratoria with approximately six months notice. The announcements are linked from the Chairs' Guidebook.
In order to ensure publication standards, upon receiving a publication request the Webmaster SHALL make a best effort to verify that the document satisfies the pubrules requirements except for the accessibility requirements of section 1.6. The Webmaster SHALL publish the document (cf. the Webmaster's guide) if the following conditions have been met:
Otherwise the Webmaster SHALL NOT publish. In this case, the Webmaster SHALL provide details to the person who sent the request about which requirements have not been satisfied.
The Webmaster SHALL NOT publish the document until the date on the title page or later. The Webmaster publishes the document by updating the appropriate technical report index and updating the latest version link, and then announcing publication as described above.
A First Public Working Group Note transition announcement MUST include the following information :