Re: [ietf-types] Update to text/html registration

[Julian Reschke <[e-mail]>]

On 09.08.2012 14:27, Michael[tm] Smith wrote:
> Julian Reschke <[e-mail]>, 2012-08-09 14:07 +0200:
>
>> On 07.08.2012 19:28, Michael[tm] Smith wrote:
>>> Mark Baker <[e-mail]>, 2012-08-07 10:00 -0400:
>>>> I left the WG when HTML5 was deliberately backwards-incompatible,
>>>
>>> Not sure what in particular you thought was deliberately backwards-
>>> incompatible, but OK.
>>
>> Some things that are valid HTML4 aren't conforming (valid) in HTML5 anymore.
>
> I wouldn't call that backwards-incompatible, because it only relates to
> validation. I take backwards-compatibility to mean that we're not breaking
> browser behavior for any existing content on the Web. Any elements or
> attributes that had browser processing/rendering behavior associated with
> them prior to HTML5 have that same behavior in HTML5. Document conformance
> and validity are a separate thing, and making that always match what HTML4
> is a non-goal.

Understood.

But media type updates are not supposed to make existing content 
invalid; thus the updated text/html registration needs to state that, 
for instance, HTML4 strict can continue to be labelled text/html.

Best regards, Julian