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

Julian Reschke <julian.reschke@gmx.de> Wed, 22 August 2012 07:56 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9E3621F867E for <ietf-types@ietfa.amsl.com>; Wed, 22 Aug 2012 00:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.488
X-Spam-Level:
X-Spam-Status: No, score=-103.488 tagged_above=-999 required=5 tests=[AWL=-0.889, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1+gyOWpwKkXU for <ietf-types@ietfa.amsl.com>; Wed, 22 Aug 2012 00:56:51 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 74C0821F867A for <ietf-types@ietf.org>; Wed, 22 Aug 2012 00:56:51 -0700 (PDT)
Received: (qmail invoked by alias); 22 Aug 2012 07:56:50 -0000
Received: from unknown (EHLO [172.24.113.24]) [192.147.117.12] by mail.gmx.net (mp002) with SMTP; 22 Aug 2012 09:56:50 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX182EY0oCfk2pW76NKx6BEzsmD/Nmf18apnhvpQKS2 1UDVdt+Nabi7w1
Message-ID: <503490C1.6090304@gmx.de>
Date: Wed, 22 Aug 2012 09:56:49 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
References: <20120807111647.GB67292@sideshowbarker> <CALcoZiqopPwsZcCy4TU_O7X1YQ5sniWjimeFFL0T-bHLZkc-jA@mail.gmail.com> <20120807172840.GH68105@sideshowbarker> <5023A808.8090007@gmx.de> <20120809122712.GP71263@sideshowbarker> <5024E121.9020906@gmx.de> <Pine.LNX.4.64.1208101714020.27616@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1208101714020.27616@ps20323.dreamhostps.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: ietf-types@ietf.org
Subject: Re: [ietf-types] Update to text/html registration
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 07:56:56 -0000

On 2012-08-10 19:17, Ian Hickson wrote:
> On Fri, 10 Aug 2012, Julian Reschke wrote:
>>
>> 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.
>
> This is obviously not true since the current text/html registration
> doesn't say HTML2 is valid, instead referencing HTML4 and XHTML1.

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

    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.

So it's indeed not a hard requirement.

RFC 2854 indeed isn't very clear about the past versions, but that 
doesn't mean we shouldn't do better this time.

The question here is: can I continue to label a (valid) HTML4 document 
which is *not* a (conforming) HTML5 document as text/html? If the answer 
is yes (and I'm pretty sure it is), the media type registration should 
mention this.

(I also note that if we don't update RFC 2854 -- which would be my 
preference -- then we should to obsolete it)

Best regards, Julian