Typos and minor changes

spec/common/README.md

@@ -7,4 +7,4 @@ This repository is meant to be used as a submodule in multiple repository holdin
 
 The `participants.js` Node script can be used to retrieve the list of working group participants. It requires an API Key.
 
-    node participants.js <apikey> wg/rdf-star > participantes.html
+    node participants.js <apikey> wg/rdf-star > participants.html

spec/common/local-biblio.js

@@ -285,4 +285,14 @@ var localBibliography = {
     "status": "WD",
     "publisher": "W3C"
   },
+  "CBD": {
+    "title": "CBD - Concise Bounded Description",
+    "href": "https://www.w3.org/Submission/CBD/",
+    "authors": [
+      "Patrick Stickler, Nokia"
+    ],
+    "rawDate": "2005-06-03",
+    "publisher": "W3C",
+    "status": "W3C Member Submission"
+  },
 };

spec/common/participants.html

@@ -1 +1 @@
-Members of the RDF-star Working Group Group included Adrian Gschwend, Andy Seaborne, Antoine Zimmermann, Dan Brickley, David Chaves-Fraga, Dominik Tomaszuk, Dörthe Arndt, Enrico Franconi, Fabien Gandon, Gregg Kellogg, Gregory Williams, Jesse Wright, Julián Arenas-Guerrero, Olaf Hartig, Ora Lassila, Pasquale Lisena, Peter Patel-Schneider, Pierre-Antoine Champin, Raphaël Troncy, Ruben Taelman, Rémi Ceres, Sarven Capadisli, Souripriya Das, Ted Thibodeau, and Timothée HAUDEBOURG.
+Members of the RDF-star Working Group Group included Adrian Gschwend, Andy Seaborne, Antoine Zimmermann, Dan Brickley, David Chaves-Fraga, Dominik Tomaszuk, Dörthe Arndt, Enrico Franconi, Fabien Gandon, Gregg Kellogg, Gregory Williams, Jesse Wright, Julián Arenas-Guerrero, Olaf Hartig, Ora Lassila, Pasquale Lisena, Peter Patel-Schneider, Pierre-Antoine Champin, Raphaël Troncy, Ruben Taelman, Rémi Ceres, Sarven Capadisli, Souripriya Das, Ted Thibodeau, and Timothée Haudebourg.

spec/common/participants.js

@@ -13,8 +13,8 @@ const process = require('process');
 const APIKEY = process.env.APIKEY || process.argv[2];
 const GROUP = process.env.GROUP || process.argv[3] || "wg/rdf-star";
 
-if (!APIKEY || !GROUP) {
-  console.error('Error: APIKEY and GROUP must be specified as either environment variables or command-line arguments.');
+if (!APIKEY) {
+  console.error('Error: APIKEY must be specified as either an environment variable or a command-line argument.');
   process.exit(1);
 }
 

spec/index.html

@@ -357,7 +357,7 @@ <h3>IRIs</h3>
     <div class="note">
       <p>The '<code>@prefix</code>' and '<code>@base</code>' directives
         require a trailing '<code>.</code>' after the IRI,
-        the equalivent '<code>PREFIX</code>' and '<code>BASE</code>'
+        the equivalent '<code>PREFIX</code>' and '<code>BASE</code>'
         must not have a trailing '<code>.</code>' after the IRI part of the directive.
     </div>
   </section>
@@ -410,13 +410,15 @@ <h3>Quoted Literals</h3>
 
       <ul>
         <li>Literals delimited by <code>'</code> (<span class="codepoint">U+0027</span>),
-          may not contain the characters <code>'</code>,
+          may not contain unescaped <code>'</code>,
           <code title="LINE FEED"><sub>LF</sub></code>(<span class="codepoint">U+000A</span>),
-          or <code title="CARRIAGE RETURN"><sub>CR</sub></code> (<span class="codepoint">U+000D</span>).</li>
-        <li>Literals delimited by <code>"</code>, may not contain the characters
+          or <code title="CARRIAGE RETURN"><sub>CR</sub></code> (<span class="codepoint">U+000D</span>)
+          characters.</li>
+        <li>Literals delimited by <code>"</code>, may not contain unescaped
           <code>"</code>,
           <code title="LINE FEED"><sub>LF</sub></code>,
-          or <code title="CARRIAGE RETURN"><sub>CR</sub></code>.</li>
+          or <code title="CARRIAGE RETURN"><sub>CR</sub></code>
+          characters.</li>
         <li>Literals delimited by <code>'''</code> may not contain the sequence of characters
           <code>'''</code>.</li>
         <li>Literals delimited by <code>"""</code> may not contain the sequence of characters
@@ -727,6 +729,7 @@ <h2>Examples</h2>
   <pre  class="example turtle untested" data-transform="updateExample">
     <!--
     @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+    @prefix : <http://example.org/stuff/1.0/>
     _:b0  rdf:first  1 ;
           rdf:rest   _:b1 .
     _:b1  rdf:first  2.0 ;
@@ -750,6 +753,8 @@ <h2>Examples</h2>
   <pre class="example turtle untested" data-transform="updateExample">
     <!--
     @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+    @prefix : <http://example.org/stuff/1.0/>
+    _:b0  :p2  :q2 .
     _:b0  rdf:first  1 ;
           rdf:rest   _:b1 .
     _:b1  rdf:first  _:b2 .
@@ -767,7 +772,7 @@ <h2>Examples</h2>
   <h3>Turtle compared to SPARQL</h3>
 
   <p>The [[[SPARQL12-QUERY]]]
-    (<abbr title="SPARQL Protocol And RDF Query Language">SPARQL</abbr>) [[SPARQL12-QUERY]]
+    (<abbr title="SPARQL 1.2 Query Language">SPARQL</abbr>) [[SPARQL12-QUERY]]
     uses a Turtle style syntax for its
     <a data-cite="SPARQL12-QUERY#rTriplesBlock">TriplesBlock production</a>.
     This production differs from the Turtle language in that:
@@ -785,7 +790,7 @@ <h3>Turtle compared to SPARQL</h3>
       (at the start of the SPARQL query).</li>
     <li>SPARQL uses case insensitive keywords, except for '<code>a</code>'.
       Turtle's <code>@prefix</code> and <code>@base</code> declarations are case sensitive,
-      the SPARQL dervied <code>PREFIX</code> and <code>BASE</code> are case insensitive.</li>
+      the SPARQL derived <code>PREFIX</code> and <code>BASE</code> are case insensitive.</li>
     <li>'<code>true</code>' and '<code>false</code>' are case insensitive in SPARQL
       and case sensitive in Turtle.
       <code>TrUe</code> is not a valid boolean value in Turtle.</li>
@@ -1416,7 +1421,7 @@ <h2>Internet Media Type, File Extension and Macintosh File Type</h2>
     <dd>Turtle 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 [[!RFC3023]] 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>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 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 MUST 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
       [[[!RFC3987]]] [[!RFC3987]] Section 8, as well as
       [[![RFC3986]]] [[!RFC3986]] Section 7.</dd>
@@ -1564,7 +1569,8 @@ <h2>Changes between Team Submission and RDF 1.1</h2>
   <h2>Changes between RDF 1.1 and RDF 1.2</h2>
 
   <ul>
-
+    <li>Update informative restrictions on included characters for `STRING_LITERAL_QUOTE`
+      and `STRING_LITERAL_SINGLE_QUOTE`.</li>
   </ul>
 </section>