From 1bb7483ceaa5a665ac00aca849f9d5810b360817 Mon Sep 17 00:00:00 2001
From: Dominik Tomaszuk <ddooss@wp.pl>
Date: Mon, 13 Feb 2023 13:48:27 +0100
Subject: [PATCH 1/9] update example 26

add missing triple
---
 spec/index.html | 1 +
 1 file changed, 1 insertion(+)

diff --git a/spec/index.html b/spec/index.html
index 8519cc2..727283c 100644
--- a/spec/index.html
+++ b/spec/index.html
@@ -750,6 +750,7 @@ <h2>Examples</h2>
   <pre class="example turtle untested" data-transform="updateExample">
     <!--
     @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+    _:b0  :p2  :q2 .
     _:b0  rdf:first  1 ;
           rdf:rest   _:b1 .
     _:b1  rdf:first  _:b2 .

From 909621adeddc6979d5b3b1c17f26f0a6f2de7a45 Mon Sep 17 00:00:00 2001
From: Dominik Tomaszuk <ddooss@wp.pl>
Date: Mon, 13 Feb 2023 13:51:46 +0100
Subject: [PATCH 2/9] key word change

"may not" -> "must not"
---
 spec/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec/index.html b/spec/index.html
index 727283c..0ff887a 100644
--- a/spec/index.html
+++ b/spec/index.html
@@ -405,7 +405,7 @@ <h3>Quoted Literals</h3>
       </p>
 
       <p>'<code>\</code>' (<span class="codepoint">U+005C</span>)
-        may not appear in any quoted literal except as part of an escape sequence.
+        must not appear in any quoted literal except as part of an escape sequence.
         Other restrictions depend on the delimiter:</p>
 
       <ul>

From a5b3b22a70a23665a769ec23e798f062a9d0ca8c Mon Sep 17 00:00:00 2001
From: Dominik Tomaszuk <ddooss@wp.pl>
Date: Mon, 13 Feb 2023 13:55:52 +0100
Subject: [PATCH 3/9] update examples 24 and 26

add missing `@prefix`
---
 spec/index.html | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/spec/index.html b/spec/index.html
index 0ff887a..52d423e 100644
--- a/spec/index.html
+++ b/spec/index.html
@@ -727,6 +727,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 +751,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  :p2  :q2 .
     _:b0  rdf:first  1 ;
           rdf:rest   _:b1 .

From eee83fe22b35ea51a8aa634231cf3d77430c04de Mon Sep 17 00:00:00 2001
From: Dominik Tomaszuk <ddooss@wp.pl>
Date: Mon, 13 Feb 2023 14:04:52 +0100
Subject: [PATCH 4/9] typo

---
 spec/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec/index.html b/spec/index.html
index 52d423e..52be489 100644
--- a/spec/index.html
+++ b/spec/index.html
@@ -788,7 +788,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>

From c68e6313cb5ed740651056bd16888dea9f277697 Mon Sep 17 00:00:00 2001
From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Mon, 13 Feb 2023 10:09:44 -0800
Subject: [PATCH 5/9] Synchronize common files.

---
 spec/common/README.md         |  2 +-
 spec/common/local-biblio.js   | 10 ++++++++++
 spec/common/participants.html |  2 +-
 spec/common/participants.js   |  4 ++--
 4 files changed, 14 insertions(+), 4 deletions(-)

diff --git a/spec/common/README.md b/spec/common/README.md
index 674e6e3..4efc497 100644
--- a/spec/common/README.md
+++ b/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
diff --git a/spec/common/local-biblio.js b/spec/common/local-biblio.js
index 3f79dd5..16d7cea 100644
--- a/spec/common/local-biblio.js
+++ b/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"
+  },
 };
diff --git a/spec/common/participants.html b/spec/common/participants.html
index c6e85c3..4ee377e 100644
--- a/spec/common/participants.html
+++ b/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.
diff --git a/spec/common/participants.js b/spec/common/participants.js
index e8d486b..42d7c1e 100644
--- a/spec/common/participants.js
+++ b/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);
 }
 

From 4024306806575ea9b6116053e787eeafebde160d Mon Sep 17 00:00:00 2001
From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Mon, 13 Feb 2023 10:43:13 -0800
Subject: [PATCH 6/9] Change literal quote requirements described in #5.

---
 spec/index.html | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/spec/index.html b/spec/index.html
index 52be489..dce1bfa 100644
--- a/spec/index.html
+++ b/spec/index.html
@@ -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
@@ -1567,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>
 

From 55babcee493564ed2e615f1de72aa837105b4227 Mon Sep 17 00:00:00 2001
From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Mon, 13 Feb 2023 10:51:31 -0800
Subject: [PATCH 7/9] Fix typo reported in erratum 11.

---
 spec/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec/index.html b/spec/index.html
index dce1bfa..a225c6d 100644
--- a/spec/index.html
+++ b/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>

From 212162c492fd36852877abf5f17bf635d2c37bb1 Mon Sep 17 00:00:00 2001
From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Mon, 13 Feb 2023 10:53:38 -0800
Subject: [PATCH 8/9] may not => MUST NOT. (use in informative sectinos is
 fine).

---
 spec/index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/spec/index.html b/spec/index.html
index a225c6d..7a2b475 100644
--- a/spec/index.html
+++ b/spec/index.html
@@ -405,7 +405,7 @@ <h3>Quoted Literals</h3>
       </p>
 
       <p>'<code>\</code>' (<span class="codepoint">U+005C</span>)
-        must not appear in any quoted literal except as part of an escape sequence.
+        may not appear in any quoted literal except as part of an escape sequence.
         Other restrictions depend on the delimiter:</p>
 
       <ul>
@@ -1421,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>

From e5ed37494ae5042c7113f3f0c752db2c1f07896d Mon Sep 17 00:00:00 2001
From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Mon, 13 Feb 2023 10:57:36 -0800
Subject: [PATCH 9/9] No fix really necessary, but abbreviation for SPARQL is
 updated. This was reported in erratum 26.

---
 spec/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec/index.html b/spec/index.html
index 7a2b475..53f9757 100644
--- a/spec/index.html
+++ b/spec/index.html
@@ -772,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: