index.html
25.8 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
<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
<html lang="en" dir="ltr">
<head>
<title>SPARQL 1.1 Query Results CSV and TSV Formats</title>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<!-- ReSpec http://dev.w3.org/2009/dap/ReSpec.js/documentation.html -->
<link charset="utf-8" type="text/css" rel="stylesheet" href="local.css">
<link charset="utf-8" type="text/css" rel="stylesheet" href="respec.css">
<link charset="utf-8" type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD">
</head>
<body style="display: inherit;"><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 class="title" id="title">SPARQL 1.1 Query Results CSV and TSV Formats</h1><h2 id="w3c-working-draft-02-august-2011">W3C Working Draft 13 September 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-sparql11-results-csv-tsv-20110913/">http://www.w3.org/TR/2011/WD-sparql11-results-csv-tsv-20110913/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/sparql11-results-csv-tsv/">http://www.w3.org/TR/sparql11-results-csv-tsv/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://www.w3.org/2009/sparql/docs/csv-tsv-results">http://www.w3.org/2009/sparql/docs/csv-tsv-results</a></dd><dt>Editor:</dt><dd><span>Andy Seaborne</span>, The Apache Software Foundation</dd>
</dl><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><hr></div>
<div class="introductory section" id="abstract"><h2>Abstract</h2>
<p>
The formats CSV [<cite><a href="#bib-RFC4180" rel="biblioentry" class="bibref">RFC4180</a></cite>] (comma separated values)
and TSV [<cite><a href="#bib-IANA-TSV" rel="biblioentry" class="bibref">IANA-TSV</a></cite>] (tab separated values)
provide simple, easy to process formats for the transmission of tabular data.
They are supported as input datat formats to many tools, particularly spreadsheets.
This document describes their use for expressing SPARQL query results from
<code>SELECT</code> queries.
</p>
<p>Editor's Note:Add ASK as well? Two lines: one line of fixed variable 'answer'
and one line of <tt>true</tt> or <tt>false</tt>
</p></div><div id="sotd" class="introductory section"><h2>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 is the First Public Working Draft of a specification for two simple additional results formats
that have been found to be convenient in practice
when consuming data obtained with SPARQL. They complement
the other standard formats in XML and in JSON.
</p>
<p>The set of SPARQL 1.1 Recommendations comprises:</p>
<ul>
<li><a href="http://www.w3.org/TR/sparql11-update/">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><a href="http://www.w3.org/TR/sparql11-results-json/">SPARQL 1.1 Query Results JSON Format</a></li>
<li><a href="http://www.w3.org/TR/rdf-sparql-XMLres/">SPARQL Query Results XML Format</a></li>
</ul>
<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 published by the <a href="http://www.w3.org/2001/sw/DataAccess/">SPARQL Working Group</a> as a Working Draft. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:public-rdf-dawg-comments@w3.org">public-rdf-dawg-comments@w3.org</a> (<a href="mailto:public-rdf-dawg-comments-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/">archives</a>). All feedback is welcome.</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 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 href="http://www.w3.org/2004/01/pp-impl/35463/status" rel="disclosure">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="section" id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#intro"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a class="tocxref" href="#general-comments"><span class="secno">2. </span>Transmission issues using CSV and TSV Formats</a></li><li class="tocline"><a class="tocxref" href="#csv"><span class="secno">3. </span>CSV - Comma Separated values</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#csv-table"><span class="secno">3.1 </span>Serializing the Results Table</a></li><li class="tocline"><a class="tocxref" href="#csv-terms"><span class="secno">3.2 </span>Serializing RDF Terms</a></li><li class="tocline"><a class="tocxref" href="#csv-example"><span class="secno">3.3 </span>Example of CSV-Serialized Results</a></li></ul></li><li class="tocline"><a class="tocxref" href="#tsv"><span class="secno">4. </span>TSV - Tab Separated values</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#tsv-table"><span class="secno">4.1 </span>Serializing the Results Table</a></li><li class="tocline"><a class="tocxref" href="#tsv-terms"><span class="secno">4.2 </span>Serializing RDF Terms</a></li><li class="tocline"><a class="tocxref" href="#tsv-example"><span class="secno">4.3 </span>Example of TSV-Serialized Results</a></li></ul></li><li class="tocline"><a class="tocxref" href="#references-1"><span class="secno">A. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#normative-references-1"><span class="secno">A.1 </span>Normative References</a></li><li class="tocline"><a class="tocxref" href="#non-normative-references"><span class="secno">A.2 </span>Non-normative References</a></li></ul></li><li class="tocline"><a class="tocxref" href="#references"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#normative-references"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div>
<div class="section" id="intro">
<!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
<p>
This document describes CSV and TSV formats for expressing
the results of a SPARQL <code>SELECT</code> query.
They provide lowest common denominator
formats between systems using different
implementation technologies.
</p>
<p>Other formats for expression SPARQL results are the
SPARQL XML Results Format [<cite><a href="#bib-RDF-SPARQL-XMLRES" rel="biblioentry" class="bibref">RDF-SPARQL-XMLRES</a></cite>]
and SPARQL JSON Results Format
<!--[[SPARQL11-JSON-RES]]-->
[<a href="#SPARQL11-JSON-RES">SPARQL11-JSON-RES</a>].
Each format is useful in different application scenarios.
</p>
<p>
The SPARQL Results CVS Results Format is a lossy encoding
of a table of results. It does not encode all the details of
each RDF term in the results but instead just gives a string
without indicating the type of the term (IRI, Literal, Literal
with datatype, Literal with language, or blank node). This makes
it simple to consume data, such as text and numbers, in
applications without needing to understand the details
of RDF. In some applications, guesses as to which
elements are hyperlinks are made pragmatically, for example,
guessing that strings starting "http://" are links.
</p>
<p>
The SPARQL Results TSV Results Format does encode the details
of RDF terms in the results table by using the syntax that SPARQL
<!--[[!SPARQL11-QUERY]]-->
[<a href="#SPARQL11-QUERY">SPARQL11-QUERY</a>]
and Turtle [<cite><a href="#bib-TURTLE" rel="biblioentry" class="bibref">TURTLE</a></cite>] use. An application receiving a TSV-encoded
results set can
split each line into elements of the result row, and extract
all the details it wishes to process of the RDF terms by
simple string processing, without a complete XML or JSON parser
required by the more complex SPARQL result formats.
</p>
<p>When this document uses the words <em title="must" class="rfc2119">must</em>, <em title="must not" class="rfc2119">must not</em>, <em title="should" class="rfc2119">should</em>, <em title="should
not" class="rfc2119">should
not</em>, <em title="may" class="rfc2119">may</em> and <em title="recommended" class="rfc2119">recommended</em>, they must be interpreted as described in
RFC 2119 [<cite><a href="#bib-RFC2119" rel="biblioentry" class="bibref">RFC2119</a></cite>].</p>
</div>
<div class="section" id="general-comments">
<!--OddPage--><h2><span class="secno">2. </span>Transmission issues using CSV and TSV Formats</h2>
<p>The SPARQL results formats described here
confirm to the formal specifications of the
relevant formats, Comma Separated values (CSV) [<cite><a href="#bib-RFC4180" rel="biblioentry" class="bibref">RFC4180</a></cite>] and
Tab Separeated Value (TSV) [<cite><a href="#bib-IANA-TSV" rel="biblioentry" class="bibref">IANA-TSV</a></cite>].
</p>
<p>Systems providing these formats should note that the content types for CSV is
<tt>text/csv</tt> and for TSV <tt>text/tab-separated-values</tt>.
Being <tt>text/*</tt>, the default character set is US-ASCII.
The <tt>charset</tt> parameter <em title="should" class="rfc2119">should</em> be used in conjunction
with SPARQL Results; UTF-8 is recommended: <tt>text/csv; charset=utf-8</tt> and
<tt>text/tab-separated-values; charset=utf-8</tt>.
</p>
<p>The end-of-line in CSV is <tt>CRLF</tt> i.e.
Unicode codepoints 13 (0x0D) and 10 (0x0A).</p>
<p>The end-of-line in TSV is <tt>EOL</tt> i.e.
Unicode codepoint 10 (0x0A).</p>
<p>Applications reading these formats are advised to cope with
both CRLF and LF as end of line markers
and not rely on conformance to the formal specifications.
</p>
</div>
<div class="section" id="csv">
<!--OddPage--><h2><span class="secno">3. </span>CSV - Comma Separated values</h2>
<p>
In the SPARQL Results CSV Format,
the results table is serialized as one line listing the variables
in the results, using the CSV header line,
followed by one line for each query solution.
Values in the results are strings, for URIs and literals,
together with numbers when the literals are of numeric XSD
datatype.
</p>
<div class="section" id="csv-table">
<h3><span class="secno">3.1 </span>Serializing the Results Table</h3>
<p>
The first line of a SPARQL CSV Results Format response
is the header line giving the names of the variables
used in the result set. The header line consists of the
variable names, without leading <tt>?</tt>, separated by commas.
</p>
<p>While the <tt>text/csv</tt> format does not require a header row,
the SPARQL CSV Results Format <em title="must" class="rfc2119">must</em> use a header row.
If the content type parameter <tt>header</tt> is used,
it <em title="must" class="rfc2119">must</em> be <tt>header=present</tt>.
</p>
<p>The remaining rows are the values of the results,
with each binding determined by the position in the row,
corresponding to the entry in the header line.
</p>
<p>If a variable is not bound, an empty field is used (e.g. <tt>,,</tt>).
Each row has the same number of fields,
with each field corresponding to a binding to the variable
in the header line in the same field position.
</p>
</div>
<div class="section" id="csv-terms">
<h3><span class="secno">3.2 </span>Serializing RDF Terms</h3>
<p>The entry in each field is the string corresponding to the RDF term value.
(c.f. SPARQL STR()) without syntax to denote what kind of
term it is. The encoding quoting rules of CSV format must be
used.
</p>
<p>
Blank nodes use the <tt>_:label</tt> form from Turtle and SPARQL.
Use of the same label indicates the same blank node within the
results but has no significance outside
the results.
</p>
<p>Fields containing any of
<tt>"</tt> (<small>QUOTATION MARK</small>, code point 34, 0x22 in Unicode[<cite><a href="#bib-UNICODE" rel="biblioentry" class="bibref">UNICODE</a></cite>]),
<tt>,</tt> ((<small>COMMA</small>, code point 44, 0x2C),
<tt>LF</tt> (code point 10, 0x0A) or
<tt>CR</tt> (code point 13, 0x0D)
must be quoted using the quoting mechanism
of RFC4180 [<cite><a href="#bib-RFC4180" rel="biblioentry" class="bibref">RFC4180</a></cite>]. Fields are limited by a pair of
quotation marks <tt>"</tt>
(code point 0x22).
Within quote strings,
all characters except <tt>"</tt>,
including new line characters have their exact meaning -
newlines do not end a CSV record.
<tt>"</tt> is written a pair of quotation marks <tt>""</tt>.
<!-- For emacs "-->
</p>
</div>
<div class="section" id="csv-example">
<h3><span class="secno">3.3 </span>Example of CSV-Serialized Results</h3>
<p>Editor's Note:More complete example</p>
<pre class="box csv">x,name,knows,hpage
_:b0,Alice,_:b1,http://work.example.org/alice/
_:b1,Bob,,http://work.example.org/bob/
</pre>
</div>
</div>
<div class="section" id="tsv">
<!--OddPage--><h2><span class="secno">4. </span>TSV - Tab Separated values</h2>
<p>
In the SPARQL Results TSV Format,
the results table is serialized as one line listing the variables
in the results, followed by one line for each query solution.
All RDF terms used in the format are encoded in the format
specified by Turtle [<cite><a href="#bib-TURTLE" rel="biblioentry" class="bibref">TURTLE</a></cite>] except that the
triple quoted forms for the lexical part of literals
<em title="must not" class="rfc2119">must not</em> be used; these forms allow raw newlines and
tabs that form part of the TSV format.
</p>
<div class="section" id="tsv-table">
<h3><span class="secno">4.1 </span>Serializing the Results Table</h3>
<p>
The results table is serialized as one line listing the variables
in the results, followed by one line for each query solution.
This first line is required by the TSV format [<cite><a href="#bib-IANA-TSV" rel="biblioentry" class="bibref">IANA-TSV</a></cite>],
unlike CSV, where it is optional.
</p>
<p>Variables are serialized in SPARQL syntax, using question mark
<tt>?</tt> character followed by the variable name.
</p>
<p>Editor's Note:Alt: Variables are serialized in SPARQL syntax, using <tt>?</tt> or
<tt>$</tt> characters followed by the variable name.
Editor's Note:This will be removed unless WG comments are received.
</p>
<p>Each row of the result set is serialized by sequence of
RDF terms in SPARQL syntax, separated by a tab
(Horizontal Tab, Unicode codepoint 9) character.
</p>
<p>If a variable is not bound in a row, an empty field is used.
Each row has the same number of fields, corresponding to the variables
listed in the first row.
</p>
</div>
<div class="section" id="tsv-terms">
<h3><span class="secno">4.2 </span>Serializing RDF Terms</h3>
<p>
The SPARQL Results TSV Results Format serializes
RDF terms in the results table by using the syntax that SPARQL
[<cite><a href="#bib-RDF-SPARQL-QUERY" rel="biblioentry" class="bibref">RDF-SPARQL-QUERY</a></cite>]
<!--[[!SPARQL11-QUERY]]-->
[<a href="#SPARQL11-QUERY">SPARQL11-QUERY</a>]
and Turtle [<cite><a href="#bib-TURTLE" rel="biblioentry" class="bibref">TURTLE</a></cite>] use.
</p>
<p>
IRIs enclosed in <tt><...></tt>,
literals are enclosed with single quotes <tt>"</tt>...<tt>"</tt>
or <tt>'</tt> ...<tt>'</tt>
with optional <tt>@lang</tt> or <tt>^^</tt> for datatype.
The quotes around the lexical
form is required.
Tab, newline and carriage return characters (Unicode codepoints
0x09, 0x0A (line feed) and 0x0D (Carriage Return))
are encoded in strings as
<tt>\t</tt>, <tt>\n</tt> and <tt>\r</tt> respectively.
The long string forms using triple quotes <tt>"""</tt> and
<tt>'''</tt> <em title="must not" class="rfc2119">must not</em> be used.
<!-- Emacs: "-->
</p>
<p>
The abbreviated forms for numbers (XSD integers, decimals and doubles)
<em title="should" class="rfc2119">should</em> be used.
</p>
<p>
Blank nodes use the <tt>_:label</tt> form from Turtle and SPARQL.
Use of the same label indicates the same blank node within the
results but has no significance outside
the results.
</p>
</div>
<div class="section" id="tsv-example">
<h3><span class="secno">4.3 </span>Example of TSV-Serialized Results</h3>
<p>Editor's Note:More complete example</p>
<pre class="box tsv">x<TAB>name<TAB>knows<TAB>hpage
_:b0<TAB>Alice<TAB>_:b1<TAB>http://work.example.org/alice/
_:b1<TAB>Bob<TAB><TAB>http://work.example.org/bob/
</pre>
</div>
<p>writing <tt><TAB></tt> for a tab character.</p>
</div>
<!-- Auto generated are [[!name]] in the text
section class='appendix references'>
-->
<!-- Manual -->
<div id="references-1" class="appendix section">
<!--OddPage--><h2><span class="secno">A. </span>References</h2>
<p>This section includes references not yet included in the standard biblio DB</p>
<div class="section" id="normative-references-1">
<h3><span class="secno">A.1 </span>Normative References</h3>
<dl class="biblography">
<!--
<dt>RFC4180</dt>
<dd>Y. Shafranovich. <a href="http://www.ietf.org/rfc/rfc4180.txt">
<cite>Common Format and MIME Type for Comma-Separated Values (CSV) Files</cite></a>
October 2005. Internet RFC 3987. URL:
<a href="http://www.ietf.org/rfc/rfc4180.txt">http://www.ietf.org/rfc/rfc4180.txt</a>
</dd>
<dt>IANA-TSV</dt>
<dd>Paul Lindner. <a
href="http://www.iana.org/assignments/media-types/text/tab-separated-values"
><cite>Definition of tab-separated-values (tsv)</cite></a>
June 1993. IANA Media Type Registration. URL:
<a href="http://www.iana.org/assignments/media-types/text/tab-separated-values">http://www.iana.org/assignments/media-types/text/tab-separated-values</a>
</dd>
-->
<dt><a id="SPARQL11-JSON-RES">SPARQL11-JSON-RES</a></dt>
<dd>Andy Seaborne.
<a href="http://www.w3.org/TR/sparql11-results-json"><cite>SPARQL 1.1 Query Results JSON Format</cite></a>
W3C (in-progress) Working Draft. URL: <a href="http://www.w3.org/TR/sparql11-results-json">http://www.w3.org/TR/sparql11-results-json</a>
</dd>
<dt><a id="SPARQL11-QUERY">SPARQL11-QUERY</a></dt>
<dd>Steve Harris, Andy Seaborne.
<a href="http://www.w3.org/TR/sparql11-query/"><cite>SPARQL 1.1 Query Language</cite></a>
W3C (in-progress) Working Draft. URL: <a href="http://www.w3.org/TR/sparql11-query">http://www.w3.org/TR/sparql11-query</a>
</dd>
</dl>
</div>
<div class="section" id="non-normative-references">
<h3><span class="secno">A.2 </span>Non-normative References</h3>
</div>
</div>
<div class="appendix section" id="references"><!--OddPage--><h2><span class="secno">B. </span>References</h2><div class="section" id="normative-references"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-IANA-TSV">[IANA-TSV]</dt><dd>Paul Lindner. <a href="http://www.iana.org/assignments/media-types/text/tab-separated-values"><cite>Definition of tab-separated-values (tsv)</cite></a> June 1993. IANA Media Type Registration. URL: <a href="http://www.iana.org/assignments/media-types/text/tab-separated-values">http://www.iana.org/assignments/media-types/text/tab-separated-values</a>
</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
</dd><dt id="bib-RFC4180">[RFC4180]</dt><dd>Y. Shafranovich. <a href="http://www.ietf.org/rfc/rfc4180.txt"> <cite>Common Format and MIME Type for Comma-Separated Values (CSV) Files</cite></a> October 2005. Internet RFC 3987. URL: <a href="http://www.ietf.org/rfc/rfc4180.txt">http://www.ietf.org/rfc/rfc4180.txt</a>
</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd>David Beckett, Tim Berners-Lee. <a href="http://www.w3.org/TeamSubmission/turtle/"><cite>Turtle: Terse RDF Triple Language.</cite></a> January 2008. W3C Team Submission. URL: <a href="http://www.w3.org/TeamSubmission/turtle/">http://www.w3.org/TeamSubmission/turtle/</a>
</dd></dl></div><div class="section" id="informative-references"><h3><span class="secno">B.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-RDF-SPARQL-QUERY">[RDF-SPARQL-QUERY]</dt><dd>Andy Seaborne; Eric Prud'hommeaux. <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115"><cite>SPARQL Query Language for RDF.</cite></a> 15 January 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115">http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115</a>
</dd><dt id="bib-RDF-SPARQL-XMLRES">[RDF-SPARQL-XMLRES]</dt><dd>Jeen Broekstra; Dave Beckett. <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-XMLres-20080115"><cite>SPARQL Query Results XML Format.</cite></a> 15 January 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-XMLres-20080115">http://www.w3.org/TR/2008/REC-rdf-sparql-XMLres-20080115</a>
</dd><dt id="bib-UNICODE">[UNICODE]</dt><dd>The Unicode Consortium. <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html"><cite>The Unicode Standard.</cite></a> 2003. Defined by: The Unicode Standard, Version 4.0 (Boston, MA, Addison-Wesley, ISBN 0-321-18578-1), as updated from time to time by the publication of new versions URL: <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html</a>
</dd></dl></div></div></body></html>