first version for FPWD
authorGuus Schreiber <guus.schreiber@vu.nl>
Sat, 06 Apr 2013 01:46:14 +0200
changeset 781 575acaaf9533
parent 780 689aa92214f3
child 782 19e599809073
first version for FPWD
drafts/n-triples/Overview.html
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/drafts/n-triples/Overview.html	Sat Apr 06 01:46:14 2013 +0200
@@ -0,0 +1,822 @@
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
+<head>
+    <title>N-Triples</title>
+    <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
+  
+  
+  
+    
+      <style type="text/css">
+    /* Style Turtle script blocks to be visable */
+    pre.example script {
+        display:block;
+    }
+    .separated thead tr th { border:1px solid black; padding: .2em; }
+    .separated tbody tr td { border:1px solid black; text-align: center; }
+    .separated tbody tr td.r { text-align: right; padding: .5em; }
+    .grammar td { font-family: monospace;}
+    .grammar-literal { color: gray;}
+    </style> 
+  <style>/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 { 
+    text-transform:     lowercase;
+    font-variant:       small-caps;
+    font-style:         normal;
+    color:              #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+    border: none;
+}
+
+dfn {
+    font-weight:    bold;
+}
+
+a.internalDFN {
+    color:  inherit;
+    border-bottom:  1px solid #99c;
+    text-decoration:    none;
+}
+
+a.externalDFN {
+    color:  inherit;
+    border-bottom:  1px dotted #ccc;
+    text-decoration:    none;
+}
+
+a.bibref {
+    text-decoration:    none;
+}
+
+cite .bibref {
+    font-style: normal;
+}
+
+code {
+    color:  #ff4500;
+}
+
+
+/* --- --- */
+ol.algorithm { counter-reset:numsection; list-style-type: none; }
+ol.algorithm li { margin: 0.5em 0; }
+ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
+
+/* --- TOC --- */
+.toc a, .tof a {
+    text-decoration:    none;
+}
+
+a .secno, a .figno {
+    color:  #000;
+}
+
+ul.tof, ol.tof {
+    list-style: none outside none;
+}
+
+.caption {
+    margin-top: 0.5em;
+    font-style:   italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    border-bottom:  3px solid #005a9c;
+}
+
+.simple th {
+    background: #005a9c;
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+}
+
+.simple th[scope="row"] {
+    background: inherit;
+    color:  inherit;
+    border-top: 1px solid #ddd;
+}
+
+.simple td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+    background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+    margin-top: 0;
+}
+
+.section dd > p:last-child {
+    margin-bottom: 0;
+}
+
+.section dd {
+    margin-bottom:  1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+    margin-bottom:  0;
+}
+</style><style>/* --- EXAMPLES --- */
+div.example-title {
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.example-title span {
+    text-transform: uppercase;   
+}
+aside.example, div.example, div.illegal-example {
+    padding: 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+div.illegal-example { color: red }
+div.illegal-example p { color: black }
+aside.example, div.example {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+    border-color: #e0cb52;
+    background: #fcfaee;    
+}
+
+aside.example div.example {
+    border-left-width: .1em;
+    border-color: #999;
+    background: #fff;
+}
+aside.example div.example div.example-title {
+    color: #999;
+}
+</style><style>/* --- ISSUES/NOTES --- */
+div.issue-title, div.note-title {
+    padding-right:  1em;
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.issue-title { color: #e05252; }
+div.note-title { color: #52e052; }
+div.issue-title span, div.note-title span {
+    text-transform: uppercase;
+}
+div.note, div.issue {
+    margin-top: 1em;
+    margin-bottom: 1em;
+}
+.note > p:first-child, .issue > p:first-child { margin-top: 0 }
+.issue, .note {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+}
+div.issue, div.note {
+    padding: 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+span.note, span.issue { padding: .1em .5em .15em; }
+
+.issue {
+    border-color: #e05252;
+    background: #fbe9e9;
+}
+.note {
+    border-color: #52e052;
+    background: #e9fbe9;
+}
+
+
+</style><link href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE" rel="stylesheet"><!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+  <body><div class="head">
+  <p>
+    
+      <a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a>
+    
+  </p>
+  <h1 class="title" id="title">N-Triples</h1>
+  
+    <h2 id="subtitle">A line-based syntax for an RDF graph</h2>
+  
+  <h2 id="w3c-working-group-note-09-april-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Working Group Note 09 April 2013</h2>
+  <dl>
+    
+      <dt>This version:</dt>
+      <dd><a href="http://www.w3.org/TR/2013/NOTE-n-triples-20130409/">http://www.w3.org/TR/2013/NOTE-n-triples-20130409/</a></dd>
+      <dt>Latest published version:</dt>
+      <dd><a href="http://www.w3.org/TR/n-triples/">http://www.w3.org/TR/n-triples/</a></dd>
+    
+    
+      <dt>Latest editor's draft:</dt>
+      <dd><a href="https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/n-triples.html">https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/n-triples.html</a></dd>
+    
+    
+    
+    
+    
+      <dt>Previous version:</dt>
+      <dd><a href=""></a></dd>
+    
+    
+    <dt>Editor:</dt>
+    <dd><span>Gavin Carothers</span>, <a href="https://lexmachina.com/">Lex Machina, Inc</a></dd>
+
+    
+      <dt>Author:</dt>
+      <dd><a href="http://www.dajobe.org/">David Beckett</a></dd>
+
+    
+  </dl>
+  
+  
+  
+  
+    
+      <p class="copyright">
+        <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 
+        2001-2013
+        
+        <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.
+        <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.
+      </p>
+    
+  
+  <hr>
+</div>
+    <section class="introductory" id="abstract"><h2>Abstract</h2><p>
+    N-Triples is a line-based, plain text format for encoding an RDF graph.
+</p></section><section id="sotd" class="introductory"><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 <abbr title="World Wide Web Consortium">W3C</abbr> publications and the latest revision
+          of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports
+          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 href="#bib-RDF-TESTCASES" class="bibref">RDF-TESTCASES</a></cite>] document. Due to its populatity
+as exchange format the <a href="http://www.w3.org/2011/rdf-wg/">RDF
+Working Group</a> decided to publish an updated
+version. This document is intended to become a Working Group Note. 
+      
+        <p>
+          This document was published by the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> as a First Public Working Group Note.
+          
+          
+          If you wish to make comments regarding this document, please send them to 
+          <a href="mailto:[email protected]">[email protected]</a> 
+          (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>,
+          <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">archives</a>).
+          
+          
+          
+          
+        All comments are welcome.
+        
+        
+          </p><p>
+            Publication as a Working Group Note does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr> 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 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+          
+          
+          
+            
+              <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46168/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 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+          
+          
+        </p>
+        
+      
+    
+  
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#sec-triples"><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-triple-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></li><li class="tocline"><a class="tocxref" href="#sec-diff-turtle"><span class="secno">A. </span>Summary of diffrences in N-Triples and Turtle</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#sec-triples"><span class="secno">A.1 </span>Triples</a></li><li class="tocline"><a class="tocxref" href="#iri-summary"><span class="secno">A.2 </span>IRI Representations</a></li><li class="tocline"><a class="tocxref" href="#literal-summary"><span class="secno">A.3 </span>Literal Representations</a></li><li class="tocline"><a class="tocxref" href="#bnode-summary"><span class="secno">A.4 </span>Summary of Blank Node Representations in N-Triples and Turtle</a></li></ul></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-triples">
+        <!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
+        <p>This document defines an easy to parse line-based subset of
+        Turtle [<cite><a href="#bib-TURTLE-TR" class="bibref">TURTLE-TR</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 a 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 seperated 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>
+
+      <div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example"><script type="application/n-triples"><http://one.example/subject1> <http://one.example/predicate1> <http://one.example/object1> . # comments here
+# or on a line by themselves
+_:subject1 <http://an.example/predicate1> "object1" .
+_:subject2 <http://an.example/predicate2> "object2" .
+</script></pre></div>
+
+      <p>
+        N-Triples triples are also Turtle <a href="#simple-triples">simple triples</a>, but Turtle includes other <a href="#terms">representations of RDF Terms</a> and <a href="#predicate-lists">abbreviations of RDF Triples</a>. When parsed by a Turtle parser, data in the N-Triples format will produce exactly the same triples as a parser for the restricted N-triples language.
+      </p>
+      <p>The RDF graph represented by an N-Triples document contains exactly each triple matching <a href="#prod-ntriples-triple">N-Triples <code>triple</code> production</a>.
+      </p></section>
+
+      <section id="sec-n-triples-language">
+        <!--OddPage--><h2><span class="secno">2. </span>N-Triples Language</h2>
+        <section id="simple-triples">
+          <h3><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">
+        <h3><span class="secno">2.2 </span>IRIs</h3>
+
+        <p>
+            <a href="../rdf-concepts/index.html#dfn-iri">IRIs</a> may be written only as absolute IRIs. 
+            IRIs are enclosed in '&lt;' and '&gt;' and may contain <a href="#numeric">numeric escape sequences</a> (described below). For example <code>&lt;http://example.org/#green-goblin&gt;</code>.
+        </p>
+      </section>
+        <section id="sec-literals">
+              <h3><span class="secno">2.3 </span>RDF Literals</h3>
+
+        <p><a href="../rdf-concepts/index.html#dfn-literal">Literals</a> are used to identify values such as strings, numbers, dates.</p>
+
+
+        <p>
+          Literals (Grammar production <a href="#grammar-production-RDFLiteral">RDFLiteral</a>) have a lexical form followed by a language tag, a datatype IRI, or neither.
+          The representation of the lexical form consists of an initial delimiter <code>"</code> (<span class="codepoint">U+0022</span>), a sequence of permitted characters or <a href="#numeric">numeric escape sequence</a> or <a href="#string">string escape sequence</a>, and a final delimiter. Literals may not contain the characters <code>"</code>, <code title="LINE FEED"><sub>LF</sub></code>, or <code title="CARRIAGE RETURN"><sub>CR</sub></code>. In addition '<code>\</code>' (<span class="codepoint">U+005C</span>) may not appear in any quoted literal except as part of an escape sequence.
+          The corresponding <a href="../rdf-concepts/index.html#dfn-lexical-form">RDF lexical form</a> is the characters between the delimiters, after processing any escape sequences.
+          If present, the <a href="../rdf-concepts/index.html#dfn-language-tagged-string">language tag</a> is preceded by a '<code>@</code>' (<span class="codepoint">U+0040</span>).
+          If there is no language tag, there may be a <a href="../rdf-concepts/index.html#dfn-datatype-URI">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>
+        <div class="issue"><div class="issue-title"><span>Issue 1</span></div><p class="">
+          Include examples with a few escapes for new lines, etc
+        </p></div>
+        </section>
+      <section id="BNodes">
+        <h3><span class="secno">2.4 </span>RDF Blank Nodes</h3>
+        <p>
+          <a href="../rdf-concepts/index.html#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:
+        </p>
+        <ul>
+          <li>The characters <code>_</code> and digits may appear anywhere in a blank node label.</li>
+          <li>The character <code>.</code> may appear anywhere except the first or last character.</li>
+          <li>The characters <code>-</code>, <code>U+00B7</code>, <code>U+0300</code> to <code>U+036F</code> and <code>U+203F</code> to <code>U+2040</code> are permitted anywhere except the first character.</li>
+        </ul>
+        <p>
+          A fresh RDF blank node is allocated for each unique blank node label in a document.
+          Repeated use of the same blank node label identifies the same RDF blank node.
+        </p>
+        <div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example"><script type="application/n-triples">_:alice <http://xmlns.com/foaf/0.1/knows> _:bob .
+_:bob <http://xmlns.com/foaf/0.1/knows> _:alice .</script></pre></div>
+  </section>
+
+    </section>
+
+        <section id="n-triple-changes" class="informative">
+          <!--OddPage--><h2><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
+            </li><li>Defines a unique media type <code>application/n-triples</code>
+            </li><li>Subset of Turtle rather than Notation 3
+            </li><li>Comments may occur after a triple production
+            </li><li>Allows <code>\b</code> and <code>\f</code> for backspace and form feed
+            </li><li>More than one way to represent a single character
+          </li></ul>
+        </section>
+
+      <section id="conformance"><!--OddPage--><h2><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 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>
+              <ul>
+                <li>N-Triple documents
+                </li><li>N-Triple parsers
+                </li><li>N-Triple seralizers
+              </li></ul>
+      <p>A conforming <strong>N-Triple document</strong> is a Unicode string that conforms to the grammar and additional constraints defined in <a href="#sec-grammar" class="sectionRef">section Not found 'sec-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 <strong>N-Triple parser</strong> 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>
+
+      <div class="issue"><div class="issue-title"><span>Issue 2</span></div><p class="">N-Triple seralizers are not defined here, will likely include optional behavior to conform to RDF Test Cases syntax as well.</p></div>
+
+      <p>The IRI that identifies the N-Triple language is: <code>http://www.w3.org/ns/formats/N-Triple</code></p>          
+
+        <section id="n-triples-mediatype">
+      <h3><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 
+      registration form.
+      </p>
+
+      <section id="sec-other-media-types">
+        <h4><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-triple-grammar">
+          <!--OddPage--><h2><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 codepoints only in the range U+0 to U+10FFFF inclusive are allowed.</p>
+          <p>The <abbr title="Extended Backus–Naur Form">EBNF</abbr> used here is defined in XML 1.0
+            [<cite><a href="#bib-EBNF-NOTATION" class="bibref">EBNF-NOTATION</a></cite>].</p>
+          <p><a href="#sec-escapes">Escape sequence rules</a> are the same as Turtle. However, as only the <code>STRING_LITERAL2</code> 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'))])">
+    <td>[1]</td>
+    <td><code>ntriplesDoc</code></td>
+    <td>::=</td>
+    <td><a href="#grammar-production-triple">triple</a>? (<a href="#grammar-production-EOL">EOL</a> <a href="#grammar-production-triple">triple</a>)<code class="grammar-star">*</code> <a href="#grammar-production-EOL">EOL</a>?</td>
+</tr>
+            <tr id="grammar-production-triple" data-grammar-original="[2]  triple             ::= WS* subject WS+ predicate WS+ object WS* '.' WS*" data-grammar-expression="(',', [('*', ('id', 'WS')), ('id', 'subject'), ('+', ('id', 'WS')), ('id', 'predicate'), ('+', ('id', 'WS')), ('id', 'object'), ('*', ('id', 'WS')), (&quot;'&quot;, '.'), ('*', ('id', 'WS'))])">
+    <td>[2]</td>
+    <td><code>triple</code></td>
+    <td>::=</td>
+    <td><a href="#grammar-production-WS">WS</a><code class="grammar-star">*</code> <a href="#grammar-production-subject">subject</a> <a href="#grammar-production-WS">WS</a><code class="grammar-plus">+</code> <a href="#grammar-production-predicate">predicate</a> <a href="#grammar-production-WS">WS</a><code class="grammar-plus">+</code> <a href="#grammar-production-object">object</a> <a href="#grammar-production-WS">WS</a><code class="grammar-star">*</code> '<code class="grammar-literal">.</code>' <a href="#grammar-production-WS">WS</a><code class="grammar-star">*</code></td>
+</tr>
+            <tr id="grammar-production-subject" data-grammar-original="[3]  subject            ::= IRIREF | BLANK_NODE_LABEL" data-grammar-expression="('|', [('id', 'IRIREF'), ('id', 'BLANK_NODE_LABEL')])">
+    <td>[3]</td>
+    <td><code>subject</code></td>
+    <td>::=</td>
+    <td><a href="#grammar-production-IRIREF">IRIREF</a> <code>| </code> <a href="#grammar-production-BLANK_NODE_LABEL">BLANK_NODE_LABEL</a></td>
+</tr>
+            <tr id="grammar-production-predicate" data-grammar-original="[4]  predicate          ::= IRIREF" data-grammar-expression="('id', 'IRIREF')">
+    <td>[4]</td>
+    <td><code>predicate</code></td>
+    <td>::=</td>
+    <td><a href="#grammar-production-IRIREF">IRIREF</a></td>
+</tr>
+            <tr id="grammar-production-object" data-grammar-original="[5]  object             ::= IRIREF | BLANK_NODE_LABEL | literal" data-grammar-expression="('|', [('id', 'IRIREF'), ('id', 'BLANK_NODE_LABEL'), ('id', 'literal')])">
+    <td>[5]</td>
+    <td><code>object</code></td>
+    <td>::=</td>
+    <td><a href="#grammar-production-IRIREF">IRIREF</a> <code>| </code> <a href="#grammar-production-BLANK_NODE_LABEL">BLANK_NODE_LABEL</a> <code>| </code> <a href="#grammar-production-literal">literal</a></td>
+</tr>
+            <tr id="grammar-production-literal" data-grammar-original="[6]  literal            ::= STRING_LITERAL_QUOTE ('^^' IRIREF | ('@' LANG) )?" data-grammar-expression="(',', [('id', 'STRING_LITERAL_QUOTE'), ('?', ('|', [(',', [(&quot;'&quot;, '^^'), ('id', 'IRIREF')]), (',', [(&quot;'&quot;, '@'), ('id', 'LANG')])]))])">
+    <td>[6]</td>
+    <td><code>literal</code></td>
+    <td>::=</td>
+    <td><a href="#grammar-production-STRING_LITERAL_QUOTE">STRING_LITERAL_QUOTE</a> ('<code class="grammar-literal">^^</code>' <a href="#grammar-production-IRIREF">IRIREF</a> <code>| </code> '<code class="grammar-literal">@</code>' <a href="#grammar-production-LANG">LANG</a>)?</td>
+</tr>
+<tr><td colspan="5"><h2 id="terminals">Productions for terminals</h2></td></tr>
+            <tr id="grammar-production-LANG" data-grammar-original="[7]  LANG               ::= [a-zA-Z]+ ( &quot;-&quot; [a-zA-Z0-9]+ )*" data-grammar-expression="(',', [('+', ('[', 'a-zA-Z')), ('*', (',', [(&quot;'&quot;, '-'), ('+', ('[', 'a-zA-Z0-9'))]))])" class="grammar-token">
+    <td>[7]</td>
+    <td><code>LANG</code></td>
+    <td>::=</td>
+    <td>[<code class="grammar-chars">a-zA-Z</code>]<code class="grammar-plus">+</code> ('<code class="grammar-literal">-</code>' [<code class="grammar-chars">a-zA-Z0-9</code>]<code class="grammar-plus">+</code>)<code class="grammar-star">*</code></td>
+</tr>
+            <tr id="grammar-production-EOL" data-grammar-original="[8]  EOL                ::= [#xD#xA]+" data-grammar-expression="('+', ('[', '#xD#xA'))" class="grammar-token">
+    <td>[8]</td>
+    <td><code>EOL</code></td>
+    <td>::=</td>
+    <td>[<code class="grammar-chars">#xD#xA</code>]<code class="grammar-plus">+</code></td>
+</tr>
+            <tr id="grammar-production-WS" data-grammar-original="[9]  WS                 ::= [#x20#x9]" data-grammar-expression="('[', '#x20#x9')" class="grammar-token">
+    <td>[9]</td>
+    <td><code>WS</code></td>
+    <td>::=</td>
+    <td>[<code class="grammar-chars">#x20#x9</code>]</td>
+</tr>
+            <tr id="grammar-production-IRIREF" data-grammar-original="[10] IRIREF ::=  '<' ([^#x00-#x20<>&quot;{}|^`\] | UCHAR)* '>'" data-grammar-expression="(',', [(&quot;'&quot;, '<'), ('*', ('|', [('[', '^#x00-#x20<>&quot;{}|^`\\'), ('id', 'UCHAR')])), (&quot;'&quot;, '>')])" class="grammar-token">
+    <td>[10]</td>
+    <td><code>IRIREF</code></td>
+    <td>::=</td>
+    <td>'<code class="grammar-literal">&lt;</code>' ([<code class="grammar-chars">^#x00-#x20&lt;&gt;"{}|^`\</code>] <code>| </code> <a href="#grammar-production-UCHAR">UCHAR</a>)<code class="grammar-star">*</code> '<code class="grammar-literal">&gt;</code>'</td>
+</tr>
+            <tr id="grammar-production-STRING_LITERAL_QUOTE" data-grammar-original="[11] STRING_LITERAL_QUOTE ::= '&quot;' ( [^#x22#x5C#xA#xD] | ECHAR | UCHAR )* '&quot;'" data-grammar-expression="(',', [(&quot;'&quot;, '&quot;'), ('*', ('|', [('[', '^#x22#x5C#xA#xD'), ('id', 'ECHAR'), ('id', 'UCHAR')])), (&quot;'&quot;, '&quot;')])" class="grammar-token">
+    <td>[11]</td>
+    <td><code>STRING_LITERAL_QUOTE</code></td>
+    <td>::=</td>
+    <td>'<code class="grammar-literal">"</code>' ([<code class="grammar-chars">^#x22#x5C#xA#xD</code>] <code>| </code> <a href="#grammar-production-ECHAR">ECHAR</a> <code>| </code> <a href="#grammar-production-UCHAR">UCHAR</a>)<code class="grammar-star">*</code> '<code class="grammar-literal">"</code>'</td>
+</tr>
+            <tr id="grammar-production-BLANK_NODE_LABEL" data-grammar-original="[141s] BLANK_NODE_LABEL ::= '_:' ( PN_CHARS_U | [0-9] ) ((PN_CHARS|'.')* PN_CHARS)?" data-grammar-expression="(',', [(&quot;'&quot;, '_:'), ('|', [('id', 'PN_CHARS_U'), ('[', '0-9')]), ('?', (',', [('*', ('|', [('id', 'PN_CHARS'), (&quot;'&quot;, '.')])), ('id', 'PN_CHARS')]))])" class="grammar-token">
+    <td>[141s]</td>
+    <td><code>BLANK_NODE_LABEL</code></td>
+    <td>::=</td>
+    <td>'<code class="grammar-literal">_:</code>' (<a href="#grammar-production-PN_CHARS_U">PN_CHARS_U</a> <code>| </code> [<code class="grammar-chars">0-9</code>]) ((<a href="#grammar-production-PN_CHARS">PN_CHARS</a> <code>| </code> '<code class="grammar-literal">.</code>')<code class="grammar-star">*</code> <a href="#grammar-production-PN_CHARS">PN_CHARS</a>)?</td>
+</tr>
+            <tr id="grammar-production-UCHAR" data-grammar-original="[12] UCHAR ::= ( &quot;\u&quot; HEX HEX HEX HEX )| ( &quot;\U&quot; HEX HEX HEX HEX HEX HEX HEX HEX )" data-grammar-expression="('|', [(',', [(&quot;'&quot;, '\\u'), ('id', 'HEX'), ('id', 'HEX'), ('id', 'HEX'), ('id', 'HEX')]), (',', [(&quot;'&quot;, '\\U'), ('id', 'HEX'), ('id', 'HEX'), ('id', 'HEX'), ('id', 'HEX'), ('id', 'HEX'), ('id', 'HEX'), ('id', 'HEX'), ('id', 'HEX')])])" class="grammar-token">
+    <td>[12]</td>
+    <td><code>UCHAR</code></td>
+    <td>::=</td>
+    <td>'<code class="grammar-literal">\u</code>' <a href="#grammar-production-HEX">HEX</a> <a href="#grammar-production-HEX">HEX</a> <a href="#grammar-production-HEX">HEX</a> <a href="#grammar-production-HEX">HEX</a> <code>| </code> '<code class="grammar-literal">\U</code>' <a href="#grammar-production-HEX">HEX</a> <a href="#grammar-production-HEX">HEX</a> <a href="#grammar-production-HEX">HEX</a> <a href="#grammar-production-HEX">HEX</a> <a href="#grammar-production-HEX">HEX</a> <a href="#grammar-production-HEX">HEX</a> <a href="#grammar-production-HEX">HEX</a> <a href="#grammar-production-HEX">HEX</a></td>
+</tr>
+            <tr id="grammar-production-ECHAR" data-grammar-original="[153s] ECHAR ::= &quot;\&quot; [tbnrf&quot;']" data-grammar-expression="(',', [(&quot;'&quot;, '\\'), ('[', 'tbnrf&quot;\'')])" class="grammar-token">
+    <td>[153s]</td>
+    <td><code>ECHAR</code></td>
+    <td>::=</td>
+    <td>'<code class="grammar-literal">\</code>' [<code class="grammar-chars">tbnrf"'</code>]</td>
+</tr>
+            <tr id="grammar-production-PN_CHARS_BASE" data-grammar-original="[157s] PN_CHARS_BASE    ::= [A-Z]| [a-z]| [#x00C0-#x00D6]| [#x00D8-#x00F6]| [#x00F8-#x02FF]| [#x0370-#x037D]| [#x037F-#x1FFF]| [#x200C-#x200D]| [#x2070-#x218F]| [#x2C00-#x2FEF]| [#x3001-#xD7FF]| [#xF900-#xFDCF]| [#xFDF0-#xFFFD]| [#x10000-#xEFFFF]" data-grammar-expression="('|', [('[', 'A-Z'), ('[', 'a-z'), ('[', '#x00C0-#x00D6'), ('[', '#x00D8-#x00F6'), ('[', '#x00F8-#x02FF'), ('[', '#x0370-#x037D'), ('[', '#x037F-#x1FFF'), ('[', '#x200C-#x200D'), ('[', '#x2070-#x218F'), ('[', '#x2C00-#x2FEF'), ('[', '#x3001-#xD7FF'), ('[', '#xF900-#xFDCF'), ('[', '#xFDF0-#xFFFD'), ('[', '#x10000-#xEFFFF')])" class="grammar-token">
+    <td>[157s]</td>
+    <td><code>PN_CHARS_BASE</code></td>
+    <td>::=</td>
+    <td>[<code class="grammar-chars">A-Z</code>] <code>| </code> [<code class="grammar-chars">a-z</code>] <code>| </code> [<code class="grammar-chars">#x00C0-#x00D6</code>] <code>| </code> [<code class="grammar-chars">#x00D8-#x00F6</code>] <code>| </code> [<code class="grammar-chars">#x00F8-#x02FF</code>] <code>| </code> [<code class="grammar-chars">#x0370-#x037D</code>] <code>| </code> [<code class="grammar-chars">#x037F-#x1FFF</code>] <code>| </code> [<code class="grammar-chars">#x200C-#x200D</code>] <code>| </code> [<code class="grammar-chars">#x2070-#x218F</code>] <code>| </code> [<code class="grammar-chars">#x2C00-#x2FEF</code>] <code>| </code> [<code class="grammar-chars">#x3001-#xD7FF</code>] <code>| </code> [<code class="grammar-chars">#xF900-#xFDCF</code>] <code>| </code> [<code class="grammar-chars">#xFDF0-#xFFFD</code>] <code>| </code> [<code class="grammar-chars">#x10000-#xEFFFF</code>]</td>
+</tr>
+            <tr id="grammar-production-PN_CHARS_U" data-grammar-original="[158s] PN_CHARS_U       ::=  PN_CHARS_BASE| '_'| ':'" data-grammar-expression="('|', [('id', 'PN_CHARS_BASE'), (&quot;'&quot;, '_'), (&quot;'&quot;, ':')])" class="grammar-token">
+    <td>[158s]</td>
+    <td><code>PN_CHARS_U</code></td>
+    <td>::=</td>
+    <td><a href="#grammar-production-PN_CHARS_BASE">PN_CHARS_BASE</a> <code>| </code> '<code class="grammar-literal">_</code>' <code>| </code> '<code class="grammar-literal">:</code>'</td>
+</tr>
+            <tr id="grammar-production-PN_CHARS" data-grammar-original="[160s] PN_CHARS         ::= PN_CHARS_U| &quot;-&quot;| [0-9]| #x00B7| [#x0300-#x036F]| [#x203F-#x2040]" data-grammar-expression="('|', [('id', 'PN_CHARS_U'), (&quot;'&quot;, '-'), ('[', '0-9'), ('#', '#x00B7'), ('[', '#x0300-#x036F'), ('[', '#x203F-#x2040')])" class="grammar-token">
+    <td>[160s]</td>
+    <td><code>PN_CHARS</code></td>
+    <td>::=</td>
+    <td><a href="#grammar-production-PN_CHARS_U">PN_CHARS_U</a> <code>| </code> '<code class="grammar-literal">-</code>' <code>| </code> [<code class="grammar-chars">0-9</code>] <code>| </code> <code class="grammar-char-escape">#x00B7</code> <code>| </code> [<code class="grammar-chars">#x0300-#x036F</code>] <code>| </code> [<code class="grammar-chars">#x203F-#x2040</code>]</td>
+</tr>
+            <tr id="grammar-production-HEX" data-grammar-original="[162s] HEX              ::= [0-9] | [A-F] | [a-f]" data-grammar-expression="('|', [('[', '0-9'), ('[', 'A-F'), ('[', 'a-f')])" class="grammar-token">
+    <td>[162s]</td>
+    <td><code>HEX</code></td>
+    <td>::=</td>
+    <td>[<code class="grammar-chars">0-9</code>] <code>| </code> [<code class="grammar-chars">A-F</code>] <code>| </code> [<code class="grammar-chars">a-f</code>]</td>
+</tr>
+</tbody></table>
+</div>
+        </section>
+        <section id="sec-parsing">
+          <!--OddPage--><h2><span class="secno">6. </span>Parsing</h2>
+          <div class="issue"><div class="issue-title"><span>Issue 3</span></div><p class="">It may be simple, but should still be defined.</p></div>
+        </section>
+
+        <section id="sec-diff-turtle" class="appendix informative">
+          <!--OddPage--><h2><span class="secno">A. </span>Summary of diffrences in N-Triples and Turtle</h2><p><em>This section is non-normative.</em></p>
+          <section id="sec-triples">
+            <h3><span class="secno">A.1 </span>Triples</h3><p><em>This section is non-normative.</em></p>
+            <p>N-Triples only allows for <a href="#simple-triples">simple triple</a> statements which <em title="MUST NOT" class="rfc2119">MUST NOT</em> contain new lines. A single triple is always a single line of the document.</p>
+          </section>
+    <section id="iri-summary">
+      <h3><span class="secno">A.2 </span>IRI Representations</h3>
+
+      <table id="term2escape1" class="separated" style="border-collapse:collapse;margin: 2em;">
+        <thead>
+    <tr>
+      <th></th>
+      <th>Turtle</th>
+      <th>N-Triples</th>
+      <th>example</th>
+    </tr>
+        </thead>
+        <tbody>
+    <tr>
+      <td class="r">absolute IRI</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td><code>&lt;http://a.example/some/path/&gt;</code></td>
+    </tr>
+    <tr>
+      <td class="r">relative IRI</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td>no</td>
+      <td><code>&lt;/some/path/&gt;</code></td>
+    </tr>
+    <tr>
+      <td class="r">prefixed name</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td>no</td>
+      <td><code>rdfs:label</code></td>
+    </tr>
+    <tr>
+      <td class="r"><code>a</code> for the predicate <code>rdf:type</code></td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td>no</td>
+      <td><code>a</code></td>
+    </tr>
+        </tbody>
+      </table>
+        </section>
+
+    <section id="literal-summary">
+          <h3><span class="secno">A.3 </span>Literal Representations</h3>
+
+      <table id="term2escape2" class="separated" style="border-collapse:collapse;margin: 2em;">
+        <thead>
+    <tr>
+      <th></th>
+      <th>Turtle</th>
+      <th>N-Triples</th>
+      <th>example</th>
+    </tr>
+        </thead>
+        <tbody>
+    <tr>
+      <td class="r">single-quoted single-line lexical representation</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td>no</td>
+      <td><code>'some literal'</code></td>
+    </tr>
+    <tr>
+      <td class="r">double-quoted single-line lexical representation</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td><code>"some literal"</code></td>
+    </tr>
+    <tr>
+      <td class="r">single-quoted multi-line lexical representation</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td>no</td>
+      <td><code>'''some<br>literal'''</code></td>
+    </tr>
+    <tr>
+      <td class="r">double-quoted multi-line lexical representation</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td>no</td>
+      <td><code>"""some<br>literal"""</code></td>
+    </tr>
+    <tr>
+      <td class="r">abbreviated numeric</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td>no</td>
+      <td><code>13</code></td>
+    </tr>
+    <tr>
+      <td class="r">abbreviated boolean</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td>no</td>
+      <td><code>true</code></td>
+    </tr>
+        </tbody>
+      </table>
+        </section>
+                <section id="bnode-summary">
+          <h3><span class="secno">A.4 </span>Summary of Blank Node Representations in N-Triples and Turtle</h3>
+
+      <table id="term2escape3" class="separated" style="border-collapse:collapse;margin: 2em;">
+        <thead>
+    <tr>
+      <th></th>
+      <th>Turtle</th>
+      <th>N-Triples</th>
+      <th>example</th>
+    </tr>
+        </thead>
+        <tbody>
+    <tr>
+      <td class="r">labeled blank node</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td><code>&lt;http://a.example/who#Alice&gt; &lt;http://xmlns.com/foaf/0.1/knows&gt; _:bob .</code></td>
+    </tr>
+    <tr>
+      <td class="r">anonymous node</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td>no</td>
+      <td><code>&lt;http://a.example/who#Alice&gt; foaf:knows [] .</code></td>
+    </tr>
+    <tr>
+      <td class="r">blank node property list</td>
+      <td style="background-color: green; border:1px solid black;">yes</td>
+      <td>no</td>
+      <td><code>&lt;http://a.example/who#Alice&gt; foaf:knows [ foaf:name "Bob" ] .</code></td>
+    </tr>
+        </tbody>
+      </table>
+        </section>
+      </section>
+
+
+<!-- END N-TRIPLES SPEC -->
+
+      <section id="sec-mediaReg-n-triples" class="appendix">
+        <!--OddPage--><h2><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>
+          <dt>See also:</dt>
+
+          <dd><a href="http://www.w3.org/2002/06/registering-mediatype">How to Register a Media Type for a <abbr title="World Wide Web Consortium">W3C</abbr> Specification</a></dd>
+          <dd><a href="http://www.w3.org/2001/tag/2002/0129-mime">Internet Media Type registration, consistency of use</a><br>TAG Finding 3 June 2002 (Revised 4 September 2002)</dd>
+        </dl>
+        <p>The Internet Media Type / MIME Type for N-Triples is "application/n-triples".</p>
+        <p>It is recommended that N-Triples files have the extension ".nt" (all lowercase) on all platforms.</p>
+
+        <p>It is recommended that N-Triples files stored on Macintosh HFS file systems be given a file type of "TEXT".</p>
+        <p>This information that follows will be submitted to the IESG for review, approval, and registration with IANA.</p>
+        <dl>
+          <dt>Type name:</dt>
+          <dd>application</dd>
+
+          <dt>Subtype name:</dt>
+          <dd>n-triples</dd>
+          <dt>Required parameters:</dt>
+          <dd>None</dd>
+          <dt>Optional parameters:</dt>
+          <dd>None</dd>
+
+          <dt>Encoding considerations:</dt>
+          <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 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 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 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 
+    as LATIN SMALL LETTER E WITH ACUTE).
+    <!-- (<code>foo:resum&#40751;code> and <code>f&#1086;&#1086;:resume&#769;</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 href="#bib-UNISEC" class="bibref">UNISEC</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>
+          <dd>There are no known interoperability issues.</dd>
+          <dt>Published specification:</dt>
+          <dd>This specification.</dd>
+          <dt>Applications which use this media type:</dt>
+
+          <dd>No widely deployed applications are known to use this media type. It may be used by some web services and clients consuming their data.</dd>
+          <dt>Additional information:</dt>
+          <dt>Magic number(s):</dt>
+          <dd>None.</dd>
+          <dt>File extension(s):</dt>
+          <dd>".nt"</dd>
+
+          <dt>Macintosh file type code(s):</dt>
+          <dd>"TEXT"</dd>
+          <dt>Person &amp; email address to contact for further information:</dt>
+
+          <dd>Eric Prud'hommeaux &lt;[email protected]&gt;</dd>
+          <dt>Intended usage:</dt>
+          <dd>COMMON</dd>
+          <dt>Restrictions on usage:</dt>
+          <dd>None</dd>
+          <dt>Author/Change controller:</dt>
+
+          <dd>The N-Triples specification is the product of the RDF WG. The <abbr title="World Wide Web Consortium">W3C</abbr> reserves change control over this specifications.</dd>
+        </dl>
+      </section>
+
+  
+
+<section class="appendix" id="references"><!--OddPage--><h2><span class="secno">C. </span>References</h2><section id="normative-references"><h3><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-EBNF-NOTATION">[EBNF-NOTATION]</dt><dd>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>Jan Grant; Dave Beckett. <a href="http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/"><cite>RDF Test Cases.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/">http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/</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-RFC3023">[RFC3023]</dt><dd>M. Murata; S. St.Laurent; D. Kohn. <a href="http://www.ietf.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a> January 2001. Internet RFC 3023. 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>T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic Syntax.</cite></a> January 2005. Internet RFC 3986. 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>M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs).</cite></a> January 2005. Internet RFC 3987. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a> 
+</dd><dt id="bib-TURTLE-TR">[TURTLE-TR]</dt><dd>Eric Prud'hommeaux; Gavin Carothers. <a href="http://www.w3.org/TR/2013/CR-turtle-20130219/"><cite>Turtle: Terse Triple Language</cite></a> 19 February 2013. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/2013/CR-turtle-20130219/">http://www.w3.org/TR/2013/CR-turtle-20130219/</a>
+</dd><dt id="bib-UNICODE">[UNICODE]</dt><dd>The Unicode Consortium. <a href="http://www.unicode.org/standard/versions/enumeratedversions.html"><cite>The Unicode Standard.</cite></a>. Defined by: The Unicode Standard, Version 6.2.0, (Mountain View, CA: The Unicode Consortium, 2012. ISBN 978-1-936213-07-8) , as updated from time to time by the publication of new versions URL: <a href="http://www.unicode.org/standard/versions/enumeratedversions.html">http://www.unicode.org/standard/versions/enumeratedversions.html</a> 
+</dd><dt id="bib-UTF-8">[UTF-8]</dt><dd>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"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-UNISEC">[UNISEC]</dt><dd>Mark Davis; Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations</cite></a> 4 August 2010. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
+</dd></dl></section></section></body></html>