Re: Backward-compatibility of text/html media type (ACTION-334, ACTION-364)

Anne van Kesteren wrote:
> On Tue, 02 Feb 2010 16:05:30 +0100, Julian Reschke 
> <julian.reschke@gmx.de> wrote:
>> So, just to be clear: once the text/html registration is changed to 
>> HTML5, I can't serve
>>
>>    http://greenbytes.de/tech/webdav/rfc2616.html
>>
>> as text/html anymore, as the document does not conform to HTML5 (due 
>> to head/@profile). Unless, of course, the definition of conformance is 
>> changed back to allow it.
> 
> Actually, you can, it just won't be conforming. You can serve "foobar" 
> as text/xml too.

That's exactly what the rules for re-registering a MIME type forbid -- 
making previously conforming content non-conforming.

Again:

    Changes should be requested only when there are serious omissions or
    errors in the published specification.  When review is required, a
    change request may be denied if it renders entities that were valid
    under the previous definition invalid under the new definition.

(<http://tools.ietf.org/html/rfc4288#section-9>)

Best regards, Julian

Received on Tuesday, 2 February 2010 15:15:37 UTC