--- a/rdf-layers/index.html Wed May 02 10:14:56 2012 -0400
+++ b/rdf-layers/index.html Wed May 02 10:36:48 2012 -0400
@@ -259,7 +259,7 @@
following [Carroll], as one of the (name, graph) pairs in a
<a>dataset</a>.</p>
- <p>In practice, the term is used more loosely to refer to the
+ <p>In practice, the term is often used more loosely to refer to the
graph part of those pairs or to the slot part of the pairs in a
<a>graph store</a>. The text of <a
href="http://www.w3.org/TR/2012/WD-sparql11-update-20120105/">SPARQL
@@ -267,14 +267,20 @@
"This example copies triples from one named graph to another named
graph".</p>
- <p>We continue that practice, using "named graph" to refer to
- specific parts of <a>dataset</a>s and <a>graph
- store</a>s. Specifically, as we use the term, a named graph is the
- graph part of the (name, graph) pair in a dataset or the slot part
- of a (name, slot) pair in a graph store. Note that even in this
- loose usage, it would be incorrect to call the default graph of a
- dataset or its corresponding slot in a graph store (which is a
- layer) a "named graph".</p>
+ <p>In this document, we use the term "named graph" to refer to the
+ graph part of a (name, graph) pair in a dataset. Strictly
+ speaking, the graph is not itself "named" (or denoted) by the
+ name, it is only associated with that name in the dataset. Note
+ that the default graph of a dataset is not a "named graph", since
+ it is not associated with a name, although technically a graph
+ could be both a named graph and the default graph of a dataset.
+ Our usage of the term always involves a relationship to a dataset:
+ a graph can be a named graph in one dataset, the default graph in
+ another dataset, and neither in a third.</p>
+
+ <p>Eschewing common usage, we do not refer to the slot part of a
+ (name, graph) pair in a <a>graph store</a> as a "named graph",
+ instead calling it a "named layer" of that graph store.</p>
</section>