Review up to 3.1.
--- a/ldpatch.html Fri Nov 21 15:09:30 2014 -0500
+++ b/ldpatch.html Fri Nov 21 15:17:52 2014 -0500
@@ -429,14 +429,14 @@
LD Patch allows <a class="internalDFN" href="#grammar-production-Var">var</a>iables in <a class="internalDFN" href="#grammar-production-subject">subject</a> and <a class="internalDFN" href="#grammar-production-predicate">predicate</a> positions.
</li>
<li>
- A variable MUST be <a title="bind">bound</a> prior to its first use in the LD Patch document, and its value is the last node to which it has been bound (in case it appears in several <a>Bind</a> statements).
+ The value of a <a class="internalDFN" href="#grammar-production-Var">var</a>iables is the last node to which it was bound (in case it appears in several <a>Bind</a> statements).
</li>
<li>
- <dfn id="blank-node-scoping">The scope of <a class="internalDFN" href="#grammar-production-BlankNode">Blank nodes</a> identifiers is the whole LD Patch document.</dfn> Hence several argument graphs can share the same blank nodes across statements.
+ <dfn id="blank-node-scoping">The scope of <a class="internalDFN" href="#grammar-production-BlankNode">Blank nodes</a> identifiers is the whole LD Patch document.</dfn> That means that <a title="argument graph">argument graphs</a> across statements all share the same blank nodes.
</li>
</ul>
<p>
-As IRIs and Literals have global scopes, such nodes in an <a>argument graph</a> represent the same resource as in the <a>target graph</a>. <a class="internalDFN" href="#grammar-production-BlankNode">Blank nodes</a>, on the other hand, pose a problem, as they have no global identifiers. Indeed, the scope of blank node identifiers is limited to the LD Patch document in which they appear. As a consequence, any blank node identifier appearing in an LD Patch document is understood to denote a <em>fresh</em> blank node, distinct from any node initially present in the <a>target graph</a>. Therefore blank node identifiers in LD Patch cannot interfere with pre-existing blank nodes in the <a>target graph</a>.
+ As IRIs and RDF Literals have global scopes, such nodes in an <a>argument graph</a> represent the same resource as in the <a>target graph</a>. Blank nodes, on the other hand, pose a problem, as they have no global identifiers. Indeed, the scope of blank node identifiers is limited to the LD Patch document in which they appear. As a consequence, any blank node identifier appearing in an LD Patch document is understood to denote a <em>fresh</em> blank node, distinct from any node initially present in the <a>target graph</a>. Therefore blank node identifiers in LD Patch cannot interfere with pre-existing blank nodes in the <a>target graph</a>.
</p>
<p>
However, LD Patch provides mechanisms to address those pre-existing blank nodes: <a>bind</a>ing a variable to a blank node reachable through a <a>path expression</a>, <a>cut</a>ting a whole tree made of blank nodes, or using <a>UpdateList</a> to deal with those blank nodes that constitute RDF collections. There are cases where those mechanisms will not be able to unambiguously address a given blank node, but those cases are deemed <a href="#pathological-graph">pathological</a>, and are out of the scope of this specification.