Also On This Page →

Publication Policies

Resources

Tools

for :

About This Document

As of 12 June 2017, this document has been superseded by a newer version.

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.

Steps for Publication of a Candidate Recommendation (update with editorial changes)

If the document contains some substantive changes since the previous publication, NONE of steps below are applicable.

Once the Group determined that the requirements of section 6.4.1 do NOT apply, the W3C follows the steps described below to update a Candidate Recommendation (update with editorial changes). 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.

Publication Planning
Publication

Please take note of the W3C Process Document provisions regarding when to publish an update to a Candidate Recommendation (update with editorial changes) without Director's approval:


Publication Request

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.

  1. Document title and URI(s). Document URI requirements are described in Publication Rules.
  2. One or two sentences of description of the specification (for communication purposes on the "current status" pages). The sentence may be taken from the abstract. As an example, see status section for specifications related to mobile web authoring. These status pages, as their name suggests, let the community know about relationships among close specifications, what to use and not to use, how things fit together, etc. Contact the Comm Team with questions at w3t-comm@w3.org. Note: The Webmaster may also ask the Document Contact for assistance in categorizing the specification in an existing (or new) group on the TR page. If there is no change in the description since the previous publication, this can be ommitted.
  3. A proposed publication schedule.
  4. Since there has been a previous Candidate Recommendation and the changes are only editorial, W3C can skip the Patent Policy Exclusion (see the Patent Policy FAQ). If not, a proper transition request with the approval of the Director will be needed.

Scheduling Publication

The Document Contact negotiates a publication date with the Webmaster. Each publication request SHOULD propose a 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.

The Webmaster publishes on Tuesdays and Thursdays (cf. the announcement to chairs). Regarding advance notice:

If the Webmaster finds errors during the publication process, he will endeavor to publish on the desired date, but he MAY also postpone publication to the next available publication date in order to resolve issues. In general, it will not be necessary to change the title page date of a document that is published a couple of days later than planned. 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.

Publication

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:

  1. The publication request is complete, and
  2. The document satisfies the pubrules requirements verified by the Webmaster.

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.


Page owned and process managed by Philippe Le Hégaret and Ralph Swick on behalf of the W3C Director.
Philippe Le Hégaret, editor
This document has been constructed by merging information from several "How to" documents created by Dan Connolly, Al Gilman, and others. A filter is applied to the document source to provide transition-specific views.
Last modified: $Date: 2017/06/12 17:56:30 $ by $Author: plehegar $