§02 Web Standards

How Web Standards Get Adopted

Web standards are the building blocks of the modern Internet, yet the path from a clever specification draft to widespread adoption is a complex, multi-stage process. Aspiring standards must clear formal checkpoints, prove implementation experience, and persuade other actors to adopt them. At every turn, consensus and practical impact matter as much as elegance.

The life of a web standard begins with a proposal. Interest in a new capability or feature will often crystallize around a use case that several W3C members wish to enable. The Director then has the authority to announce the launch of a charter for an Interest Group or Working Group focused on that theme, allowing willing members and invited experts to join in developing the idea.

A draft is given Working Draft status so that the team can iterate and the community can engage with the material. The Working Group’s work proceeds through cycles of revision and public review, with each of several drafts published as a new Working Draft. The drafts incrementally incorporate feedback from reviewers and move toward a more complete specification.

Still, drafts are not the finish line. A Working Draft may issue a Call for Implementations and a Proposed Recommendation when it believes the material ready for final review. In the 2005 process, the Director could exempt the Working Group from a Call for Implementation if the entrance criteria for the next stage were already satisfied. The CSS Working Group today explains that it uses a “Last Call for Comments” after resolving known issues, signaling that it now needs feedback on how the specification operates in real world tests and implementations.

The work of securing adoption intensifies after the Last Call stage. That marks the beginning of the Candidate Recommendation phase, which requires the Working Group to build a robust test suite for the proposed specification and generate an implementation report. Only candidates that can demonstrate two correct, independent implementations of each feature may advance to the Proposed Recommendation stage for broad review by Members as well as the public. The candidacy process in turn sharpens the focus on interoperability and consensus, since a spec may appeal technically but still fail because the design calls for incompatible implementations or the team cannot assemble a second one.

Finally, when a Proposed Recommendation is reviewed and endorsed by the W3C Director as a full Recommendation, it is published as a W3C standard. Note the process is not finished when a recommendation is published — it has to be truly broadly adopted. W3C says public endorsement by Members and the web community is crucial for a specification to be considered a true web standard

The need for widespread adoption is the reason that technical elegance alone does not determine a standard’s fate.

This is the stage that decides a standard’s fates.

In CSS, the path from Last Call to full Recommendation may leave a standard’s fate in the hands of engineering teams who decide whether to implement the feature in a browser release. If the feature is implemented, but not widely picked up by web developers, it cannot develop the developer experience feedback that proves it is an operational success

The importance of independent implementation cannot be overstated. Techniques like test-driven development and continuous integration have moved into the development of CSS and other web standards in part to sidestep the problem of advertising a technique that can only be demonstrated with screen shots and hand-built demonstrations. A standard that can embody itself in a browser release, and can be monitored and discussed as it is tested by web developers, stands a much greater chance of proceeding all the way through to adoption.

In all, the journey from draft to Recommendation is a long one that requires significant course corrections and consensus building. Even a working draft that is very beautiful technically might fall by the wayside when rival techniques make it through to full Recommendation. Even a recommendation which uniquely satisfies a web capability may be sideline if its complexity sets a too-high barrier to adoption or some reality of web development makes it impractical to implement widely.

When the web development community is weighing where to place a new technology in a site’s design or a site’s browser-dependent workflow, standards support is still an important factor. A recommendation from W3C sends a strong signal about the stability and openness of a technology, which makes it much easier to justify its selection over novel or proprietary alternatives. But, even at that stage, a web developer still has to weigh the technical fitness of a standards recommendation and the wider existence of practical tools support.