--- a/drafts/n-quads/Overview.html Fri Nov 01 12:10:42 2013 -0700
+++ b/drafts/n-quads/Overview.html Fri Nov 01 12:12:34 2013 -0700
@@ -1,10 +1,10 @@
<!DOCTYPE html>
-<html lang="en" dir="ltr" typeof="bibo:Document w3p:CR" about="" property="dcterms:language" content="en" prefix="bibo: http://purl.org/ontology/bibo/ w3p: http://www.w3.org/2001/02pd/rec54#">
+<html lang="en" dir="ltr" typeof="bibo:Document w3p:CR" about="" property="dcterms:language" content="en">
<head>
- <title>N-Quads; A line-based syntax for an RDF datasets</title>
+ <title>RDF 1.1 N-Quads</title>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
-
-
+
+
<style type="text/css">
/* Style Turtle script blocks to be visable */
@@ -17,7 +17,7 @@
.separated tbody tr td.r { text-align: right; padding: .5em; }
.grammar td { font-family: monospace;}
.grammar-literal { color: gray;}
- </style>
+ </style>
<style>/*****************************************************************
* ReSpec 3 CSS
* Robin Berjon - http://berjon.com/
@@ -198,18 +198,18 @@
}
-</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-CR"></head>
- <body class="h-entry" role="document" id="respecDocument"><div class="head" role="contentinfo" id="respecHeader">
+</style><link href="https://www.w3.org/StyleSheets/TR/W3C-CR" rel="stylesheet"><!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--><script src="https://raw.github.com/darobin/respec/gh-pages/js/ui/save-html.js" data-requiremodule="ui/save-html" data-requirecontext="_" async="" charset="utf-8" type="text/javascript"></script></head>
+ <body id="respecDocument" role="document" class="h-entry"><div id="respecHeader" role="contentinfo" class="head">
<p>
- <a href="http://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/Icons/w3c_home" alt="W3C"></a>
+ <a href="http://www.w3.org/"><img src="https://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a>
</p>
- <h1 class="title p-name" id="title" property="dcterms:title">N-Quads</h1>
+ <h1 class="title p-name" id="title" property="dcterms:title">RDF 1.1 N-Quads</h1>
<h2 property="bibo:subtitle" id="subtitle">A line-based syntax for an RDF datasets</h2>
- <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2013-11-05T08:00:00.000Z" id="w3c-candidate-recommendation-05-november-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Candidate Recommendation <time class="dt-published" datetime="2013-11-05">05 November 2013</time></h2>
+ <h2 id="w3c-candidate-recommendation-05-november-2013" property="dcterms:issued" datatype="xsd:dateTime" content="2013-11-05T08:00:00.000Z"><abbr title="World Wide Web Consortium">W3C</abbr> Candidate Recommendation <time class="dt-published" datetime="2013-11-05">05 November 2013</time></h2>
<dl>
<dt>This version:</dt>
@@ -251,18 +251,24 @@
<a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
- <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved.
+ <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>),
+
+ All Rights Reserved.
+
<abbr title="World Wide Web Consortium">W3C</abbr> <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.
+
+ <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
+
+ rules apply.
</p>
<hr>
</div>
- <section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#abstract" rel="bibo:chapter"><h2 aria-level="1" role="heading" id="h2_abstract">Abstract</h2><p>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" datatype="" property="dcterms:abstract" class="introductory" id="abstract"><h2 id="h2_abstract" role="heading" aria-level="1">Abstract</h2><p>
N-Quads is a line-based, plain text format for encoding an RDF dataset.
-</p></section><section id="sotd" class="introductory" typeof="bibo:Chapter" resource="#sotd" rel="bibo:chapter"><h2 aria-level="1" role="heading" id="h2_sotd">Status of This Document</h2>
+</p></section><section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sotd" class="introductory"><h2 id="h2_sotd" role="heading" aria-level="1">Status of This Document</h2>
@@ -274,8 +280,8 @@
</p>
<p>The N-Quads format has a similar flavor as N-Triples
-[<cite><a class="bibref" href="#bib-n-triples">n-triples</a></cite>]. The main distinction is that N-Quads allows encoding
-multiple graphs. In a change from previous publication, this document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.</p>
+[<cite><a href="#bib-N-TRIPLES" class="bibref">N-TRIPLES</a></cite>]. The main distinction is that N-Quads allows encoding
+multiple graphs. In a change from previous publication, this document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.</p>
<p>
This document was published by the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> as a Candidate Recommendation.
@@ -330,12 +336,12 @@
-</section><section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#sec-intro" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#n-quads-language" class="tocxref"><span class="secno">2. </span>N-Quads Language</a><ul class="toc"><li class="tocline"><a href="#simple-triples" class="tocxref"><span class="secno">2.1 </span>Simple Statements</a></li><li class="tocline"><a href="#sec-iri" class="tocxref"><span class="secno">2.2 </span>IRIs</a></li><li class="tocline"><a href="#sec-literals" class="tocxref"><span class="secno">2.3 </span>RDF Literals</a></li><li class="tocline"><a href="#BNodes" class="tocxref"><span class="secno">2.4 </span>RDF Blank Nodes</a></li></ul></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">3. </span>Conformance</a><ul class="toc"><li class="tocline"><a href="#sec-mediatype" class="tocxref"><span class="secno">3.1 </span>Media Type and Content Encoding</a></li></ul></li><li class="tocline"><a href="#sec-grammar" class="tocxref"><span class="secno">4. </span>Grammar</a></li><li class="tocline"><a href="#sec-parsing" class="tocxref"><span class="secno">5. </span>Parsing</a><ul class="toc"><li class="tocline"><a href="#sec-parsing-terms" class="tocxref"><span class="secno">5.1 </span>RDF Term Constructors</a></li><li class="tocline"><a href="#rdf-dataset-construction" class="tocxref"><span class="secno">5.2 </span>RDF Dataset Construction</a></li></ul></li><li class="tocline"><a href="#section-ack" class="tocxref"><span class="secno">6. </span>Acknowledgements</a></li><li class="tocline"><a href="#sec-changes" class="tocxref"><span class="secno">A. </span>Changes to this document</a></li><li class="tocline"><a href="#sec-mediaReg" class="tocxref"><span class="secno">B. </span>N-Quads Internet Media Type, File Extension and Macintosh File Type </a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></section>
+</section><section id="toc"><h2 id="h2_toc" role="heading" aria-level="1" class="introductory">Table of Contents</h2><ul id="respecContents" role="directory" class="toc"><li class="tocline"><a class="tocxref" href="#sec-intro"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a class="tocxref" href="#n-quads-language"><span class="secno">2. </span>N-Quads Language</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#simple-triples"><span class="secno">2.1 </span>Simple Statements</a></li><li class="tocline"><a class="tocxref" href="#sec-iri"><span class="secno">2.2 </span>IRIs</a></li><li class="tocline"><a class="tocxref" href="#sec-literals"><span class="secno">2.3 </span>RDF Literals</a></li><li class="tocline"><a class="tocxref" href="#BNodes"><span class="secno">2.4 </span>RDF Blank Nodes</a></li></ul></li><li class="tocline"><a class="tocxref" href="#conformance"><span class="secno">3. </span>Conformance</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#sec-mediatype"><span class="secno">3.1 </span>Media Type and Content Encoding</a></li></ul></li><li class="tocline"><a class="tocxref" href="#sec-grammar"><span class="secno">4. </span>Grammar</a></li><li class="tocline"><a class="tocxref" href="#sec-parsing"><span class="secno">5. </span>Parsing</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#sec-parsing-terms"><span class="secno">5.1 </span>RDF Term Constructors</a></li><li class="tocline"><a class="tocxref" href="#rdf-dataset-construction"><span class="secno">5.2 </span>RDF Dataset Construction</a></li></ul></li><li class="tocline"><a class="tocxref" href="#section-ack"><span class="secno">6. </span>Acknowledgements</a></li><li class="tocline"><a class="tocxref" href="#sec-changes"><span class="secno">A. </span>Changes to this document</a></li><li class="tocline"><a class="tocxref" href="#sec-mediaReg"><span class="secno">B. </span>N-Quads Internet Media Type, File Extension and Macintosh File Type </a></li><li class="tocline"><a class="tocxref" href="#references"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#normative-references"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></section>
- <section id="sec-intro" typeof="bibo:Chapter" resource="#sec-intro" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_sec-intro"><span class="secno">1. </span>Introduction</h2>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-intro">
+ <!--OddPage--><h2 id="h2_sec-intro" role="heading" aria-level="1"><span class="secno">1. </span>Introduction</h2>
<p>This document defines an easy to parse line-based language named N-Quads.</p>
<p>N-quads statements are a sequence of RDF terms representing the subject, predicate, object and graph label of an RDF Triple and the graph it is part of in a dataset. These may be separated by white space (spaces <code>#x20</code> or tabs <code>#x9</code>). This sequence is terminated by a '<code>.</code>' and a new line (optional at the end of a document).
</p>
@@ -349,23 +355,23 @@
</section>
<section id="n-quads-language">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_n-quads-language"><span class="secno">2. </span>N-Quads Language</h2>
- <section id="simple-triples" typeof="bibo:Chapter" resource="#simple-triples" rel="bibo:chapter">
- <h3 aria-level="2" role="heading" id="h3_simple-triples"><span class="secno">2.1 </span>Simple Statements</h3>
+ <!--OddPage--><h2 id="h2_n-quads-language" role="heading" aria-level="1"><span class="secno">2. </span>N-Quads Language</h2>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="simple-triples">
+ <h3 id="h3_simple-triples" role="heading" aria-level="2"><span class="secno">2.1 </span>Simple Statements</h3>
<p>The simplest statement is a sequence of (subject, predicate, object) terms forming an RDF triple and an optional blank node label or IRI labeling what graph in a dataset the triple belongs to, all are separated by whitespace and terminated by '<code>.</code>' after each statement.</p>
<div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example"><script type="application/n-quads"><http://example.org/#spiderman> <http://www.perceive.net/schemas/relationship/enemyOf> <http://example.org/#green-goblin> <http://example.org/graphs/spiderman> .</script></pre></div>
<p>The graph label IRI can be omitted, in which case the triples are considered part of the default graph of the RDF dataset.</p><p>
</p></section>
- <section id="sec-iri" typeof="bibo:Chapter" resource="#sec-iri" rel="bibo:chapter">
- <h3 aria-level="2" role="heading" id="h3_sec-iri"><span class="secno">2.2 </span>IRIs</h3>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-iri">
+ <h3 id="h3_sec-iri" role="heading" aria-level="2"><span class="secno">2.2 </span>IRIs</h3>
<p>
- <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-iri">IRIs</a> may be written only as absolute IRIs.
+ <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-iri">IRIs</a> may be written only as absolute IRIs.
IRIs are enclosed in '<' and '>' and may contain numeric escape sequences (described below). For example <code><http://example.org/#green-goblin></code>.
</p>
</section>
- <section id="sec-literals" typeof="bibo:Chapter" resource="#sec-literals" rel="bibo:chapter">
- <h3 aria-level="2" role="heading" id="h3_sec-literals"><span class="secno">2.3 </span>RDF Literals</h3>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-literals">
+ <h3 id="h3_sec-literals" role="heading" aria-level="2"><span class="secno">2.3 </span>RDF Literals</h3>
<p><a href="http://www.w3.org/TR/rdf11-concepts/#dfn-literal">Literals</a> are used to identify values such as strings, numbers, dates.</p>
@@ -378,8 +384,8 @@
If there is no language tag, there may be a <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-datatype-iri">datatype IRI</a>, preceeded by '<code>^^</code>' (<span class="codepoint">U+005E</span> <span class="codepoint">U+005E</span>). If there is no datatype IRI and no language tag, the datatype is <code>xsd:string</code>.
</p>
</section>
- <section id="BNodes" typeof="bibo:Chapter" resource="#BNodes" rel="bibo:chapter">
- <h3 aria-level="2" role="heading" id="h3_BNodes"><span class="secno">2.4 </span>RDF Blank Nodes</h3>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="BNodes">
+ <h3 id="h3_BNodes" role="heading" aria-level="2"><span class="secno">2.4 </span>RDF Blank Nodes</h3>
<p>
<a href="http://www.w3.org/TR/rdf11-concepts/#dfn-blank-node">RDF blank nodes</a> in N-Quads are expressed as <code>_:</code> followed by a blank node label which is a series of name characters.
The characters in the label are built upon <a href="#grammar-production-PN_CHARS_BASE">PN_CHARS_BASE</a>, liberalized as follows:
@@ -399,15 +405,15 @@
</section>
- <section id="conformance" typeof="bibo:Chapter" resource="#conformance" rel="bibo:chapter"><!--OddPage--><h2 aria-level="1" role="heading" id="h2_conformance"><span class="secno">3. </span>Conformance</h2>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="conformance"><!--OddPage--><h2 id="h2_conformance" role="heading" aria-level="1"><span class="secno">3. </span>Conformance</h2>
<p>
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples,
and notes in this specification are non-normative. Everything else in this specification is
normative.
</p>
<p>
- The key words <em class="rfc2119" title="MUST">MUST</em>, <em class="rfc2119" title="MUST NOT">MUST NOT</em>, <em class="rfc2119" title="REQUIRED">REQUIRED</em>, <em class="rfc2119" title="SHOULD">SHOULD</em>, <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em>, <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>, <em class="rfc2119" title="MAY">MAY</em>,
- and <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> in this specification are to be interpreted as described in [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].
+ The key words <em title="MUST" class="rfc2119">MUST</em>, <em title="MUST NOT" class="rfc2119">MUST NOT</em>, <em title="REQUIRED" class="rfc2119">REQUIRED</em>, <em title="SHOULD" class="rfc2119">SHOULD</em>, <em title="SHOULD NOT" class="rfc2119">SHOULD NOT</em>, <em title="RECOMMENDED" class="rfc2119">RECOMMENDED</em>, <em title="MAY" class="rfc2119">MAY</em>,
+ and <em title="OPTIONAL" class="rfc2119">OPTIONAL</em> in this specification are to be interpreted as described in [<cite><a href="#bib-RFC2119" class="bibref">RFC2119</a></cite>].
</p>
<p>This specification defines conformance criteria for:</p>
@@ -415,35 +421,35 @@
<li>N-Quad documents
</li><li>N-Quad parsers
</li></ul>
- <p>A conforming <strong>N-Quad document</strong> is a Unicode string that conforms to the grammar and additional constraints defined in <a href="#sec-grammar" class="sectionRef sec-ref">section 4. Grammar</a>, starting with the <a href="#grammar-production-nquadsDoc"><code>nquadsDoc</code> production</a>. A N-Quad document serializes an RDF dataset.</p>
-
- <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_1"><span>Note</span></div><p class="">N-Quad documents do not provide a way of serializing empty graphs that may be part of an RDF dataset.</p></div>
-
- <p>A conforming <strong>N-Quad parser</strong> is a system capable of reading N-Quad documents on behalf of an application. It makes the serialized RDF graph, as defined in <a href="#sec-parsing" class="sectionRef sec-ref">section 5. Parsing</a>, available to the application, usually through some form of API.</p>
+ <p>A conforming <strong>N-Quad document</strong> is a Unicode string that conforms to the grammar and additional constraints defined in <a href="#sec-grammar" class="sectionRef sec-ref">section <span class="secno">4.</span> <span class="sec-title">Grammar</span></a>, starting with the <a href="#grammar-production-nquadsDoc"><code>nquadsDoc</code> production</a>. A N-Quad document serializes an RDF dataset.</p>
- <p>The IRI that identifies the N-Quad language is: <code>http://www.w3.org/ns/formats/N-Quads</code></p>
+ <div class="note"><div id="h_note_1" role="heading" aria-level="2" class="note-title"><span>Note</span></div><p class="">N-Quad documents do not provide a way of serializing empty graphs that may be part of an RDF dataset.</p></div>
- <section id="sec-mediatype" typeof="bibo:Chapter" resource="#sec-mediatype" rel="bibo:chapter">
- <h3 aria-level="2" role="heading" id="h3_sec-mediatype"><span class="secno">3.1 </span>Media Type and Content Encoding</h3>
-
+ <p>A conforming <strong>N-Quad parser</strong> is a system capable of reading N-Quad documents on behalf of an application. It makes the serialized RDF graph, as defined in <a href="#sec-parsing" class="sectionRef sec-ref">section <span class="secno">5.</span> <span class="sec-title">Parsing</span></a>, available to the application, usually through some form of API.</p>
+
+ <p>The IRI that identifies the N-Quad language is: <code>http://www.w3.org/ns/formats/N-Quads</code></p>
+
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-mediatype">
+ <h3 id="h3_sec-mediatype" role="heading" aria-level="2"><span class="secno">3.1 </span>Media Type and Content Encoding</h3>
+
<p>The media type of N-Quads is <code>application/n-quads</code>.
- The content encoding of N-Quads is always UTF-8.
- See <a href="#sec-mediaReg">N-Quads Media Type</a> for the media type
+ The content encoding of N-Quads is always UTF-8.
+ See <a href="#sec-mediaReg">N-Quads Media Type</a> for the media type
registration form.
</p>
</section>
</section>
- <section id="sec-grammar" typeof="bibo:Chapter" resource="#sec-grammar" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_sec-grammar"><span class="secno">4. </span>Grammar</h2>
- <p>A N-Quads document is a Unicode[<cite><a class="bibref" href="#bib-UNICODE">UNICODE</a></cite>] character string encoded in UTF-8.
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-grammar">
+ <!--OddPage--><h2 id="h2_sec-grammar" role="heading" aria-level="1"><span class="secno">4. </span>Grammar</h2>
+ <p>A N-Quads document is a Unicode[<cite><a href="#bib-UNICODE" class="bibref">UNICODE</a></cite>] character string encoded in UTF-8.
Unicode code points only in the range U+0 to U+10FFFF inclusive are allowed.</p>
<p>White space (tab <code>U+0009</code> or space <code>U+0020</code>) is used to separate two terminals which would otherwise be (mis-)recognized as one terminal. White space is significant in the production <a href="#grammar-production-STRING_LITERAL_QUOTE">STRING_LITERAL_QUOTE</a>.</p>
<p>Comments in N-Quads take the form of '<code>#</code>', outside an <code>IRIREF</code> or <code>STRING_LITERAL_QUOTE</code>, and continue to the end of line (<code>EOL</code>) or end of file if there is no end of line after the comment marker. Comments are treated as white space.</p>
<p>The <abbr title="Extended Backus–Naur Form">EBNF</abbr> used here is defined in XML 1.0
- [<cite><a class="bibref" href="#bib-EBNF-NOTATION">EBNF-NOTATION</a></cite>].</p>
+ [<cite><a href="#bib-EBNF-NOTATION" class="bibref">EBNF-NOTATION</a></cite>].</p>
<p>Escape sequence rules are the same as Turtle
- [<cite><a class="bibref" href="#bib-turtle">turtle</a></cite>]. However, as only the <a href="#grammar-production-STRING_LITERAL_QUOTE"><code>STRING_LITERAL_QUOTE</code></a> production is allowed new lines in literals <em class="rfc2119" title="MUST">MUST</em> be escaped.</p>
+ [<cite><a href="#bib-TURTLE" class="bibref">TURTLE</a></cite>]. However, as only the <a href="#grammar-production-STRING_LITERAL_QUOTE"><code>STRING_LITERAL_QUOTE</code></a> production is allowed new lines in literals <em title="MUST" class="rfc2119">MUST</em> be escaped.</p>
<div><table class="grammar">
<tbody class="grammar-productions">
<tr id="grammar-production-nquadsDoc" data-grammar-original="[1] nquadsDoc ::= statement? (EOL statement)* EOL?" data-grammar-expression="(',', [('?', ('id', 'statement')), ('*', (',', [('id', 'EOL'), ('id', 'statement')])), ('?', ('id', 'EOL'))])">
@@ -501,7 +507,7 @@
<td>::=</td>
<td>[<code class="grammar-chars">#xD#xA</code>]<code class="grammar-plus">+</code></td>
</tr>
- <tr id="grammar-production-IRIREF" data-grammar-original="[10] IRIREF ::= '<' ([^#x00-#x20<>"{}|^`\] | UCHAR)* '>'" data-grammar-expression="(',', [("'", '<'), ('*', ('|', [('[', '^#x00-#x20<>"{}|^`\\'), ('id', 'UCHAR')])), ("'", '>')])" class="grammar-token">
+ <tr id="grammar-production-IRIREF" data-grammar-original="[10] IRIREF ::= '<' ([^#x00-#x20<>"{}|^`\] | UCHAR)* '>'" data-grammar-expression="(',', [("'", '<'), ('*', ('|', [('[', '^#x00-#x20<>"{}|^`\\'), ('id', 'UCHAR')])), ("'", '>')])" class="grammar-token">
<td>[10]</td>
<td><code>IRIREF</code></td>
<td>::=</td>
@@ -558,16 +564,16 @@
</tbody></table>
</div>
</section>
- <section id="sec-parsing" typeof="bibo:Chapter" resource="#sec-parsing" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_sec-parsing"><span class="secno">5. </span>Parsing</h2>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-parsing">
+ <!--OddPage--><h2 id="h2_sec-parsing" role="heading" aria-level="1"><span class="secno">5. </span>Parsing</h2>
<p>Parsing N-Quads requires a state of one item:</p>
<ul>
- <li id="bnodeLabels">Map[<a class="type string">string</a> -> <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-blank-node">blank node</a>] <code class="dfn">bnodeLabels</code> — A mapping from string to blank node.</li>
+ <li id="bnodeLabels">Map[string -> <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-blank-node">blank node</a>] <code class="dfn">bnodeLabels</code> — A mapping from string to blank node.</li>
</ul>
- <section id="sec-parsing-terms" typeof="bibo:Chapter" resource="#sec-parsing-terms" rel="bibo:chapter">
- <h3 aria-level="2" role="heading" id="h3_sec-parsing-terms"><span class="secno">5.1 </span>RDF Term Constructors</h3>
- <p>This table maps productions and lexical tokens to <code>RDF terms</code> or components of <code>RDF terms</code> listed in <a href="#sec-parsing" class="sectionRef sec-ref">section 5. Parsing</a>:</p>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-parsing-terms">
+ <h3 id="h3_sec-parsing-terms" role="heading" aria-level="2"><span class="secno">5.1 </span>RDF Term Constructors</h3>
+ <p>This table maps productions and lexical tokens to <code>RDF terms</code> or components of <code>RDF terms</code> listed in <a href="#sec-parsing" class="sectionRef sec-ref">section <span class="secno">5.</span> <span class="sec-title">Parsing</span></a>:</p>
<table class="simple">
<thead>
<tr><th>production</th><th>type</th><th>procedure</th></tr>
@@ -582,21 +588,21 @@
</table>
</section>
<section id="rdf-dataset-construction">
- <h3 aria-level="2" role="heading" id="h3_rdf-dataset-construction"><span class="secno">5.2 </span>RDF Dataset Construction</h3>
+ <h3 id="h3_rdf-dataset-construction" role="heading" aria-level="2"><span class="secno">5.2 </span>RDF Dataset Construction</h3>
<p>A N-Quad document defines an RDF dataset composed of RDF graphs composed of a set of RDF triples. The <code><a href="#grammar-production-statement">statement</a></code> production produces a triple defined by the terms constructed for <code><a href="#grammar-production-subject">subject</a></code>, <code><a href="#grammar-production-predicate">predicate</a></code> and <code><a href="#grammar-production-object">object</a></code>. This RDF triple is added to the graph labeled by the production <code><a href="#grammar-production-graphLabel">graphLabel</a></code>, if no <code>graphLabel</code> is present the triple is added to the RDF datasets default graph.</p>
</section>
</section>
- <section id="section-ack" class="informative" typeof="bibo:Chapter" resource="#section-ack" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_section-ack"><span class="secno">6. </span>Acknowledgements</h2><p><em>This section is non-normative.</em></p>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="section-ack" class="informative">
+ <!--OddPage--><h2 id="h2_section-ack" role="heading" aria-level="1"><span class="secno">6. </span>Acknowledgements</h2><p><em>This section is non-normative.</em></p>
<p>The editor of the 2013 edition acknowledges valuable contributions from Gregg Kellogg, Andy Seaborn, Eric Prud'hommeaux, Dave Beckett, David Robillard, Gregory Williams, Antoine Zimmermann, Sandro Hawke, Richard Cyganiak, Pat Hayes, Henry S. Thompson, Bob Ferris, Henry Story, Andreas Harth, Lee Feigenbaum, Peter Ansell, and David Booth.</p>
- <p>This specification is a product of extended deliberations by the
+ <p>This specification is a product of extended deliberations by the
<a href="http://www.w3.org/2000/09/dbwg/details?group=46168&public=1">members of the RDF Working Group</a> chaired by Guus Schreiber and David Wood. It draws upon the eariler specification in <em><a href="http://sw.deri.org/2008/07/n-quads/">N-Quads: Extending N-Triples with Context</a></em>, edited by Richard Cyganiak, Andreas Harth, and Aidan Hogan.</p>
</section>
- <section id="sec-changes" class="appendix" typeof="bibo:Chapter" resource="#sec-changes" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_sec-changes"><span class="secno">A. </span>Changes to this document</h2><h2 id="generatedID">
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-changes" class="appendix">
+ <!--OddPage--><h2 id="h2_sec-changes" role="heading" aria-level="1"><span class="secno">A. </span>Changes to this document</h2><h2 id="generatedID">
</h2><h2 id="changes-since-last-publication-as-last-call-working-draft">Changes since last publication as Last Call Working Draft</h2>
<p>No substitutive changes.</p>
<h2 id="changes-since-original-publication-as-note">Changes since original publication as Note</h2>
@@ -608,8 +614,8 @@
</li></ul>
</section>
- <section id="sec-mediaReg" class="appendix" typeof="bibo:Chapter" resource="#sec-mediaReg" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_sec-mediaReg"><span class="secno">B. </span>N-Quads Internet Media Type, File Extension and Macintosh File Type </h2>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-mediaReg" class="appendix">
+ <!--OddPage--><h2 id="h2_sec-mediaReg" role="heading" aria-level="1"><span class="secno">B. </span>N-Quads Internet Media Type, File Extension and Macintosh File Type </h2>
<dl>
<dt>Contact:</dt>
<dd>Eric Prud'hommeaux</dd>
@@ -635,29 +641,29 @@
<dd>None</dd>
<dt>Encoding considerations:</dt>
- <dd>The syntax of N-Quads is expressed over code points in Unicode [<cite><a class="bibref" href="#bib-UNICODE">UNICODE</a></cite>]. The encoding is always UTF-8 [<cite><a class="bibref" href="#bib-UTF-8">UTF-8</a></cite>].</dd>
+ <dd>The syntax of N-Quads is expressed over code points in Unicode [<cite><a href="#bib-UNICODE" class="bibref">UNICODE</a></cite>]. The encoding is always UTF-8 [<cite><a href="#bib-UTF-8" class="bibref">UTF-8</a></cite>].</dd>
<dd>Unicode code points may also be expressed using an \uXXXX (U+0 to U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a hexadecimal digit [0-9A-F]</dd>
<dt>Security considerations:</dt>
- <dd>N-Quads is a general-purpose assertion language; applications may evaluate given data to infer more assertions or to dereference IRIs, invoking the security considerations of the scheme for that IRI. Note in particular, the privacy issues in [<cite><a class="bibref" href="#bib-RFC3023">RFC3023</a></cite>] section 10 for HTTP IRIs. Data obtained from an inaccurate or malicious data source may lead to inaccurate or misleading conclusions, as well as the dereferencing of unintended IRIs. Care must be taken to align the trust in consulted resources with the sensitivity of the intended use of the data; inferences of potential medical treatments would likely require different trust than inferences for trip planning.</dd>
+ <dd>N-Quads is a general-purpose assertion language; applications may evaluate given data to infer more assertions or to dereference IRIs, invoking the security considerations of the scheme for that IRI. Note in particular, the privacy issues in [<cite><a href="#bib-RFC3023" class="bibref">RFC3023</a></cite>] section 10 for HTTP IRIs. Data obtained from an inaccurate or malicious data source may lead to inaccurate or misleading conclusions, as well as the dereferencing of unintended IRIs. Care must be taken to align the trust in consulted resources with the sensitivity of the intended use of the data; inferences of potential medical treatments would likely require different trust than inferences for trip planning.</dd>
<dd>N-Quads is used to express arbitrary application data; security considerations will vary by domain of use. Security tools and protocols applicable to text (e.g. PGP encryption, MD5 sum validation, password-protected compression) may also be used on N-Quads documents. Security/privacy protocols must be imposed which reflect the sensitivity of the embedded information.</dd>
- <dd>N-Quads can express data which is presented to the user, for example, RDF Schema labels. Application rendering strings retrieved from untrusted N-Quads documents must ensure that malignant strings may not be used to mislead the reader. The security considerations in the media type registration for XML ([<cite><a class="bibref" href="#bib-RFC3023">RFC3023</a></cite>] section 10) provide additional guidance around the expression of arbitrary data and markup.</dd>
+ <dd>N-Quads can express data which is presented to the user, for example, RDF Schema labels. Application rendering strings retrieved from untrusted N-Quads documents must ensure that malignant strings may not be used to mislead the reader. The security considerations in the media type registration for XML ([<cite><a href="#bib-RFC3023" class="bibref">RFC3023</a></cite>] section 10) provide additional guidance around the expression of arbitrary data and markup.</dd>
<dd>N-Quads uses IRIs as term identifiers. Applications interpreting data expressed in N-Quads should address the security issues of
- <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>] Section 8, as well as
- <a class="norm" href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifier (URI): Generic Syntax</a> [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>] Section 7.</dd>
+ <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [<cite><a href="#bib-RFC3987" class="bibref">RFC3987</a></cite>] Section 8, as well as
+ <a class="norm" href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifier (URI): Generic Syntax</a> [<cite><a href="#bib-RFC3986" class="bibref">RFC3986</a></cite>] Section 7.</dd>
- <dd>Multiple IRIs may have the same appearance. Characters in different scripts may
- look similar (a Cyrillic "о" may appear similar to a Latin "o"). A character followed
- by combining characters may have the same visual representation as another character
- (LATIN SMALL LETTER E followed by COMBINING ACUTE ACCENT has the same visual representation
+ <dd>Multiple IRIs may have the same appearance. Characters in different scripts may
+ look similar (a Cyrillic "о" may appear similar to a Latin "o"). A character followed
+ by combining characters may have the same visual representation as another character
+ (LATIN SMALL LETTER E followed by COMBINING ACUTE ACCENT has the same visual representation
as LATIN SMALL LETTER E WITH ACUTE).
<!-- (<code>foo:resum鼯code> and <code>fоо:resumé</code>)-->
Any person or application that is writing or interpreting data in Turtle must take care to use the IRI that matches the intended semantics, and avoid IRIs that make look similar.
- Further information about matching of similar characters can be found
- in <a class="inform" href="http://www.unicode.org/reports/tr36/">Unicode Security
- Considerations</a> [<cite><a class="bibref" href="#bib-UNICODE-SECURITY">UNICODE-SECURITY</a></cite>] and
- <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource
- Identifiers (IRIs)</a> [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>] Section 8.
+ Further information about matching of similar characters can be found
+ in <a class="inform" href="http://www.unicode.org/reports/tr36/">Unicode Security
+ Considerations</a> [<cite><a href="#bib-UNICODE-SECURITY" class="bibref">UNICODE-SECURITY</a></cite>] and
+ <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource
+ Identifiers (IRIs)</a> [<cite><a href="#bib-RFC3987" class="bibref">RFC3987</a></cite>] Section 8.
</dd>
<dt>Interoperability considerations:</dt>
@@ -690,14 +696,14 @@
-<section id="references" class="appendix" typeof="bibo:Chapter" resource="#references" rel="bibo:chapter"><!--OddPage--><h2 aria-level="1" role="heading" id="h2_references"><span class="secno">C. </span>References</h2><section id="normative-references" typeof="bibo:Chapter" resource="#normative-references" rel="bibo:chapter"><h3 aria-level="2" role="heading" id="h3_normative-references"><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-EBNF-NOTATION">[EBNF-NOTATION]</dt><dd rel="dcterms:requires">Tim Bray; Jean Paoli; C. M. Sperberg-McQueen; Eve Maler; François Yergeau. <a href="http://www.w3.org/TR/REC-xml/#sec-notation"><cite>EBNF Notation</cite></a> 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/REC-xml/#sec-notation">http://www.w3.org/TR/REC-xml/#sec-notation</a>
+<section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="references" class="appendix"><!--OddPage--><h2 id="h2_references" role="heading" aria-level="1"><span class="secno">C. </span>References</h2><section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="normative-references"><h3 id="h3_normative-references" role="heading" aria-level="2"><span class="secno">C.1 </span>Normative references</h3><dl about="" class="bibliography"><dt id="bib-EBNF-NOTATION">[EBNF-NOTATION]</dt><dd rel="dcterms:requires">Tim Bray; Jean Paoli; C. M. Sperberg-McQueen; Eve Maler; François Yergeau. <a href="http://www.w3.org/TR/REC-xml/#sec-notation"><cite>EBNF Notation</cite></a> 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/REC-xml/#sec-notation">http://www.w3.org/TR/REC-xml/#sec-notation</a>
</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd rel="dcterms:requires">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-RFC3023">[RFC3023]</dt><dd rel="dcterms:requires">M. Murata; S. St.Laurent; D. Kohn. <a href="http://www.ietf.org/rfc/rfc3023.txt"><cite>XML Media Types (RFC 3023)</cite></a>. January 2001. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a>
</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd rel="dcterms:requires">T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic Syntax (RFC 3986)</cite></a>. January 2005. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd rel="dcterms:requires">M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs)</cite></a>. January 2005. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>
</dd><dt id="bib-UNICODE">[UNICODE]</dt><dd rel="dcterms:requires"><a href="http://www.unicode.org/versions/latest/"><cite>The Unicode Standard</cite></a>. URL: <a href="http://www.unicode.org/versions/latest/">http://www.unicode.org/versions/latest/</a>
</dd><dt id="bib-UTF-8">[UTF-8]</dt><dd rel="dcterms:requires">F. Yergeau. <a href="http://www.ietf.org/rfc/rfc3629.txt"><cite>UTF-8, a transformation format of ISO 10646</cite></a>. IETF RFC 3629. November 2003. URL: <a href="http://www.ietf.org/rfc/rfc3629.txt">http://www.ietf.org/rfc/rfc3629.txt</a>
-</dd></dl></section><section id="informative-references" typeof="bibo:Chapter" resource="#informative-references" rel="bibo:chapter"><h3 aria-level="2" role="heading" id="h3_informative-references"><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-UNICODE-SECURITY">[UNICODE-SECURITY]</dt><dd rel="dcterms:references">Mark Davis; Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations</cite></a>. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
-</dd><dt id="bib-n-triples">[n-triples]</dt><dd rel="dcterms:references">Gavin Carothers. <a href="http://www.w3.org/TR/n-triples/"><cite>N-Triples</cite></a>. 5 September 2013. W3C Last Call Working Draft. URL: <a href="http://www.w3.org/TR/n-triples/">http://www.w3.org/TR/n-triples/</a>
-</dd><dt id="bib-turtle">[turtle]</dt><dd rel="dcterms:references">Eric Prud'hommeaux; Gavin Carothers. <a href="http://www.w3.org/TR/turtle/"><cite>Turtle</cite></a>. 19 February 2013. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
+</dd></dl></section><section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="informative-references"><h3 id="h3_informative-references" role="heading" aria-level="2"><span class="secno">C.2 </span>Informative references</h3><dl about="" class="bibliography"><dt id="bib-N-TRIPLES">[N-TRIPLES]</dt><dd rel="dcterms:references">Gavin Carothers, Editor. <cite><a href="http://www.w3.org/TR/2013/CR-n-triples-20131105/">RDF 1.1 N-Triples</a></cite>. 5 November 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/CR-n-triples-20131105/">http://www.w3.org/TR/2013/CR-n-triples-20131105/</a>. The latest edition is available at <a href="http://www.w3.org/TR/n-triples/">http://www.w3.org/TR/n-triples/</a>
+</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd rel="dcterms:references">Eric Prud'hommeaux, Gavin Carothers, Editors. <cite><a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">RDF 1.1 Turtle: Terse RDF Triple Language.</a></cite> 19 February 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">http://www.w3.org/TR/2013/CR-turtle-20130219/</a>. The latest edition is available at <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
+</dd><dt id="bib-UNICODE-SECURITY">[UNICODE-SECURITY]</dt><dd rel="dcterms:references">Mark Davis; Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations</cite></a>. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
</dd></dl></section></section></body></html>
\ No newline at end of file
--- a/drafts/n-triples/Overview.html Fri Nov 01 12:10:42 2013 -0700
+++ b/drafts/n-triples/Overview.html Fri Nov 01 12:12:34 2013 -0700
@@ -1,7 +1,7 @@
<!DOCTYPE html>
-<html lang="en" dir="ltr" typeof="bibo:Document w3p:CR" about="" property="dcterms:language" content="en" prefix="bibo: http://purl.org/ontology/bibo/ w3p: http://www.w3.org/2001/02pd/rec54#">
+<html lang="en" dir="ltr" typeof="bibo:Document w3p:CR" about="" property="dcterms:language" content="en">
<head>
- <title>N-Triples</title>
+ <title>RDF 1.1 N-Triples</title>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
@@ -17,7 +17,7 @@
.separated tbody tr td.r { text-align: right; padding: .5em; }
.grammar td { font-family: monospace;}
.grammar-literal { color: gray;}
- </style>
+ </style>
<style>/*****************************************************************
* ReSpec 3 CSS
* Robin Berjon - http://berjon.com/
@@ -159,18 +159,18 @@
aside.example div.example div.example-title {
color: #999;
}
-</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-CR"></head>
- <body class="h-entry" role="document" id="respecDocument"><div class="head" role="contentinfo" id="respecHeader">
+</style><link href="https://www.w3.org/StyleSheets/TR/W3C-CR" rel="stylesheet"><!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--><script src="https://raw.github.com/darobin/respec/gh-pages/js/ui/save-html.js" data-requiremodule="ui/save-html" data-requirecontext="_" async="" charset="utf-8" type="text/javascript"></script></head>
+ <body id="respecDocument" role="document" class="h-entry"><div id="respecHeader" role="contentinfo" class="head">
<p>
- <a href="http://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/Icons/w3c_home" alt="W3C"></a>
+ <a href="http://www.w3.org/"><img src="https://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a>
</p>
- <h1 class="title p-name" id="title" property="dcterms:title">N-Triples</h1>
+ <h1 class="title p-name" id="title" property="dcterms:title">RDF 1.1 N-Triples</h1>
<h2 property="bibo:subtitle" id="subtitle">A line-based syntax for an RDF graph</h2>
- <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2013-11-05T08:00:00.000Z" id="w3c-candidate-recommendation-05-november-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Candidate Recommendation <time class="dt-published" datetime="2013-11-05">05 November 2013</time></h2>
+ <h2 id="w3c-candidate-recommendation-05-november-2013" property="dcterms:issued" datatype="xsd:dateTime" content="2013-11-05T08:00:00.000Z"><abbr title="World Wide Web Consortium">W3C</abbr> Candidate Recommendation <time class="dt-published" datetime="2013-11-05">05 November 2013</time></h2>
<dl>
<dt>This version:</dt>
@@ -217,18 +217,24 @@
<a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
- <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved.
+ <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>),
+
+ All Rights Reserved.
+
<abbr title="World Wide Web Consortium">W3C</abbr> <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.
+
+ <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
+
+ rules apply.
</p>
<hr>
</div>
- <section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#abstract" rel="bibo:chapter"><h2 aria-level="1" role="heading" id="h2_abstract">Abstract</h2><p>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" datatype="" property="dcterms:abstract" class="introductory" id="abstract"><h2 id="h2_abstract" role="heading" aria-level="1">Abstract</h2><p>
N-Triples is a line-based, plain text format for encoding an RDF graph.
-</p></section><section id="sotd" class="introductory" typeof="bibo:Chapter" resource="#sotd" rel="bibo:chapter"><h2 aria-level="1" role="heading" id="h2_sotd">Status of This Document</h2>
+</p></section><section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sotd" class="introductory"><h2 id="h2_sotd" role="heading" aria-level="1">Status of This Document</h2>
@@ -239,11 +245,11 @@
index</a> at http://www.w3.org/TR/.</em>
</p>
-N-Triples was originally defined as a syntax for
-the RDF Test Cases [<cite><a class="bibref" href="#bib-RDF-TESTCASES">RDF-TESTCASES</a></cite>] document. Due to its popularity
+N-Triples was originally defined as a syntax for
+the RDF Test Cases [<cite><a href="#bib-RDF-TESTCASES" class="bibref">RDF-TESTCASES</a></cite>] document. Due to its popularity
as an exchange format the <a href="http://www.w3.org/2011/rdf-wg/">RDF
Working Group</a> decided to publish an updated
-version. In a change from previous publication, this document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
+version. In a change from previous publication, this document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
<p>
This document was published by the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> as a Candidate Recommendation.
@@ -298,16 +304,16 @@
-</section><section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#sec-introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#sec-n-triples-language" class="tocxref"><span class="secno">2. </span>N-Triples Language</a><ul class="toc"><li class="tocline"><a href="#simple-triples" class="tocxref"><span class="secno">2.1 </span>Simple Triples</a></li><li class="tocline"><a href="#sec-iri" class="tocxref"><span class="secno">2.2 </span>IRIs</a></li><li class="tocline"><a href="#sec-literals" class="tocxref"><span class="secno">2.3 </span>RDF Literals</a></li><li class="tocline"><a href="#BNodes" class="tocxref"><span class="secno">2.4 </span>RDF Blank Nodes</a></li></ul></li><li class="tocline"><a href="#n-triple-changes" class="tocxref"><span class="secno">3. </span>Changes from RDF Test Cases format</a></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">4. </span>Conformance</a><ul class="toc"><li class="tocline"><a href="#n-triples-mediatype" class="tocxref"><span class="secno">4.1 </span>Media Type and Content Encoding</a><ul class="toc"><li class="tocline"><a href="#sec-other-media-types" class="tocxref"><span class="secno">4.1.1 </span>Other Media Types</a></li></ul></li></ul></li><li class="tocline"><a href="#n-triples-grammar" class="tocxref"><span class="secno">5. </span>Grammar</a></li><li class="tocline"><a href="#sec-parsing" class="tocxref"><span class="secno">6. </span>Parsing</a><ul class="toc"><li class="tocline"><a href="#sec-parsing-terms" class="tocxref"><span class="secno">6.1 </span>RDF Term Constructors</a></li><li class="tocline"><a href="#rdf-triple-construction" class="tocxref"><span class="secno">6.2 </span>RDF Triple Construction</a></li></ul></li><li class="tocline"><a href="#section-ack" class="tocxref"><span class="secno">7. </span>Acknowledgements</a></li><li class="tocline"><a href="#sec-changes" class="tocxref"><span class="secno">A. </span>Changes to this document</a></li><li class="tocline"><a href="#sec-mediaReg-n-triples" class="tocxref"><span class="secno">B. </span>N-Triples Internet Media Type, File Extension and Macintosh File Type </a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></section>
+</section><section id="toc"><h2 id="h2_toc" role="heading" aria-level="1" class="introductory">Table of Contents</h2><ul id="respecContents" role="directory" class="toc"><li class="tocline"><a class="tocxref" href="#sec-introduction"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a class="tocxref" href="#sec-n-triples-language"><span class="secno">2. </span>N-Triples Language</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#simple-triples"><span class="secno">2.1 </span>Simple Triples</a></li><li class="tocline"><a class="tocxref" href="#sec-iri"><span class="secno">2.2 </span>IRIs</a></li><li class="tocline"><a class="tocxref" href="#sec-literals"><span class="secno">2.3 </span>RDF Literals</a></li><li class="tocline"><a class="tocxref" href="#BNodes"><span class="secno">2.4 </span>RDF Blank Nodes</a></li></ul></li><li class="tocline"><a class="tocxref" href="#n-triple-changes"><span class="secno">3. </span>Changes from RDF Test Cases format</a></li><li class="tocline"><a class="tocxref" href="#conformance"><span class="secno">4. </span>Conformance</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#n-triples-mediatype"><span class="secno">4.1 </span>Media Type and Content Encoding</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#sec-other-media-types"><span class="secno">4.1.1 </span>Other Media Types</a></li></ul></li></ul></li><li class="tocline"><a class="tocxref" href="#n-triples-grammar"><span class="secno">5. </span>Grammar</a></li><li class="tocline"><a class="tocxref" href="#sec-parsing"><span class="secno">6. </span>Parsing</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#sec-parsing-terms"><span class="secno">6.1 </span>RDF Term Constructors</a></li><li class="tocline"><a class="tocxref" href="#rdf-triple-construction"><span class="secno">6.2 </span>RDF Triple Construction</a></li></ul></li><li class="tocline"><a class="tocxref" href="#section-ack"><span class="secno">7. </span>Acknowledgements</a></li><li class="tocline"><a class="tocxref" href="#sec-changes"><span class="secno">A. </span>Changes to this document</a></li><li class="tocline"><a class="tocxref" href="#sec-mediaReg-n-triples"><span class="secno">B. </span>N-Triples Internet Media Type, File Extension and Macintosh File Type </a></li><li class="tocline"><a class="tocxref" href="#references"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#normative-references"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></section>
<!-- BEGIN N-TRIPLES SPEC -->
- <section id="sec-introduction" typeof="bibo:Chapter" resource="#sec-introduction" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_sec-introduction"><span class="secno">1. </span>Introduction</h2>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-introduction">
+ <!--OddPage--><h2 id="h2_sec-introduction" role="heading" aria-level="1"><span class="secno">1. </span>Introduction</h2>
<p>This document defines an easy to parse line-based subset of
- Turtle [<cite><a class="bibref" href="#bib-turtle">turtle</a></cite>] named N-Triples.</p>
- <p>The syntax is a revised version of N-Triples as originally defined in the RDF Test Cases [<cite><a class="bibref" href="#bib-RDF-TESTCASES">RDF-TESTCASES</a></cite>] document. Its original intent was for writing test cases, but it has proven to be popular as an exchange format for RDF data.</p>
+ Turtle [<cite><a href="#bib-TURTLE" class="bibref">TURTLE</a></cite>] named N-Triples.</p>
+ <p>The syntax is a revised version of N-Triples as originally defined in the RDF Test Cases [<cite><a href="#bib-RDF-TESTCASES" class="bibref">RDF-TESTCASES</a></cite>] document. Its original intent was for writing test cases, but it has proven to be popular as an exchange format for RDF data.</p>
<p>An N-Triples document contains no parsing directives.
</p>
<p>N-Triples triples are a sequence of RDF terms representing the subject, predicate and object of an RDF Triple. These may be separated by white space (spaces <code>U+0020</code> or tabs <code>U+0009</code>). This sequence is terminated by a '<code>.</code>' and a new line (optional at the end of a document).
@@ -324,30 +330,30 @@
</p>
<p>The RDF graph represented by an N-Triples document contains
exactly each triple matching the N-Triples <a href="#grammar-production-triple"><code>triple</code></a>
- production.
+ production.
</p></section>
- <section id="sec-n-triples-language" typeof="bibo:Chapter" resource="#sec-n-triples-language" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_sec-n-triples-language"><span class="secno">2. </span>N-Triples Language</h2>
- <section id="simple-triples" typeof="bibo:Chapter" resource="#simple-triples" rel="bibo:chapter">
- <h3 aria-level="2" role="heading" id="h3_simple-triples"><span class="secno">2.1 </span>Simple Triples</h3>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-n-triples-language">
+ <!--OddPage--><h2 id="h2_sec-n-triples-language" role="heading" aria-level="1"><span class="secno">2. </span>N-Triples Language</h2>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="simple-triples">
+ <h3 id="h3_simple-triples" role="heading" aria-level="2"><span class="secno">2.1 </span>Simple Triples</h3>
<p>The simplest triple statement is a sequence of (subject, predicate, object) terms, separated by whitespace and terminated by '<code>.</code>' after each triple.</p>
<div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example"><script type="application/n-triples"><http://example.org/#spiderman> <http://www.perceive.net/schemas/relationship/enemyOf> <http://example.org/#green-goblin> .</script></pre></div>
</section>
- <section id="sec-iri" typeof="bibo:Chapter" resource="#sec-iri" rel="bibo:chapter">
- <h3 aria-level="2" role="heading" id="h3_sec-iri"><span class="secno">2.2 </span>IRIs</h3>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-iri">
+ <h3 id="h3_sec-iri" role="heading" aria-level="2"><span class="secno">2.2 </span>IRIs</h3>
<p>
- <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-iri">IRIs</a> may be written only as absolute IRIs.
+ <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-iri">IRIs</a> may be written only as absolute IRIs.
IRIs are enclosed in '<code><</code>' and '<code>></code>' and may contain numeric escape sequences (described below). For example <code><http://example.org/#green-goblin></code>.
</p>
</section>
- <section id="sec-literals" typeof="bibo:Chapter" resource="#sec-literals" rel="bibo:chapter">
- <h3 aria-level="2" role="heading" id="h3_sec-literals"><span class="secno">2.3 </span>RDF Literals</h3>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-literals">
+ <h3 id="h3_sec-literals" role="heading" aria-level="2"><span class="secno">2.3 </span>RDF Literals</h3>
<p><a href="http://www.w3.org/TR/rdf11-concepts/#dfn-literal">Literals</a>
are used to identify values such as strings, numbers,
- dates.</p>
+ dates.</p>
<p>
@@ -362,14 +368,14 @@
<div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example"><script type="application/n-triples"><http://example.org/show/218> <http://www.w3.org/2000/01/rdf-schema#label> "That Seventies Show"^^<http://www.w3.org/2001/XMLSchema#string> . # literal with XML Schema string datatype
<http://example.org/show/218> <http://www.w3.org/2000/01/rdf-schema#label> "That Seventies Show" . # same as above
<http://example.org/show/218> <http://example.org/show/localName> "That Seventies Show"@en . # literal with a language tag
-<http://example.org/show/218> <http://example.org/show/localName> "Cette Série des Années Septante"@fr-be . # literal outside of ASCII range with a region subtag
+<http://example.org/show/218> <http://example.org/show/localName> "Cette Série des Années Septante"@fr-be . # literal outside of ASCII range with a region subtag
<http://example.org/#spiderman> <http://example.org/text> "This is a multi-line\nliteral with many quotes (\"\"\"\"\")\nand two apostrophes ('')." .
-<http://en.wikipedia.org/wiki/Helium> <http://example.org/elements/atomicNumber> "2"^^<http://www.w3.org/2001/XMLSchema#integer> . # xsd:integer
-<http://en.wikipedia.org/wiki/Helium> <http://example.org/elements/specificGravity> "1.663E-4"^^<http://www.w3.org/2001/XMLSchema#double> . # xsd:double
+<http://en.wikipedia.org/wiki/Helium> <http://example.org/elements/atomicNumber> "2"^^<http://www.w3.org/2001/XMLSchema#integer> . # xsd:integer
+<http://en.wikipedia.org/wiki/Helium> <http://example.org/elements/specificGravity> "1.663E-4"^^<http://www.w3.org/2001/XMLSchema#double> . # xsd:double
</script></pre></div>
</section>
- <section id="BNodes" typeof="bibo:Chapter" resource="#BNodes" rel="bibo:chapter">
- <h3 aria-level="2" role="heading" id="h3_BNodes"><span class="secno">2.4 </span>RDF Blank Nodes</h3>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="BNodes">
+ <h3 id="h3_BNodes" role="heading" aria-level="2"><span class="secno">2.4 </span>RDF Blank Nodes</h3>
<p>
<a href="http://www.w3.org/TR/rdf11-concepts/#dfn-blank-node">RDF blank nodes</a> in N-Triples are expressed as <code>_:</code> followed by a blank node label which is a series of name characters.
The characters in the label are built upon <a href="#grammar-production-PN_CHARS_BASE">PN_CHARS_BASE</a>, liberalized as follows:
@@ -389,8 +395,8 @@
</section>
- <section id="n-triple-changes" class="informative" typeof="bibo:Chapter" resource="#n-triple-changes" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_n-triple-changes"><span class="secno">3. </span>Changes from RDF Test Cases format</h2><p><em>This section is non-normative.</em></p>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="n-triple-changes" class="informative">
+ <!--OddPage--><h2 id="h2_n-triple-changes" role="heading" aria-level="1"><span class="secno">3. </span>Changes from RDF Test Cases format</h2><p><em>This section is non-normative.</em></p>
<ul>
<li>Encoding is UTF-8 rather than US-ASCII
</li><li>Uses IRIs rather than RDF URI References
@@ -403,15 +409,15 @@
</li></ul>
</section>
- <section id="conformance" typeof="bibo:Chapter" resource="#conformance" rel="bibo:chapter"><!--OddPage--><h2 aria-level="1" role="heading" id="h2_conformance"><span class="secno">4. </span>Conformance</h2>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="conformance"><!--OddPage--><h2 id="h2_conformance" role="heading" aria-level="1"><span class="secno">4. </span>Conformance</h2>
<p>
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples,
and notes in this specification are non-normative. Everything else in this specification is
normative.
</p>
<p>
- The key words <em class="rfc2119" title="MUST">MUST</em>, <em class="rfc2119" title="MUST NOT">MUST NOT</em>, <em class="rfc2119" title="REQUIRED">REQUIRED</em>, <em class="rfc2119" title="SHOULD">SHOULD</em>, <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em>, <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>, <em class="rfc2119" title="MAY">MAY</em>,
- and <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> in this specification are to be interpreted as described in [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].
+ The key words <em title="MUST" class="rfc2119">MUST</em>, <em title="MUST NOT" class="rfc2119">MUST NOT</em>, <em title="REQUIRED" class="rfc2119">REQUIRED</em>, <em title="SHOULD" class="rfc2119">SHOULD</em>, <em title="SHOULD NOT" class="rfc2119">SHOULD NOT</em>, <em title="RECOMMENDED" class="rfc2119">RECOMMENDED</em>, <em title="MAY" class="rfc2119">MAY</em>,
+ and <em title="OPTIONAL" class="rfc2119">OPTIONAL</em> in this specification are to be interpreted as described in [<cite><a href="#bib-RFC2119" class="bibref">RFC2119</a></cite>].
</p>
<p>This specification defines conformance criteria for:</p>
@@ -420,49 +426,49 @@
</li><li>Canonical N-Triple documents
</li><li>N-Triple parsers
</li></ul>
- <p>A conforming <dfn id="dfn-n-triple-document">N-Triple document</dfn> is a Unicode string that conforms to the grammar and additional constraints defined in <a href="#n-triples-grammar" class="sectionRef sec-ref">section 5. Grammar</a>, starting with the <a href="#grammar-production-ntriplesDoc"><code>ntriplesDoc</code> production</a>. A N-Triple document serializes an RDF graph.</p>
+ <p>A conforming <dfn id="dfn-n-triple-document">N-Triple document</dfn> is a Unicode string that conforms to the grammar and additional constraints defined in <a href="#n-triples-grammar" class="sectionRef sec-ref">section <span class="secno">5.</span> <span class="sec-title">Grammar</span></a>, starting with the <a href="#grammar-production-ntriplesDoc"><code>ntriplesDoc</code> production</a>. A N-Triple document serializes an RDF graph.</p>
<p>A <dfn id="dfn-canonical-n-triple-document">canonical N-Triple document</dfn> is a <strong>N-Triple document</strong> with additional constraints:</p><p>
</p><ul>
- <li>Whitespace following <code>subject</code>, <code>predicate</code>, and <code>object</code> <em class="rfc2119" title="MUST">MUST</em> be a single space, (<code>U+0020</code>) all other locations that allow whitespace <em class="rfc2119" title="MUST">MUST</em> be empty.
- </li><li>All comments <em class="rfc2119" title="MUST">MUST</em> be removed.
- </li><li><code>HEX</code> <em class="rfc2119" title="MUST">MUST</em> use only uppercase letters (<code>[A-F]</code>).
- </li><li>Characters not allowed directly in STRING_LITERAL_QUOTE (<code>U+0022</code>, <code>U+005C</code>, <code>U+000A</code>, <code>U+000D</code>) <em class="rfc2119" title="MUST">MUST</em> use <code>ECHAR</code> not <code>UCHAR</code>.
- </li><li>Characters <em class="rfc2119" title="MUST">MUST</em> be represented directly and not by <code>UCHAR</code>.
+ <li>Whitespace following <code>subject</code>, <code>predicate</code>, and <code>object</code> <em title="MUST" class="rfc2119">MUST</em> be a single space, (<code>U+0020</code>) all other locations that allow whitespace <em title="MUST" class="rfc2119">MUST</em> be empty.
+ </li><li>All comments <em title="MUST" class="rfc2119">MUST</em> be removed.
+ </li><li><code>HEX</code> <em title="MUST" class="rfc2119">MUST</em> use only uppercase letters (<code>[A-F]</code>).
+ </li><li>Characters not allowed directly in STRING_LITERAL_QUOTE (<code>U+0022</code>, <code>U+005C</code>, <code>U+000A</code>, <code>U+000D</code>) <em title="MUST" class="rfc2119">MUST</em> use <code>ECHAR</code> not <code>UCHAR</code>.
+ </li><li>Characters <em title="MUST" class="rfc2119">MUST</em> be represented directly and not by <code>UCHAR</code>.
</li></ul>
- <p>A conforming <dfn id="dfn-n-triple-parser">N-Triple parser</dfn> is a system capable of reading N-Triple documents on behalf of an application. It makes the serialized RDF graph, as defined in <a href="#sec-parsing" class="sectionRef sec-ref">section 6. Parsing</a>, available to the application, usually through some form of API.</p>
-
- <p>The IRI that identifies the N-Triple language is: <code>http://www.w3.org/ns/formats/N-Triples</code></p>
+ <p>A conforming <dfn id="dfn-n-triple-parser">N-Triple parser</dfn> is a system capable of reading N-Triple documents on behalf of an application. It makes the serialized RDF graph, as defined in <a href="#sec-parsing" class="sectionRef sec-ref">section <span class="secno">6.</span> <span class="sec-title">Parsing</span></a>, available to the application, usually through some form of API.</p>
- <section id="n-triples-mediatype" typeof="bibo:Chapter" resource="#n-triples-mediatype" rel="bibo:chapter">
- <h3 aria-level="2" role="heading" id="h3_n-triples-mediatype"><span class="secno">4.1 </span>Media Type and Content Encoding</h3>
-
+ <p>The IRI that identifies the N-Triple language is: <code>http://www.w3.org/ns/formats/N-Triples</code></p>
+
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="n-triples-mediatype">
+ <h3 id="h3_n-triples-mediatype" role="heading" aria-level="2"><span class="secno">4.1 </span>Media Type and Content Encoding</h3>
+
<p>The media type of N-Triples is <code>application/n-triples</code>.
- The content encoding of N-Triples is always UTF-8.
- See <a href="#sec-mediaReg-n-triples">N-Triples Media Type</a> for the media type
+ The content encoding of N-Triples is always UTF-8.
+ See <a href="#sec-mediaReg-n-triples">N-Triples Media Type</a> for the media type
registration form.
</p>
- <section id="sec-other-media-types" typeof="bibo:Chapter" resource="#sec-other-media-types" rel="bibo:chapter">
- <h4 aria-level="3" role="heading" id="h4_sec-other-media-types"><span class="secno">4.1.1 </span>Other Media Types</h4>
- <p>N-Triples has been historically provided with other media types. N-Triples may also be provided as <code>text/plain</code>. When used in this way N-Triples <em class="rfc2119" title="MUST">MUST</em> use the escaped form of any character outside US-ASCII. As N-Triples is a subset of Turtle a N-Triples document <em class="rfc2119" title="MAY">MAY</em> also be provided as <code>text/turtle</code>. In both of these cases the document is not an N-Triples document as an N-Triples document is only provided as <code>application/n-triples</code>.</p>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-other-media-types">
+ <h4 id="h4_sec-other-media-types" role="heading" aria-level="3"><span class="secno">4.1.1 </span>Other Media Types</h4>
+ <p>N-Triples has been historically provided with other media types. N-Triples may also be provided as <code>text/plain</code>. When used in this way N-Triples <em title="MUST" class="rfc2119">MUST</em> use the escaped form of any character outside US-ASCII. As N-Triples is a subset of Turtle a N-Triples document <em title="MAY" class="rfc2119">MAY</em> also be provided as <code>text/turtle</code>. In both of these cases the document is not an N-Triples document as an N-Triples document is only provided as <code>application/n-triples</code>.</p>
</section>
</section>
</section>
- <section id="n-triples-grammar" typeof="bibo:Chapter" resource="#n-triples-grammar" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_n-triples-grammar"><span class="secno">5. </span>Grammar</h2>
- <p>A N-Triples document is a Unicode [<cite><a class="bibref" href="#bib-UNICODE">UNICODE</a></cite>] character string encoded in UTF-8.
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="n-triples-grammar">
+ <!--OddPage--><h2 id="h2_n-triples-grammar" role="heading" aria-level="1"><span class="secno">5. </span>Grammar</h2>
+ <p>A N-Triples document is a Unicode [<cite><a href="#bib-UNICODE" class="bibref">UNICODE</a></cite>] character string encoded in UTF-8.
Unicode code points only in the range U+0 to U+10FFFF inclusive are allowed.</p>
<p>White space (tab <code>U+0009</code> or space <code>U+0020</code>) is used to separate two terminals which would otherwise be (mis-)recognized as one terminal. White space is significant in the production <a href="#grammar-production-STRING_LITERAL_QUOTE">STRING_LITERAL_QUOTE</a>.</p>
<p>Comments in N-Triples take the form of '<code>#</code>', outside an <code>IRIREF</code> or <code>STRING_LITERAL_QUOTE</code>, and continue to the end of line (<code>EOL</code>) or end of file if there is no end of line after the comment marker. Comments are treated as white space.</p>
<p>The <abbr title="Extended Backus–Naur Form">EBNF</abbr> used here is defined in XML 1.0
- [<cite><a class="bibref" href="#bib-EBNF-NOTATION">EBNF-NOTATION</a></cite>].</p>
+ [<cite><a href="#bib-EBNF-NOTATION" class="bibref">EBNF-NOTATION</a></cite>].</p>
<p>Escape sequence rules are the same as Turtle
- [<cite><a class="bibref" href="#bib-turtle">turtle</a></cite>]. However, as only the <a href="#grammar-production-STRING_LITERAL_QUOTE"><code>STRING_LITERAL_QUOTE</code></a> production is allowed new lines in literals <em class="rfc2119" title="MUST">MUST</em> be escaped.</p>
+ [<cite><a href="#bib-TURTLE" class="bibref">TURTLE</a></cite>]. However, as only the <a href="#grammar-production-STRING_LITERAL_QUOTE"><code>STRING_LITERAL_QUOTE</code></a> production is allowed new lines in literals <em title="MUST" class="rfc2119">MUST</em> be escaped.</p>
<div><table class="grammar">
<tbody class="grammar-productions">
<tr id="grammar-production-ntriplesDoc" data-grammar-original="[1] ntriplesDoc ::= triple? (EOL triple)* EOL?" data-grammar-expression="(',', [('?', ('id', 'triple')), ('*', (',', [('id', 'EOL'), ('id', 'triple')])), ('?', ('id', 'EOL'))])">
@@ -514,7 +520,7 @@
<td>::=</td>
<td>[<code class="grammar-chars">#xD#xA</code>]<code class="grammar-plus">+</code></td>
</tr>
- <tr id="grammar-production-IRIREF" data-grammar-original="[8] IRIREF ::= '<' ([^#x00-#x20<>"{}|^`\] | UCHAR)* '>'" data-grammar-expression="(',', [("'", '<'), ('*', ('|', [('[', '^#x00-#x20<>"{}|^`\\'), ('id', 'UCHAR')])), ("'", '>')])" class="grammar-token">
+ <tr id="grammar-production-IRIREF" data-grammar-original="[8] IRIREF ::= '<' ([^#x00-#x20<>"{}|^`\] | UCHAR)* '>'" data-grammar-expression="(',', [("'", '<'), ('*', ('|', [('[', '^#x00-#x20<>"{}|^`\\'), ('id', 'UCHAR')])), ("'", '>')])" class="grammar-token">
<td>[8]</td>
<td><code>IRIREF</code></td>
<td>::=</td>
@@ -572,16 +578,16 @@
</div>
</section>
- <section id="sec-parsing" typeof="bibo:Chapter" resource="#sec-parsing" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_sec-parsing"><span class="secno">6. </span>Parsing</h2>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-parsing">
+ <!--OddPage--><h2 id="h2_sec-parsing" role="heading" aria-level="1"><span class="secno">6. </span>Parsing</h2>
<p>Parsing N-Triples requires a state of one item:</p>
<ul>
- <li id="bnodeLabels">Map[<a class="type string">string</a> -> <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-blank-node">blank node</a>] <code class="dfn">bnodeLabels</code> — A mapping from string to blank node.</li>
+ <li id="bnodeLabels">Map[string -> <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-blank-node">blank node</a>] <code class="dfn">bnodeLabels</code> — A mapping from string to blank node.</li>
</ul>
- <section id="sec-parsing-terms" typeof="bibo:Chapter" resource="#sec-parsing-terms" rel="bibo:chapter">
- <h3 aria-level="2" role="heading" id="h3_sec-parsing-terms"><span class="secno">6.1 </span>RDF Term Constructors</h3>
- <p>This table maps productions and lexical tokens to <code>RDF terms</code> or components of <code>RDF terms</code> listed in <a href="#sec-parsing" class="sectionRef sec-ref">section 6. Parsing</a>:</p>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-parsing-terms">
+ <h3 id="h3_sec-parsing-terms" role="heading" aria-level="2"><span class="secno">6.1 </span>RDF Term Constructors</h3>
+ <p>This table maps productions and lexical tokens to <code>RDF terms</code> or components of <code>RDF terms</code> listed in <a href="#sec-parsing" class="sectionRef sec-ref">section <span class="secno">6.</span> <span class="sec-title">Parsing</span></a>:</p>
<table class="simple">
<thead>
<tr><th>production</th><th>type</th><th>procedure</th></tr>
@@ -596,23 +602,23 @@
</table>
</section>
<section id="rdf-triple-construction">
- <h3 aria-level="2" role="heading" id="h3_rdf-triple-construction"><span class="secno">6.2 </span>RDF Triple Construction</h3>
- <p>A N-Triple document defines an RDF graphs composed of a set of RDF triples. The <code><a href="#grammar-production-triple">triple</a></code> production produces a triple defined by the terms constructed for <code><a href="#grammar-production-subject">subject</a></code>, <code><a href="#grammar-production-predicate">predicate</a></code> and <code><a href="#grammar-production-object">object</a></code>.
+ <h3 id="h3_rdf-triple-construction" role="heading" aria-level="2"><span class="secno">6.2 </span>RDF Triple Construction</h3>
+ <p>A N-Triple document defines an RDF graphs composed of a set of RDF triples. The <code><a href="#grammar-production-triple">triple</a></code> production produces a triple defined by the terms constructed for <code><a href="#grammar-production-subject">subject</a></code>, <code><a href="#grammar-production-predicate">predicate</a></code> and <code><a href="#grammar-production-object">object</a></code>.
</p></section>
</section>
- <section id="section-ack" class="informative" typeof="bibo:Chapter" resource="#section-ack" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_section-ack"><span class="secno">7. </span>Acknowledgements</h2><p><em>This section is non-normative.</em></p>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="section-ack" class="informative">
+ <!--OddPage--><h2 id="h2_section-ack" role="heading" aria-level="1"><span class="secno">7. </span>Acknowledgements</h2><p><em>This section is non-normative.</em></p>
<p>The editor of the 2013 edition acknowledges valuable contributions from Gregg Kellogg, Andy Seaborn, Eric Prud'hommeaux, Dave Beckett, David Robillard, Gregory Williams, Pat Hayes, Richard Cyganiak, Henry S. Thompson, and David Booth.</p>
- <p>This specification is a product of extended deliberations by the
+ <p>This specification is a product of extended deliberations by the
<a href="http://www.w3.org/2000/09/dbwg/details?group=46168&public=1">members of the RDF Working Group</a>.
It draws upon the earlier specification in <a href="http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#ntriples">RDF Test Cases</a>, edited by Dave Beckett.</p>
</section>
- <section id="sec-changes" class="appendix" typeof="bibo:Chapter" resource="#sec-changes" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_sec-changes"><span class="secno">A. </span>Changes to this document</h2><h2 id="generatedID">
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-changes" class="appendix">
+ <!--OddPage--><h2 id="h2_sec-changes" role="heading" aria-level="1"><span class="secno">A. </span>Changes to this document</h2><h2 id="generatedID">
</h2><h2 id="changes-since-last-publication-as-last-call-working-draft">Changes since last publication as Last Call Working Draft</h2>
<p>No substitutive changes.</p>
<h2 id="changes-since-original-publication-as-note">Changes since original publication as Note</h2>
@@ -626,8 +632,8 @@
</li></ul>
</section>
- <section id="sec-mediaReg-n-triples" class="appendix" typeof="bibo:Chapter" resource="#sec-mediaReg-n-triples" rel="bibo:chapter">
- <!--OddPage--><h2 aria-level="1" role="heading" id="h2_sec-mediaReg-n-triples"><span class="secno">B. </span>N-Triples Internet Media Type, File Extension and Macintosh File Type </h2>
+ <section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="sec-mediaReg-n-triples" class="appendix">
+ <!--OddPage--><h2 id="h2_sec-mediaReg-n-triples" role="heading" aria-level="1"><span class="secno">B. </span>N-Triples Internet Media Type, File Extension and Macintosh File Type </h2>
<dl>
<dt>Contact:</dt>
<dd>Eric Prud'hommeaux</dd>
@@ -653,29 +659,29 @@
<dd>None</dd>
<dt>Encoding considerations:</dt>
- <dd>The syntax of N-Triples is expressed over code points in Unicode [<cite><a class="bibref" href="#bib-UNICODE">UNICODE</a></cite>]. The encoding is always UTF-8 [<cite><a class="bibref" href="#bib-UTF-8">UTF-8</a></cite>].</dd>
+ <dd>The syntax of N-Triples is expressed over code points in Unicode [<cite><a href="#bib-UNICODE" class="bibref">UNICODE</a></cite>]. The encoding is always UTF-8 [<cite><a href="#bib-UTF-8" class="bibref">UTF-8</a></cite>].</dd>
<dd>Unicode code points may also be expressed using an \uXXXX (U+0 to U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a hexadecimal digit [0-9A-F]</dd>
<dt>Security considerations:</dt>
- <dd>N-Triples is a general-purpose assertion language; applications may evaluate given data to infer more assertions or to dereference IRIs, invoking the security considerations of the scheme for that IRI. Note in particular, the privacy issues in [<cite><a class="bibref" href="#bib-RFC3023">RFC3023</a></cite>] section 10 for HTTP IRIs. Data obtained from an inaccurate or malicious data source may lead to inaccurate or misleading conclusions, as well as the dereferencing of unintended IRIs. Care must be taken to align the trust in consulted resources with the sensitivity of the intended use of the data; inferences of potential medical treatments would likely require different trust than inferences for trip planning.</dd>
+ <dd>N-Triples is a general-purpose assertion language; applications may evaluate given data to infer more assertions or to dereference IRIs, invoking the security considerations of the scheme for that IRI. Note in particular, the privacy issues in [<cite><a href="#bib-RFC3023" class="bibref">RFC3023</a></cite>] section 10 for HTTP IRIs. Data obtained from an inaccurate or malicious data source may lead to inaccurate or misleading conclusions, as well as the dereferencing of unintended IRIs. Care must be taken to align the trust in consulted resources with the sensitivity of the intended use of the data; inferences of potential medical treatments would likely require different trust than inferences for trip planning.</dd>
<dd>N-Triples is used to express arbitrary application data; security considerations will vary by domain of use. Security tools and protocols applicable to text (e.g. PGP encryption, MD5 sum validation, password-protected compression) may also be used on N-Triples documents. Security/privacy protocols must be imposed which reflect the sensitivity of the embedded information.</dd>
- <dd>N-Triples can express data which is presented to the user, for example, RDF Schema labels. Application rendering strings retrieved from untrusted N-Triples documents must ensure that malignant strings may not be used to mislead the reader. The security considerations in the media type registration for XML ([<cite><a class="bibref" href="#bib-RFC3023">RFC3023</a></cite>] section 10) provide additional guidance around the expression of arbitrary data and markup.</dd>
+ <dd>N-Triples can express data which is presented to the user, for example, RDF Schema labels. Application rendering strings retrieved from untrusted N-Triples documents must ensure that malignant strings may not be used to mislead the reader. The security considerations in the media type registration for XML ([<cite><a href="#bib-RFC3023" class="bibref">RFC3023</a></cite>] section 10) provide additional guidance around the expression of arbitrary data and markup.</dd>
<dd>N-Triples uses IRIs as term identifiers. Applications interpreting data expressed in N-Triples should address the security issues of
- <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>] Section 8, as well as
- <a class="norm" href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifier (URI): Generic Syntax</a> [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>] Section 7.</dd>
+ <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [<cite><a href="#bib-RFC3987" class="bibref">RFC3987</a></cite>] Section 8, as well as
+ <a class="norm" href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifier (URI): Generic Syntax</a> [<cite><a href="#bib-RFC3986" class="bibref">RFC3986</a></cite>] Section 7.</dd>
- <dd>Multiple IRIs may have the same appearance. Characters in different scripts may
- look similar (a Cyrillic "о" may appear similar to a Latin "o"). A character followed
- by combining characters may have the same visual representation as another character
- (LATIN SMALL LETTER E followed by COMBINING ACUTE ACCENT has the same visual representation
+ <dd>Multiple IRIs may have the same appearance. Characters in different scripts may
+ look similar (a Cyrillic "о" may appear similar to a Latin "o"). A character followed
+ by combining characters may have the same visual representation as another character
+ (LATIN SMALL LETTER E followed by COMBINING ACUTE ACCENT has the same visual representation
as LATIN SMALL LETTER E WITH ACUTE).
<!-- (<code>foo:resum鼯code> and <code>fоо:resumé</code>)-->
Any person or application that is writing or interpreting data in Turtle must take care to use the IRI that matches the intended semantics, and avoid IRIs that make look similar.
- Further information about matching of similar characters can be found
- in <a class="inform" href="http://www.unicode.org/reports/tr36/">Unicode Security
- Considerations</a> [<cite><a class="bibref" href="#bib-UNICODE-SECURITY">UNICODE-SECURITY</a></cite>] and
- <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource
- Identifiers (IRIs)</a> [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>] Section 8.
+ Further information about matching of similar characters can be found
+ in <a class="inform" href="http://www.unicode.org/reports/tr36/">Unicode Security
+ Considerations</a> [<cite><a href="#bib-UNICODE-SECURITY" class="bibref">UNICODE-SECURITY</a></cite>] and
+ <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource
+ Identifiers (IRIs)</a> [<cite><a href="#bib-RFC3987" class="bibref">RFC3987</a></cite>] Section 8.
</dd>
<dt>Interoperability considerations:</dt>
@@ -707,14 +713,14 @@
</section>
-<section id="references" class="appendix" typeof="bibo:Chapter" resource="#references" rel="bibo:chapter"><!--OddPage--><h2 aria-level="1" role="heading" id="h2_references"><span class="secno">C. </span>References</h2><section id="normative-references" typeof="bibo:Chapter" resource="#normative-references" rel="bibo:chapter"><h3 aria-level="2" role="heading" id="h3_normative-references"><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-EBNF-NOTATION">[EBNF-NOTATION]</dt><dd rel="dcterms:requires">Tim Bray; Jean Paoli; C. M. Sperberg-McQueen; Eve Maler; François Yergeau. <a href="http://www.w3.org/TR/REC-xml/#sec-notation"><cite>EBNF Notation</cite></a> 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/REC-xml/#sec-notation">http://www.w3.org/TR/REC-xml/#sec-notation</a>
+<section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="references" class="appendix"><!--OddPage--><h2 id="h2_references" role="heading" aria-level="1"><span class="secno">C. </span>References</h2><section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="normative-references"><h3 id="h3_normative-references" role="heading" aria-level="2"><span class="secno">C.1 </span>Normative references</h3><dl about="" class="bibliography"><dt id="bib-EBNF-NOTATION">[EBNF-NOTATION]</dt><dd rel="dcterms:requires">Tim Bray; Jean Paoli; C. M. Sperberg-McQueen; Eve Maler; François Yergeau. <a href="http://www.w3.org/TR/REC-xml/#sec-notation"><cite>EBNF Notation</cite></a> 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/REC-xml/#sec-notation">http://www.w3.org/TR/REC-xml/#sec-notation</a>
</dd><dt id="bib-RDF-TESTCASES">[RDF-TESTCASES]</dt><dd rel="dcterms:requires">jan grant; Dave Beckett. <a href="http://www.w3.org/TR/rdf-testcases"><cite>RDF Test Cases</cite></a>. 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/rdf-testcases">http://www.w3.org/TR/rdf-testcases</a>
</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd rel="dcterms:requires">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-RFC3023">[RFC3023]</dt><dd rel="dcterms:requires">M. Murata; S. St.Laurent; D. Kohn. <a href="http://www.ietf.org/rfc/rfc3023.txt"><cite>XML Media Types (RFC 3023)</cite></a>. January 2001. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a>
</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd rel="dcterms:requires">T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic Syntax (RFC 3986)</cite></a>. January 2005. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd rel="dcterms:requires">M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs)</cite></a>. January 2005. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>
+</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd rel="dcterms:requires">Eric Prud'hommeaux, Gavin Carothers, Editors. <cite><a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">RDF 1.1 Turtle: Terse RDF Triple Language.</a></cite> 19 February 2013. W3C Candidate Recommendation (work in progress). URL: <a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">http://www.w3.org/TR/2013/CR-turtle-20130219/</a>. The latest edition is available at <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
</dd><dt id="bib-UNICODE">[UNICODE]</dt><dd rel="dcterms:requires"><a href="http://www.unicode.org/versions/latest/"><cite>The Unicode Standard</cite></a>. URL: <a href="http://www.unicode.org/versions/latest/">http://www.unicode.org/versions/latest/</a>
</dd><dt id="bib-UTF-8">[UTF-8]</dt><dd rel="dcterms:requires">F. Yergeau. <a href="http://www.ietf.org/rfc/rfc3629.txt"><cite>UTF-8, a transformation format of ISO 10646</cite></a>. IETF RFC 3629. November 2003. URL: <a href="http://www.ietf.org/rfc/rfc3629.txt">http://www.ietf.org/rfc/rfc3629.txt</a>
-</dd><dt id="bib-turtle">[turtle]</dt><dd rel="dcterms:requires">Eric Prud'hommeaux; Gavin Carothers. <a href="http://www.w3.org/TR/turtle/"><cite>Turtle</cite></a>. 19 February 2013. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
-</dd></dl></section><section id="informative-references" typeof="bibo:Chapter" resource="#informative-references" rel="bibo:chapter"><h3 aria-level="2" role="heading" id="h3_informative-references"><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-UNICODE-SECURITY">[UNICODE-SECURITY]</dt><dd rel="dcterms:references">Mark Davis; Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations</cite></a>. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
+</dd></dl></section><section rel="bibo:Chapter" resource="#ref" typeof="bibo:Chapter" id="informative-references"><h3 id="h3_informative-references" role="heading" aria-level="2"><span class="secno">C.2 </span>Informative references</h3><dl about="" class="bibliography"><dt id="bib-UNICODE-SECURITY">[UNICODE-SECURITY]</dt><dd rel="dcterms:references">Mark Davis; Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations</cite></a>. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
</dd></dl></section></section></body></html>
\ No newline at end of file