WHATWG and W3C split over HTML5 spec: worrying for devs?
The two primary organisations focusing on the development of HTML5, the World Wide Web Consortium (W3C) and the Web Hypertext Application Technology Working Group (WHATWG), have gone their separate ways and decided to officially pursue the open web standard in different methods.
The WHATWG is working on the evolving “living standard” for HTML5, while the W3C continues to work at recreating static “snapshots” of the standard.
The organisations announced their partnership back in October 2006 as both pushed forward to find a common web standard, but according to WHATWG’s Ian Hickson:
“Not long after [the naming of HTML5], the W3C side of this effort decided to split their version of the spec into subspecs (e.g. splitting out the 2D canvas API, server-sent events, post message etc), and for a while we tried to match that on the WHATWG side.
“The result was an increasing confusion of versions of the spec, so we eventually went back to just having a single spec on the WHATWG side which contains everything I work on, which we now call the ‘HTML Living Standard’”, Hickson explained.
WHATWG had aligned with W3C, boasting the support of Apple, Mozilla and Opera, because of fears over how slowly W3C was working towards the common format.
Consequently, their approaches differed significantly over the years, to the extent where bug tracking couldn’t be done by one body – hence the divergence.
Worrying for developers?
It could be argued that, rid of the shackles from W3C, WHATWG’s ‘living standard’ could accelerate the development of HTML5 at an unprecedented pace.
But according to developer Ian Elliot, the fork between the two organisations is “being formalised”, saying: “If you think that these two organisations are now going their separate ways...I think you are likely to be correct”.
“Overall this doesn’t seem to be a good development. It will no longer be possible to say exactly what HTML5 is,” he added.
But do you agree? Could this be a potential disaster for the developer zone? It may have the potential to, as companies may choose one standard over another. Let us know in the comments...
- » Report: Over half of people working with APIs are not developers
- » Facebook announces winners of its 2019 Developer Circles Community Challenge
- » Python libraries imitating ‘dateutil’ and ‘jellyfish’ caught stealing SSH and GPG keys
- » Ethereum founder Vitalik Buterin supports petition to release arrested dev
- » Sophos launches a security analysis platform for developers