Replaced sub-section on prefixes with whole new section on comparing ld patch with turtle and sparql ldpatch
authorAlexandre Bertails <bertails@gmail.com>
Fri, 21 Nov 2014 01:18:14 -0500
branchldpatch
changeset 899 6d9fd90830da
parent 898 f76821641fca
child 900 17d919a48bfa
Replaced sub-section on prefixes with whole new section on comparing ld patch with turtle and sparql
ldpatch.html
--- a/ldpatch.html	Fri Nov 21 00:58:12 2014 -0500
+++ b/ldpatch.html	Fri Nov 21 01:18:14 2014 -0500
@@ -408,6 +408,8 @@
     </section>
 
 
+
+
     <section class='normative' id='semantics'>
       <h1>LD Patch Semantics</h1>
       <p>
@@ -415,19 +417,7 @@
       </p>
 
 
-      <section id="prefixes">
-        <h2><dfn>Prefixes</dfn></h2>
-        <p>
-<!-- @@ TODO should defer to Turtle's syntax. Not only Prefixes, but everything in http://www.w3.org/TR/2014/REC-turtle-20140225/#language-features. Proposed section name: Inherited from (the?) Turtle language. @@ -->
-An LD Patch document starts with a preamble that MAY contain a number of <code>@prefix</code> directives (similar to the <a href="http://www.w3.org/TR/turtle/#prefixed-name">same directive in Turtle</a> [[Turtle]]). They allow declaring a short prefix name for a long prefix of repeated IRIs. This is useful for many RDF vocabularies that are all defined in nearby namespace IRIs [[!rdf11-concepts]]. Note: the <code>@prefix</code> keyword is <em>case sensitive</em>.
-        </p>
-        <p>
-A prefix directive is defined by a prefix <var>p</var> and an IRI <var>ns</var>. Any further <a class="internalDFN" href="#grammar-production-PrefixedName">PrefixedName</a> in the LD Patch document whose <a class="internalDFN" href="#grammar-production-PNAME_NS">PNAME_NS</a> is <var>p</var> MUST be interpreted as the IRI formed by concatenating <var>ns</var> with the <a class="internalDFN" href="#grammar-production-PrefixedName">PrefixedName</a>'s <a class="internalDFN" href="#grammar-production-PN_LOCAL">PN_LOCAL</a>.
-        </p>
-        <p>
-For example, once the directive <code>@prefix foo: &lt;http://example.org/ns#&gt;</code> is defined, any <a class="internalDFN" href="#grammar-production-PrefixedName">PrefixedName</a> that starts with <code>foo:</code> can be interpreted as an IRI, <i>e.g.</i> <code>foo:bar</code> is a shorthand for the IRI <code>&lt;http://example.org/ns#bar&gt;</code>.
-        </p>
-      </section>
+
 
       <section id="node-matching-semantics">
         <h2><dfn>Nodes and triples Semantics</dfn></h2>
@@ -691,6 +681,24 @@
       </section>
     </section>
 
+
+
+    <section id="turtle-sparql-comparison">
+        <h1>LD Patch compared to Turtle and SPARQL</h1>
+        <p>
+            The LD Patch syntax uses a Turtle [[!Turtle]] style syntax for its <a class="internalDFN" href="#grammar-production-triples">triples</a> production. This production differs from the Turtle language in that the <a class="internalDFN" href="#grammar-production-subject">subject</a> and <a class="internalDFN" href="#grammar-production-predicate">predicate</a> production rules allow the use of variables.
+        </p>
+        <p>
+            LD Patch variables are restricted to the <a class="internalDFN" href="#grammar-production-VAR1">VAR1</a> production rule from SPARQL 1.1 [[!sparql11-query]], only allowing a trailing '<code>?</code>'.
+        </p>
+        <p>
+            Finally, the prefix directive is restricted to the <a class="internalDFN" href="#grammar-production-prefixID">prefixID</a> production rule in Turtle [[!Turtle]], only allowing <code>@prefix</code>. 
+        </p>
+
+    </section>
+
+
+
     <section id='concrete-syntax'>
       <h1>Concrete Syntax</h1>