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

Gregg Kellogg <> Thu, 30 September 2010 20:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 092933A6E8E for <>; Thu, 30 Sep 2010 13:23:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sWzBDVxxC9Ez for <>; Thu, 30 Sep 2010 13:23:16 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id A3EFE3A6E87 for <>; Thu, 30 Sep 2010 13:23:16 -0700 (PDT)
Received: from (unknown []) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id ADEE5AC765; Thu, 30 Sep 2010 16:22:08 -0400 (EDT)
Received: from ([]) by ([]) with mapi; Thu, 30 Sep 2010 16:23:35 -0400
From: Gregg Kellogg <>
To: "" <>
Date: Thu, 30 Sep 2010 16:23:33 -0400
Thread-Topic: [ietf-types] Q's regarding development of +json media types
Thread-Index: Actg3Vt9YKkEgscDSW278jffJWoX4g==
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MailStreet-MailScanner-ID: ADEE5AC765.18DD8
X-MailStreet-MailScanner: Found to be clean
Cc: "" <>
Subject: Re: [ietf-types] Q's regarding development of +json media types
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Media \(MIME\) type review" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 30 Sep 2010 20:23:18 -0000

I don't think it makes sense to describe JSON serializations of Notation 3 or N-Triples, as these are themselves just serializations of RDF. Perhaps what you're describing is two different JSON serializations of RDF, one which is more closely related to Notation-3 and the other N-Triples. Although, note that Notation-3 is, itself, a super-set of N-Triples (as is Turtle [1]), so is there really a requirement for two different serializations, or isn't it up to the author to chose a particular syntax using different capabilities of the format.

Also, note that Notation-3 is more than a syntax, as it includes behavior as well as representation, which is one reason Turtle was created. A purely syntactic version of Notation-3 is n3-rdf [2], which is a relatively small super-set of Turtle itself.

Does this relate, in anyway to JSON-LD [3], which is also an RDF serialization in JSON?

Perhaps application/rdf+json would be an appropriate mime-type.


[2] See N3-rdf at

On Sep 30, 2010, at 12: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?
> 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 
> stage?
> Best & TIA for any response,
> Nathan
> _______________________________________________
> ietf-types mailing list