Registration of media type application/sparql-results+json

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

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
participants (2)
-
Elias Torres
-
Mark Baker