Re: [apps-discuss] A modest proposal for MIME types (and URI schemes)

Graham Klyne <GK@ninebynine.org> Mon, 14 November 2011 10:10 UTC

Return-Path: <GK@ninebynine.org>
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 E7B4821F8D26 for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 02:10:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.584
X-Spam-Level:
X-Spam-Status: No, score=-6.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FPaMoz-FgqE8 for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 02:10:26 -0800 (PST)
Received: from relay8.mail.ox.ac.uk (relay8.mail.ox.ac.uk [129.67.1.171]) by ietfa.amsl.com (Postfix) with ESMTP id 3635321F85CE for <apps-discuss@ietf.org>; Mon, 14 Nov 2011 02:02:33 -0800 (PST)
Received: from smtp1.mail.ox.ac.uk ([129.67.1.207]) by relay8.mail.ox.ac.uk with esmtp (Exim 4.75) (envelope-from <GK@ninebynine.org>) id 1RPtMx-00088X-Qj; Mon, 14 Nov 2011 10:02:27 +0000
Received: from tinos.zoo.ox.ac.uk ([129.67.24.47]) by smtp1.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1RPtMx-000206-3m; Mon, 14 Nov 2011 10:02:27 +0000
Message-ID: <4EC0CA2A.80005@ninebynine.org>
Date: Mon, 14 Nov 2011 07:58:34 +0000
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Larry Masinter <masinter@adobe.com>
References: <C68CB012D9182D408CED7B884F441D4D0611DABF22@nambxv01a.corp.adobe.com>
In-Reply-To: <C68CB012D9182D408CED7B884F441D4D0611DABF22@nambxv01a.corp.adobe.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
Cc: Roy Fielding <fielding@adobe.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] A modest proposal for MIME types (and URI schemes)
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: Mon, 14 Nov 2011 10:10:27 -0000

On 13/11/2011 18:59, Larry Masinter wrote:
 > I find this perspective appealing, and can't find anything wrong with it 
except that it's a break with tradition.

+1

In particular, I think, the tradition that IANA registries were/are an extension 
point for the IETF standards series (a perspective, if not strictly true).  The 
concern, and this was voiced quite strongly by some participants when we were 
working on the header field registry, is that appearance in an IANA registry may 
give the appearance of being an IETF standard.

But I sense that, in the applications area at least, the world has moved on and 
there are other ways for developers to figure out which options are likely to be 
interoperable.

I think it's worth considering.

#g
--

> I'd like to discuss the proposal for MIME registrations from Roy Fielding in http://www.ietf.org/mail-archive/web/happiana/current/msg00187.html
> and the possibility that such changes should also apply to URI schemes.
>
> You can read Roy's rationale, which makes sense to me, but my summary is:
>
> * Eliminate standards, vendor, personal trees distinction for MIME types (For URI schemes, eliminate distinction between provisional and permanent schemes)
> * ENCOURAGE vendors to ship with vendor-neutral short-named types regardless of whether they have been registered yet or not;
>     ENCOURAGE the public to register any names that they have seen in deployed software. (same for URI schemes)
> * DO NOT try to avoid duplicates
> * EXPERT REVIEW for updates to existing registrations
> * Eliminate any IESG or consensus review requirement
>
> "There is absolutely no need to prevent name collisions in the registry itself because those collisions are irrelevant -- what matters is how the names are interpreted by recipients of messages."
> "There is absolutely no need to prevent people who are not the owners of a media type from registering that type without any prefixes."
> "The registry is not operable -- it is just documentation of how the Internet is operating, and it should reflect the reality of that operation even if that means we have multiple definitions per registered type."
>
> I find this perspective appealing, and can't find anything wrong with it except that it's a break with tradition. If you're at IETF this week and want to talk about it, find me.
>
> Larry
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>