Recently, Adobe, along with many others in the community, initiated a major community effort to build a common suite of developer-oriented documentation of the Open Web Platform as a community effort sponsored by the World Wide Web Consortium (W3C) .
One of the problems with standards is that generally, they are meant more for implementors and less for users of the standards (often by design). Those who actually write the standards and work on the committees that create them know that they are fragile interface descriptions – and this fragility is what requires the care in their crafting.
Standards specifications are necessarily quite detailed, in order to really promote interoperability and ensure things work the same. And this is where things get sticky. The implementations are based on the standard or the specification, and all standards (well, nearly all) are written in native language by people who are usually specialists in technology, as are many people who implement the developer-oriented documentation.
What’s exciting here is that the Web Platform Docs (WPD) effort is really targeted at the user community to help document the standards in a way that is useful to that community.
But a standard really only gains value when it is implemented and widely deployed. And this is why the WPD is so innovative. WPD is about use and deployment of the standard. It has tutorials on how to use a feature; it has examples of uses. This is the kind of material that the W3C working group does not have time to create, but values. It is what the vendors provide to get their implementations used.
The importance of the site, from a standards point of view, is that it helps build an informed user base. Not at all a simple task.
The Web is evolving – and in its evolution, it is forcing others to change as well. Ten years ago, this type of common activity, open to all (for both contributions and information) would have been if not unthinkable, at least foreign. With this announcement, the contributors and the W3C have (hopefully) begun to change the way standards are seen – to an easier and kinder environment. And this is a good thing.
For an Adobe developer’s view, see: What’s one of the biggest things missing from the Web?