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

Kris Zyp <kris@sitepen.com> Thu, 30 September 2010 19:36 UTC

Return-Path: <kris@sitepen.com>
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 6E5AB3A6E4B for <ietf-types@core3.amsl.com>; Thu, 30 Sep 2010 12:36:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 2PAnyJwVDo9l for <ietf-types@core3.amsl.com>; Thu, 30 Sep 2010 12:36:00 -0700 (PDT)
Received: from rs61.luxsci.com (rs61.luxsci.com [65.61.166.69]) by core3.amsl.com (Postfix) with ESMTP id DF8B63A6D77 for <ietf-types@ietf.org>; Thu, 30 Sep 2010 12:35:59 -0700 (PDT)
Received: from [172.19.164.211] ([198.202.202.21]) (authenticated bits=0) by rs61.luxsci.com (8.13.8/8.13.7) with ESMTP id o8UJajZ6029861 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 30 Sep 2010 14:36:45 -0500
Message-ID: <4CA4E6D6.2040004@sitepen.com>
Date: Thu, 30 Sep 2010 13:36:54 -0600
From: Kris Zyp <kris@sitepen.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3
MIME-Version: 1.0
To: nathan@webr3.org
References: <4CA4E494.1010803@webr3.org>
In-Reply-To: <4CA4E494.1010803@webr3.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: 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
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:36:03 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 


On 9/30/2010 1:27 PM, Nathan wrote:
> Hi,
>
> 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?

These aren't mutually exclusive. JSON Schema doesn't discourage new
+json media types (in fact I think that should be encouraged), it
simply suggests a couple ways that new media types might choose to
reference a json schema.

Anyway, glad to hear of more +json media types in the works.

- -- 
Kris Zyp
SitePen
(503) 806-1841
http://sitepen.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
iEYEARECAAYFAkyk5tYACgkQ9VpNnHc4zAx+rwCcCb2+O2wge0ZkNpYJCFisjLUq
gh4AnAr/yAacEkV+6Q+jI0DZDW9b6fg7
=Jj1F
-----END PGP SIGNATURE-----