I think his point about reading the browser vendors' blogs rather than specs
gets to the heart of the matter.  The browser vendors are just not going to
wait until 2022 for the HTML5 to be Proposed Recommendation.  Even 2012 --
when it looks like we'll actually be able to start using HTML 5 -- seems a
bit far off.  In the 10 years that it is going to take to develop a test
suite, the browser vendors are likely to have implemented any part of HTML5
that is likely to be relevant and useful.  And their implementation, rather
than the test suite implemetation, will be the de facto standard.

What really confuses me about this is that WHATWG *is* the browser vendors.
It was started to ensure the HTML standard didn't stagnate and reflected
real-world concerns.  What happened?

It really feels as if we need a standards process that is much more agile
and iterative.  Something that is much less monolithic.  If WHATWG and the
W3C are unable to do this, the browser vendors -- and the market -- will.

-jeff


2008/9/12 Andrew Duck <[EMAIL PROTECTED]>

> Jeff Croft posted an interesting comment on the state of the HTML WG/Web
> standards.
>
> http://jeffcroft.com/blog/2008/sep/11/two-thousand-twenty-two/
>
> Regards,
> Andrew
>
>
> andrew duck
> executive director | asia-pacific | quiqcorp.com
> unit 4, 243 blenheim rd | riccarton, christchurch 8041 new zealand
> p +64 3 341 7692 | f +64 3 341 7693 | m +64 212 934 985 (nz) | e
> [EMAIL PROTECTED]
>
> *******************************************************************
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: [EMAIL PROTECTED]
> *******************************************************************




-- 
Jeff Van Campen
[EMAIL PROTECTED]


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to