Re: Proposal to Adopt HTML5

> So what exactly is your opinion of 
> http://wiki.whatwg.org/wiki/Changes_from_HTML4 ? What does it not 
> offer that you really need?

Well, first of all I hear its not complete :-)

I guess the level of detail is ok. The important thing is to ensure 
that it is kept up to date when things are removed/added/modified in 
HTML5 so that we don't have to compare the specs all the time.

It would also save a lot of time if there could also be a few comments 
on the rationale behind the proposals and some info on their current 
status in the WG. E.g. if there is consensus about a particular change, 
it would be useful to keep a note in the log to restrain people from 
bringing it up for discussion again.

>>> The idea of the HTML5 proposal is to effectively replace HTML4, 
>>> XHTML1 and DOM2HTML with something (substantially) better. Not to 
>>> update them.
>>
>> The charter says our mission is to "continue the evolution of HTML" 
>> that we "will maintain and produce incremental revisions of the HTML 
>> standard". This sounds more like revolution to me.
>
> Why? (Note that the HTML5 proposal is backwards compatible with 
> deployed content and implementations.)

In my mind "effectively replacing" and "not updating" is not the same 
as "continuing the evolution" and "producing incremental revisions". 
Consequently, I don't think adopting this idea will be in accord with 
the charter.

Even though HTML5 is to be backwards compatible with HTML4, the 
recommended document set will be changed significantly. If you want to 
draw on the experience of web developers, it is important to relate 
this to the corresponding recommended set in HTML4, including those 
places where we are strenghtening and tightening the spec.

--
Henrik

Received on Tuesday, 10 April 2007 23:38:28 UTC