index.html
25.4 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="EN"><head><title>SPARQL 1.1 Query Results JSON Format</title><style type="text/css">
@import url("local.css");
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
ol.enumar { list-style-type: decimal; }
ol.enumla { list-style-type: lower-alpha; }
ol.enumlr { list-style-type: lower-roman; }
ol.enumua { list-style-type: upper-alpha; }
ol.enumur { list-style-type: upper-roman; }
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
em.rfc2119 { text-transform: lowercase;
font-variant: small-caps;
font-style: normal; }
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WD.css"/></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"/></a></p>
<h1><a name="title" id="title"/>SPARQL 1.1 Query Results JSON Format</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"/>W3C Working Draft 13 September 2011</h2><dl><dt>This version:</dt><dd>
<a href="http://www.w3.org/TR/2011/WD-sparql11-results-json-20110913/">http://www.w3.org/TR/2011/WD-sparql11-results-json-20110913/</a>
</dd><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/sparql11-results-json/">http://www.w3.org/TR/sparql11-results-json/</a></dd><dt>Derived from Group Note:</dt><dd>
<a href="http://www.w3.org/TR/rdf-sparql-json-res/">http://www.w3.org/TR/rdf-sparql-json-res/</a>
</dd><dt>Editor:</dt><dd>Andy Seaborne, The Apache Software Foundation</dd><dt>Previous Editors:</dt><dd>Kendall Grant Clark, UMD Mindswap</dd><dd>Lee Feigenbaum, IBM</dd><dd>Elias Torres, IBM</dd></dl>
<p>See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=sparql11-results-json"><strong>translations</strong></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
<h2><a name="abstract" id="abstract"/>Abstract</h2><p>
<a href="http://www.w3.org/TR/sparql11-query/">SPARQL</a> is a set of standards for the
query and update of RDF data, along with ways to access such data over the web.
This document describes the representation of SELECT and ASK query results using
<a href="http://www.ietf.org/rfc/rfc4627.txt">JSON</a>.
</p></div><div>
<h2><a name="status" id="status"/>Status of This Document</h2><p><em>This section describes the status of this document at the
time of its publication. Other documents may supersede this
document. A list of current W3C publications and the latest
revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at
http://www.w3.org/TR/.</em></p>
<p>This document is both a <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#first-wd">First Public Working Draft</a> and a <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#last-call">Last Call Working Draft</a>.
Publication as a Last Call Working Draft indicates that the <a href="http://www.w3.org/2001/sw/DataAccess/">SPARQL Working Group</a> believes it has
addressed all substantive issues and that the document is stable. The Working Group expects to advance this specification to <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#RecsW3C">Recommendation Status</a>.</p><p>Comments on this document should be sent to <a href="mailto:public-rdf-dawg-comments@w3.org">public-rdf-dawg-comments@w3.org</a>, a mailing list with
a <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/">public archive</a>. Comments on this working draft are due on or before
<strong>26 October 2011</strong>. </p>
<p>Publication as a Working Draft does not imply endorsement by the W3C Membership.
This is a draft document and may be updated, replaced or obsoleted by other documents at any time.
It is inappropriate to cite this document as other than work in progress.</p><p>This is an <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsWD">Editors' Working Draft</a>.</p><p>The set of SPARQL documents comprises:</p><ul><li><a href="http://www.w3.org/TR/sparql11-query/">SPARQL 1.1 Query</a></li><li><a href="http://www.w3.org/TR/sparql11-update/">SPARQL 1.1 Update</a></li><li><a href="http://www.w3.org/TR/sparql11-protocol/">SPARQL 1.1 Protocol for RDF</a></li><li><a href="http://www.w3.org/TR/sparql11-http-rdf-update/">SPARQL 1.1 Graph Store HTTP Protocol</a></li><li><a href="http://www.w3.org/TR/sparql11-entailment/">SPARQL 1.1 Entailment Regimes</a></li><li><a href="http://www.w3.org/TR/sparql11-service-description/">SPARQL 1.1 Service Description</a></li><li><a href="http://www.w3.org/TR/sparql11-federated-query/">SPARQL 1.1 Federation Extensions</a></li><li><a href="http://www.w3.org/2009/sparql/docs/tests/">SPARQL 1.1 Conformance Tests</a></li><li>SPARQL 1.1 Query Results JSON Format (this document)</li><li><a href="http://www.w3.org/TR/rdf-sparql-XMLres/">SPARQL Query Results XML Format</a></li></ul><p>The JSON result format was previously available as a Working Group Note:
<a href="http://www.w3.org/TR/2007/NOTE-rdf-sparql-json-res-20070618/">Serializing SPARQL Query Results in JSON</a>. That Note is superseded by this specification, which does not change the normative definition of the SPARQL Query Results JSON Format. The SPARQL Working Group has not revised the <a href="http://www.w3.org/TR/rdf-sparql-XMLres/">SPARQL Query Results XML Format</a>.</p><p>The design of the features presented here is work-in-progress and does not represent
the final decisions of the working group. Implementers and application writers should
not assume that the designs in this document will not change.</p><p>Comments on this document should be sent to <a href="mailto:public-rdf-dawg-comments@w3.org">public-rdf-dawg-comments@w3.org</a>, a mailing list with a <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments">public archive</a>. Questions and comments about SPARQL that are not related to this specification, including extensions and features, can be discussed on the mailing list <a href="mailto:public-sparql-dev@w3.org">public-sparql-dev@w3.org</a>, (<a href="http://lists.w3.org/Archives/Public/public-sparql-dev">public archive</a>).</p><p>This document was produced by the <a href="http://www.w3.org/2001/sw/DataAccess/">SPARQL Working Group</a>, which is part of the <a href="http://www.w3.org/2001/sw/Activity">W3C Semantic Web Activity</a>.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/35463/status">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p></div><div class="toc">
<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <b><a href="#introduction">Introduction</a></b><br/>
2 <b><a href="#json-result-object">JSON Results Object</a></b><br/>
3 <b><a href="#select-results-form">Variable Binding Results</a></b><br/>
3.1 <a href="#select-head">"head"</a><br/>
3.1.1 <a href="#select-vars">"vars"</a><br/>
3.1.2 <a href="#select-link">"link"</a><br/>
3.2 <a href="#select-results">"results"</a><br/>
3.2.1 <a href="#select-bindings">"bindings"</a><br/>
3.2.2 <a href="#select-encode-terms">Encoding RDF terms</a><br/>
4 <b><a href="#ask-result-form">Boolean Results</a></b><br/>
4.1 <a href="#ask-head">"head"</a><br/>
4.1.1 <a href="#ask-link">"link"</a><br/>
4.2 <a href="#ask-boolean">"boolean"</a><br/>
5 <b><a href="#example">Example</a></b><br/>
6 <b><a href="#content-type">Internet Media Type, File Extension and Macintosh File Type</a></b><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <b><a href="#sec-bibliography">References</a></b><br/>
A.1 <a href="#sec-normative-refs">Normative References</a><br/>
A.2 <a href="#sec-non-normative-refs">Other References</a><br/>
</p></div><hr/><div class="body"><div class="div1">
<h2><a name="introduction" id="introduction"/>1 Introduction</h2><p>This document describes how to serialize SPARQL results (SELECT and ASK query forms)
in a <a href="http://www.ietf.org/rfc/rfc4627.txt">JSON</a> format.
The format is designed to be a complete representation of the information
in the query results. The results of a SELECT query are serilialized as
an array, where each array element is one "row" of the query results;
the results of an ASK query give the boolean value of the query result.
</p><p>An Internet Media Type is provied for <code>application/sparql-results+json</code>.</p><p>
There is also a <a href="http://www.w3.org/TR/rdf-sparql-XMLres/">SPARQL Query Results XML Format</a>
[<a href="#SRX">SRX</a>] which follows a similar design pattern but uses XML as the serialization.
</p><p>
Unless otherwise noted in the section heading, all sections
and appendices in this document are normative.
</p></div><div class="div1">
<h2><a name="json-result-object" id="json-result-object"/>2 JSON Results Object</h2><p>The results of a SPARQL Query are serialized in JSON as a single top-level JSON object. This object has a <code>"head"</code> member and either a <code>"results"</code> member or a <code>"boolean"</code> member, depending on the query form.
</p><p>This example shows the results of a <code>SELECT</code> query. The query solutions are represented in an array which is the value of the <code>"bindings"</code> key, in turn part of an object that is the value of the <code>"results"</code> key:</p><pre class="json">{
"head": { "vars": [ "book" , "title" ]
} ,
"results": {
"bindings": [
{
"book": { "type": "uri" , "value": "http://example.org/book/book6" } ,
"title": { "type": "literal" , "value": "Harry Potter and the Half-Blood Prince" }
} ,
{
"book": { "type": "uri" , "value": "http://example.org/book/book7" } ,
"title": { "type": "literal" , "value": "Harry Potter and the Deathly Hallows" }
} ,
{
"book": { "type": "uri" , "value": "http://example.org/book/book5" } ,
"title": { "type": "literal" , "value": "Harry Potter and the Order of the Phoenix" }
} ,
{
"book": { "type": "uri" , "value": "http://example.org/book/book4" } ,
"title": { "type": "literal" , "value": "Harry Potter and the Goblet of Fire" }
} ,
{
"book": { "type": "uri" , "value": "http://example.org/book/book2" } ,
"title": { "type": "literal" , "value": "Harry Potter and the Chamber of Secrets" }
} ,
{
"book": { "type": "uri" , "value": "http://example.org/book/book3" } ,
"title": { "type": "literal" , "value": "Harry Potter and the Prisoner Of Azkaban" }
} ,
{
"book": { "type": "uri" , "value": "http://example.org/book/book1" } ,
"title": { "type": "literal" , "value": "Harry Potter and the Philosopher's Stone" }
}
]
}
}</pre><p>This example shows the result from an <code>ASK</code> query:</p><pre class="json">{
"head" : { } ,
"boolean" : true
}</pre><p>Other keys, with different names, may be present in the JSON Results Object
but are not defined by this specification.</p></div><div class="div1">
<h2><a name="select-results-form" id="select-results-form"/>3 Variable Binding Results</h2><p>The results of a SPARQL <code>SELECT</code> query are serialized as
an array of bindings of variables. The value of the <code>"head"</code> key is an array of all variables projected in the query's <code>SELECT</code> clause.</p><div class="div2">
<h3><a name="select-head" id="select-head"/>3.1 "head"</h3><p>The <code>"head"</code> member gives the variables mentioned in the results and
may contain a <code> "link"</code> member.</p><pre class="json">{
"head" {
"vars" : [ ... ] ,
"link" : [ ... ] }</pre><div class="div3">
<h4><a name="select-vars" id="select-vars"/>3.1.1 "vars"</h4><p>
The <code>"vars"</code> member is an array giving the names of the variables used in the results.
These are the projected variables from the query.
A variable is not necessarily given a value in every query solution of the results.
</p><pre class="json">"vars" [ "book" , "title" ] </pre><p>The order of variable names should correspond to the variables in the SELECT clause of the query,
unless the query is of the form <code>SELECT *</code> in which case order is not significant.</p></div><div class="div3">
<h4><a name="select-link" id="select-link"/>3.1.2 "link"</h4><p>The optional <code>"link"</code> member gives an array
of URIs, as strings, to refer for further information.
The format and content of these link references is not
defined by this document.</p><pre class="json">"link" : [ "http://example/dataset/metadata.ttl" ] </pre></div></div><div class="div2">
<h3><a name="select-results" id="select-results"/>3.2 "results"</h3><p>The value of the <code>"results"</code> member is an object with a single key, <code>"bindings"</code>.</p><div class="div3">
<h4><a name="select-bindings" id="select-bindings"/>3.2.1 "bindings"</h4><p>The value of the <code>"bindings"</code> member is an array with zero
or more elements, one element per query solution.
Each query solution is a JSON object. Each key
of this object is a variable name from the query solution. The value for
a given variable name is a JSON object that
<a href="#select-encode-terms">encodes the variable's bound value, an RDF term.</a>
There are zero elements in the array if the query returned an
empty solution sequence.
Variables names do not include the initial "?" or "$" character.
Each variable name that appears as a key within the <code>"bindings"</code> array will have appeared in the <a href="#select-vars"><code>"vars"</code></a>
array in the results header.</p><p>A variable does not appear in an array element if it is
not bound in that particular query solution.
</p><p>The order of elements in the bindings array reflects the order, if any,
of the query solution sequence.</p><pre class="json">"bindings" : [
{
"a" : { ... } ,
"b" : { ... }
} ,
{
"a" : { ... } ,
"b" : { ... }
}
]</pre><p>If the query returns no solutions, an empty array is used.
</p><pre class="json">"bindings" : []</pre></div><div class="div3">
<h4><a name="select-encode-terms" id="select-encode-terms"/>3.2.2 Encoding RDF terms</h4><p>An RDF term (IRI, literal or blank node) is encoded as a JSON object.
All aspects of the RDF term are represented. The JSON object has
a <code>"type"</code> member and other members depending on the
specific kind of RDF term.</p><table style="border-collapse: collapse; border-color: #000000" border="1" cellpadding="5"><tr><th>RDF Term</th><th>JSON form</th></tr><tr><td>IRI <em><b>I</b></em></td><td><code>{"type": "uri", "value": "<em><b>I</b></em>"}</code></td></tr><tr><td>Literal <em><b>S</b></em></td><td><code>{"type": "literal","value": "<em><b>S</b></em>"}</code></td></tr><tr><td>Literal <em><b>S</b></em> with language tag <em><b>L</b></em></td><td><code>{ "type": "literal", "value": "<em><b>S</b></em>", "xml:lang": "<em><b>L</b></em>"}</code></td></tr><tr><td>Literal <em><b>S</b></em> with datatype IRI <em><b>D</b></em></td><td><code>{ "type": "literal", "value": "<em><b>S</b></em>", "datatype": "<em><b>D</b></em>"}</code></td></tr><tr><td>Blank node, label <em><b>B</b></em></td><td><code>{"type": "bnode", "value": "<em><b>B</b></em>"}</code></td></tr></table><p>The blank node label is scoped to the results object.
That is, two blank nodes with the same label in a single SPARQL Results
JSON object are the same blank node. This is not an indication of any
internal system identifier the SPARQL processor may use.
Use of the same label in another SPARQL Results
JSON object does not imply it is the same blank node.</p></div></div></div><div class="div1">
<h2><a name="ask-result-form" id="ask-result-form"/>4 Boolean Results</h2><p>The results of a SPARQL <code>ASK</code> query are serialized as
a boolean value, giving the result of the query evaluation.</p><div class="div2">
<h3><a name="ask-head" id="ask-head"/>4.1 "head"</h3><div class="div3">
<h4><a name="ask-link" id="ask-link"/>4.1.1 "link"</h4><p>The <code>"link"</code> member has the same format as the <a href="#select-link">SELECT <code>"link"</code></a> member.</p></div></div><div class="div2">
<h3><a name="ask-boolean" id="ask-boolean"/>4.2 "boolean"</h3><p>The result of an <code>ASK</code> query form are encoded by the <code>"boolean"</code> member,
which takes either the JSON value <code>true</code> or the JSON value <code>false</code>.</p><pre class="json">"boolean" : true </pre></div></div><div class="div1">
<h2><a name="example" id="example"/>5 Example</h2><p>This section is not normative.</p><p>The following JSON is a serialization of the XML document <a class="reference" href="http://www.w3.org/TR/rdf-sparql-XMLres/output.srx">output.srx</a>:</p><pre class="json">{
"head": {
"link": [
"http://www.w3.org/TR/rdf-sparql-XMLres/example.rq"
],
"vars": [
"x",
"hpage",
"name",
"mbox",
"age",
"blurb",
"friend"
]
},
"results": {
"bindings": [
{
"x" : { "type": "bnode", "value": "r1" },
"hpage" : { "type": "uri", "value": "http://work.example.org/alice/" },
"name" : { "type": "literal", "value": "Alice" } ,
"mbox" : { "type": "literal", "value": "" } ,
"blurb" : {
"datatype": "http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral",
"type": "literal",
"value": "<p xmlns=\"http://www.w3.org/1999/xhtml\">My name is <b>alice</b></p>"
},
"friend" : { "type": "bnode", "value": "r2" }
},
{
"x" : { "type": "bnode", "value": "r2" },
"hpage" : { "type": "uri", "value": "http://work.example.org/bob/" },
"name" : { "type": "literal", "value": "Bob", "xml:lang": "en" },
"mbox" : { "type": "uri", "value": "mailto:bob@work.example.org" },
"friend" : { "type": "bnode", "value": "r1" }
}
]
}
}</pre></div><div class="div1">
<h2><a name="content-type" id="content-type"/>6 Internet Media Type, File Extension and Macintosh File Type</h2><p>The Internet Media Type / MIME Type for the SPARQL Query Results JSON Format
is "application/sparql-results+json".</p><p>It is recommended that SPARQL Query Results JSON Format files have the extension ".srj" (all
lowercase) on all platforms.</p><p>It is recommended that SPARQL Query Results JSON Format files stored on Macintosh HFS file
systems be given a file type of "TEXT".</p><p>This information that follows is intended to be submitted to the IESG
for review, approval, and registration with IANA.</p><dl>
<dt>Type name:</dt>
<dd>application</dd>
<dt>Subtype name:</dt>
<dd>sparql-results+json</dd>
<dt>Required parameters:</dt>
<dd>None</dd>
<dt>Optional parameters:</dt>
<dd>None</dd>
<dt>Encoding considerations:</dt>
<dd>The encoding considerations of the SPARQL Query Results JSON
Format is identical to those of the "application/json" as specified in
[<a href="#JSON-RFC">JSON-RFC</a>].</dd>
<dt>Security considerations:</dt>
<dd>SPARQL query results uses URIs. See Section 7 of [<a href="#RFC3986">RFC3986</a>].<br/>
SPARQL query results uses IRIs. See Section 8 of [<a href="#RFC3987">RFC3987</a>].<br/>
The security considerations of the SPARQL Query Results JSON
Format is identical to those of the "application/json" as specified in
[<a href="#JSON-RFC">JSON-RFC</a>].</dd>
<dt>Interoperability considerations:</dt>
<dd>There are no known interoperability issues.</dd>
<dt>Published specification:</dt>
<dd>http://www.w3.org/TR/sparql11-results-json/</dd>
<dt>Applications which use this media type:</dt>
<dd>No known applications currently use this media type.</dd>
<dt>Additional information:</dt>
<dt>Magic number(s):</dt>
<dd>n/a</dd>
<dt>File extension(s): </dt>
<dd>".srj"</dd>
<dt>Macintosh file type code(s):</dt>
<dd>"TEXT"</dd>
<dt>Person & email address to contact for further information:</dt>
<dd>Andy Seaborne <public-rdf-dawg-comments@w3.org></dd>
<dt>Intended usage:</dt>
<dd>COMMON</dd>
<dt>Restrictions on usage:</dt>
<dd>None</dd>
<dt>Author/Change controller:</dt>
<dd>The SPARQL specification is a work product of the World Wide Web
Consortium's SPARQL Working Group. The W3C has change
control over these specifications.</dd>
</dl></div></div><div class="back"><div class="div1">
<h2><a name="sec-bibliography" id="sec-bibliography"/>A References</h2><div class="div2">
<h3><a name="sec-normative-refs" id="sec-normative-refs"/>A.1 Normative References</h3><dl>
<dt>
<a name="JSON-RFC" id="JSON-RFC">[JSON-RFC]</a>
</dt>
<dd>
<a href="http://www.ietf.org/rfc/rfc4627.txt">RFC 4627</a>,<br/>
The application/json Media Type for JavaScript Object Notation (JSON),<br/>
D. Crockford,<br/>
<a href="http://www.ietf.org/rfc/rfc4627.txt">http://www.ietf.org/rfc/rfc4627.txt</a>
</dd>
<dt>
<a name="RFC3986" id="RFC3986">[RFC3986]</a>
</dt>
<dd>
<a href="http://www.ietf.org/rfc/rfc3986.txt">RFC 3986</a>,<br/>
Uniform Resource Identifier (URI): Generic Syntax,<br/>
T. Berners-Lee, R. Fielding, L. Masinter, <br/>
<a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
</dd>
<dt>
<a name="RFC3987" id="RFC3987">[RFC3987]</a>
</dt>
<dd>
<a href="http://www.ietf.org/rfc/rfc3987.txt">RFC 3987</a>,<br/>
Internationalized Resource Identifiers (IRIs),<br/>
M. Dürst, M. Suignard, <br/>
<a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>
</dd>
</dl></div><div class="div2">
<h3><a name="sec-non-normative-refs" id="sec-non-normative-refs"/>A.2 Other References</h3><dl>
<dt>
<a name="SRX" id="SRX">[SRX]</a>
</dt>
<dd>
<a href="http://www.w3.org/TR/rdf-sparql-XMLres/">SPARQL Query Results XML Format</a>,<br/>
D. Beckett and J. Broekstra (Editors),<br/>
W3C Recommendation 15 January 2008.
</dd>
</dl></div></div></div></body></html>