--- a/people/index.html Sun Jan 29 11:53:41 2012 +0000
+++ b/people/index.html Sun Jan 29 12:13:42 2012 +0000
@@ -54,10 +54,11 @@
<section>
<h2 id="characteristics">What is a person?</h2>
<p>The core concept we are dealing with in this document is that of a person. A <dfn>person</dfn> in the context of this specification is defined as an entity of type <code><a href="http://xmlns.com/foaf/spec/#term_Person" title="FOAF Vocabulary Specification">foaf:Person</a></code>.</p>
+<p>If only the person's name is known <code><a href="http://xmlns.com/foaf/spec/#term_name" title="FOAF Vocabulary Specification">foaf:name</a></code> MUST be used. 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>.</p>
<p class="editorsnote">@@TODO: describe a person's fundamental characteristics (@@TODO: evaluate ISA <a href="http://joinup.ec.europa.eu/asset/core_person/description">Core Person Vocabulary</a>).</p>
<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 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 enable greater interoperability and 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">More about this ...</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 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>
</div>
</section>
@@ -74,30 +75,37 @@
</section>
<section>
-<h3>Relating a person to other people</h3>
-<p>In order to relate a person to another person one MUST use the <a href="http://xmlns.com/foaf/spec/" title="FOAF Vocabulary Specification">FOAF Vocabulary Specification</a>.</p>
+<h3 id="relations-to-people">Relating a person to other people</h3>
+<p>In order to relate a person to another person one MUST use the <a href="http://xmlns.com/foaf/spec/" title="FOAF Vocabulary Specification">FOAF Vocabulary Specification</a>:</p>
+<ul>
+ <li>To state that one person knows another person, <code><a href="http://xmlns.com/foaf/spec/#term_knows" title="FOAF Vocabulary Specification">foaf:knows</a></code> MUST be used.</li>
+</ul>
+<div class="practice">
+ <p><span id="sample-practice" class="practicelab">Trusting people's relationships</span></p>
+ <p class="practicedesc">A <code>foaf:knows</code> only establishes an unidirectional claim that someone knows someone else. The relation SHOULD only be considered to be of a mutual nature if the other person sets a <code>foaf:knows</code> relation as well. <a href="http://redcatco.com/blog/communication/foaf-building-networks-with-a-friend-of-a-friend/" title="FOAF – Building Networks With a Friend of a Friend | redcatco blog">Read more ...</a></p>
+</div>
</section>
<section>
-<h3>Relating a person to an organization</h3>
+<h3 id="relations-to-org">Relating a person to an organization</h3>
<p>In order to relate a person to an organization one MUST use the <a href="http://www.w3.org/ns/org#">Organization Ontology</a>.</p>
<p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/19">ISSUE-19</a></p>
</section>
<section>
-<h3>Relating a person to a building or room</h3>
+<h3 id="relations-to-building-room">Relating a person to a building or room</h3>
<p>In order to relate a person to a building or room one MUST use the <a href="http://vocab.deri.ie/rooms#">Buildings and Rooms Vocabulary</a>.</p>
<p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/23">ISSUE-23</a></p>
</section>
<section>
-<h3>Relating a person to a project</h3>
+<h3 id="relations-to-project">Relating a person to a project</h3>
<p>In order to relate a person to a project one MUST use the <a href="http://xmlns.com/foaf/spec/" title="FOAF Vocabulary Specification">FOAF Vocabulary Specification</a>.</p>
<p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/20">ISSUE-20</a></p>
</section>
<section>
-<h3>Relating a person to online posts</h3>
+<h3 id="relations-to-contact-online-post">Relating a person to online posts</h3>
<p>In order to relate a person to online posts such as blog posts, mailing list posts, etc, one MUST use the <a href="http://www.w3.org/Submission/sioc-spec/" title="SIOC Core Ontology Specification">SIOC Core Ontology Specification</a>.</p>
</section>