--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/people/WD-vocab-people-20120403/index.html Thu Mar 29 16:11:00 2012 +0100
@@ -0,0 +1,411 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.1//EN"
+ "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <title>Terms for describing people</title>
+ <meta name="description" content="Terms for describing people" />
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+ <script type="text/javascript"src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+ <script src="respec-ref.js"></script>
+ <script src="respec-config.js"></script>
+ <link rel="stylesheet" type="text/css" href="local-style.css" />
+</head>
+<body>
+
+
+<section id="abstract">
+<p>
+This document defines a set of terms for describing people. It defines how to describe people's characteristics such as names or addresses and how to relate people to other things, for example to organizations or projects. For each term, guidance on the usage within a running example is provided. This document also defines mappings to widely used vocabularies to enable interoperability.
+</p>
+</section>
+
+<section id="sotd">
+ <p>This document is work in progress. You might also want to check the accompanying <a href="http://www.w3.org/2011/gld/wiki/Terms_for_describing_people">Wiki page</a> of the GLD Working Group for ongoing discussions.</p>
+</section>
+
+
+<section class="introductory">
+<h2>Scope</h2>
+<p>
+This document is aimed at both publishers and consumers of Linked Data. We assume that the reader has a certain familiarity with RDF and RDF Schema as well as well-known vocabularies, such as FOAF or Dublin Core. The goal of the document is to specify an interoperable way to describe people and their relationships to other entities such as organisations or projects.
+</p>
+</section>
+
+<section class='informative'>
+<h2 id="intro">Introduction</h2>
+<section>
+<h3>Terminology</h3>
+<dl>
+ <dt><dfn>source data</dfn></dt>
+ <dd>Data from datastores such as RDBs or spreadsheets that acts as a source for the Linked Data publishing process.</dd>
+ <dt><dfn>publisher</dfn></dt>
+ <dd>A person or organization that exposes source data as Linked Data on the Web.</dd>
+ <dt><dfn>consumer</dfn></dt>
+ <dd>A person or agent that uses Linked Data from the Web.</dd>
+</dl>
+<p class="editorsnote">@@TODO: point out definition of source data in the <a href="https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html">BP document</a> for further details.</p>
+</section>
+<section>
+<h3>Conventions</h3>
+<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>Examples of RDF serialisations in this document are written in the Turtle [[TURTLE]] syntax; we assume the following namespace prefix bindings unless otherwise stated:</p>
+<table class="simple" summary="list of prefixes used in the document">
+ <thead>
+ <tr><th>Prefix</th><th>IRI</th></tr>
+ <thead>
+ <tbody>
+ <tr><td><code>rdf:</code></td><td><pre>http://www.w3.org/1999/02/22-rdf-syntax-ns#</pre></td></tr>
+ <tr><td><code>rdfs:</code></td><td><pre>http://www.w3.org/2000/01/rdf-schema#</pre></td></tr>
+ <tr><td><code>dct:</code></td><td><pre>http://purl.org/dc/terms/</pre></td></tr>
+ <tr><td><code>xsd:</code></td><td><pre>http://www.w3.org/2001/XMLSchema#</pre></td></tr>
+ </tbody>
+</table>
+</section>
+<section>
+<h3>Walkthrough example</h3>
+<p>In many cases, <a title='source data'>source data</a> contains data about people and other, related entities. We will use the following text as an 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
+ point in the County of Santa Clara is Björk Guðmundsdóttir. To ensure a successful project delivery, Jane has
+ 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>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"><a href="img/people-example-big.png"><img src="img/people-example.png" alt="GLD people example" /></a><div>A visual representation of the walkthrough example as a graph (<a href="img/people-example-big.png">big version</a>).</div></div>
+</section>
+</section>
+
+<section class='informative'>
+<h2 id="ucr">Use Cases and requirements</h2>
+<p class="editorsnote">@@TODO: describe real world use cases and derive requirements common to all to decide what is and what is not in scope re target entities.</p>
+<!-- UC 1 -->
+<section>
+<h3 id="uc-find-politician">UC1 — Finding a politician</h3>
+<section>
+<h4>Scenario</h4>
+ <p>A <a title="publisher">publisher</a> wants to provide contact details for politicians, responsible for a certain region and/or topic.</p>
+ <p>Real-world example: <a href="http://www.writetothem.com/" title="WriteToThem - Email or fax your Councillor, MP, MEP, MSP or Welsh, NI, London Assembly Member for free">WriteToThem</a>.</p>
+</section>
+<section>
+<h4>Requirements</h4>
+ <ul>
+ <li>Contact details of politician, incl. name, address, email, phone number, fax number</li>
+ <li>Area of responsibility</li>
+ <li>Office location</li>
+ <li>Membership in a body (such as parliament, etc.)</li>
+ </ul>
+</section>
+</section>
+<!-- UC 2 -->
+<section>
+<h3 id="uc-spending">UC2 — Provide spending of local authority</h3>
+<section>
+<h4>Scenario</h4>
+ <p>A <a title="publisher">publisher</a> wants to provide an overview of how a local authority, such as a County Council, spends its money.</p>
+ <p>Real-world example: <a href="http://data.fingal.ie/ViewDataSets/Details/default.aspx?datasetID=375" title="Councillors Allowances and Expenses 2010">Councillors Allowances and Expenses 2010</a>, Fingal County Council, Ireland.</p>
+</section>
+<section>
+<h4>Requirements</h4>
+ <ul>
+ <li>Contact details of politician, incl. name, address, email, phone number, fax number</li>
+ <li>Membership in a body (such as parliament, etc.)</li>
+ <li>Expense, incl. type, event, amount</li>
+ </ul>
+</section>
+</section>
+<!-- UC 3 -->
+<section>
+<h3 id="uc-tender">UC3 — Public tenders</h3>
+<section>
+<h4>Scenario</h4>
+ <p>A <a title="publisher">publisher</a> wants to provide access to public tenders for transparency or accountability applications.</p>
+ <p>Real-world example: <a href="http://ted.europa.eu/" title="TED">Tenders Electronic Daily</a> by the European Union and it's Linked Open Data <a href="http://loted.eu" title="LOTED - Linked Open Tenders Electronic Daily">version</a>.</p>
+</section>
+<section>
+<h4>Requirements</h4>
+ <ul>
+ <li>Contact details of contracting authority</li>
+ <li>Object of the contract</li>
+ <li>Contract duration and conditions</li>
+ </ul>
+</section>
+</section>
+<!-- UC 4 -->
+<section>
+<h3 id="uc-awardedbids">UC4 — Awarded bids</h3>
+<section>
+<h4>Scenario</h4>
+ <p>A <a title="publisher">publisher</a> wants to provide a listing of awarded bids.</p>
+ <p>Real-world example: <a href="http://purchasing.alabama.gov/txt/awards.aspx" title="Alabama Department of Finance-Purchasing Division">Awarded Bids</a>, Alabama Department of Finance, USA.</p>
+</section>
+<section>
+<h4>Requirements</h4>
+ <ul>
+ <li>Contact details of contracting authority and buyer</li>
+ <li>Object of the contract</li>
+ <li>Action date</li>
+ </ul>
+</section>
+</section>
+<!-- UC 5 -->
+<section>
+<h3 id="uc-budgetpos">UC5 — Budget positions and salaries</h3>
+<section>
+<h4>Scenario</h4>
+ <p>A <a title="publisher">publisher</a> wants to inform about the budget positions along with salaries.</p>
+ <p>Real-world example: <a href="http://data.cityofchicago.org/Administration-Finance/Budget-Positions-and-Salaries-in-2011-Appropriatio/g398-fhbm" title="Budget - Positions and Salaries in 2011 Appropriation Ordinance | City of Chicago | Data Portal">Budget - Positions and Salaries in 2011 Appropriation Ordinance</a>, City of Chicago, USA.</p>
+</section>
+<section>
+<h4>Requirements</h4>
+ <ul>
+ <li>Department codes and details such as area of responsibility</li>
+ <li>Position, incl. title, assigned budget type, etc.</li>
+ <li>Amount</li>
+ </ul>
+</section>
+</section>
+<!-- UC 6 -->
+<section>
+<h3 id="uc-lobbying">UC6 — Lobbying activity</h3>
+<section>
+<h4>Scenario</h4>
+ <p>A <a title="publisher">publisher</a> wants to disclose lobbying activities.</p>
+ <p>Real-world example: <a href="http://www.data.ca.gov/dataset/lobbying-activity" title="Lobbying Activity | Data.ca.gov">Lobbying Activity</a>, State of California, USA.</p>
+</section>
+<section>
+<h4>Requirements</h4>
+ <ul>
+ <li>Contact details of individual lobbyists</li>
+ <li>Lobbyist relationships to companies, such as membership in a body, etc.</li>
+ </ul>
+</section>
+</section>
+<!-- UC 7 -->
+<section>
+<h3 id="uc-qa">UC7 — Question time archive</h3>
+<section>
+<h4>Scenario</h4>
+ <p>A <a title="publisher">publisher</a> wants to provide an archive of online question times for a certain topic and/or politician.</p>
+ <p>Real-world example: <a href="https://twitter.com/#!/search?q=%23AskNeelie">#AskNeelie</a> by Neelie Kroes, Vice President of the European Commission, Europe.</p>
+</section>
+<section>
+<h4>Requirements</h4>
+ <ul>
+ <li>Online handle of person who answers and people who ask questions</li>
+ <li>Topics via hashtags or indirect via question</li>
+ <li>Sequence of questions and answers such as follow-ups, etc.</li>
+ </ul>
+</section>
+</section>
+<section>
+<h3 id="uc-req">Requirements</h3>
+<table class="simple" summary="Use cases vs. requirements">
+ <thead>
+ <tr><th>Requirement</th><th><a href="#uc-find-politician">UC1</a></th><th><a href="#uc-spending">UC2</a></th><th><a href="#uc-tender">UC3</a></th><th><a href="#uc-awardedbids">UC4</a></th><th><a href="#uc-budgetpos">UC5</a></th><th><a href="#uc-lobbying">UC6</a></th><th><a href="#uc-qa">UC7</a></th></tr>
+ <thead>
+ <tbody>
+ <tr><td>Contact details</td><td>•</td><td>•</td><td>•</td><td>•</td><td>•</td><td>•</td><td></td></tr>
+ <tr><td>Area of responsibility</td><td>•</td><td></td><td></td><td></td><td>•</td><td></td><td></td></tr>
+ <tr><td>Location</td><td>•</td><td></td><td></td><td></td><td></td><td>•</td><td></td></tr>
+ <tr><td>Membership in body</td><td>•</td><td>•</td><td></td><td></td><td></td><td>•</td><td></td></tr>
+ <tr><td>Expense or budget type</td><td></td><td>•</td><td></td><td></td><td>•</td><td></td><td></td></tr>
+ <tr><td>Events</td><td></td><td>•</td><td>•</td><td>•</td><td></td><td>•</td><td>•</td></tr>
+ <tr><td>Amount</td><td></td><td>•</td><td>•</td><td>•</td><td>•</td><td></td><td></td></tr>
+ <tr><td>Object of contract</td><td></td><td></td><td>•</td><td>•</td><td></td><td></td><td></td></tr>
+ <tr><td>Online handle</td><td></td><td></td><td></td><td></td><td></td><td></td><td>•</td></tr>
+ <tr><td>Conversation topic</td><td></td><td></td><td></td><td></td><td></td><td></td><td>•</td></tr>
+ </tbody>
+</table>
+
+<p class="editorsnote">@@TODO: describe how we determine which requirements are common to all UC: for example, we could say that a requirement must at least show up in half of the UC, etc.</p>
+</section>
+</section>
+
+<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.</p>
+<pre class="example">
+ <http://data.sccgov.org/people/björkg> rdf:type foaf:Person ;
+ foaf:name "Björk Guðmundsdóttir" .
+</pre>
+<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="subclassing-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 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 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>
+<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:</p>
+<ol>
+ <li>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 <p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/22">ISSUE-22</a></p>
+ </li>
+ <li>the link type used between a person and a contact information MUST be <code><a href="#gldp-terms-card">gldp:card</a></code>. <p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/24">ISSUE-24</a></p></li>
+</ol>
+<pre class="example">
+ @prefix gldp: <http://www.w3.org/ns/people#> .
+ @prefix : <http://colcids.com/person/> .
+
+ :42 a foaf:Person ;
+ gldp:card :42#bc .
+
+ :42#bc a v:VCard ;
+ v:fn "Jane Doe" ;
+ ...
+</pre>
+
+</section>
+
+<section>
+<h3 id="relations-to-people">Relating a person to another person</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>
+ <li>To state other relationships between people, the <a href="http://vocab.org/relationship/" title="RELATIONSHIP: A vocabulary for describing relationships between people">RELATIONSHIP vocabulary</a> SHOULD be used.</li>
+</ul>
+<pre class="example">
+ <http://colcids.com/person/42> foaf:knows <http://opendataguru.net/me> .
+</pre>
+<div class="practice">
+ <p><span id="knows-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 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>
+<pre class="example">
+ <http://colcids.com/company> a org:FormalOrganization .
+
+ <http://colcids.com/person/42> a foaf:Person .
+
+ _:bn123 a org:Membership ;
+ org:organization <http://colcids.com/company> ;
+ org:member <http://colcids.com/person/42> .
+</pre>
+<p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/19">ISSUE-19</a></p>
+</section>
+
+<section>
+<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>To state that a person is located in a building or room <code><a href="http://vocab.deri.ie/rooms#occupant" title="Buildings and Rooms Vocabulary">rooms:occupant</a></code> MUST be used.</p>
+<pre class="example">
+ @prefix rooms: <http://vocab.deri.ie/rooms#> .
+ @prefix : <>.
+
+ <http://colcids.com/person/42> a foaf:Person .
+
+ :CCHQ a rooms:Building ;
+ rooms:contains :r101 .
+
+ :r101 a rooms:Room ;
+ rooms:occupant <http://colcids.com/person/42> .
+</pre>
+<p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/23">ISSUE-23</a></p>
+</section>
+
+<section>
+<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>
+<pre class="example">
+ @prefix gldp: <http://www.w3.org/ns/people#> .
+ @prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+ @prefix : <http://data.sccgov.org/project/> .
+
+ <http://data.sccgov.org/people/björkg> a foaf:Person .
+
+ :OpenData4SantaClara a foaf:Project ;
+ gldp:title "OpenData4SantaClara" ;
+ rdfs:label "OpenData4SantaClara" ;
+ gldp:lead <http://data.sccgov.org/people/björkg> ;
+ gldp:starts "2013-02-01T00:00:00Z"^^xsd:dateTime ;
+ gldp:ends "2013-05-01T00:00:00Z"^^xsd:dateTime .
+</pre>
+<div class="practice">
+ <p><span id="label-practice" class="practicelab">Multiple label properties</span></p>
+ <p class="practicedesc">In order to enable generic Linked Data browsers, such as <a href="https://github.com/linkeddata/tabulator">Tabulator</a>, which typically hard-code well-known label terms to display human readable labels rather than URIs, one SHOULD repeat the content of the <code>gldp:title</code>'s literal object in an <code>rdfs:label</code> literal object.</p>
+</div>
+
+<p class="editorsnote"><a href="https://www.w3.org/2011/gld/track/issues/20">ISSUE-20</a></p>
+</section>
+
+<section>
+<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>
+<pre class="example">
+ @prefix sioc: <http://rdfs.org/sioc/ns#> .
+
+ <http://blog.colcids.com/2012/12/01/launching-opendata4santaclara/> a sioc:Post ;
+ dct:title "OpenData4SantaClara will launch in early 2013" ;
+ dct:created "2012-12-01T17:25:30Z" ;
+ sioc:has_creator <http://colcids.com/person/42> .
+
+ <http://colcids.com/person/42> a sioc:User .
+</pre>
+</section>
+</section>
+
+<section>
+<h2 id="gldp-terms">Terms</h2>
+<p>This section defines terms that allow to relate a person 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> and 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 id="gldp-terms-card"><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 id="gldp-terms-ends"><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 project ends on date</em>.</td></tr>
+ <tr id="gldp-terms-lead"><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 id="gldp-terms-starts"><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 project starts on date</em>.</td></tr>
+ <tr id="gldp-terms-title"><td><code>gldp:title</code></td><td>Specifies the title of a <code>foaf:Project</code> as an <code><a href="http://www.w3.org/TR/xmlschema11-2/#string" title="W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes">xsd:string</a></code> [[!XMLSCHEMA2]]; read: <em>a projects has a title</em>.</td></tr>
+
+ </tbody>
+</table>
+</section>
+
+
+<section>
+<h2 id="i18y">Interoperability considerations</h2>
+<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">
+<h2>Acknowledgments</h2>
+<p>
+The Editor would like to thank the following people for their input and directions: Phil, Renato, George, Sandro, Richard.
+</p>
+</section>
+</body>
+</html>
\ No newline at end of file