Also On This Page →

Nearby

One of the main accomplishments at W3C is to write specifications and create standards out of them. While the Working Groups at large are responsible for building consensus on the technical decisions, the editors have the heavy responsibility of transforming these decisions into actual specifications.

This page tries to gather resources that can help editors do their job: documentation, tools, tutorials, etc. If you know other resources that would benefit editors by being listed here, please inform the W3C Communication Team at w3t-comm@w3.org.

Read the W3C Publication Rules (often referred as pubrules) and ask advice on the points that are unclear; if your document doesn't comply with these rules, it cannot be published as a W3C technical report.

The Link Checker catches all the broken links that may have popped up in your document.

The Namespace checker finds potential namespaces URIs in the documents, and makes a few checks on them

HTML Tidy, originally by Dave Raggett and now maintained at SourceForge.net, is a lint that cleans up but does not validate HTML and XHTML. With indent off, Tidy can sometimes shave 10% or more off file size.

Most of these tools can be quickly accessed using the so called ,tools interface: appending ,keyword to a www.w3.org URI triggers a certain tool on this URI; for instance, appending ,validate to this page's URI will send it to the HTML validator.

Specifications should, of course, be device-independent. But,
with care, you can still include certain kinds of scripts. If
the script you want is in W3C's repository of common JavaScript libraries, you're
recommended to link to that repository, rather than make a copy
of the script. (Note that, together with the common style
sheets, these scripts are the only resources that may
be outside the specification's own directory.)