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 firstname.lastname@example.org.
If you are a newly appointed editor in your Working Group, here is some advice that should be useful to get you started.
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.
W3C has developed a set of resources giving advices and guidelines on editing W3C specifications in varous domains:
During the internal development of a specification, make sure to distinguish official drafts from internal ones using the style for Group-internal Drafts.
W3C editors have developed several types of HTML and XML based grammars to make it easier to develop and maintain their specifications.
Here are tools that can prove to be useful when developing your specification.
diffbetween 2 HTML versions of a document; W3C offers an on-line HTMLDiff service
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.
There is no documentation for now (except for MathJax).
Feedback is to @w3c/tilt and is welcome on GitHub