Re: [apps-discuss] font/* (and draft-freed-media-type-regs)

Ned Freed <ned.freed@mrochek.com> Mon, 14 November 2011 21:52 UTC

Return-Path: <ned.freed@mrochek.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 E0DBB21F8EA5 for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 13:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.431
X-Spam-Level:
X-Spam-Status: No, score=-2.431 tagged_above=-999 required=5 tests=[AWL=-0.132, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 3kztmOf7fNSq for <apps-discuss@ietfa.amsl.com>; Mon, 14 Nov 2011 13:52:32 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6271A21F8AD6 for <apps-discuss@ietf.org>; Mon, 14 Nov 2011 13:52:32 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O8EV9BVJCG011863@mauve.mrochek.com> for apps-discuss@ietf.org; Mon, 14 Nov 2011 13:52:27 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O8DV7Q11A800RCTX@mauve.mrochek.com>; Mon, 14 Nov 2011 13:52:21 -0800 (PST)
Message-id: <01O8EV98HXC800RCTX@mauve.mrochek.com>
Date: Mon, 14 Nov 2011 13:44:09 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Mon, 14 Nov 2011 16:27:04 +0900" <4EC0C2C8.2010500@it.aoyama.ac.jp>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format=flowed
References: <C68CB012D9182D408CED7B884F441D4D0611DABF0F@nambxv01a.corp.adobe.com> <4EC0C2C8.2010500@it.aoyama.ac.jp>
To: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Cc: "gadams@xfsi.com" <gadams@xfsi.com>, David Singer <singer@apple.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] font/* (and draft-freed-media-type-regs)
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 21:52:33 -0000

> On 2011/11/13 5:25, Larry Masinter wrote:
> > I see no use case for why having font/opentype is any better than application/opentype

> It's just fine if you, and some others, don't see it. Does that mean
> that you have to fight against it? You haven't shown, even less
> mentioned, any problem for font/opentype.

Good point. I have no skin in this particular game - aside from slightly
complicating the media review process I have no personal need for font/*. But
if there's a constituency this type helps, I'm all for it.

> My guess is that we would have around 10 or so font types registered
> (and no font type sniffing) if a font/ top level type had been approved
> in a 1990'ish timeframe.

And we may or may not have any luck rectifying this at this late date. But I'm
not  seeing a reason not to try.

> ...

> > I also recall a number of years ago an attempt to define "chemical/*" as a
> > new top level type for use in defining file formats?

> So what? Were there good reasons to reject it? Or was it rejected
> because some people believed that new top level types were "A BIG
> NO-NO"? Or because of some FUD?

Didn't chemical kind of morph into model? Or am I getting the history confused?

> > My conclusion from this discussion is that we should declare the MIME
> > hierarchy closed to new top level types; we've only gotten very limited use and
> > value out of the hierarchy, compared to the pain and difficulty (text/xml vs
> > application/xml).

> The problems between text/xml and application/xml are very specific. And
> they may be interpreted to say that tying particular processing rules to
> particular types, unless absolutely necessary (e.g. structured types),
> may be a bad idea. That doesn't mean that top-level types in general are
> a bad idea.

Agreed.

> The reason that we have gotten very little value out of registering new
> top level types may be mostly that virtually no new types have been
> registered, because people are claiming that we get very little value
> out of them. It sounds funny, but it isn't.

No, it really isn't funny, is it?

				Ned