extended I18Y with mappings
authorMichael Hausenblas http://sw-app.org/mic.xhtml#i
Sun, 29 Jan 2012 11:53:41 +0000
changeset 33 3d2c4748ca49
parent 32 d351f399f51e
child 34 d4770c304b68
extended I18Y with mappings
people/index.html
--- a/people/index.html	Sun Jan 29 11:11:09 2012 +0000
+++ b/people/index.html	Sun Jan 29 11:53:41 2012 +0000
@@ -53,7 +53,7 @@
 
 <section>
 <h2 id="characteristics">What is a person?</h2>
-<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>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 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>
@@ -105,16 +105,17 @@
 
 <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>
+<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>. The <a href="http://prefix.cc/gldp">preferred</a> namespace prefix for the namespace URI is <code>gldp</code>.</p>
+<p>An implementer of this spec MUST support the following terms:</p>
 <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>Specifies 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>
-		<tr><td><code>gldp:ends</code></td><td>Specifies the end 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>
+		<tr><td><code>gldp:card</code></td><td>Relates a <code>foaf:Person</code> to a <code>v:VCard</code>; read: <em>a person has a business card</em>.</td></tr>
+		<tr><td><code>gldp:ends</code></td><td>Specifies the end 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]]; read: <em>a projects ends on date</em>.</td></tr>
+		<tr><td><code>gldp:lead</code></td><td>Relates a <code>foaf:Project</code> to a <code>foaf:Person</code>; read: <em>a project has a project lead</em>.</td></tr>
+		<tr><td><code>gldp:starts</code></td><td>Specifies 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]]; read: <em>a projects start on date</em>.</td></tr>
 	</tbody>
 </table>
 </section>
@@ -122,8 +123,25 @@
 
 <section>
 <h2 id="i18y">Interoperability considerations</h2>
-<p class="editorsnote">@@TODO: describe how characteristics and relations should be mapped to other, widely deployed terms, such as Schema.org</p>
+<p>Our concept of a person is based on <code>foaf:Person</code>, but there are many more conceptualisations in use, for example as defined by the <em>Interoperability Solutions for European Public Administrations</em> (<a href="http://ec.europa.eu/isa/">ISA</a>) project, the <a href="http://schema.org/" title="Home - schema.org">Schema.org</a> project by the search engine providers Bing, Google, Yahoo! or as found in the Personal Information Model (PIMO) by the <a href="http://www.semanticdesktop.org/" title="Semantic Desktop">Semantic Desktop</a> project.</p>
+<p>To enable interoperability and, in general, to make the data more useful, we define mappings of terms, in the following. An implementer of this spec SHOULD support these mappings.</p> 
 <p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/21">ISSUE-21</a></p>
+
+<section>
+<h3>Mapping to ISA Core Person Vocabulary</h3>
+<p class="editorsnote">@@TODO: evaluate ISA <a href="http://joinup.ec.europa.eu/asset/core_person/description">Core Person Vocabulary</a> and identify how and what to map.</p>
+</section>
+
+<section>
+<h3>Mapping to Schema.org</h3>
+<p class="editorsnote">@@TODO: evaluate <a href="http://schema.org/Person">schema:Person</a> and identify how and what to map.</p>
+</section>
+
+<section>
+<h3>Mapping to Personal Information Model (PIMO)</h3>
+<p class="editorsnote">@@TODO: evaluate <a href="http://www.semanticdesktop.org/ontologies/pimo/#Person">pimo:Person</a> and identify how and what to map.</p>
+</section>
+
 </section>
 
 <section class="appendix">