--- a/people/index.html Sun Jan 29 09:40:49 2012 +0000
+++ b/people/index.html Sun Jan 29 10:38:09 2012 +0000
@@ -35,10 +35,10 @@
<p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/17">ISSUE-17</a></p>
-<section>
+<section class='informative'>
<h2 id="intro">Introduction</h2>
-<p>In many cases, source data (@@TODO: link to BP document and the definition of source data therein) contains data about people. We will use the following plain text example throughout the document to demonstrate the usage of terms:</p>
-<pre>
+<p>In many cases, <dfn title="Data from datastores such as RDBs or spreadsheets that acts as a source for the Linked Data publishing process.">source data</dfn> contains data about people. We will use the following plain text example throughout the document to demonstrate the usage of terms:</p>
+<pre class='example sh_html'>
Jane Doe is CEO of ColCids Inc., headquartered in 2242 Old Middlefield Way, Mountain View, CA, United States.
Recently, ColCids won a contract for providing an Open Data platform, awarded by the Santa Clara County. The
project, called OpenData4SantaClara, starts on 1 Feb 2013 and runs initially for three months. Jane's contact
@@ -46,26 +46,30 @@
invited 東海林賢蔵, a business contact and Open Data guru she recently met at a local event, to brief her and
the CoolCids team on the challenges and requirements in the domain.
</pre>
-
+<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. @@TODO: complete the graph.</div></div>
+<div class="fig"><img src="img/people-example.png" alt="GLD people example" /><div>A visual representation of the walkthrough example as a graph.</div></div>
</section>
<section>
<h2 id="characteristics">What is a person?</h2>
-<p>The core concept is that of a person, which is defined as an entity of type <code>foaf:Person</code>.</p>
-<p>@@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>
+<p>The core concept we are dealing with is that of a person, which is defined as an entity of type <code>foaf:Person</code>.</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>
+</div>
</section>
<section>
<h2 id="relations">Relating people</h2>
-<p>@@TODO: describe in which way people can be related to other entities such as other people, organisations, etc.</p>
+<p class="editorsnote">@@TODO: describe in which way people can be related to other entities such as other people, organisations, etc.</p>
<p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/18">ISSUE-18</a></p>
<section>
<h3 id="relations-to-contact-info">Relating a person to a contact information</h3>
<p>In order to relate a person to a contact information, such as typically found on a business card, 1. the contact information MUST be represented using <a href="http://www.w3.org/TR/vcard-rdf/" title="Representing vCard Objects in RDF">vCard</a>, and 2. the link type used between a person and a contact information MUST be <code>gldp:card</code>.</p>
-<p>@@TODO: define a term that relates a person to a vCard object, based on the semantics of <a href="http://open.vocab.org/docs/businessCard" title="ov:businessCard, a property in the OpenVocab RDF schema">ov:businessCard</a>.</p>
+<p class="editorsnote">@@TODO: define a term that relates a person to a vCard object, based on the semantics of <a href="http://open.vocab.org/docs/businessCard" title="ov:businessCard, a property in the OpenVocab RDF schema">ov:businessCard</a>.</p>
<p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/22">ISSUE-22</a></p>
</section>
@@ -96,23 +100,29 @@
<section>
<h2 id="gldp-terms">Terms</h2>
<p>This section defines terms that allow to relate people to other entities, such as contact information, etc. - the terms below are defined in the namespace URI <code>http://www.w3.org/ns/people#</code> with the preferred prefix <code>gldp:</code>.</p>
-<table class="def">
- <tr><th>Term</th><th>Definition</th></tr>
- <tr><td><code>gldp:card</code></td><td>Relates a <code>foaf:Person</code> to a <code>v:VCard</code>.</td></tr>
+<table class="simple">
+ <thead>
+ <tr><th>Term</th><th>Definition</th></tr>
+ </thead>
+ <tbody>
+ <tr><td><code>gldp:card</code></td><td>Relates a <code>foaf:Person</code> to a <code>v:VCard</code>.</td></tr>
+ <tr><td><code>gldp:lead</code></td><td>Relates a <code>foaf:Project</code> to a <code>foaf:Person</code>.</td></tr>
+ <tr><td><code>gldp:starts</code></td><td>Defines the start date of a <code>foaf:Project</code> as an <code><a href="http://www.w3.org/TR/xmlschema11-2/#dateTime" title="W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes">xsd:dateTime</a></code> [[!XMLSCHEMA2]] .</td></tr>
+ </tbody>
</table>
</section>
<section>
<h2 id="i18y">Interoperability considerations</h2>
-<p>@@TODO: describe how characteristics and relations should be mapped to other, widely deployed terms, such as Schema.org</p>
+<p class="editorsnote">@@TODO: describe how characteristics and relations should be mapped to other, widely deployed terms, such as Schema.org</p>
<p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/21">ISSUE-21</a></p>
</section>
<section class="appendix">
<h2>Acknowledgments</h2>
<p>
-The Editor would like to thank the following people for their input and directions: Phil, Renato, George, Sandro, etc.
+The Editor would like to thank the following people for their input and directions: Phil, Renato, George, Sandro, Richard, etc.
</p>
</section>
</body>