We’re done arguing why web standards are important. Accessibility, stability, quality control, uncomplicatness and ease of use have all help us put this debate to rest a long time ago. Sites championing these ideas, creat just to promote web standards — such as Chris Heilmann’s Web Standards for Business or the Web Standards Project — haven’t had to change at all since their inception in the middle of the first decade of this century.
web However, something has chang
The way standards are develop — a matter probably as important as the standards themselves. So the next community debate isn’t about web standards per se; but about how web standards should be standardiz.
What’s in the standard?
The idea that standardization is important is reflect in the language we use to describe projects and communities. For example, the home page of the JSON API states that it is a “Standard for building application programming interfaces in JSON”. The frequently ask questions (FAQ) page describes the JSON API as a specification , [1] developers talk about its use in terms of whether it is compliant . A competing project, HAL , refers to the visual language of standardization on its website — a page flow reminiscent of a formal Request For Comment (RFC) document, before you’re rirect to the actual Internet Engineering Task Force (Internet Engineering Task Force) RFC IETF).
These projects illustrate the unification of ideas about standards that, if left neglect, could lead to confusion.
These projects illustrate the unification of ideas about standards that, if left neglect, could lead to confusion. Both the JSON API and HAL specifications are de facto standards — the idea of approaching a common russia phone number data problem with a best practice that spreads organically through the development community.
The specifications we tend to think
As more common, such as those for HTML and JavaScript, are voluntary consensus each traffic source has its own standards , meaning that international standards-setting bodies and industry consortia have agre to work on and accept these specifications, as well as create incentives for their implementation. But even in a voluntary consensus environment, differing bz lists opinions can split the technology — JSON (not to be confus with the JSON API) currently has two competing voluntary consensus.