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

Nathan <nathan@webr3.org> Thu, 30 September 2010 19:27 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 []) by core3.amsl.com (Postfix) with ESMTP id 59EEC3A6E60 for <ietf-types@core3.amsl.com>; Thu, 30 Sep 2010 12:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id Xbc3Cw-i18kE for <ietf-types@core3.amsl.com>; Thu, 30 Sep 2010 12:27:10 -0700 (PDT)
Received: from smtpauth04.prod.mesa1.secureserver.net (smtpauth04.prod.mesa1.secureserver.net []) by core3.amsl.com (Postfix) with SMTP id 06C783A6E7E for <ietf-types@ietf.org>; Thu, 30 Sep 2010 12:27:07 -0700 (PDT)
Received: (qmail 12578 invoked from network); 30 Sep 2010 19:27:51 -0000
Received: from unknown ( by smtpauth04.prod.mesa1.secureserver.net ( with ESMTP; 30 Sep 2010 19:27:50 -0000
Message-ID: <4CA4E494.1010803@webr3.org>
Date: Thu, 30 Sep 2010 20:27:16 +0100
From: Nathan <nathan@webr3.org>
Organization: webr3
User-Agent: Thunderbird (Windows/20100228)
MIME-Version: 1.0
To: ietf-types@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [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 19:27:11 -0000


I'm currently working on / experimenting with two JSON based 
media-types, the first is a JSON based serialization of Notation 3, the 
other a JSON based serialization of N-Triples.

I've got to the point now where I have implementations of both and need 
to content-negotiate over them, thus my initial question is what media 
type should I use in the interim whilst experimenting?

For a later date, if I were to move towards seeking registration, would 
the best approach be to work on the specifications out with any 
standards body, or to do the work as an internet-draft, or?

Would the recommended approach be to work towards a json-schema approach 
or towards a "+json" type?

And finally, for JSON based media-types do you have any special 
considerations or gotcha's I should be taking in to account at an early 

Best & TIA for any response,