Re: [apps-discuss] font/*

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Mon, 14 November 2011 07:36 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 5D3EA11E80C2 for <apps-discuss@ietfa.amsl.com>; Sun, 13 Nov 2011 23:36:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.608
X-Spam-Level:
X-Spam-Status: No, score=-99.608 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, 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 bzQFBaJ04hZR for <apps-discuss@ietfa.amsl.com>; Sun, 13 Nov 2011 23:36:03 -0800 (PST)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 9687311E80B6 for <apps-discuss@ietf.org>; Sun, 13 Nov 2011 23:36:02 -0800 (PST)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id pAE7a16C025943 for <apps-discuss@ietf.org>; Mon, 14 Nov 2011 16:36:01 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 73af_28bc_4d488db2_0e93_11e1_aa25_001d096c566a; Mon, 14 Nov 2011 16:36:01 +0900
Received: from [IPv6:::1] ([133.2.210.1]:40639) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S156D021> for <apps-discuss@ietf.org> from <duerst@it.aoyama.ac.jp>; Mon, 14 Nov 2011 16:36:01 +0900
Message-ID: <4EC0C4E0.9000304@it.aoyama.ac.jp>
Date: Mon, 14 Nov 2011 16:36:00 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Tony Hansen <tony@att.com>
References: <4EB86078.8070904@stpeter.im> <BDC0F178EEB88CC4B3D24020@PST.JCK.COM> <4EB8D0F4.9020907@it.aoyama.ac.jp> <555BA718-A5FA-4111-9A8B-1DE99921CCE2@standardstrack.com> <60D34A5D-985C-4C97-A4FA-3CBF5CD31FCF@mnot.net> <4EB9D49C.5010100@it.aoyama.ac.jp><4EBB2FEA.5060602@dcrocker.net> <4EBB50F4.7020501@it.aoyama.ac.jp> <4EBB54E0.9090005@dcrocker.net> <00bb01cc9f87$ff24b9a0$4001a8c0@gateway.2wire.net> <4EBBABC1.1010101@it.aoyama.ac.jp> <003201cca12e$1f35f860$4001a8c0@gateway.2wire.net> <4EBF15DD.4050801@att.com>
In-Reply-To: <4EBF15DD.4050801@att.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] font/*
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 07:36:03 -0000

On 2011/11/13 9:57, Tony Hansen wrote:

> I've seen several hints of wanting to do web Accept-style queries along
> the line of
>
> Accept: font/arial, font/comicsans

Where did you see that?

> What is it that is really desired?
>
> While this sounds like it might be a nice capability,

It's a nice capability, but it's something for search engines, not for 
content negotiation.


> it really doesn't
> agree with what media types are all about.

Of course not.

> The Arial font can be
> described in many different font file formats.
>
> Media types are more for describing things like:
> MMMM/datafork-truetype
> MMMM/intellifont
> MMMM/postscriptfont
> MMMM/truedocfont
> MMMM/truetype
> MMMM/webopenfont
>
> (where MMMM is some prefix yet to be determined), within which you can
> have a description of many different fonts, including Arial and ComicSans.
>
> =======
>
> *IF* we were to define a top-level media type, I do *not* think it
> should be named "font", but instead should name it "fontformat" or
> something like that. I think naming it "font" just leads people to have
> false expectations.

I don't think so. At least once there are a few registrations, things 
should be clear. As Julian pointed out, it hasn't be a problem for 
image/, video/, ...

Regards,    Martin.


> =======
>
> I notice that if "application" were used for font format file names,
> some of the font format names would need to include the word "font" as
> part of the name. For example, "application/postscript" can not be used
> for the font format defined in the postscript standard. Instead, it
> would have to be "application/postscriptfont". This *could* be taken an
> argument for using "fontformat" as a top level type, as in
> "fontformat/postscript". However, I don't find it a convincing argument
> by itself.
>
> Tony Hansen
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss