Use drafted 'at-risk' text from http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0138.html
authorAndy Seaborne <andy.seaborne@epimorphics.com>
Mon, 02 Sep 2013 13:51:19 +0100
changeset 1051 b64a69d83369
parent 1050 2e1337bac0a0
child 1052 7b73b80af7d2
Use drafted 'at-risk' text from http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0138.html
trig/index.html
--- a/trig/index.html	Sun Sep 01 14:57:47 2013 +0100
+++ b/trig/index.html	Mon Sep 02 13:51:19 2013 +0100
@@ -315,43 +315,10 @@
 		  <h2>TriG Grammar</h2>
 
 
-              <p>The RDF Working Group has included the following
-                features; these may be removed due to implementor feedback.
-              </p>
-
-              <p>Feedback, both positive and negative, is invited by 
-                sending email to mailing list 
-                <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>).</p>              
-
-              <div class="atrisk"><p class="atrisktext">Feature At Risk</p>
-                <p>The inclusion of the keyword <tt>GRAPH</tt> at the start
-                  of a named graph to align with SPARQL.
-                </p>
-                <p>Previous
-                  publications of Turtle and TriG 
-                  already included <tt>PREFIX</tt> and <tt>BASE</tt> keywords.
-                </p>
-              </div>
-
-              <div class="atrisk"><p class="atrisktext">Feature At Risk</p>
-            	<p>This grammar allows the default graph to be specified
-                  without requiring enclosing <tt>{</tt>...<tt>}</tt>.</p>
-                <p>This means a Turtle document is valid as a TriG document
-                  and describes an RDF dataset with a default graph
-                  containing the triples described, and no named graphs.
-                </p>
-              </div>
-
-
-          <p>A TriG document is a
-          Unicode[[!UNICODE]]
-          character string encoded in UTF-8.
-          Unicode characters only in the range U+0000 to U+10FFFF inclusive are
-          allowed.
+          <p>A TriG document is a Unicode[[!UNICODE]] character string
+            encoded in UTF-8. 
+            Unicode characters only in the range U+0000 to U+10FFFF inclusive are
+            allowed.
           </p>
           <section id="sec-grammar-ws">
             <h3>White Space</h3>
@@ -540,6 +507,83 @@
           </section>
 		  <section id="grammar-ebnf">
 			<h3>Grammar</h3>
+
+            <p>The RDF Working Group has included the following
+              features; these may be removed due to implementor feedback.
+            </p>
+
+            <p>Feedback, both positive and negative, is invited by 
+              sending email to mailing list 
+              <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>).</p>              
+
+            <div class="atrisk"><p class="atrisktext">Feature At Risk</p>
+
+              <p><b><tt>GRAPH</tt> keyword</b></p>
+              <p>In this version of TriG, but not previous versions, 
+                the keyword <tt>GRAPH</tt> may occur before graph
+                names, as specified in the grammar.
+              </p>
+              <p>
+                This feature aligns with the syntax of
+                SPARQL, specifically SPARQL Update,
+                so sections of a TriG document can be cut-and-pasted into SPARQL 
+                update requests, and people used to reading SPARQL can more
+                easily understand TriG documents.</p>
+              <p>
+                This keyword may cause a syntax error in older parsers, so its
+                use should be avoided until all likely TriG-consuming
+                systems have updated parsers.  Once updated parsers are 
+                widespread, the use of GRAPH keyword is suggested to 
+                provide alignment with SPARQL.</p>
+
+              <p>
+                This feature is marked as being "at risk", which means the Working Group 
+                seeks feedback from the community on whether to allow the
+                <tt>GRAPH</tt> keyword.  The group may remove this feature without 
+                publishing another Last Call Working Draft.  Users with a strong 
+                preference or with information which might influence the Working Group's 
+                decision whether to keep this feature are encouraged to send feedback.</p>
+              <p>Previous publications of Turtle and TriG 
+                already included <tt>PREFIX</tt> and <tt>BASE</tt> keywords.
+            </p>
+          </div>
+
+          <div class="atrisk"><p class="atrisktext">Feature At Risk</p>
+            <p><b>Unenclosed Triples</b></p>
+            <p>In this version of TriG, but not previous versions,
+              triples in the default graph are allowed to 
+              occur without requiring enclosing braces (
+              <tt>{</tt>...<tt>}</tt>).
+              outside of any curly braces. </p>
+            <p>
+              This 
+              feature is provided in order to align the TriG syntax with the SPARQL 
+              syntax, to allow for cut-and-paste and for easier TriG comprehension by 
+              people working with SPARQL.  It also makes TriG an extension of Turtle; 
+              a TriG file using bare triples and no named graphs is also a Turtle file 
+              (with the same semantics).
+            </p>
+            <p>
+              Bare triples will not be understood by some older TriG parsers, so their 
+              use should be avoided until all likely TriG-consuming systems have 
+              updated parsers.  Once updated parsers are widespread, the use of bare 
+              triples is suggested to provide alignment with SPARQL.
+            </p>
+            <p>
+              This feature is marked as being "at risk", which means the Working Group 
+              seeks feedback from the community on whether to allow bare triple in 
+              TriG.  The group might remove this feature without publishing another 
+              Last Call Working Draft.   Users with a strong preference or with 
+              information which might influence the Working Group's decision whether 
+              to keep this feature are encouraged to send feedback.
+            </p>
+          </div>
+
+          <hr/>
             
             <p>The <abbr title="Extended Backus–Naur Form">EBNF</abbr> used here is defined in XML 1.0
               [[!EBNF-NOTATION]]. Production labels consisting of a number and a final 'g' are unique to TriG. All Production labels consisting of only a number reference the production with that number in the Turtle grammar [[turtle]]. Production labels consisting of a number and a final 's', e.g. [<a href="http://www.w3.org/TR/sparql11-query/#rRDFLiteral"><span class="prodNo">60s</span></a>], reference the production with that number in the <a href="http://www.w3.org/TR/sparql11-query/#sparqlGrammar">SPARQL Query Language for RDF grammar</a> [[RDF-SPARQL-QUERY]].
