--- a/people/index.html Sun Jan 29 15:32:23 2012 +0000
+++ b/people/index.html Sun Jan 29 15:38:20 2012 +0000
@@ -46,8 +46,9 @@
<p class="editorsnote">@@TODO: link to the definition of source data in the <a href="https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html">BP document</a></p>
<p>Note: if you're not familiar with people's names throughout the world, you might want to read the <a href="http://www.w3.org/International/questions/qa-personal-names" title="Personal names around the world">personal names around the world</a> article provided by the W3C Internationalization (I18n) Activity.</p>
<div class="fig"><img src="img/people-example.png" alt="GLD people example" /><div>A visual representation of the walkthrough example as a graph (<a href="img/people-example-big.png">big version</a>).</div></div>
-<p>Note that RDF serialisations examples in this document are written in the Turtle [[TURTLE]] syntax.</p>
-<p>The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this specification are to be interpreted as described in RFC 2119 [[!RFC2119]].
+<p>Note that RDF serialisation examples in this document are written in the Turtle [[TURTLE]] syntax.</p>
+<p>The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this specification are to be interpreted as described in RFC 2119 [[!RFC2119]].</p>
+<p class="editorsnote">@@TODO: define publisher and consumer roles.</p>
</section>
<section>
@@ -61,13 +62,13 @@
<p>How to provide further details about a person, such as an address, is specified in section <a href="#relations-to-contact-info">relating a person to a contact information</a>.
<div class="practice">
<p><span id="sample-practice" class="practicelab">Deriving domain-specific person types</span></p>
- <p class="practicedesc">One sometimes finds specialisations of a person in a domain, for example, in the legal domain there is a distinction made between a natural person and a legal person. In such a case one should, in addition to the domain-specific type (e.g., <code>legal:NaturalPerson</code>) explicitly set the type <code>foaf:Person</code> in order to increase interoperability. This also allow systems that do not perform reasoning, for example, plain SPARQL processors to benefit from it. <a href="http://answers.semanticweb.com/questions/13715/owl-subclassing-vs-new-properties-for-existing-classes" title="OWL subclassing vs new properties for existing classes - ANSWERS">Read more ...</a></p>
+ <p class="practicedesc">One sometimes finds specialisations of a person in a domain, for example, in the legal domain there is a distinction made between a natural person and a legal person. In such a case the publisher should, in addition to the domain-specific type (e.g., <code>legal:NaturalPerson</code>) explicitly set the type <code>foaf:Person</code> in order to increase interoperability. This also allow systems that do not perform reasoning, for example, plain SPARQL processors to benefit from it. <a href="http://answers.semanticweb.com/questions/13715/owl-subclassing-vs-new-properties-for-existing-classes" title="OWL subclassing vs new properties for existing classes - ANSWERS">Read more ...</a></p>
</div>
</section>
<section>
-<h2 id="relations">Relating people</h2>
-<p>Beyond stating the basic characteristics of a person one can relate a person to a <dfn>target entity</dfn> such as an organisation or project. The following sections normatively specify how to do this. For any target entity type not listed in the below sections one is free to use any appropriate vocabulary. See also the <a href="https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html#vocabulary-selection---boris">vocabulary selection</a> section of the <em>Best Practices for Publishing Linked Data</em> document for guidance on how to find and select such a vocabulary.</p>
+<h2 id="relations">Relating a person to other entities</h2>
+<p>Beyond stating the basic characteristics of a person one can relate a person to a <dfn>target entity</dfn> such as an organisation or project. The following sections normatively specify how to do this. For any target entity type not listed in the below sections the publisher is free to use any appropriate vocabulary. See also the <a href="https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html#vocabulary-selection---boris">vocabulary selection</a> section of the <em>Best Practices for Publishing Linked Data</em> document for guidance on how to find and select such a vocabulary.</p>
<p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/18">ISSUE-18</a></p>
<section>