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

Mark Nottingham <mnot@mnot.net> Mon, 14 November 2011 22:46 UTC

Return-Path: <mnot@mnot.net>
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 DC44A11E817C for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 14:46:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.907
X-Spam-Level:
X-Spam-Status: No, score=-102.907 tagged_above=-999 required=5 tests=[AWL=-0.308, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 neZB5O2fr0NG for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 14:46:46 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 281C911E80D6 for <apps-discuss@ietf.org>; Mon, 14 Nov 2011 14:46:46 -0800 (PST)
Received: from [10.6.129.23] (unknown [64.39.4.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 884CA22E1EB; Mon, 14 Nov 2011 17:46:39 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <C68CB012D9182D408CED7B884F441D4D0611DABF22@nambxv01a.corp.adobe.com>
Date: Mon, 14 Nov 2011 16:46:41 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <5900EAE0-9572-42DB-990C-5ADAD3B443A6@mnot.net>
References: <C68CB012D9182D408CED7B884F441D4D0611DABF22@nambxv01a.corp.adobe.com>
To: Larry Masinter <masinter@adobe.com>
X-Mailer: Apple Mail (2.1251.1)
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 22:46:47 -0000

Larry,

I was happy to see your positive response to this; what we're trying to do with happiana is aligned with the spirit of what Roy is proposing (as was said later in this thread, to reduce the cost of registration), if not the details (because that's where the devil lies, as pointed out by Frank and others).

Folks who haven't been following that list may want to have a quick look through:
  http://www.w3.org/wiki/FriendlyRegistries
  http://www.w3.org/wiki/FriendlyRegistryProcess

Cheers,


On 13/11/2011, at 12:59 PM, Larry Masinter wrote:

> 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

--
Mark Nottingham
http://www.mnot.net/