--- a/rdf-turtle/index.html Fri Jun 10 16:32:45 2011 -0700
+++ b/rdf-turtle/index.html Fri Jun 10 16:40:36 2011 -0700
@@ -882,6 +882,142 @@
sections of the SPARQL query document [[RDF-SPARQL-QUERY]].
</p>
</section>
+
+
+ <section id="sec-mediaReg" class="appendix">
+ <h2>Internet Media Type, File Extension and Macintosh File Type (Normative)</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 W3C 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 Turtle is "text/turtle".</p>
+ <p>It is recommended that Turtle files have the extension ".ttl" (all lowercase) on all platforms.</p>
+
+ <p>It is recommended that Turtle files stored on Macintosh HFS file systems be given a file type of "TEXT".</p>
+ <p>This information that follows has been <a href="http://www.w3.org/mid/20071218114549.GQ8244@w3.org">submitted to the IESG</a> for review, approval, and registration with IANA.</p>
+ <dl>
+ <dt>Type name:</dt>
+ <dd>text</dd>
+
+ <dt>Subtype name:</dt>
+ <dd>turtle</dd>
+ <dt>Required parameters:</dt>
+ <dd>None</dd>
+ <dt>Optional parameters:</dt>
+ <dd><tt>charset</tt> — this parameter is required when transferring non-ASCII data. If present, the value of <tt>charset</tt> is always <tt>UTF-8</tt>.</dd>
+
+ <dt>Encoding considerations:</dt>
+ <dd>The syntax of Turtle is expressed over code points in Unicode [<a href="#UNICODE">UNICODE</a>]. The encoding is always UTF-8 [<a href="#rfc3629">RFC3629</a>].</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>Turtle is a general-purpose assertion language; applications may evaluate given data to infer more assertions or to dereference URIs, invoking the security considerations of the scheme for that URI. Note in particular, the privacy issues in [<a href="#rfc3023">RFC3023</a>] section 10 for HTTP URIs. Data obtained from an inaccurate or malicious data source may lead to inaccurate or misleading conclusions, as well as the dereferencing of unintended URIs. 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>Turtle 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 Turtle documents. Security/privacy protocols must be imposed which reflect the sensitivity of the embedded information.</dd>
+ <dd>Turtle can express data which is presented to the user, for example, RDF Schema labels. Application rendering strings retrieved from untrusted Turtle documents must ensure that malignant strings may not be used to mislead the reader. The security considerations in the media type registration for XML ([RFC3023] section 10) provide additional guidance around the expression of arbitrary data and markup.</dd>
+ <dd>Turtle uses IRIs as term identifiers. Applications interpreting data expressed in Turtle should address the security issues of
+ <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [<a href="#rfc3987">RFC3987</a>] Section 8, as well as
+ <a class="norm" href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifier (URI): Generic Syntax</a> [<a href="#rfc3986">RFC3986</a>] 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鼯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> [<a href="#UNISEC">UNISEC</a>] and
+ <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource
+ Identifiers (IRIs)</a> [<a href="#rfc3987">RFC3987</a>] Section 8.
+
+ <!--@@ no security considerations section at this time. @@
+ See Turtle - Terse RDF Triple Language appendix X, <a href="#security">Security Considerations</a>
+ as well as <a class="norm" href="http://www.ietf.org/rfc/rfc3629.txt">RFC 3629</a>
+ [<a href="#rfc3629">RFC3629</a>] section 7, Security Considerations. --></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>Turtle documents may have the strings '@prefix' or '@base' (case dependent) near the beginning of the document.</dd>
+ <dt>File extension(s):</dt>
+ <dd>".ttl"</dd>
+
+ <dt>Base URI:</dt>
+ <dd>The Turtle '@base <IRIref>' term can change the current base URI for relative IRIrefs in the query language that are used sequentially later in the document.</dd>
+ <dt>Macintosh file type code(s):</dt>
+ <dd>"TEXT"</dd>
+ <dt>Person & email address to contact for further information:</dt>
+
+ <dd>Eric Prud'hommeaux <eric@w3.org></dd>
+ <dt>Intended usage:</dt>
+ <dd>COMMON</dd>
+ <dt>Restrictions on usage:</dt>
+ <dd>None</dd>
+ <dt>Author/Change controller:</dt>
+
+ <dd>The Turtle specification is the product of David Beckett and Tim Berners-Lee. A W3C Working Group may assume maintenance of this document; W3C reserves change control over this specifications.</dd>
+ </dl>
+ </section>
+
+
+ <section id="sec-acks" class="appendix">
+ <h2>Acknowledgements (Informative)</h2>
+
+ <p>This work was described in the paper
+ <a href="http://www.dajobe.org/2003/11/new-syntaxes-rdf/">New Syntaxes for RDF</a>
+ which discusses other RDF syntaxes and the background
+ to the Turtle (Submitted to WWW2004, referred to as <em>N-Triples
+ Plus</em> there).</p>
+
+ <p>This work was started during the
+ <a href="http://www.w3.org/2001/sw/Europe/">Semantic Web Advanced Development Europe (SWAD-Europe)</a>
+ project funded by the EU IST-7 programme IST-2001-34732 (2002-2004)
+ and further development supported by the
+ <a href="http://www.ilrt.bris.ac.uk/">Institute for Learning and Research Technology</a> at the <a href="http://www.bristol.ac.uk/">University of Bristol</a>, UK (2002-Sep 2005).
+ </p>
+
+ </section>
+ <section id="sec-changelog" class="appendix">
+ <h2>Changes (Informative)</h2>
+
+ <p>Changes since the last publication of this document
+ <a href="http://www.w3.org/TeamSubmission/2008/SUBM-turtle-20080114">W3C Turtle Submission 2008-01-14</a>
+ . See the
+ <a href="http://www.w3.org/TeamSubmission/2008/SUBM-turtle-20080114#sec-changelog">Previous changelog for further information</a>
+ </p>
+
+
+ <ul>
+
+ <li>Adopted three additional string syntaxes from SPARQL: <a href="#prod-turtle2-STRING_LITERAL2">STRING_LITERAL2</a>, <a href="#prod-turtle2-STRING_LITERAL_LONG1">STRING_LITERAL_LONG1</a>, <a href="#prod-turtle2-STRING_LITERAL_LONG2">STRING_LITERAL_LONG2</a></li>
+
+ <li>Adopted case-independent constants for XSD booleans <code>true</code> and <code>false</code>.</li>
+ <li>Adopted SPARQL's syntax for prefixed names (see <a href="../../../2009/sparql/docs/query-1.1/rq25#rPrefixedName">editor's draft</a>):
+ <ul>
+ <li>'.'s in names in all positions of a local name apart from the first or last, e.g. <code>ex:first.name</code>.</li>
+
+ <li>digits in the first character of the <a href="http://www.w3.org/TR/rdf-sparql-query/#rPN_LOCAL">PN_LOCAL</a> lexical token, e.g. <code>ex:7tm</code>.</li>
+ </ul></li>
+ <li>Made <a href="#sec-syntax">syntax section</a> normative.
+ <ul>
+ <li>adopted SPARQL's IRI resolution and prefix substitution text.</li>
+
+ <li>explicitly allowed re-use of the same prefix.</li>
+ </ul></li>
+ <li>Added <a href="#sec-grammar-parsing">parsing rules</a>.</li>
+ </ul>
+ </section>