Minor editorial changes in response to a review by Pat Hayes
authorMarkus Lanthaler <mail@markus-lanthaler.com>
Tue, 17 Dec 2013 18:22:43 +0100
changeset 1620 e7714e56114b
parent 1619 dd3f142d523b
child 1621 3b723ff82954
Minor editorial changes in response to a review by Pat Hayes

See http://lists.w3.org/Archives/Public/public-rdf-wg/2013Dec/0225.html
rdf-concepts/index.html
--- a/rdf-concepts/index.html	Tue Dec 17 17:14:48 2013 +0100
+++ b/rdf-concepts/index.html	Tue Dec 17 18:22:43 2013 +0100
@@ -219,11 +219,10 @@
     expressed in RDF</a> [[SWBP-N-ARYRELATIONS]].)</p>
 
     <p>Unlike <a title="IRI">IRIs</a> and <a title="literal">literals</a>,
-    <a title="blank node">blank nodes</a> do not denote specific
-    <a title="resource">resources</a>.
-    <a title="RDF statement">Statements</a> involving
-    blank nodes say that something with the given
-    relationships exists, without explicitly naming it.</p>
+      <a title="blank node">blank nodes</a> do not identify specific
+      <a title="resource">resources</a>. <a title="RDF statement">Statements</a>
+      involving blank nodes say that something with the given relationships
+      exists, without explicitly naming it.</p>
 </section>
 
 
@@ -329,10 +328,8 @@
 <section id="change-over-time">
     <h2>RDF and Change Over Time</h2>
 
-    <p>The RDF data model is <em>atemporal</em>: It does not deal with time,
-    and does not have a built-in notion of temporal validity of information.
-    <a title="RDF graph">RDF graphs</a> are static snapshots of
-    information.</p>
+    <p>The RDF data model is <em>atemporal</em>: <a title="RDF graph">RDF graphs</a>
+      are static snapshots of information.</p>
 
     <p>However, <a title="RDF graph">RDF graphs</a> can express information
     about events and about temporal aspects of other entities,
@@ -794,39 +791,39 @@
     <h2>RDF Datasets</h2>
 
     <p>An <dfn>RDF dataset</dfn> is a collection of
-    <a title="RDF graph">RDF graphs</a>, and comprises:</p>
+      <a title="RDF graph">RDF graphs</a>, and comprises:</p>
 
     <ul>
-    <li>Exactly one <dfn>default graph</dfn>, being an <a>RDF graph</a>.
-    The default graph does not have a name and MAY be empty.</li>
-    <li>Zero or more <dfn title="named graph">named graphs</dfn>.
-    Each named graph is a pair consisting of an <a title="IRI">IRI</a> or a blank node
-    (the <dfn>graph name</dfn>), and an <a>RDF graph</a>.
-    Graph names are unique within an RDF dataset.</li>
+      <li>Exactly one <dfn>default graph</dfn>, being an <a>RDF graph</a>.
+        The default graph does not have a name and MAY be empty.</li>
+      <li>Zero or more <dfn title="named graph">named graphs</dfn>.
+        Each named graph is a pair consisting of an <a title="IRI">IRI</a> or a blank node
+        (the <dfn>graph name</dfn>), and an <a>RDF graph</a>.
+        Graph names are unique within an RDF dataset.</li>
     </ul>
 
-    <p><a title="blank node">Blank nodes</a> MAY be shared between graphs
-    in an <a title="RDF Dataset">RDF dataset</a>.</p>
+    <p><a title="blank node">Blank nodes</a> can be be shared between graphs
+      in an <a title="RDF Dataset">RDF dataset</a>.</p>
 
     <div class="note" id="note-datasets">
-    <p>Despite the use of the word “name”
-    in “<a>named graph</a>”, the <a>graph name</a> does not formally
-    <a>denote</a> the graph. It is merely syntactically paired with
-    the graph. RDF does not place any formal restrictions on what
-    <a>resource</a> the graph name may denote, nor on the relationship between
-    that resource and the graph.</p>
+      <p>Despite the use of the word “name” in “<a>named graph</a>”, the
+        <a>graph name</a> is not required to <a>denote</a> the graph. It is
+        merely syntactically paired with the graph. RDF does not place any
+        formal restrictions on what <a>resource</a> the graph name may denote,
+        nor on the relationship between that resource and the graph.
+        A discussion of different RDF dataset semantics can be found in
+        [[RDF11-DATASETS]].</p>
 
-    <p>Some <a title="RDF Dataset">RDF dataset</a>
-    implementations do not track empty <a title="named graph">named graphs</a>.
-    Applications can avoid interoperability issues by not
-    ascribing importance to the presence or absence of empty named graphs.</p>
+      <p>Some <a title="RDF Dataset">RDF dataset</a> implementations do not
+        track empty <a title="named graph">named graphs</a>. Applications
+        can avoid interoperability issues by not ascribing importance to
+        the presence or absence of empty named graphs.</p>
 
-    <p>Blank nodes as graph names are new.  Existing SPARQL implementations
-      might not accept this new feature for some time, so the use of blank
-      nodes as graph names can cause interoperability problems.
-      <a href="#section-skolemization">Skolemizing</a> blank nodes used as
-      graph names can be used to overcome these interoperability problems.</p>
-
+      <p>Blank nodes as graph names are new.  Existing SPARQL implementations
+        might not accept this new feature for some time, so the use of blank
+        nodes as graph names can cause interoperability problems.
+        <a href="#section-skolemization">Skolemizing</a> blank nodes used as
+        graph names can be used to overcome these interoperability problems.</p>
     </div>
 
 <section id="section-dataset-isomorphism">
@@ -1349,6 +1346,8 @@
     <a href="http://www.w3.org/TR/2013/CR-rdf11-concepts-20131105/">5 November 2013 Candidate Recommendation (CR)</a>.</p>
 
   <ul>
+    <li>2013-12-17: Minor editorial changes in response to a review by
+      <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2013Dec/0225.html">Pat Hayes</a></li>
     <li>2013-12-17: Update SPARQL reference in the introduction</li>
     <li>2013-12-16: Minor editorial changes to <a href="#referents"></a> in response to a review by
       <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/2013Oct/0008.html">David Booth</a></li>