W3C names four new editors of HTML5 spec
They just keep plugging away on that standard
Agentless Backup is Not a Myth
The Worldwide Web Consortium (W3C) has named four people as the new editors of its HTML5 specification, following a recent split that divided the HTML standardization process into two parallel efforts.
The new editors were announced on Wednesday by HTML Working Group co-chair Paul Cotton in a message posted to the W3C's public HTML mailing list.
They are Travis Leithead and Erika Doyle Navara, both Microsoft employees; Ted O'Connor, an Apple employee; and Silvia Pfieffer, an independent consultant whose company, Ginger Technologies, specializes in HTML video.
Cotton gave no specific explanation for any of the appointments, saying only, "After evaluating all the applications, we chose the above HTML5 editorial team based on the individual qualifications of the new editors as well as the combination of the individual appointee's qualifications."
The four co-editors will be tasked with maintaining the W3C's formal HTML5 specification, which seeks to be the definitive document of the markup language that underlies the web.
Previously, the HTML5 spec had a single editor, Google's Ian Hickson. But Hickson quit the W3C effort in April to concentrate on editing the alternate HTML standard documents maintained by the Web Hypertext Applications Technology Working Group (WHATWG), a splinter organization of the W3C.
"The WHATWG effort is focused on developing the canonical description of HTML and related technologies, meaning fixing bugs as we find them, adding new features as they become necessary and viable, and generally tracking implementations," Hickson explained in a mailing list post last week.
In keeping with that approach, WHATWG has dropped the version number from its HTML spec, and says that henceforth it should be considered "a living standard," where the current version is always the canonical one.
By comparison, Hickson said, the W3C effort is focused on creating "a snapshot" of HTML in its current form – which the W3C is still calling HTML5 – and developing it using "the venerable W3C process." (Get it? WHATWG is young. W3C is old.)
"My hope is that the net effect of all this will be that work on the HTML Living Standard will accelerate again, resuming the pace it had before we started working with the W3C working group," Hickson wrote.
Critics of WHATWG's approach say the whole idea of a living standard is silly, and that it will be impossible for browsers to maintain compatibility with the HTML standard if the specifications are in constant flux.
Overall, however, browser makers appear to disagree. WHATWG was founded by representatives of Apple, Mozilla, and Opera, and its current steering committee includes reps from Google. All of those companies' browsers have already implemented HTML5 features, even though the standard is not yet final.
But the consensus is not total. Although Internet Explorer has also implemented HTML5 features, Microsoft has yet to join WHATWG. Also, half of the new W3C HTML5 edit team hails from Redmond.
The W3C gave no word on whether it expects four editors to get the job of drafting the HTML5 spec done any faster than one would have. At its present rate, the standards org says not to expect HTML5 to reach "Recommendation" status – the final phase of the standardization process – until 2014. ®
Regcast training : Hyper-V 3.0, VM high availability and disaster recovery
COMMENTS
Microsoft and standards?
Also, half of the new W3C HTML5 edit team hails from Redmond.
So we can expect HTML5 to become more like the OOXML faux-standard, containing definitions such as "works like in IE9"?
Just mirroring what devs already do.
CSS3 colours have been in common use for years now, even thought CSS3 is still under development - any transparency on a website other than from GIF/PNG is thanks to this. Likewise border-radius for round borders, CSS3 transform (think google maps and openstreetmap), Server-Sent events (gaining traction for webapps), gradients video and other fun stuff.
All of these can be applied now, across browsers, without too much difficulty (I'm not too familiar with IE but I believe IE9 is not too bad, astonishingly). There is a steering commitee of sorts and the architects of the various browsers collaberate: things are not like the bad old days, this stuff is documented and tested so there's no need to guess and the vast majority of browser hacks are no longer necessary - usually it's just a matter of browser-dependent CSS prefixes, becuase the official spec is unfinalized.
Meanwhile the W3C, with the same goals and even mostly the same people, only managed to ratify CSS2.1 last June. It's prototype-led development vs. mythical-man-month style formal specification. Without the WHATWG we'd have to rely on just the latter and that, IMHO, would be a disaster.
Clarke's law should have said:
Any sufficiently large bureaucracy is indistinguishable from a snail.

IT infrastructure monitoring strategies
Agentless Backup is Not a Myth
Top 10 SIEM implementer’s checklist
Steps to Take Before Choosing a Business Continuity Partner
Enabling efficient data center monitoring