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

Nathaniel Borenstein <nsb@guppylake.com> Mon, 14 November 2011 15:32 UTC

Return-Path: <nsb@guppylake.com>
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 F059511E81A3 for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 07:32:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 3cK9Nktympxa for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 07:32:18 -0800 (PST)
Received: from server1.netnutz.com (server1.netnutz.com [72.233.90.3]) by ietfa.amsl.com (Postfix) with ESMTP id 1D62911E80CF for <apps-discuss@ietf.org>; Mon, 14 Nov 2011 07:32:17 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=guppylake.com; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer; b=mIM4OBy84Cm9tIGsvvpbkryYc7Gtw/3hPUX1iJOB6+qXX0sk72PmA0dViJ+FdLF77t+rq0ai7jdGkdysWjiAKPlWvkKG9E/u+ikifx2J9TznDirHHx+rPwIkR14T3Czu;
Received: from [108.98.149.133] (helo=[192.168.0.197]) by server1.netnutz.com with esmtpa (Exim 4.69) (envelope-from <nsb@guppylake.com>) id 1RPyW8-0001vx-D2; Mon, 14 Nov 2011 10:32:17 -0500
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <C68CB012D9182D408CED7B884F441D4D0611DABF22@nambxv01a.corp.adobe.com>
Date: Mon, 14 Nov 2011 10:32:12 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A0C559FC-A348-456B-A4F0-F8DED0C177DC@guppylake.com>
References: <C68CB012D9182D408CED7B884F441D4D0611DABF22@nambxv01a.corp.adobe.com>
To: Larry Masinter <masinter@adobe.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server1.netnutz.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - guppylake.com
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 15:32:19 -0000

I certainly don't believe that name collisions are irrelevant; they can cause plenty of problems.  In particular, I don't understand what's supposed to happen in this kind of case:

1.  Company X designs a new media type, perhaps even only for internal use, and registers it as application/foobar

2.  Company Y designs something entirely different and registers it as application/foobar as well.

3.  Each company builds up months or years of experience with their own type, which gets scattered all through the archives, etc.

4.  Company X buys company Y and starts to integrate its infrastructure.

This wouldn't trouble me so much if there were *any* way to tell the two uses apart.  Isn't that the whole point of a registry?  If name collisions are to be allowed, why do we need a registry at all?  Why not just have independent communities of folk wisdom with their own interpretations of media type names, and pay big bucks to consultants to sort out the problems? 

If I want to define a media type for a moving picture flip-book, is it really OK if I call it "My Pictures Emerge Galloping" and use a media type of video/mpeg?  Mightn't my doing that cause problems for a whole lot of people with no responsibility for my idiocy?  -- Nathaniel


On Nov 13, 2011, at 1: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