Bureaucracy is the price we pay for standardization. You imply that there is an easier way that could have standardized these technologies "long ago", I'd like to hear it.
Bureaucracies don't have to be slow. Why not publish the draft and say you're going to finalize six months after that? Right now the idea of a W3C certified HTML5 standard is useless- browsers are already implementing what we have now, and people are writing code against it.
If that doesn't work for you, how about the idea of splitting this stuff up? Web browsers are now rapidly iterating through versions, why not do the same with web standards? Small changes each time. Uncouple stuff like the <canvas> tag from HTML5 as a whole. I'm not saying that it's the ideal solution, but it might make the web standards practise at least slightly relevant.
Comments
Bureaucracy is the price we pay for standardization. You imply that there is an easier way that could have standardized these technologies "long ago", I'd like to hear it.
Bureaucracies don't have to be slow. Why not publish the draft and say you're going to finalize six months after that? Right now the idea of a W3C certified HTML5 standard is useless- browsers are already implementing what we have now, and people are writing code against it.
If that doesn't work for you, how about the idea of splitting this stuff up? Web browsers are now rapidly iterating through versions, why not do the same with web standards? Small changes each time. Uncouple stuff like the <canvas> tag from HTML5 as a whole. I'm not saying that it's the ideal solution, but it might make the web standards practise at least slightly relevant.