Re: [ietf-types] Q's regarding development of +json media types

Nathan <nathan@webr3.org> Thu, 30 September 2010 21:13 UTC

Return-Path: <nathan@webr3.org>
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 85F253A6E85 for <ietf-types@core3.amsl.com>; Thu, 30 Sep 2010 14:13:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level:
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599]
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 BQhgK-qPaMLM for <ietf-types@core3.amsl.com>; Thu, 30 Sep 2010 14:13:16 -0700 (PDT)
Received: from smtpout07.prod.mesa1.secureserver.net (smtpout07-01.prod.mesa1.secureserver.net [64.202.165.230]) by core3.amsl.com (Postfix) with SMTP id C19873A6E5F for <ietf-types@ietf.org>; Thu, 30 Sep 2010 14:12:31 -0700 (PDT)
Received: (qmail 19729 invoked from network); 30 Sep 2010 21:13:16 -0000
Received: from unknown (86.132.168.41) by smtpout07.prod.mesa1.secureserver.net (64.202.165.230) with ESMTP; 30 Sep 2010 21:13:16 -0000
Message-ID: <4CA4FD4B.8090803@webr3.org>
Date: Thu, 30 Sep 2010 22:12:43 +0100
From: Nathan <nathan@webr3.org>
Organization: webr3
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Sandro Hawke <sandro@w3.org>
References: <4CA4E494.1010803@webr3.org> <B8818F73-6970-4A9E-9DF6-F187AEAD70AB@kellogg-assoc.com> <1285878779.22377.146.camel@waldron>
In-Reply-To: <1285878779.22377.146.camel@waldron>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf-types@ietf.org" <ietf-types@ietf.org>
Subject: Re: [ietf-types] Q's regarding development of +json media types
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: nathan@webr3.org
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: Thu, 30 Sep 2010 21:13:21 -0000

Sandro Hawke wrote:
> On Thu, 2010-09-30 at 16:23 -0400, Gregg Kellogg wrote:
>>
>> Perhaps application/rdf+json would be an appropriate mime-type.
> 
> When there's a W3C standard for this, in a year or two, sure.  Using
> that for one of a dozen experimental candidates doesn't seem like it
> would help interop very much.

Exactly, couldn't have said it better! I'd be keen to avoid 
application/(x-)(rdf+)json all together for what I'm working on.

> On the other hand, I don't have a good answer for Nathan's question.
> What kind of media type name should one use for a random format that
> might be forgotten in 3 months or might take over the world (and be very
> widely implemented)?  I can't figure that one out.

Snap, hoping somebody like Ned can give guidance :) (or anybody who has 
more of a clue than I do!)

Best,

Nathan