W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > June 2006

[OK?] Re: Registration of media type application/sparql-results+json

From: Elias Torres <elias@torrez.us>
Date: Tue, 20 Jun 2006 17:10:24 -0400
Message-ID: <44986440.90500@torrez.us>
To: public-rdf-dawg-comments@w3.org

Hi Mark,

---
 Please respond indicating whether you are or are not satisfied with
 this response. If you are, you can help our issue tracking system by
 prefixing the subject of your response with [CLOSED] (where this
 subject has [OK?]).
---

Sorry it took me long to answer, but I wanted to run my answer by the WG
so I could speak on its behalf. Although we know application/json could
suffice, we felt that it'd be important to distinguish between JSON
encoded graphs and SPARQL results format. Admittedly, JSON is a data
model, but unfortunately, there are no conventions to specify the model
type. This the same reason why we didn't use application/xml for SPARQL
Results XML Format to be able to distinguish it from RDF/XML.

-Elias

Mark Baker wrote:
> 
> Hey Elias,
> 
> Ok, I'll bite; why won't application/json suffice?
> 
> I ask because I see JSON as more akin to RDF/XML than XML, in that it
> defines a data model.  You use application/rdf+xml for SPARQL results
> in RDF/XML, right?
> 
> Mark.
> 
> 
> On 6/16/06, Elias Torres <eliast@us.ibm.com> wrote:
>>
>> see also http://www.w3.org/2001/sw/DataAccess/json-sparql/#mediaType
>>
>> Type name:
>>     application
>> Subtype name:
>>     sparql-results+json
>> Required parameters:
>>     None
>> Optional parameters:
>>     None
>> Encoding considerations:
>>     The encoding considerations of the SPARQL Query Results JSON
>> Format is
>> identical to those of the "application/json" as specified in
>> [JSON-IETF-DRAFT]
>> Security considerations:
>>     SPARQL query results uses URIs. See Section 7 of [RFC3986].
>>     SPARQL query results uses IRIs. See Section 8 of [RFC3987].
>>     The security considerations of the SPARQL Query Results JSON
>> Format is
>> identical to those of the "application/json" as specified in
>> [JSON-IETF-DRAFT]
>> Interoperability considerations:
>>     There are no known interoperability issues.
>> Published specification:
>>     http://www.w3.org/2001/sw/DataAccess/json-sparql/
>> Applications which use this media type:
>>     No known applications currently use this media type.
>> Additional information:
>> Magic number(s):
>>     n/a
>> File extension(s):
>>     ".srj"
>> Macintosh file type code(s):
>>     "TEXT"
>> Person & email address to contact for further information:
>>     Kendall Clark, Elias Torres, Lee Feigenbaum
>> <public-rdf-dawg-comments@w3.org>
>> Intended usage:
>>     COMMON
>> Restrictions on usage:
>>     None
>> Author/Change controller:
>>     The SPARQL specification is a work product of the World Wide Web
>> Consortium's RDF Data Access Working Group. The W3C has change control
>> over
>> these specifications.
>>
>> References
>>
>>  [JSON-IETF-DRAFT]
>>     JavaScript Object Notation (JSON), Internet Draft, D. Crockford,
>> http://www.ietf.org/internet-drafts/draft-crockford-jsonorg-json-04.txt
>>
>> Regards,
>>
>> Elias Torres
>> Member of RDF Data Access Working Group
>> W3C/IBM
>>
>>
> 
> 
Received on Tuesday, 20 June 2006 21:10:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:14:50 GMT