Re: Support Existing Content (was: Proposed Design Principles review)

Hi Maciej and Murray,

How about

"New versions of HTML should enable user agents to handle existing 
content. Where possible, documents and applications which work 
properly in older UA's should not malfunction under new versions, 
particularly in cases that the content has become common practice in 
multiple environments."

?

It seems to preserve the intent of the current statement but without 
undo emphasis on browsers per se. Maybe in striving for generality, 
I've become too vague?

The version I currently see in the wiki looks like this:

--------<quote>-----------
<http://esw.w3.org/topic/HTML//topic/SupportExistingContent>SupportExistingContent: 
Browsers implementing the new version of HTML should still be able to 
handle existing content. Ideally, it should be possible to process 
web documents and applications via an HTML5 implementation even if 
they were authored against older implementations and do not 
specifically request HTML5 processing.

All changes and additions could cause some content to malfunction at 
least in theory, but this will vary in degree. We need to judge 
whether the value of the change is worth the cost. Cross-browser 
content on the public Web should be given the most weight.
--------------</quote>-------------

I haven't followed the conversation well enough to know if both of 
your concerns are handled or not, but fewer words are often better 
words (according to the meta-principle of Occam's razor), and I think 
the "where possible" conveys the gist of both sentences in the second 
paragraph just fine.

David 

Received on Monday, 30 April 2007 17:13:14 UTC