Remove at risk text.\nRefined section on previous TriG\nNote in the media type registration the indicators 'base' and 'prefix', not @ forms.
authorAndy Seaborne <andy.seaborne@apache.org>
Wed, 16 Oct 2013 21:41:01 +0100
changeset 1147 9d66fe0b8d07
parent 1146 c295d75198e8
child 1148 2489ba87ebc5
Remove at risk text.\nRefined section on previous TriG\nNote in the media type registration the indicators 'base' and 'prefix', not @ forms.
trig/index.html
--- a/trig/index.html	Wed Oct 16 12:56:50 2013 -0400
+++ b/trig/index.html	Wed Oct 16 21:41:01 2013 +0100
@@ -526,83 +526,6 @@
 		  <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><code>GRAPH</code> keyword</b></p>
-              <p>In this version of TriG, but not previous versions, 
-                the keyword <code>GRAPH</code> 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
-                <code>GRAPH</code> 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 <code>PREFIX</code> and <code>BASE</code> 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 (
-              <code>{</code>...<code>}</code>).
-              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 
 <a href="http://www.w3.org/TR/turtle/">Turtle</a> grammar
@@ -837,7 +760,7 @@
         <section id="sec-differences" class="appendix informative">
       	<h2>Differences from Previous TriG</h2>
         <p>This section describes the main differences between TriG, as
-defined in this document, and earlier forms. 
+          defined in this document, and earlier forms. 
       	<ul>
           <li>Syntax is aligned to the 
             <a href="http://www.w3.org/TR/turtle/">Turtle</a> [[!turtle]] recommendation
@@ -852,8 +775,9 @@
             for that graph to be included in the resulting graph.
             Sections with the same label are combined by set union.</li>
           <li>Keywords <code>BASE</code>, 
-            <code>PREFIX</code> (see also [[!turtle]]) and 
-            <code>GRAPH</code> are introduced.
+            <code>PREFIX</code> as in [[!turtle]].</li>
+          <li>The optional <code>GRAPH</code> keyword is allowed to aid
+            SPARQL alignment.
   		</ul>
       </section>
       <section id="sec-mediaReg" class="appendix">
@@ -912,16 +836,19 @@
           <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>
+          <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>TriG documents may have the strings '@prefix' or '@base' (case dependent) near the beginning of the document.</dd>
+          <dd>TriG documents may have the strings 'prefix' or 'base' (case
+            independent) near the beginning of the document.</dd> 
           <dt>File extension(s):</dt>
           <dd>".trig"</dd>
 
           <dt>Base URI:</dt>
-          <dd>The TriG base directive can change the current base URI for relative IRIrefs in the language that are used sequentially later in the document.</dd>
+          <dd>The TriG base directive can change the current base URI
+            for relative IRIrefs in the language that are used sequentially
+            later in the document.</dd>
           <dt>Macintosh file type code(s):</dt>
           <dd>&quot;TEXT&quot;</dd>
           <dt>Person &amp; email address to contact for further information:</dt>