W3C home > Mailing lists > Public > public-html@w3.org > October 2009

Re: ISSUE-55: Re-enable @profile in HTML5 (draft 1)

From: Henri Sivonen <hsivonen@iki.fi>
Date: Mon, 12 Oct 2009 10:26:56 +0300
Cc: HTMLWG WG <public-html@w3.org>
Message-Id: <13080D5C-69BE-437A-8E91-A8899882A111@iki.fi>
To: Manu Sporny <msporny@digitalbazaar.com>
On Oct 10, 2009, at 22:43, Manu Sporny wrote:

> * HTML5 breaks backwards compatibility for several good reasons.

I think the HTML5 processing rules don't break a substantial body of  
existing content. (A body of Web content is substantial if it is so  
large that the top browser vendors wouldn't dare to break it.)

Compatibility with the letter of previous specs is worthless.  
Compatibility with existing content matters. Aligning with the  
behavior of existing browsers that have had success in the market is  
used as a substitute for assessing compatibility with existing content.

> * There is currently no way for an author to specify that they would
>   like their documents to be processed as HTML5 instead of HTML6.

That's a feature, not a bug.

> * There is currently no way for an author to specify that their
>   document uses a number of extended processing behaviors built on top
>   of HTML5.

That's a feature, not a bug. To opt into extended processing, content  
should simply use extended features.

> * There is currently no way for an author to specify that their
>   document should be processed via extended processing behavior
>   using FeatureX version 1.0 instead of FeatureX version 2.0.


That's a feature, not a bug.

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/
Received on Monday, 12 October 2009 07:27:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:09 UTC