W3C home > Mailing lists > Public > public-html@w3.org > April 2007

Re: Intent to Conform (was Re: Version information)

From: Maciej Stachowiak <mjs@apple.com>
Date: Thu, 12 Apr 2007 10:54:59 -0700
Message-Id: <D6C4E1FE-8FDA-4EF3-8B59-43A1403754D5@apple.com>
Cc: Laurens Holst <lholst@students.cs.uu.nl>, Lachlan Hunt <lachlan.hunt@lachy.id.au>, "public-html@w3.org" <public-html@w3.org>
To: Chris Wilson <Chris.Wilson@microsoft.com>

On Apr 12, 2007, at 9:37 AM, Chris Wilson wrote:

> Laurens Holst [mailto:lholst@students.cs.uu.nl] wrote:
>> Chris Wilson schreef:
>>> All,
>>>         I need to detail an essay about compatibility and opt-in to
>>> explain the Microsoft viewpoint on this.  I have a few things on my
>>> plate I must do today, so it will probably take a day or two.  I'm
>>> going to likely be silent until then on this topic.
>> I wonder how much merit it has to discuss/decide this now; isnít the
>> necessity of this depending on the output of this working group and
>> the opinion of implementors on the feasibility to implement it  
>> without
>> breaking current pages?  Assuming on beforehand the spec will  
>> never be
>> able to define HTML5 in a way that doesnít break existing pages is I
>> think premature.
> The current HTML5 spec has severe breakages from IE's  
> implementation already.  (E.g. removing the classid and codebase  
> attributes from <object>.)  This is why I needed to write up my  
> thoughts.

I'm not sure how this is a breakage. IE could process those  
attributes and still be conformant. But content could not use them  
and remain conformant. Nothing in the spec says you can't have  

(I don't know the reasoning for this decision but I imagine it is  
because classid and codebase are generally used to request plugins  
that use a Microsoft-specific technology and only work in IE.)

>> You mentioned HTML6; if HTML6 is not interoperable without breaking
>> backwards compatibility, a version switch can be added in HTML6.
>> Saying that HTML5 wonít have versioning information does I think
>> not prevent future specifications from not having any.
> And saying that the DOCTYPE is <!DOCTYPE html5> rather than <! 
> DOCTYPE html> doesn't say that the next version actually needs to  
> be HTML6, or that it will necessitate a new DOCTYPE version.

Fair enough, but <!DOCTYPE html> has the significant advantage that  
it triggers standards mode in current browsers, so it's easier to  
make content that degrades gracefully. I don't think <!DOCTYPE html5>  

And conversely, saying that HTML5 documents start with <!DOCTYPE  
html><html> (which is already distinguishable from HTML4) would not  
rule out requiring <!DOCTYPE html><html version=6> for HTML6.

Received on Thursday, 12 April 2007 17:55:56 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:44:08 UTC