@@ -610,8 +654,6 @@
 		</section>
         <section id="sec-parsing"> 
           <h2>Parsing</h2>
-          <p><small><tt>@@Not up to [email protected]@</tt></small></p>
-
           <p>The <a href="../rdf-concepts/index.html">RDF Concepts and Abstract Syntax</a> ([[!RDF-CONCEPTS]]) specification defines three types of <em>RDF Term</em>:
 
           <a href="../rdf-concepts/index.html#dfn-iri">IRIs</a>,
@@ -623,8 +665,7 @@
           This section maps a string conforming to the grammar in <a href="#sec-grammar-grammar" class="sectionRef"></a> to a set of triples by mapping strings matching productions and lexical tokens to RDF terms or their components (e.g. language tags, lexical forms of literals). Grammar productions change the parser state and emit triples.</p>
           <section id="sec-parsing-state">
           <h3>Parser State</h3>
-
-              <p>Parsing TriG requires a state of six items:</p>
+          <p>Parsing TriG requires a state of six items:</p>
 
               <ul>
                 <li id="baseURI">IRI <code class="dfn">baseURI</code> — When the <a href="#grammar-production-base">base production</a> is reached, the second rule argument, <code>IRIREF</code>, is the base URI used for relative IRI resolution <span class="testrefs">(test: <a href="tests/#base1">base1</a> <a href="tests/#base2">base2</a>)</span>.</li>
@@ -678,8 +719,8 @@
           <h3>RDF Triples Constructors</h3>
           <p><small>@@ formatting of references to grammar rules</small></p>
           <p><small>@@ first draft wording - needs refining</small></p>
-              <p>
-		        A TriG document defines an <a href="http://www.w3.org/TR/rdf11-concepts/#section-dataset"
+          <p>
+		    A TriG document defines an <a href="http://www.w3.org/TR/rdf11-concepts/#section-dataset"
                 >RDF Dataset</a> composed of one default graph and zero or
                 more named graphs. Each graph is composed of a set of 
                 <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-triple">RDF triple</a>s.
@@ -691,39 +732,39 @@
               <p style="padding-top:0; margin-top:0;">The state <code class="curGraph">curGraph</code> is
                 initially unset.</p>
               <p>
-                The grammar production starting <code>"<code class="grammar-literal">GRAPH</code>"</code> in
-                rule <code><a href="#grammar-production-block">block</a></code>
-                or the production <code>(iri | BlankNode) wrappedGraph</code>
+                The grammar production starting <tt>"GRAPH"</tt> in
+                rule <tt><a href="#grammar-production-block">block</a></tt>
+                or the production <tt>(iri | BlankNode) wrappedGraph</tt>
                 in rule 
-                <code><a href="#grammar-production-triplesOrGraph">triplesOrGraph</a></code>
+                <tt><a href="#grammar-production-triplesOrGraph">triplesOrGraph</a></tt>
                 set <code class="curGraph">curGraph</code> to the IRI or
                 blank node just matched.
               </p>
 
               <p>
-                The grammar production <code>wrappedGraph</code> in rule  <code><a href="#grammar-production-block">block</a></code>
+                The grammar production <tt>wrappedGraph</tt> in rule <tt><a href="#grammar-production-block">block</a></tt>
                 sets <code class="curGraph">curGraph</code> to be
                 undefined.
               </p>
 
               <p>
                 The grammar production 
-                <code>(iri | BlankNode) predicateObjectList '.'</code>
-                in rule  <code><a href="#grammar-production-triplesOrGraph">triplesOrGraph</a></code>
+                <tt>(iri | BlankNode) predicateObjectList '.'</tt>
+                in rule  <tt><a href="#grammar-production-triplesOrGraph">triplesOrGraph</a></tt>
                 sets <code class="curGraph">curGraph</code> to be
                 undefined.
               </p>
                   
-              <pre>
+              <p>
                 The grammar production in rule  
-                <code><a href="#grammar-production-triples2">triples2</a></code>
+                <tt><a href="#grammar-production-triples2">triples2</a></tt>
                 sets <code class="curGraph">curGraph</code> to be
                 undefined.
-              </pre>
+              </p>
 
               <p>
               Each RDF triple produced is added to 
-              <code class="curGraph">curGraph</code>
+              <code class="curGraph">curGraph</code>,
               or the default graph if 
               <code class="curGraph">curGraph</code> is not set at that
               point in the parsing process.