Re: [apps-discuss] HTML5 and RFC 2854

Julian Reschke <julian.reschke@gmx.de> Sat, 25 June 2011 09:52 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD4021F8493 for <apps-discuss@ietfa.amsl.com>; Sat, 25 Jun 2011 02:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.768
X-Spam-Level:
X-Spam-Status: No, score=-103.768 tagged_above=-999 required=5 tests=[AWL=-1.169, 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 f7ulPzaA6805 for <apps-discuss@ietfa.amsl.com>; Sat, 25 Jun 2011 02:52:58 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 2182321F8447 for <apps-discuss@ietf.org>; Sat, 25 Jun 2011 02:52:57 -0700 (PDT)
Received: (qmail invoked by alias); 25 Jun 2011 09:52:55 -0000
Received: from p508FBF56.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.191.86] by mail.gmx.net (mp015) with SMTP; 25 Jun 2011 11:52:55 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/dZTFBgvXdaVPZV3NhFPRl5XuqtIP379yqdL6W5s CMZNpg+25d1+YN
Message-ID: <4E05AFF0.9080705@gmx.de>
Date: Sat, 25 Jun 2011 11:52:48 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
References: <4E04C38A.6090505@gmail.com>
In-Reply-To: <4E04C38A.6090505@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Apps-discuss list <apps-discuss@ietf.org>, public-html-comments-request@w3.org
Subject: Re: [apps-discuss] HTML5 and RFC 2854
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2011 09:52:59 -0000

On 2011-06-24 19:04, Mykyta Yevstifeyev wrote:
> Hello all,
>
> Cross-posting this to Apps-discuss and html-comments lists. The proposed
> HTML5 specification (http://dev.w3.org/html5/spec/), which is currently
> in Last Call, in its Section 12.1 updates the registration of text/html
> media type. I should note that we have RFC 2854
> (http://tools.ietf.org/html/rfc2854) which also specifies this media
> type. Therefore the question is what should be done with this RFC.
> Should it be retired upon approval of HTML5? Or something else?
>
> Mykyta Yevstifeyev

HTML5 currently tries to obsolete RFC 2854; I believe this is a problem.

 From <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.

Note the second sentence; many currently valid HTML4 documents aren't 
valid HTML5 documents anymore. Thus, a document updating the media type 
registration for text/html will need to continue to allow HTML4.01 
documents as well.

See related HTML WG issue: <http://www.w3.org/html/wg/tracker/issues/53>

Best regards, Julian