Count BBC director of future media and technology Erik Huggers among those who don’t buy the concept of HTML5 becoming a suitable substitute for Adobe’s Flash — at least the way it is currently being developed.

In a post on the BBC Internet Blog, Huggers wrote:

The fact is that there’s still a lot of work to be done on HTML5 before we can integrate it fully into our products. As things stand, I have concerns about HTML5′s ability to deliver on the vision of a single open browser standard, which goes beyond the whole debate around video playback.

HTML5 can deliver so much more than a new way of delivering video playback in a browser. Its aims are rooted in the philosophies of Netscape (the browser as the operating system), and even Larry Ellison‘s (Network Computer concepts) — you take complexity out of the client and deliver it from the cloud. This speaks to a far greater cause than the delivery of video content. The potential democratizing power of cloud computing (to make technology and services easily accessible to anyone on the planet) is a noble cause that we support.

For this reason, we are committed to the aims of HTML5. In combination with CSS3 and Javascript, it promises a step forward for the Web. A truly interoperable experience would materially advance the capabilities we can offer to our audiences by ushering in a new class of rich interactive experiences on the Web. The benefits are not one-dimensional. As HTML5 promises to allow us to create new online products with the confidence they will work across the Web, the savings in our development and operating costs mean we can spend less on reversioning for different browsers and focus on product development. HTML5 can bring the Web together in a way that will better allow us to serve our audiences and business partners.

Not too long ago, some browser vendors were showcasing proprietary HTML5 implementations; which, in my view, threaten to undermine the fundamental promise. Recent activity in the HTML5 Working Group and the apparent split between W3C and WhatWG suggests that HTML5 might not be on the path we expect, or deliver what I believe our industry requires. Despite grand overtures from Microsoft toward HTML5 support, their new browser is yet to ship, and so the jury is out. The tension between individual motivation and collective consensus has brought an end to many noble causes in the past, and here, the pace of progress appears to be slowing on bringing HTML5 to a ratified state. History suggests that multiple competing proprietary standards lead to a winner-takes-all scenario, with one proprietary standard at the top of the stack, which is not where most of us want to be…

So my request to the W3C, HTML5 Working Group, and major browser vendors is to continue fervently on the path you began. Understand you are representing the future of the Web, as well as businesses like ours with your efforts. HTML5 is more important than any one motivation. Speed is of the essence. Professional integrity is of the essence. We are counting on you to bring one HTML5 to the Web and the W3C to help make this happen.