Re: [ietf-types] Update on the pending registration of text/n3
"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Wed, 26 January 2011 06:23 UTC
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf-types@core3.amsl.com
Delivered-To: ietf-types@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 55B6B3A6938 for <ietf-types@core3.amsl.com>; Tue, 25 Jan 2011 22:23:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.948
X-Spam-Level:
X-Spam-Status: No, score=-99.948 tagged_above=-999 required=5 tests=[AWL=-0.758, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_45=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hm8LwMeFoJAs for <ietf-types@core3.amsl.com>; Tue, 25 Jan 2011 22:23:26 -0800 (PST)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by core3.amsl.com (Postfix) with ESMTP id E72C73A692E for <ietf-types@ietf.org>; Tue, 25 Jan 2011 22:23:25 -0800 (PST)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id p0Q6QINp020138 for <ietf-types@ietf.org>; Wed, 26 Jan 2011 15:26:18 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 6537_3189_2f0abc26_2915_11e0_b6a8_001d096c5782; Wed, 26 Jan 2011 15:26:18 +0900
Received: from [IPv6:::1] ([133.2.210.1]:36688) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S14BEBFA> for <ietf-types@ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 26 Jan 2011 15:26:17 +0900
Message-ID: <4D3FBE77.8060906@it.aoyama.ac.jp>
Date: Wed, 26 Jan 2011 15:25:59 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: nathan@webr3.org
References: <4D3F7F88.9060204@webr3.org>
In-Reply-To: <4D3F7F88.9060204@webr3.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: Tim Berners-Lee <timbl@w3.org>, ietf-types <ietf-types@ietf.org>
Subject: Re: [ietf-types] Update on the pending registration of text/n3
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 06:23:32 -0000
Hello Nathan, others, I suggest you have a look at http://www.w3.org/2002/06/registering-mediatype. It may be that not everything on that page can be applied directly, but I hope it still helps. Regards, Martin. On 2011/01/26 10:57, Nathan wrote: > Hi, > > I've been asked to find out about the registration of the 'text/n3' > media type, relating to Notation3 [1,2]. To quote from the annotated > design issue [2]: > > """The type application/n3 was applied for in 2002 and again in 2006. > The IETF-W3C liaison meeting established that the mime type would be > formally awarded when the N3 specification was in a 'published' form. In > the mean time, it should be used as part of the point of N3 is to be > human readable, and so the text tree is indicated. The application for > text/rdf+n3 with the IANA registry is pending as of 2006-02 as IANA > #5004. There was an agreement to change it to text/n3 as the rdf+ idea > met with significant criticism. While registration is pending, > applications should use the proposed type in anticipation of > registration, not an x- type.""" > > The specification is now 'solid', and has been for a considerable time, > further: > > - There are many implementations which have been made over the 10 years > - There is a significant amount of Notation3 data available on the web > and in use > - There is significant reluctance to further deploy Notation3 data based > PURELY on the lack of MIME registration. > - There is still a lot of confusion as to what the content-type is (as > no media type is registered) > - There is no entry in the default Apache mime.types file, so serving > and negotiating these files is more difficult. > > Consequently, can you give either myself or Tim Berners-Lee (cc-d) an > update on the pending application, or inform us as to the best course of > action in order to get the 'text/n3' media type registered in a timely > fashion. > > Best, > > Nathan > > [1] http://www.w3.org/TeamSubmission/n3/ > [2] http://www.w3.org/DesignIssues/Notation3 > _______________________________________________ > ietf-types mailing list > ietf-types@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-types > > -- #-# Martin J. Dürst, Professor, Aoyama Gakuin University #-# http://www.sw.it.aoyama.ac.jp mailto:duerst@it.aoyama.ac.jp