Editorial changes in response to ISSUE-148
authorMarkus Lanthaler <mail@markus-lanthaler.com>
Mon, 16 Dec 2013 17:47:06 +0100
changeset 1611 3cde0ca96344
parent 1610 1766898feb84
child 1612 352c518db27d
Editorial changes in response to ISSUE-148

(IRIs do *not* always denote the same resource)
rdf-concepts/index.html
--- a/rdf-concepts/index.html	Mon Dec 16 17:05:09 2013 +0100
+++ b/rdf-concepts/index.html	Mon Dec 16 17:47:06 2013 +0100
@@ -231,61 +231,59 @@
     <h3>The Referent of an IRI</h3>
 
     <p>The <a>resource</a> <a title="denote">denoted</a> by an <a title="IRI">IRI</a>
-    is also called its <dfn>referent</dfn>. For some IRIs with particular
-    meanings, such as those identifying XSD datatypes, the referent is
-    fixed by this specification. For all other IRIs, what exactly is
-    denoted by any given IRI is not defined by this specification. Other
-    specifications may fix IRI referents, or apply other constraints on
-    what may be the referent of any IRI.</p>
+      is also called its <dfn>referent</dfn>. For some IRIs with particular
+      meanings, such as those identifying XSD datatypes, the referent is
+      fixed by this specification. For all other IRIs, what exactly is
+      denoted by any given IRI is not defined by this specification. Other
+      specifications may fix IRI referents, or apply other constraints on
+      what may be the referent of any IRI.</p>
 
     <p>Guidelines for determining the <a>referent</a> of an <a title="IRI">IRI</a> are
     provided in other documents, like
-    <em><a href="http://www.w3.org/TR/webarch/">Architecture of the
-    World Wide Web, Volume One</a></em> [[WEBARCH]] and
-    <em><a href="http://www.w3.org/TR/cooluris/">Cool URIs for the
-    Semantic Web</a></em> [[COOLURIS]].
-    A very brief, informal and partial account follows:</p>
+    <em><a href="http://www.w3.org/TR/webarch/">Architecture of the World Wide Web, Volume One</a></em> [[WEBARCH]]
+    and <em><a href="http://www.w3.org/TR/cooluris/">Cool URIs for the Semantic Web</a></em> [[COOLURIS]].
+    A very brief, informal, and partial account follows:</p>
 
     <ul>
-    <li>IRIs have global scope: Two different appearances of an IRI
-    <a>denote</a> the same <a>resource</a>.</li>
-
-    <li>By social convention, the
-    <a href="http://www.w3.org/TR/webarch/#uri-ownership">IRI owner</a>
-    [[WEBARCH]] gets to say what the intended (or usual)
-    referent of an <a title="IRI">IRI</a> is.  Applications and users need not
-    abide by this intended denotation, but there may be a loss of
-    interoperability with other applications and users if they do
-    not do so.</li>
+      <li>IRIs have global scope by design. Thus, two different appearances
+        of an IRI identify the same <a>resource</a>. RDF is based on this principle
+        and violations of it might lead to inconsistencies or interoperability problems.</li>
 
-    <li>The IRI owner can establish the intended <a>referent</a>
-    by means of a specification or other document that explains
-    what is denoted. For example, the
-    <a href="http://www.w3.org/TR/vocab-org/">Organization Ontology
-    document</a> [[VOCAB-ORG]] specifies the intended referents
-    of various IRIs that start with
-    <code>http://www.w3.org/ns/org#</code>.</li>
+      <li>By social convention, the
+        <a href="http://www.w3.org/TR/webarch/#uri-ownership">IRI owner</a>
+        [[WEBARCH]] gets to say what the intended (or usual)
+        referent of an <a title="IRI">IRI</a> is.  Applications and users need not
+        abide by this intended denotation, but there may be a loss of
+        interoperability with other applications and users if they do
+        not do so.</li>
 
-    <li>A good way of communicating the intended referent
-    is to set up the IRI so that it
-    <a href="http://www.w3.org/TR/webarch/#uri-dereference">dereferences</a>
-    [[WEBARCH]] to such a document.</li>
+      <li>The IRI owner can establish the intended <a>referent</a>
+        by means of a specification or other document that explains
+        what is denoted. For example, the
+        <a href="http://www.w3.org/TR/vocab-org/">Organization Ontology document</a> [[VOCAB-ORG]]
+        specifies the intended referents of various IRIs that start with
+        <code>http://www.w3.org/ns/org#</code>.</li>
 
-    <li>Such a document can, in fact, be an <a>RDF document</a>
-    that describes the denoted resource by means of
-    <a title="RDF statement">RDF statements</a>.</li>
+      <li>A good way of communicating the intended referent
+        is to set up the IRI so that it
+        <a href="http://www.w3.org/TR/webarch/#uri-dereference">dereferences</a> [[WEBARCH]]
+        to such a document.</li>
+
+      <li>Such a document can, in fact, be an <a>RDF document</a>
+        that describes the denoted resource by means of
+        <a title="RDF statement">RDF statements</a>.</li>
     </ul>
 
     <p>Perhaps the most important characteristic of <a title="IRI">IRIs</a>
-    in web architecture is that they can be
-    <a href="http://www.w3.org/TR/webarch/#uri-dereference">dereferenced</a>,
-    and hence serve as starting points for interactions with a remote server.
-    This specification is not concerned with such interactions.
-    It does not define an interaction model. It only treats IRIs as globally
-    unique identifiers in a graph data model that describes resources.
-    However, those interactions are critical to the concept of
-    <em><a href="http://www.w3.org/DesignIssues/LinkedData.html">Linked Data</a></em> [[LINKED-DATA]],
-    which makes use of the RDF data model and serialization formats.</p>
+      in web architecture is that they can be
+      <a href="http://www.w3.org/TR/webarch/#uri-dereference">dereferenced</a>,
+      and hence serve as starting points for interactions with a remote server.
+      This specification is not concerned with such interactions.
+      It does not define an interaction model. It only treats IRIs as globally
+      unique identifiers in a graph data model that describes resources.
+      However, those interactions are critical to the concept of
+      <em><a href="http://www.w3.org/DesignIssues/LinkedData.html">Linked Data</a></em> [[LINKED-DATA]],
+      which makes use of the RDF data model and serialization formats.</p>
 </section>
 
 <section id="vocabularies">
@@ -1319,7 +1317,7 @@
   <h2>Acknowledgments</h2>
 
   <p>The editors acknowledge valuable contributions from Thomas Baker,
-    Tim Berners-Lee, Dan Brickley, Gavin Carothers, Jeremy Carroll,
+    Tim Berners-Lee, David Booth, Dan Brickley, Gavin Carothers, Jeremy Carroll,
     Pierre-Antoine Champin, Dan Connolly, John Cowan, Martin J. Dürst,
     Alex Hall, Steve Harris, Pat Hayes, Ivan Herman, Peter F. Patel-Schneider,
     Addison Phillips, Eric Prud'hommeaux, Andy Seaborne, Leif Halvard Silli,
@@ -1356,6 +1354,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-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>
     <li>2013-12-16: Make <code>rdf:HTML</code> and <code>rdf:XMLLiteral</code> non-normative</li>
     <li>2013-12-16: Update acknowledgments</li>
     <li>2013-12-12: Editorial changes in response to a review by