UK Web Focus (Brian Kelly)

Innovation and best practices for the Web

The HTML5 Standardisation Journey Won’t Be Easy

Posted by Brian Kelly on 3 Feb 2011

I recently published a post on Further HTML5 Developments in which I described how the W3C were being supportive of approaches to the promotion of HTML5 and the Open Web Platform. However in a post entitled  HTML is the new HTML5 published on 19th January 2011 on the WhatWG blog Ian Hickson, editor of the HTML5 specification (and graduate of the University of Bath who now works for Google) announced that “The HTML specification will henceforth just be known as ‘HTML'”. As described in the FAQ it is intended that HTML5 will be a “living standard:

… standards that are continuously updated as they receive feedback, either from Web designers, browser vendors, tool vendors, or indeed any other interested party. It also means that new features get added to them over time, at a rate intended to keep the specifications a little ahead of the implementations but not so far ahead that the implementations give up.

What this means for the HTML5 marketing activities is unclear. But, perhaps more worrying is what this will mean for the formal standardisation process which W3C has been involved in.  Since it seems that new HTML(5) features can be implemented by browser and tool vendors this seems to herald a return to the days of the browser wars, during which Netscape and Microsoft introduced ‘innovative’ features such as the BLINK and MARQEE tags.

On the W3C’s public-html list Joshue O Connor (a member of the W3C WAI Protocol and Formats Working Group) feels that:

What this move effectively means is that HTML (5) will be implemented in a piecemeal manner, with vendors (browser manufacturers/AT makers etc) cherry picking the parts that they want. … This current move by the WHATWG, will mean that discussions that have been going on about how best to implement accessibility features in HTML 5 could well become redundant, or unfinished or maybe never even implemented at all.

In response Anne van Kesteren of Opera points out that:

Browsers have always implemented standards piecemeal because implementing them completely is simply not doable. I do not think that accepting reality will actually change reality though. That would be kind of weird. We still want to implement the features.

and goes on to add:

Specifications have been in flux forever. The WHATWG HTML standard since 2004. This has not stopped browsers implementing features from it. E.g. Opera shipped Web Forms 2.0 before it was ready and has since made major changes to it. Gecko experimented with storage APIs before they were ready, etc. Specifications do not influence such decisions.

Just over a year ago a CETIS meeting on The Future of Interoperability and Standards in Education explored “the role of informal specification communities in rapidly developing, implementing and testing specifications in an open process before submission to more formal, possibly closed, standards bodies“. But while the value of rapid development, implementation and testing was felt to be valuable there was a recognition of the continued need for the more formal standardisation process.  Perhaps the importance of rapid development which was highlighted at the CETIS event has been demonstrated by the developments centred around HTML5, with the W3C providing snapshots once the implementation and testing of new HTML developments have taken place, but I feel uneasy at the developments. This unease has much to do with the apparent autonomy of browser vendors: I have mentioned comments from employees of Google and Opera who seem to be endorsing this move (how would we feel if it was Microsoft which was challenging the W3C’s  standardisation process?). But perhaps we should accept that significant Web developments are no longer being driven by a standards organisation or from grass-roots developments but from the major global players in the market-place? Doesn’t sound good, does it – a twenty-first century return to browser vendors introducing updated versions of BLINK and MARQUEE elements as they’ll know what users want :-(

3 Responses to “The HTML5 Standardisation Journey Won’t Be Easy”

  1. Hello.

    I think this is a bit of a misunderstanding of the situation. The main aim of the ‘living standard’ of HTML isn’t to ensure that every browser implements every feature in the same way. The aim instead is to ensure that for the features that the browser vendors do decide to implement, they implement them in the same way.

    This solves the main problem with the ‘browser wars’ – which was that two different browsers would implement the same feature (most famously, the CSS box model) in different ways.

    Different browsers implementing different sets of features isn’t that much of a problem – as good development practice has always meant ‘progressive enhancement’ – ie if a feature exists, then it adds an enhancement to the page design/functionality, but if it’s not implements, the page is still usable.

    Even if all new browsers did implement the same sets of features, we’d still need to follow this approach, so that our pages are backwards-compatible with older browsers (the approach of saying ‘this page is HTML version X, if you don’t support that then please don’t bother to render it’, which XHTML kinda did, isn’t really very sustainable or realistic).

    When it comes to browser vendors having an active role in the HTML living standardisation process – well, that’s just a pragmatic way of trying to make sure that the features that do get standardised are likely to actually get implemented.


  2. […] The HTML5 Standardisation Journey Won’t Be Easy […]

  3. Jon Warbrick said

    Hmm. “The evolving standard that is HTML makes me uneasy but the evolving non-standard that is Twitter doesn’t” – discuss. :-)

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: