--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/org/respec-config-cr.js Thu May 02 22:56:05 2013 +0100
@@ -0,0 +1,97 @@
+var respecConfig = {
+ // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+ specStatus: "CR",
+ publishDate: "2013-05-23",
+ //copyrightStart: "2010",
+ //lcEnd: "2013-04-08",
+
+ // the specification's short name, as in http://www.w3.org/TR/short-name/
+ shortName: "vocab-org",
+ //subtitle: "",
+ // if you wish the publication date to be other than today, set this
+ // publishDate: "2009-08-06",
+
+ // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+ // and its maturity status
+ previousPublishDate: "2012-10-23",
+ previousMaturity: "LC",
+ //previousDiffURI: "http://dvcs.w3.org/hg/gld/bp/",
+ //diffTool: "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
+
+ // if there a publicly available Editor's Draft, this is the link
+ edDraftURI: "http://dvcs.w3.org/hg/gld/raw-file/default/org/index.html",
+
+ // if this is a LCWD, uncomment and set the end of its review period
+ // lcEnd: "2009-08-05",
+
+ // if you want to have extra CSS, append them to this list
+ // it is recommended that the respec.css stylesheet be kept
+ extraCSS: [
+ "http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"
+ ],
+
+ // editors, add as many as you like
+ // only "name" is required
+ editors: [
+ { name: "Dave Reynolds", company: "Epimorphics Ltd.", companyURL: "http://www.epimorphics.com/" }
+ ],
+
+ // authors, add as many as you like.
+ // This is optional, uncomment if you have authors as well as editors.
+ // only "name" is required. Same format as editors.
+
+ //authors: [],
+
+ // name of the WG
+ wg: "Government Linked Data Working Group",
+
+ // URI of the public WG page
+ wgURI: "http://www.w3.org/2011/gld/",
+
+ // name of the public mailing to which comments are due
+ wgPublicList: "public-gld-wg",
+
+ // URI of the patent status for this WG, for Rec-track documents
+ // !!!! IMPORTANT !!!!
+ // This is important for Rec-track documents, do not copy a patent URI from a random
+ // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+ // Team Contact.
+ //wgPatentURI: "",
+ maxTocLevel: 3,
+ preProcess: [ preProc ]
+ //alternateFormats: [ {uri: "diff-20110507.html", label: "diff to previous version"} ],
+};
+
+function updateExample(doc, content) {
+ // perform transformations to make it render and prettier
+ content = content.replace(/<!--/, '');
+ content = content.replace(/-->/, '');
+ content = doc._esc(content);
+ content = content.replace(/\*\*\*\*([^*]*)\*\*\*\*/g, '<span class="diff">$1</span>') ;
+ return content ;
+}
+
+function updateDTD(doc, content) {
+ // perform transformations to
+ // make it render and prettier
+ content = '<pre class="dtd">' + doc._esc(content) + '</pre>';
+ content = content.replace(/!ENTITY % ([^ \t\r\n]*)/g, '!ENTITY <span class="entity">% $1</span>');
+ content = content.replace(/!ELEMENT ([^ \t$]*)/mg, '!ELEMENT <span class="element">$1</span>');
+ return content;
+}
+
+function updateSchema(doc, content) {
+ // perform transformations to
+ // make it render and prettier
+ content = '<pre class="dtd">' + doc._esc(content) + '</pre>';
+ content = content.replace(/<xs:element\s+name="([^&]*)"/g, '<xs:element name="<span class="element" id="schema_element_$1">$1</span>"') ;
+ return content;
+}
+
+function updateTTL(doc, content) {
+ // perform transformations to
+ // make it render and prettier
+ content = '<pre class="sh_sourceCode">' + doc._esc(content) + '</pre>';
+ content = content.replace(/@prefix/g, '<span class="sh_keyword">@prefix</span>');
+ return content;
+}
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/org/respec-config-current.js Thu May 02 22:56:05 2013 +0100
@@ -0,0 +1,97 @@
+var respecConfig = {
+ // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+ specStatus: "ED",
+ //publishDate: "2013-05-23",
+ //copyrightStart: "2010",
+ //lcEnd: "2013-04-08",
+
+ // the specification's short name, as in http://www.w3.org/TR/short-name/
+ shortName: "vocab-org",
+ //subtitle: "",
+ // if you wish the publication date to be other than today, set this
+ // publishDate: "2009-08-06",
+
+ // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+ // and its maturity status
+ previousPublishDate: "2012-10-23",
+ previousMaturity: "LC",
+ //previousDiffURI: "http://dvcs.w3.org/hg/gld/bp/",
+ //diffTool: "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
+
+ // if there a publicly available Editor's Draft, this is the link
+ edDraftURI: "https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html",
+
+ // if this is a LCWD, uncomment and set the end of its review period
+ // lcEnd: "2009-08-05",
+
+ // if you want to have extra CSS, append them to this list
+ // it is recommended that the respec.css stylesheet be kept
+ extraCSS: [
+ "http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"
+ ],
+
+ // editors, add as many as you like
+ // only "name" is required
+ editors: [
+ { name: "Dave Reynolds", company: "Epimorphics Ltd.", companyURL: "http://www.epimorphics.com/" }
+ ],
+
+ // authors, add as many as you like.
+ // This is optional, uncomment if you have authors as well as editors.
+ // only "name" is required. Same format as editors.
+
+ //authors: [],
+
+ // name of the WG
+ wg: "Government Linked Data Working Group",
+
+ // URI of the public WG page
+ wgURI: "http://www.w3.org/2011/gld/",
+
+ // name of the public mailing to which comments are due
+ wgPublicList: "public-gld-wg",
+
+ // URI of the patent status for this WG, for Rec-track documents
+ // !!!! IMPORTANT !!!!
+ // This is important for Rec-track documents, do not copy a patent URI from a random
+ // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+ // Team Contact.
+ //wgPatentURI: "",
+ maxTocLevel: 3,
+ preProcess: [ preProc ]
+ //alternateFormats: [ {uri: "diff-20110507.html", label: "diff to previous version"} ],
+};
+
+function updateExample(doc, content) {
+ // perform transformations to make it render and prettier
+ content = content.replace(/<!--/, '');
+ content = content.replace(/-->/, '');
+ content = doc._esc(content);
+ content = content.replace(/\*\*\*\*([^*]*)\*\*\*\*/g, '<span class="diff">$1</span>') ;
+ return content ;
+}
+
+function updateDTD(doc, content) {
+ // perform transformations to
+ // make it render and prettier
+ content = '<pre class="dtd">' + doc._esc(content) + '</pre>';
+ content = content.replace(/!ENTITY % ([^ \t\r\n]*)/g, '!ENTITY <span class="entity">% $1</span>');
+ content = content.replace(/!ELEMENT ([^ \t$]*)/mg, '!ELEMENT <span class="element">$1</span>');
+ return content;
+}
+
+function updateSchema(doc, content) {
+ // perform transformations to
+ // make it render and prettier
+ content = '<pre class="dtd">' + doc._esc(content) + '</pre>';
+ content = content.replace(/<xs:element\s+name="([^&]*)"/g, '<xs:element name="<span class="element" id="schema_element_$1">$1</span>"') ;
+ return content;
+}
+
+function updateTTL(doc, content) {
+ // perform transformations to
+ // make it render and prettier
+ content = '<pre class="sh_sourceCode">' + doc._esc(content) + '</pre>';
+ content = content.replace(/@prefix/g, '<span class="sh_keyword">@prefix</span>');
+ return content;
+}
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/org/static-cr.html Thu May 02 22:56:05 2013 +0100
@@ -0,0 +1,1975 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+ <title>An organization ontology</title>
+ <meta name="description" content="An organization ontology">
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+
+
+
+
+
+ <style type="text/css">
+ table {
+ border-collapse:collapse;
+ }
+ td, th {
+ border:1px solid black;
+ padding:1em;
+ }
+ table#namespaces td {
+ font-family: monospace;
+ }
+ table.definition {
+ width:100%;
+ }
+ table.definition td.prop {
+ width:10em;
+ }
+ pre {
+ padding: 1em;
+ border: 1px dashed #2f6fab;
+ color: black;
+ background-color: #f9f9f9;
+ line-height: 1.1em;
+ }
+ </style>
+<style>/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 {
+ text-transform: lowercase;
+ font-variant: small-caps;
+ font-style: normal;
+ color: #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+ border: none;
+}
+
+dfn {
+ font-weight: bold;
+}
+
+a.internalDFN {
+ color: inherit;
+ border-bottom: 1px solid #99c;
+ text-decoration: none;
+}
+
+a.externalDFN {
+ color: inherit;
+ border-bottom: 1px dotted #ccc;
+ text-decoration: none;
+}
+
+a.bibref {
+ text-decoration: none;
+}
+
+cite .bibref {
+ font-style: normal;
+}
+
+code {
+ color: #ff4500;
+}
+
+
+/* --- --- */
+ol.algorithm { counter-reset:numsection; list-style-type: none; }
+ol.algorithm li { margin: 0.5em 0; }
+ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
+
+/* --- TOC --- */
+.toc a, .tof a {
+ text-decoration: none;
+}
+
+a .secno, a .figno {
+ color: #000;
+}
+
+ul.tof, ol.tof {
+ list-style: none outside none;
+}
+
+.caption {
+ margin-top: 0.5em;
+ font-style: italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+ border-spacing: 0;
+ border-collapse: collapse;
+ border-bottom: 3px solid #005a9c;
+}
+
+.simple th {
+ background: #005a9c;
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+}
+
+.simple th[scope="row"] {
+ background: inherit;
+ color: inherit;
+ border-top: 1px solid #ddd;
+}
+
+.simple td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+ background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+ margin-top: 0;
+}
+
+.section dd > p:last-child {
+ margin-bottom: 0;
+}
+
+.section dd {
+ margin-bottom: 1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+ margin-bottom: 0;
+}
+</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-CR"><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+<body><div class="head">
+ <p>
+
+ <a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a>
+
+ </p>
+ <h1 class="title" id="title">An organization ontology</h1>
+
+ <h2 id="w3c-candidate-recommendation-23-may-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Candidate Recommendation 23 May 2013</h2>
+ <dl>
+
+ <dt>This version:</dt>
+ <dd><a href="http://www.w3.org/TR/2013/CR-vocab-org-20130523/">http://www.w3.org/TR/2013/CR-vocab-org-20130523/</a></dd>
+ <dt>Latest published version:</dt>
+ <dd><a href="http://www.w3.org/TR/vocab-org/">http://www.w3.org/TR/vocab-org/</a></dd>
+
+
+ <dt>Latest editor's draft:</dt>
+ <dd><a href="http://dvcs.w3.org/hg/gld/raw-file/default/org/index.html">http://dvcs.w3.org/hg/gld/raw-file/default/org/index.html</a></dd>
+
+
+
+
+
+ <dt>Previous version:</dt>
+ <dd><a href="http://www.w3.org/TR/2012/WD-vocab-org-20121023/">http://www.w3.org/TR/2012/WD-vocab-org-20121023/</a></dd>
+
+
+ <dt>Editor:</dt>
+ <dd><span>Dave Reynolds</span>, <a href="http://www.epimorphics.com/">Epimorphics Ltd.</a></dd>
+
+
+ </dl>
+
+
+
+
+
+ <p class="copyright">
+ <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
+ 2013
+
+ <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
+ (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
+ <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
+ <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved.
+ <abbr title="World Wide Web Consortium">W3C</abbr> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
+ <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
+ <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
+ </p>
+
+
+ <hr>
+</div>
+
+<section id="abstract" class="introductory"><h2>Abstract</h2>
+
+<p> This document describes a core ontology for organizational structures, aimed
+at supporting linked data publishing of organizational information across
+a number of domains. It is designed to allow domain-specific extensions to add classification
+of organizations and roles, as well as extensions to support neighbouring information
+such as organizational activities.
+</p>
+</section><section id="sotd" class="introductory"><h2>Status of This Document</h2>
+
+
+
+ <p>
+ <em>This section describes the status of this document at the time of its publication. Other
+ documents may supersede this document. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the latest revision
+ of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports
+ index</a> at http://www.w3.org/TR/.</em>
+ </p>
+
+This ontology was originally
+ developed <a href="http://www.epimorphics.com/public/vocabulary/org.html">
+ and published</a> outside of <abbr title="World Wide Web Consortium">W3C</abbr>, but has been extended and further
+ developed within the Government Linked Data Working group.
+
+ <p>
+ This document was published by the <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a> as a Candidate Recommendation.
+
+ This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
+
+
+ If you wish to make comments regarding this document, please send them to
+ <a href="mailto:public-gld-wg@w3.org">public-gld-wg@w3.org</a>
+ (<a href="mailto:public-gld-wg-request@w3.org?subject=subscribe">subscribe</a>,
+ <a href="http://lists.w3.org/Archives/Public/public-gld-wg/">archives</a>).
+
+
+
+ <abbr title="World Wide Web Consortium">W3C</abbr> publishes a Candidate Recommendation to indicate that the document is believed
+ to be stable and to encourage implementation by the developer community. This
+ Candidate Recommendation is expected to advance to Proposed Recommendation no earlier than
+ 30 November 1899.
+
+
+ All comments are welcome.
+
+
+ </p><p>
+ Publication as a Candidate Recommendation does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr> Membership.
+ This is a draft document and may be updated, replaced or obsoleted by other documents at
+ any time. It is inappropriate to cite this document as other than work in progress.
+ </p>
+
+
+ <p>
+
+ This document was produced by a group operating under the
+ <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+
+
+
+
+ <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="" rel="disclosure">public list of any patent disclosures</a>
+
+ made in connection with the deliverables of the group; that page also includes instructions for
+ disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains
+ <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the
+ information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+ 6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+
+
+ </p>
+
+
+
+
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#overview-of-ontology" class="tocxref"><span class="secno">1. </span>Overview of ontology</a><ul class="toc"><li class="tocline"><a href="#example-1" class="tocxref"><span class="secno">1.1 </span>Example</a></li></ul></li><li class="tocline"><a href="#description" class="tocxref"><span class="secno">2. </span>Description and commentary</a><ul class="toc"><li class="tocline"><a href="#organizational_structure" class="tocxref"><span class="secno">2.1 </span>Organizational structure</a></li><li class="tocline"><a href="#reporting_structure" class="tocxref"><span class="secno">2.2 </span>Membership and Reporting structure</a></li><li class="tocline"><a href="#location_information" class="tocxref"><span class="secno">2.3 </span>Location information</a></li><li class="tocline"><a href="#organizational_history" class="tocxref"><span class="secno">2.4 </span>Organizational history</a></li><li class="tocline"><a href="#notes-on-modelling-style" class="tocxref"><span class="secno">2.5 </span>Notes on modelling style</a></li></ul></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">3. </span>Conformance</a></li><li class="tocline"><a href="#namespaces-1" class="tocxref"><span class="secno">4. </span>Namespaces</a></li><li class="tocline"><a href="#ontology_reference" class="tocxref"><span class="secno">5. </span>Ontology Reference</a><ul class="toc"><li class="tocline"><a href="#ontology_index" class="tocxref"><span class="secno">5.1 </span>Index of classes and properties</a></li><li class="tocline"><a href="#organizational-structure" class="tocxref"><span class="secno">5.2 </span>Organizational structure</a><ul class="toc"><li class="tocline"><a href="#class-organization" class="tocxref"><span class="secno">5.2.1 </span>Class: Organization</a></li><li class="tocline"><a href="#class-formalorganization" class="tocxref"><span class="secno">5.2.2 </span>Class: FormalOrganization</a></li><li class="tocline"><a href="#class-organizationalunit" class="tocxref"><span class="secno">5.2.3 </span>Class: OrganizationalUnit</a></li></ul></li><li class="tocline"><a href="#membership-roles-posts-and-reporting" class="tocxref"><span class="secno">5.3 </span>Membership, roles, posts and reporting</a><ul class="toc"><li class="tocline"><a href="#property-memberof" class="tocxref"><span class="secno">5.3.1 </span>Property: memberOf</a></li><li class="tocline"><a href="#property-hasmember" class="tocxref"><span class="secno">5.3.2 </span>Property: hasMember</a></li><li class="tocline"><a href="#property-headof" class="tocxref"><span class="secno">5.3.3 </span>Property: headOf</a></li><li class="tocline"><a href="#class-membership" class="tocxref"><span class="secno">5.3.4 </span>Class: Membership</a></li><li class="tocline"><a href="#class-role" class="tocxref"><span class="secno">5.3.5 </span>Class: Role</a></li><li class="tocline"><a href="#class-post" class="tocxref"><span class="secno">5.3.6 </span>Class: Post</a></li><li class="tocline"><a href="#property-reportsto" class="tocxref"><span class="secno">5.3.7 </span>Property: reportsTo</a></li></ul></li><li class="tocline"><a href="#location" class="tocxref"><span class="secno">5.4 </span>Location</a><ul class="toc"><li class="tocline"><a href="#class-site" class="tocxref"><span class="secno">5.4.1 </span>Class: Site</a></li><li class="tocline"><a href="#property-location" class="tocxref"><span class="secno">5.4.2 </span>Property: location</a></li></ul></li><li class="tocline"><a href="#projects-and-other-activities" class="tocxref"><span class="secno">5.5 </span>Projects and other activities</a><ul class="toc"><li class="tocline"><a href="#class-organizationalcollaboration" class="tocxref"><span class="secno">5.5.1 </span>Class: OrganizationalCollaboration</a></li></ul></li><li class="tocline"><a href="#historical-information" class="tocxref"><span class="secno">5.6 </span>Historical information</a><ul class="toc"><li class="tocline"><a href="#class-changeevent" class="tocxref"><span class="secno">5.6.1 </span>Class: ChangeEvent</a></li></ul></li></ul></li><li class="tocline"><a href="#change-history" class="tocxref"><span class="secno">A. </span>Change history</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">B. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></section>
+
+
+
+
+<!-- INTRODUCTION -->
+
+<section class="introductory">
+
+<h2 id="introduction">Introduction</h2>
+<p>This document describes a core ontology (ORG) for organizational
+ structures, aimed
+at supporting linked data publishing of organizational information across
+a number of domains. It is designed to allow domain-specific extensions to add classification
+of organizations and roles, as well as extensions to support neighbouring information
+such as organizational activities.</p>
+
+<p>This document does not prescribe any particular method of deploying
+ data expressed in ORG. ORG is applicable in many contexts including
+ RDF accessible via SPARQL endpoints, embedded in HTML pages,
+ or serialized as an RDF/XML or Turtle. The examples in this
+ document use Turtle [<cite><a class="bibref" href="#bib-TURTLE">TURTLE</a></cite>] in the interests of readability.</p>
+
+</section>
+
+
+<!-- Overview of ontology -->
+
+<section class="informative" id="overview-of-ontology">
+<!--OddPage--><h2><span class="secno">1. </span>Overview of ontology</h2><p><em>This section is non-normative.</em></p>
+
+<p>This ontology is designed to enable publication of information on
+ organizations and organizational structures including governmental
+ organizations. It is intended to provide a generic, reusable core
+ ontology that can be extended or specialized for use in particular situations.</p>
+
+<p>The ontology gives terms to support the representation of:</p>
+<ul>
+ <li><a href="#organizational_structure">organizational structure</a>
+ <ul>
+ <li>notion of an organization</li>
+ <li>decomposition into sub-organizations and units</li>
+ <li>purpose and classification of organizations</li>
+ </ul>
+ </li>
+ <li><a href="#reporting_structure">reporting structure</a>
+ <ul>
+ <li>membership and reporting structure within an organization</li>
+ <li>roles, posts, and the relationship between people and organizations</li>
+ </ul>
+ </li>
+ <li><a href="#location_information">location information</a>
+ <ul>
+ <li>sites or buildings, locations within sites</li>
+ </ul>
+ </li>
+ <li><a href="#organizational_history">organizational history (merger, renaming)</a></li>
+</ul>
+
+<p>This coverage corresponds to the type of information typically
+ found in organizational charts. As such it does not offer a
+ complete representation for all the nuances of organizational
+ control structures and flows of accountability and empowerment.
+ Developers are encouraged to create extension vocabularies for such
+ purposes, building upon this generic foundation.</p>
+
+<p>The ontology does not provide category structures for organization
+type, organization purpose or roles. Different domains will have different
+requirements for classification of such concepts. Instead the ontology
+provides just the core base concepts needed to allow extensions to add specific
+sub-class structures or classification schemes as required. Users of
+ the ontology are encouraged to define <strong>profiles</strong>
+ which strengthen interoperability by specifying particular
+ controlled vocabularies to use for these concepts.
+</p>
+
+<p>A pictorial illustration of the main classes and relationships in
+ ORG is shown below. All terms are within the
+ ORG namespace (<code>http://www.w3.org/ns/org#</code>, preferred
+ prefix <em>org:</em>) unless an explicit prefix is
+ given. The namespaces for all referenced vocabularies are giving
+ in the section on <a href="#ns">Namespaces</a>.
+ </p>
+
+<img src="img/diagram.png" alt="Diagram depicting core classes and relationships">
+
+<section class="informative" id="example-1">
+<h3 id="example"><span class="secno">1.1 </span>Example</h3><p><em>This section is non-normative.</em></p>
+<p>This example illustrates a small fragment of the organizational
+ structure of the UK Cabinet Office:</p>
+
+<pre><http://reference.data.gov.uk/id/department/co>
+ rdf:type org:Organization , central-government:Department;
+ skos:prefLabel "Cabinet Office" ;
+ org:hasUnit <http://reference.data.gov.uk/id/department/co/unit/cabinet-office-communications> .
+
+<http://reference.data.gov.uk/id/department/co/unit/cabinet-office-communications>
+ rdf:type org:OrganizationalUnit ;
+ skos:prefLabel "Cabinet Office Communications" ;
+ org:unitOf <http://reference.data.gov.uk/id/department/co> ;
+ org:hasPost <http://reference.data.gov.uk/id/department/co/post/246> .
+
+<http://reference.data.gov.uk/id/department/co/post/246>
+ skos:prefLabel "Deputy Director, Deputy Prime Minister's Spokesperson/Head of Communications" .
+ org:postIn <http://reference.data.gov.uk/id/department/co/unit/cabinet-office-communications> ;
+ org:heldBy <#person161> .
+ </pre>
+
+</section>
+
+</section>
+
+
+<!-- Descriptive section -->
+
+<section id="description">
+
+<!--OddPage--><h2><span class="secno">2. </span>Description and commentary</h2>
+
+<section id="organizational_structure" class="informative">
+<h3><span class="secno">2.1 </span>Organizational structure</h3><p><em>This section is non-normative.</em></p>
+
+<p>The core class in the ontology
+ is <a href="#org:Organization">org:Organization</a> which is
+ intended to be applicable to a very broad range of organizations. It
+ represents a collection of people organized together into a
+ community or other social, commercial or political structure. The group
+ has some common purpose or reason for existence which goes beyond the
+ set of people belonging to it. An organization may itself be able to
+ act as an agent.</p>
+
+<p>We distinguish a particular sub-class of
+ organization <a href="#org:FormalOrganization">org:FormalOrganization</a>
+ to indicate organizations that are recognized in the world at large, in
+ particular in legal jurisdictions, with associated rights and
+ responsibilities. Examples include a corporation, charity, government or
+ church.</p>
+
+<p>The ontology then supports the notion of organizations being
+ composed of other organizations in some hierarchy. The
+ relations <a href="#org:subOrganizationOf">org:subOrganizationOf</a>
+ and <a href="#org:hasSubOrganization">org:hasSubOrganization</a>
+ establish these hierarchical links. </p>
+
+<p>In some cases the sub-organization can be regarded as standalone -
+ for example a legally recognized business may be part of a larger group or holding
+ company. In other cases it is useful to refer to departments or
+ organizational units such as <emphasis>the IT department</emphasis>
+ which only have meaning within the context of the containing
+ organization. The ontology supports that situation through a specialization
+ of <a href="#org:Organization">org:Organization</a>
+ called <a href="#org:OrganizationalUnit">org:OrganizationalUnit</a>. For
+ convenience it also provides the relations <a href="#org:hasUnit">org:hasUnit</a>
+ and <a href="#org:unitOf">org:unitOf</a> which are specializations
+ of the generic sub-organization links.</p><p>
+
+</p><p>Note that the containment hierarchy is completely open. For
+ example, <a href="#org:FormalOrganization">org:FormalOrganization</a>s are free to contain
+ other <a href="#org:FormalOrganization">org:FormalOrganization</a>s.</p>
+
+<h3 id="organizational-hierarchy">Organizational hierarchy</h3>
+
+<p>In many organizations there is a hierarchy of unit structures. For example we might see a containment hierarchy like:</p>
+
+<pre class="code">Corporation
+ BusinessUnit
+ Division
+ Function
+</pre>
+
+<p>Such hierarchies are specific to the particular organization, or class of
+ organization being modelled. Profiles of ORG may include
+ sub-classes
+ of <a href="#org:Organization">org:Organization</a> and <a href="#org:OrganizationalUnit">org:OrganizationalUnit</a> to
+ represent such structures and specialize or restrict the use
+ of <a href="#org:hasSubOrganization">org:hasSubOrganization</a> to match the desired hierarchy.</p>
+
+<h3 id="organizational-classification">Organizational classification</h3>
+
+<p>In a number of circumstances we wish to classify organizations. There are many approaches that could be
+taken for this. It can be based on the legal structure under which the organization operates.
+For example in UK legislation there are defined notions of Partnership, Limited Company etc
+that can be used as a basis for classification.
+Alternatively organizations can be classified by the service they
+ provide (e.g. educational, manufacturing, legal service etc).</p>
+
+<p>ORG is neutral with respect to such choices.
+ It is anticipated that profiles will either introduce
+ sub-classes of <a href="#org:Organization">org:Organization</a> or
+ define a classification scheme for organizations. To support the
+ latter the ontology supplies a
+ property <a href="#org:classification">org:classification</a> which
+ can be used the classify an organization using a SKOS
+ [<cite><a class="bibref" href="#bib-SKOS-REFERENCE">SKOS-REFERENCE</a></cite>] concept scheme.</p>
+
+<p>Which of these mechanisms to use depends on the situation. If the classification is not intrinsic to the organization
+ but simply some way to group organizations, for example as part of a
+ directory, then <a href="#org:classification">org:classification</a> should be used. If the
+ classification is a reflection of the intrinsic nature of the
+ organization and affects other properties then the sub-class
+ approach should be used.
+ For example, only charities have charity numbers so it would be better to represent a
+ charity as a sub-class of <a href="#org:FormalOrganization">org:FormalOrganization</a> rather
+ than via a taxonomic labelling.</p>
+
+</section>
+
+<section id="reporting_structure" class="informative">
+<h3><span class="secno">2.2 </span>Membership and Reporting structure</h3><p><em>This section is non-normative.</em></p>
+
+<p>ORG provides a number of ways to represent the relationship between
+ people and organizations, together with the internal reporting
+ structure of an organization. Experience with early versions of the
+ ontology demonstrated that there is no "one size that fits
+ all". In some cases a very simple direct representation is preferred
+ for ease of consumption. In other cases a more complex
+ representation is needed to capture the nuances of the situation.
+ An ORG profile may specify that a particular subset of these
+ mechanisms be used.</p>
+
+<h3 id="direct-membership-relation">Direct membership relation</h3>
+
+<p>
+This simplest representation provided by ORG is to directly state that
+some individual (represented as a <a href="http://xmlns.com/foaf/spec/#term_Agent">foaf:Agent</a>) is <a href="#org:memberOf">org:memberOf</a> an organization. To represent
+specific roles that the person plays, ORG profiles may define
+sub-properties of <a href="#org:memberOf">org:memberOf</a>. In particular, the notion
+of a leader or head of a organization is so common that ORG provides a
+built in property specialization of <a href="#org:memberOf">org:memberOf</a>, namely
+<a href="#org:headOf">org:headOf</a> for this purpose.</p>
+
+<p>For example:</p>
+
+<pre class="code"><http://example.com/people#ceo>
+ org:headOf <http://example.com/org#id>.
+</pre>
+
+<h3 id="membership-n-ary-relationship">Membership n-ary relationship</h3>
+
+<p>However, in general it is advantageous to have an explicit
+ representation of the organizational role that the person fulfils (e.g.
+for publication of responsibilities associated with the role). This is supported
+by the <a href="#org:Role">org:Role</a> class. The situation of an Agent fulfilling that role within an organization
+is then expressed through instances of the <a href="#org:Membership">org:Membership</a> n-ary relationship. This also
+makes it possible to annotate the relationship with qualifying information such as duration, salary,
+reference to the employment contract and so forth.</p>
+
+<p>For example:</p>
+
+<pre class="code"><http://example.com/org#id> a org:FormalOrganization;
+ skos:prefLabel "Example Ltd".
+
+eg:ctoRole a org:Role;
+ skos:prefLabel "CTO".
+
+[] a org:Membership;
+ org:member <http://example.com/people#jo>;
+ org:organization <http://example.com/org#id>;
+ org:role eg:ctoRole;
+ org:memberDuring [a time:Interval; time:hasBeginning [
+ time:inXSDDateTime "2009-11-01T09:00:00Z"^^xsd:dateTime]].
+</pre>
+
+<p>The relationship between this full n-ary relationship and the
+ direct <a href="#org:memberOf">org:memberOf</a> property can be expressed
+ as an entailment rule, using SPARQL Construct [<cite><a class="bibref" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>]:</p>
+
+<pre class="code">CONSTRUCT {
+ ?agent org:memberOf ?org.
+} WHERE {
+ [] a org:Membership;
+ org:member ?agent;
+ org:organization ?org.
+}
+</pre>
+
+<p>Since this representation can be a little less convenient to query and
+explore via linked data browsing tools the core allows both explicit roles and
+simple direct relations to be used simultaneously. The relationship between
+the Role resource and the corresponding property can be indicated through
+the <a href="#org:roleProperty">org:roleProperty</a> annotation. Thus we might extend the above example with:</p>
+
+<pre class="code">eg:ctoRole a org:Role;
+ org:roleProperty eg:ctoOf.
+
+eg:ctoOf a owl:ObjectProperty, rdf:Property;
+ skos:prefLabel "CTO";
+ rdfs:subPropertyOf org:memberOf.
+
+<http://example.com/people#jo>
+ eg:ctoOf <http://example.com/org#id>.
+</pre>
+
+<p>The semantics of <a href="#org:roleProperty">org:roleProperty</a> can be expressed
+ using a second closure rule:</p>
+
+<pre class="code">CONSTRUCT {
+ ?agent ?roleprop ?org.
+} WHERE {
+ [] a org:Membership;
+ org:member ?agent;
+ org:organization ?org;
+ org:role [ org:roleProperty ?roleprop ].
+}
+</pre>
+
+<p>Tool chains may generate <a href="#org:Membership">org:Membership</a> instances
+ and then apply this closure rule to add any corresponding
+ short-cut specializations of <a href="#org:memberOf">org:memberOf</a>.</p>
+
+<h4 id="posts">Posts</h4><p><em>This section is non-normative.</em></p>
+
+<p>The third representation that is provided by ORG is that of
+ a <a href="#org:Post">org:Post</a> which represents some position in the
+ organization that may or may not be currently filled. Posts enable
+ reporting structures and organization charts to be represented
+ independently of the individuals holding those posts. Posts can
+ report to other Posts.</p><p>
+
+</p><p>So a <a href="#org:Post">org:Post</a> can exist without someone holding that
+ post. In contrast, a <a href="#org:Membership">org:Membership</a> represents the relationship between
+ a particular individual (Agent) and the organization and does not
+ exist unless there is an Agent to partake of the relationship.</p>
+
+<p>While commonly a Post would be held by a single person there are
+ situations in government organizations where a Post may itself be, or
+ be treated as, an Organization. There are no disjointness
+ constraints precluding an application of ORG from treating an entity
+ as both a <a href="#org:Post">org:Post</a> and
+ an <a href="#org:Organization">org:Organization</a> simultaneously,
+ if that is an appropriate modelling of the situation.</p>
+
+<p>A post can have an associated <a href="#org:Role">org:Role</a>.</p>
+
+<h4 id="relationship-between-posts-and-memberships">Relationship between Posts and Memberships</h4>
+
+<p>
+ In many situations only one of Post or Membership is needed, and ORG
+ profiles may specify that use of one of the two is preferred.
+ In cases where the structure of the organization is to be
+ given, independently of the people within that
+ structure, then <a href="#org:Post">org:Post</a> is the appropriate
+ representation to choose. In cases where the aim is to record
+ the people who make up the organization and those memberships are
+ likely to be annotated (e.g. with duration of the membership)
+ then <a href="#org:Membership">org:Membership</a> is appropriate.</p>
+
+<p>We can state a formal relationship between these
+ representations in the form of two entailment rules:</p>
+
+<pre class="code">CONSTRUCT {
+ ?agent org:memberOf ?org.
+} WHERE {
+ ?agent org:holds ?post.
+ ?post org:postIn ?org.
+}
+</pre>
+
+<pre class="code">CONSTRUCT {
+ [] a org:Membership;
+ org:member ?agent;
+ org:organization ?org;
+ org:role ?role.
+} WHERE {
+ ?agent org:holds ?post.
+ ?post org:postIn ?org.
+ ?post org:role ?role.
+}
+</pre>
+
+</section>
+
+<section id="location_information" class="informative">
+<h3><span class="secno">2.3 </span>Location information</h3><p><em>This section is non-normative.</em></p>
+
+<p>ORG provides
+<a href="#org:Site">org:Site</a> to represent locations at which organizations exist. The
+relations <a href="#org:siteOf">org:siteOf</a> and <a href="#org:hasSite">org:hasSite</a> establish links between a
+<a href="#org:Site">org:Site</a> and an organization. We distinguish a
+primary site
+(<a href="#org:hasPrimarySite">org:hasPrimarySite</a>)
+to indicate the default means by which an
+organization can be contacted, and a registered site
+(<a href="#org:hasRegisteredSite">org:hasRegisteredSite</a>)
+to indicate a legally registered site for the
+organization.</p>
+
+<p>The ontology
+ provides <a href="#org:siteAddress">org:siteAddress</a> to define
+ the address of a site using a vocabulary such as the vCard [<cite><a class="bibref" href="#bib-VCARD">VCARD</a></cite>] vocabulary.</p>
+
+</section>
+
+<section id="organizational_history" class="informative">
+<h3><span class="secno">2.4 </span>Organizational history</h3><p><em>This section is non-normative.</em></p>
+
+<p>Any aspect of organizational structure is subject to change over time.
+For the most part this should be handled by an external mechanism such as named graphs.
+When Organizations change substantially (not simply a change of personnel or internal structure),
+for example a merger to create a new organization, then the new Organization
+will typically be denoted by a new URI. In that case we need some
+ vocabulary to describe that change over time
+ and the relationship between the original and resulting resources.
+ORG provides <a href="#org:ChangeEvent">org:ChangeEvent</a> and
+ associated properties as a
+ foundation for this, building upon
+ the PROV-O Provenance Vocabulary [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>].</p>
+
+<p>For example to indicate that an organization now called "Department
+ for Education" was formed as a result of rebranding and
+ restructuring and organization called "Department for Children
+ Schools and Family" we might state:</p>
+
+<pre class="code"> <http://example.com/DfE> a org:Organization;
+ skos:prefLabel "Department for Education"@en .
+
+ <http://example.com/DCSF> a org:Organization;
+ skos:prefLabel "Department for Children Schools and Family"@en .
+
+ <http://example.com/regorgMay2010> a org:ChangeEvent;
+ rdfs:comment "Post-election re-organization and rebranding"@en ;
+ org:originalOrganization <http://example.com/DfE> ;
+ org:resultingOrganization <http://example.com/DCSF> .
+</pre>
+
+<p>An application can use terms from the PROV-O vocabulary to further describe the
+ change event, for example the period of time over which it
+ occurred. Such usage of PROV-O terms should take into account the
+ semantic constraints [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] of the PROV model. </p><p>
+
+</p><p>It is sometimes convenient to be able to directly link from an
+ organization to a previous organization from which it descended. This
+ is supported by using
+ the <a href="http://www.w3.org/TR/prov-o/#wasDerivedFrom">prov:wasDerivedFrom</a>
+ relationship. ORG declares the property chain axiom:</p><p>
+
+</p><pre class="code"> SubObjectPropertyOf( ObjectPropertyChain( org:resultedFrom org:originalOrganization ) prov:wasDerivedFrom )
+</pre>
+
+<p>Which can also be expressed using a SPARQL CONSTRUCT</p>
+<pre class="code">CONSTRUCT {
+ ?orgR prov:wasDerivedFrom ?orgO .
+} WHERE {
+ ?orgR org:resultedFrom / org:originalOrganization ?orgO .
+}
+</pre>
+
+<p>Thus in our previous example, given
+ that <a href="#org:resultedFrom">org:resultedFrom</a>
+ and <a href="#org:resultingOrganization">org:resultingOrganization</a>
+ are inverse of each other, we can deduce:</p><p>
+
+</p><pre class="code"> <http://example.com/DfE> prov:wasDerivedFrom <http://example.com/DCSF> .
+</pre>
+
+<h3 id="note">Note</h3>
+
+<p>In earlier versions of this ontology
+ the <a href="http://open-biomed.sourceforge.net/opmv/ns">OPMV
+ Provenance Vocabulary</a> was used.
+ We believe that the PROV-O terms used here are equivalent to the corresponding
+ OPMV terms previously used and that this change does not affect the
+ semantics of the ontology. </p>
+
+</section>
+
+<section class="informative" id="notes-on-modelling-style">
+<h3><span class="secno">2.5 </span>Notes on modelling style</h3><p><em>This section is non-normative.</em></p>
+
+<p><em>Use of inverses:</em> designers differ on whether providing pairs of inverse relationships between
+concepts is good practice compared to declaring each relationship in just one direction. In this design we
+provide inverses for most relations (omitting attribute-like relations). This makes it easier to query
+the data in linked data settings where a (non-symmetric) closed bounded description is often the
+default description of each resource. This does incur a cost in terms
+ of maintenance of those relationships.
+Particular applications of the ontology may adopt a profile in which only certain directions are asserted in the
+ data and leave it up to clients to apply any inverseOf reasoning they require.</p>
+
+<p><em>Naming:</em> some designers prefer to name properties by nouns which describe the object
+of the property, others prefer to treat property names as names of the link and use a pattern
+to indicate the direction of the link. Here we adopt the latter approach for those properties
+which are relational and especially when the direction is ambiguous.
+We use the URI pattern <code>org:hasFoo/org:fooOf</code> for this but simplify the labels to "foo"
+and "foo of" to improve readability in linked data viewers.</p>
+</section>
+
+</section> <!-- End of descriptive section -->
+
+<section id="conformance"><!--OddPage--><h2><span class="secno">3. </span>Conformance</h2>
+<p>
+ As well as sections marked as non-normative, all authoring guidelines, diagrams, examples,
+ and notes in this specification are non-normative. Everything else in this specification is
+ normative.
+</p>
+<p>
+ The key words <em class="rfc2119" title="must">must</em>, <em class="rfc2119" title="must not">must not</em>, <em class="rfc2119" title="required">required</em>, <em class="rfc2119" title="should">should</em>, <em class="rfc2119" title="should not">should not</em>, <em class="rfc2119" title="recommended">recommended</em>, <em class="rfc2119" title="may">may</em>,
+ and <em class="rfc2119" title="optional">optional</em> in this specification are to be interpreted as described in [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].
+</p>
+
+<p>A data interchange, however that interchange occurs, is conformant
+ with ORG if:
+</p><ul>
+<li>it uses terms (classes and properties) from ORG in a way consistent with
+ their semantics as declared in this specification;</li>
+<li>it does <strong>not</strong> use terms from other vocabularies <strong>instead</strong> of ones defined
+ in this vocabulary that could reasonably be used (use of such
+ terms <strong>in addition</strong> to ORG terms is permissible).</li>
+</ul>
+<p></p>
+
+<p>A conforming data interchange:
+</p><ul>
+<li><em class="rfc2119" title="may">may</em> include terms from other vocabularies;</li>
+<li><em class="rfc2119" title="may">may</em> use only a subset of ORG terms.</li>
+</ul>
+<p></p>
+
+<p>An <strong>ORG profile</strong> is a specification for data
+ interchange that adds additional constraints to ORG. Additional
+ constraints in a profile <em class="rfc2119" title="may">may</em>
+ include (but are not limited to):
+</p><ul>
+<li>a minimum set of required terms;</li>
+<li>classes and properties for additional terms not covered in ORG;</li>
+<li>controlled vocabularies or controlled sets of URIs to use as acceptable values for
+ properties;</li>
+<li>guidance on use of pairs of inverse properties (such as selecting only one
+ member of the pair to be included, or requiring that both
+ members be explicitly included);</li>
+<li>guidance on choice of modelling approach for roles
+ (see <a href="#reporting_structure">Membership and Reporting
+ structure</a>).</li>
+</ul>
+<p></p>
+
+</section>
+
+<!-- Namespaces -->
+<section id="namespaces-1">
+<!--OddPage--><h2 id="ns"><span class="secno">4. </span>Namespaces</h2>
+<p>The namespace for ORG is <code>http://www.w3.org/ns/org#</code>. However,
+it should be noted that ORG extends and uses terms from other vocabularies. A full set of alphabetically ordered namespaces and prefixes used in this
+document is shown in the table below.</p>
+<!-- Alphabetically ordered-->
+<table id="namespaces">
+ <thead><tr><th>Prefix</th><th>Namespace</th><th>Reference</th></tr></thead>
+ <tbody>
+
+ <tr><td>foaf</td><td><a href="http://xmlns.com/foaf/0.1/">http://xmlns.com/foaf/0.1/</a></td><td>[<cite><a class="bibref" href="#bib-FOAF">FOAF</a></cite>]</td></tr>
+ <tr><td>gr</td><td><a href="http://purl.org/goodrelations/v1">http://purl.org/goodrelations/v1#</a></td><td>[<cite><a class="bibref" href="#bib-GOOD-RELATIONS">GOOD-RELATIONS</a></cite>]</td></tr>
+ <tr><td>prov</td><td><a href="http://www.w3.org/ns/prov">http://www.w3.org/ns/prov#</a></td><td>[<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>]</td></tr>
+ <tr><td>org</td><td><a href="http://www.w3.org/ns/org">http://www.w3.org/ns/org#</a></td><td></td></tr>
+ <tr><td>owl</td><td><a href="http://www.w3.org/2002/07/owl">http://www.w3.org/2002/07/owl#</a></td><td>[<cite><a class="bibref" href="#bib-OWL2-PRIMER">OWL2-PRIMER</a></cite>]</td></tr>
+ <tr><td>time</td><td><a href="http://www.w3.org/2006/time">http://www.w3.org/2006/time#</a></td><td>[<cite><a class="bibref" href="#bib-OWL-TIME">OWL-TIME</a></cite>]</td></tr>
+ <tr><td>rdf</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns">http://www.w3.org/1999/02/22-rdf-syntax-ns#</a></td><td>[<cite><a class="bibref" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>]</td></tr>
+ <tr><td>rdfs</td><td><a href="http://www.w3.org/2000/01/rdf-schema">http://www.w3.org/2000/01/rdf-schema#</a></td><td>[<cite><a class="bibref" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]</td></tr>
+ <tr><td>skos</td><td><a href="http://www.w3.org/2004/02/skos/core">http://www.w3.org/2004/02/skos/core#</a></td><td>[<cite><a class="bibref" href="#bib-SKOS-REFERENCE">SKOS-REFERENCE</a></cite>]</td></tr>
+ <tr><td>vcard</td><td><a href="http://www.w3.org/2006/vcard/ns#">http://www.w3.org/2006/vcard/ns#</a></td><td>[<cite><a class="bibref" href="#bib-VCARD">VCARD</a></cite>]</td></tr>
+ <tr><td>dct</td><td><a href="http://purl.org/dc/terms/">http://purl.org/dc/terms/</a></td><td>[<cite><a class="bibref" href="#bib-DC11">DC11</a></cite>]</td></tr>
+ </tbody>
+</table>
+</section>
+
+
+<!-- Ontology section -->
+
+<section id="ontology_reference">
+<!--OddPage--><h2><span class="secno">5. </span>Ontology Reference</h2>
+
+<section id="ontology_index">
+<h3><span class="secno">5.1 </span>Index of classes and properties</h3>
+
+<p><strong>Classes:</strong>
+ | <a href="#org:ChangeEvent">ChangeEvent</a>
+ | <a href="#org:FormalOrganization">FormalOrganization</a>
+ | <a href="#org:Membership">Membership</a>
+ | <a href="#org:OrganizationalCollaboration">OrganizationalCollaboration</a>
+ | <a href="#org:OrganizationalUnit">OrganizationalUnit</a>
+ | <a href="#org:Organization">Organization</a>
+ | <a href="#org:Post">Post</a>
+ | <a href="#org:Role">Role</a>
+ | <a href="#org:Site">Site</a> |
+</p>
+
+<p><strong>Properties:</strong>
+ | <a href="#org:basedAt">basedAt</a>
+ | <a href="#org:changedBy">changedBy</a>
+ | <a href="#org:classification">classification</a>
+ | <a href="#org:hasMember">hasMember</a>
+ | <a href="#org:hasMembership">hasMembership</a>
+ | <a href="#org:hasPost">hasPost</a>
+ | <a href="#org:hasPrimarySite">hasPrimarySite</a>
+ | <a href="#org:hasRegisteredSite">hasRegisteredSite</a>
+ | <a href="#org:hasSite">hasSite</a>
+ | <a href="#org:hasSubOrganization">hasSubOrganization</a>
+ | <a href="#org:hasUnit">hasUnit</a>
+ | <a href="#org:headOf">headOf</a>
+ | <a href="#org:heldBy">heldBy</a>
+ | <a href="#org:holds">holds</a>
+ | <a href="#org:identifier">identifier</a>
+ | <a href="#org:linkedTo">linkedTo</a>
+ | <a href="#org:location">location</a>
+ | <a href="#org:memberDuring">memberDuring</a>
+ | <a href="#org:memberOf">memberOf</a>
+ | <a href="#org:member">member</a>
+ | <a href="#org:organization">organization</a>
+ | <a href="#org:originalOrganization">originalOrganization</a>
+ | <a href="#org:postIn">postIn</a>
+ | <a href="#org:purpose">purpose</a>
+ | <a href="#org:remuneration">remuneration </a>
+ | <a href="#org:reportsTo">reportsTo</a>
+ | <a href="#org:resultedFrom">resultedFrom</a>
+ | <a href="#org:resultingOrganization">resultingOrganization</a>
+ | <a href="#org:role">role</a>
+ | <a href="#org:roleProperty">roleProperty</a>
+ | <a href="#org:siteAddress">siteAddress</a>
+ | <a href="#org:siteOf">siteOf</a>
+ | <a href="#org:subOrganizationOf">subOrganizationOf</a>
+ | <a href="#org:transitiveSubOrganizationOf">transitiveSubOrganizationOf</a>
+ | <a href="#org:unitOf">unitOf</a> |
+</p>
+
+</section>
+
+<!-- Organizational structure -->
+<section id="organizational-structure">
+<h3><span class="secno">5.2 </span>Organizational structure</h3>
+
+<!-- Class Organization -->
+<section id="class-organization">
+<h4 id="org:Organization"><span class="secno">5.2.1 </span>Class: Organization</h4>
+<p>Represents a collection of people organized together into a
+community or other social, commercial or political structure. The group
+has some common purpose or reason for existence which goes beyond the
+set of people belonging to it and can act as an Agent. Organizations are
+ often decomposable into hierarchical structures. </p>
+<table class="definition">
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">subClassOf:</td><td> <a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+ <tr><td class="prop">equivalentClass:</td><td> <a href="http://xmlns.com/foaf/0.1/Organization">foaf:Organization</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td> It is recommended
+that SKOS lexical labels should be used to label the Organization. In
+particular <a href="http://www.w3.org/2004/02/skos/core#prefLabel">skos:prefLabel</a> for the primary (e.g. legally
+ recognized name), <a href="http://www.w3.org/2004/02/skos/core#altLabel">skos:altLabel</a> for alternative
+ names (trading names, colloquial names)
+ and <a href="http://www.w3.org/2004/02/skos/core#notation">skos:notation</a> to denote codes from a code
+ list. Alternative names: <em>Collective</em>, <em>Body</em>, <em>Group</em>.</td></tr>
+ </tbody>
+</table>
+
+<!-- Property subOrganizationOf -->
+<section>
+<h5 id="org:subOrganizationOf">Property: subOrganizationOf</h5>
+<p>Represents hierarchical containment of Organizations or OrganizationalUnits; indicates an Organization which contains this Organization.</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#subOrganizationOf">org:subOrganizationOf</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain and Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td> Inverse of <a href="#org:hasSubOrganization">org:hasSubOrganization</a>. </td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property transitiveSubOrganizationOf -->
+<section>
+<h5 id="org:transitiveSubOrganizationOf">Property: transitiveSubOrganizationOf</h5>
+<p>Represents hierarchical containment of Organizations or
+ OrganizationalUnits; indicates an Organization which contains this
+ Organization, directly or indirectly.</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#transitiveSubOrganizationOf">org:transitiveSubOrganizationOf</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain and Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Transitive super property of:</td><td><a href="#org:subOrganizationOf">org:subOrganizationOf</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td> The transitive closure of subOrganizationOf, giving a representation of all organizations that contain this one. Note that technically this is a super property of the transitive closure so it could contain additional assertions but such usage is discouraged.</td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property hasSubOrganization -->
+<section>
+<h5 id="org:hasSubOrganization">Property: hasSubOrganization</h5>
+<p>Represents hierarchical containment of Organizations or OrganizationalUnits; indicates an organization which is a sub-part or child of this organization.</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasSubOrganization">org:hasSubOrganization</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain and Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td> Inverse of <a href="#org:subOrganizationOf">org:subOrganizationOf</a>.</td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property purpose -->
+<section>
+<h5 id="org:purpose">Property: purpose</h5>
+<p>Indicates the purpose of this Organization. There can be many purposes at different levels of abstraction but the nature of an organization is to have a reason for existence and this property is a means to document that reason. An Organization may have multiple purposes.</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#purpose">org:purpose</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td> It is recommended that the purpose be denoted by a controlled
+term or code list, ideally a <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a>. However, the
+range is left open to allow for other types of descriptive schemes. It
+is expected that profiles of this
+vocabulary will constrain the range of <a href="#org:purpose">org:purpose</a>. Alternative names: <em>remit</em>, <em>responsibility</em> (esp. if applied to OrganizationalUnits such as Government Departments).</td></tr>
+ </tbody>
+</table>
+</section>
+
+
+<!-- Property classification -->
+<section>
+<h5 id="org:classification">Property: classification</h5>
+<p>Indicates a classification for this Organization within some
+classification scheme. </p>
+<p>Note that it also permissible for applications to define
+ sub-classes of <a href="#org:Organization">org:Organization</a> as a means to represent
+ organizational categories.</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#classification">org:classification</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ Extension vocabularies may wish to specialize
+this property to have a range corresponding to a specific <a href="http://www.w3.org/2004/02/skos/core#ConceptScheme">skos:ConceptScheme</a>
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+
+<!-- Property identifier -->
+<section>
+<h5 id="org:identifier">Property: identifier</h5>
+<p>Gives an identifier, such as a company registration number, that can
+ be used to used to uniquely identify the organization.</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#identifier">org:identifier</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">subPropertyOf:</td><td> <a href="http://www.w3.org/2004/02/skos/core#notation">skos:notation</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ Many different national and international identifier schemes are available from other
+ vocabularies. The ORG ontology is neutral to which schemes are used. The particular identifier
+ scheme should be indicated by the datatype of the identifier value.
+Using datatypes to distinguish the notation scheme used is consistent
+with recommended best practice for <a href="http://www.w3.org/2004/02/skos/core#notation">skos:notation</a> of which this property is a specialization.
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property linkedTo -->
+<section>
+<h5 id="org:linkedTo">Property: linkedTo</h5>
+<p>Indicates an arbitrary relationship between two organizations.</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#linkedTo">org:linkedTo</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain and Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Usage note:</td>
+ <td>
+ Specializations of this can be used to, for example, denote funding or supply chain relationships.
+ </td>
+ </tr>
+ </tbody>
+</table>
+</section>
+
+</section> <!-- end of Class Organization-->
+
+<!-- Class FormalOrganization -->
+<section id="class-formalorganization">
+<h4 id="org:FormalOrganization"><span class="secno">5.2.2 </span>Class: FormalOrganization</h4>
+<p>
+ An Organization which is recognized in the world at large, in
+particular in legal jurisdictions, with associated rights and
+responsibilities. Examples include a corporation, charity, government or
+ church.
+</p>
+<table class="definition">
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#FormalOrganization">org:FormalOrganization</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">subClassOf:</td><td> <a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+
+ Note that this is a super class
+ of <a href="http://www.heppnetz.de/ontologies/goodrelations/v1.html#BusinessEntity">gr:BusinessEntity</a>
+and it is recommended to use the GoodRelations vocabulary to denote Business classifications such as DUNS or NAICS.
+</td></tr>
+</tbody>
+</table>
+
+</section> <!-- end of Class FormalOrganization-->
+
+
+<!-- Class OrganizationalUnit -->
+<section id="class-organizationalunit">
+<h4 id="org:OrganizationalUnit"><span class="secno">5.2.3 </span>Class: OrganizationalUnit</h4>
+<p>
+An Organization such as a department or support unit which is part of some
+larger Organization and only has full recognition within the
+context of that Organization. In particular the unit would not be
+regarded as a legal entity in its own right.
+</p>
+<table class="definition">
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#OrganizationalUnit">org:OrganizationalUnit</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">subClassOf:</td><td> <a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+Units can be large and complex containing other Units. Alternative names: <em>Department</em>
+</td></tr>
+</tbody>
+</table>
+
+<!-- Property hasUnit -->
+<section>
+<h5 id="org:hasUnit">Property: hasUnit</h5>
+<p>Indicates a unit which is part of this Organization, e.g. a Department within a larger Organization.</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasUnit">org:hasUnit</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:OrganizationalUnit">org:OrganizationalUnit</a></td></tr>
+ <tr><td class="prop">subPropertyOf:</td><td> <a href="#org:hasSubOrganization">org:hasSubOrganization</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ Inverse of <a href="#org:unitOf">org:unitOf</a>.
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property unitOf -->
+<section>
+<h5 id="org:unitOf">Property: unitOf</h5>
+<p>Indicates an Organization of which this Unit is a part, e.g. a
+Department within a larger Organization.</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#unitOf">org:unitOf</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:OrganizationalUnit">org:OrganizationalUnit</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">subPropertyOf:</td><td> <a href="#org:subOrganizationOf">org:subOrganizationOf</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ This is the inverse of <a href="#org:hasUnit">org:hasUnit</a>.
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+</section> <!-- end of Class OrganizationalUnit-->
+
+</section>
+
+<!-- End of section Organizational structure -->
+
+<!-- Reporting relationships and roles -->
+<section id="membership-roles-posts-and-reporting">
+<h3><span class="secno">5.3 </span>Membership, roles, posts and reporting</h3>
+
+
+<!-- Property memberOf -->
+<section id="property-memberof">
+<h4 id="org:memberOf"><span class="secno">5.3.1 </span>Property: memberOf</h4>
+<p>
+ Indicates that a person is a member of the Organization with no
+ indication of the nature of that membership or the role
+ played. Note that the choice of property name is not meant to
+ limit the property to only formal membership arrangements, it
+ is also intended to cover related concepts such as
+ affiliation or other involvement in the
+ organization. Extensions can specialize this relationship to
+ indicate particular roles within the organization or more
+ nuanced relationships to the organization.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#memberOf">org:memberOf</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">inverseOf:</td><td><a href="#org:hasMember">org:hasMember</a></td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property hasMember -->
+<section id="property-hasmember">
+<h4 id="org:hasMember"><span class="secno">5.3.2 </span>Property: hasMember</h4>
+<p>
+ Indicates a person who is a member of the subject Organization.
+Inverse of <a href="#org:memberOf">org:memberOf</a>, see that property for further clarification.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasMember">org:hasMember</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+ <tr><td class="prop">Equivalent property:</td><td><a href="http://xmlns.com/foaf/0.1/member">foaf:member</a></td></tr>
+ <tr><td class="prop">inverseOf:</td><td><a href="#org:memberOf">org:memberOf</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ Provided for compatibility with <a href="http://xmlns.com/foaf/spec/#term_member">foaf:member</a>.
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property headOf -->
+<section id="property-headof">
+<h4 id="org:headOf"><span class="secno">5.3.3 </span>Property: headOf</h4>
+<p>
+ Indicates that a person (or other agent) is the leader or formal
+head of the Organization.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#headOf">org:headOf</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">subPropertyOf:</td><td><a href="#org:memberOf">org:memberOf</a></td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Class Membership -->
+<section id="class-membership">
+<h4 id="org:Membership"><span class="secno">5.3.4 </span>Class: Membership</h4>
+<p>
+Indicates the nature of an Agent's membership of an organization.
+</p>
+<table class="definition">
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></th></tr></thead>
+ <tbody>
+ <!--tr><td class="prop">subClassOf:</td><td> <a href="#org:Organization">org:Organization</a></td></tr-->
+ <tr><td class="prop">Usage note:</td><td>
+
+ Represents an n-ary relationship between an Agent, an Organization and a
+Role. It is possible to directly indicate membership, independent of the
+ specific Role, through use of the <a href="#org:memberOf">org:memberOf</a> property.
+</td></tr>
+</tbody>
+</table>
+
+
+<!-- Property member -->
+<section>
+<h5 id="org:member">Property: member</h5>
+<p>
+ Indicates the Person (or other Agent including Organization) involved in the Membership relationship.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#member">org:member</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:Membership">org:Membership</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+ <tr><td class="prop">Type:</td><td><a href="http://www.w3.org/TR/owl2-syntax/#Functional_Object_Properties">owl:FunctionalProperty</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ Inverse of <a href="#org:hasMembership">org:hasMembership</a>
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+
+
+<!-- Property organization -->
+<section>
+<h5 id="org:organization">Property: organization</h5>
+<p>
+ Indicates the organization in which the Agent is a member.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#organization">org:organization</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:Membership">org:Membership</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Type:</td><td><a href="http://www.w3.org/TR/owl2-syntax/#Functional_Object_Properties">owl:FunctionalProperty</a></td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property role -->
+<section>
+<h5 id="org:role">Property: role</h5>
+<p>
+ Indicates the Role that the Agent plays in a Membership
+ relationship with an Organization. Can also be used on
+ a <a href="#org:Post">org:Post</a> to indicate the role that any holder
+ of the Post plays.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#role">org:role</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><code>owl:unionOf</code>(<a href="#org:Membership">org:Membership</a> <a href="#org:Post">org:Post</a>)</td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Role">org:Role</a></td></tr>
+
+ </tbody>
+</table>
+</section>
+
+<!-- Property hasMembership -->
+<section>
+<h5 id="org:hasMembership">Property: hasMembership</h5>
+<p>
+ Indicates a membership relationship that the Agent plays.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasMembership">org:hasMembership</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Membership">org:Membership</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ Inverse of <a href="#org:member">org:member</a>.
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property memberDuring -->
+<section>
+<h5 id="org:memberDuring">Property: memberDuring</h5>
+<p>
+ Optional property to indicate the interval for which the membership is/was valid.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#memberDuring">org:memberDuring</a></th></tr></thead>
+ <tbody>
+
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:Membership">org:Membership</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2006/time#Interval">time:Interval</a></td></tr>
+
+ </tbody>
+</table>
+</section>
+
+</section> <!-- end of Class Membership-->
+
+<!-- Class Role -->
+<section id="class-role">
+<h4 id="org:Role"><span class="secno">5.3.5 </span>Class: Role</h4>
+<p>
+Denotes a role that a Person or other Agent can take in an
+organization. Instances of this class describe the abstract role; to
+denote a specific instance of a person playing that role in a specific
+organization use an instance of <a href="#org:Membership">org:Membership</a>.
+</p>
+<table class="definition">
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#Role">org:Role</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">subClassOf:</td><td> <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+It is
+common for roles to be arranged in some taxonomic structure and we use
+SKOS to represent that. The normal SKOS lexical properties should be
+used when labelling the Role. Additional descriptive properties for the
+Role, such as a Salary band, may be added by extension vocabularies.
+</td></tr>
+</tbody>
+</table>
+
+<!-- Property roleProperty -->
+<section>
+<h5 id="org:roleProperty">Property: roleProperty</h5>
+<p>
+ This is a metalevel property which is used to annotate a <a href="#org:Role">org:Role</a> instance with a sub-property of <a href="#org:memberOf">org:memberOf</a>
+ that can be used to directly indicate the role for ease of query.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#roleProperty">org:roleProperty</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:Role">org:Role</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property">rdf:Property</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ The
+intended semantics is that a Membership relation involving the Role implies
+the existence of a direct property relationship through an inference
+rule of the form: <code>{ [] org:member ?a; org:organization ?o; org:role [org:roleProperty ?r] } -> {?a ?r ?o}</code>
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property remuneration -->
+<section>
+<h5 id="org:remuneration">Property: remuneration</h5>
+<p>
+ Indicates a salary or other reward associated with the role.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#remuneration">org:remuneration </a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain:</td><td><a href="#org:Role">org:Role</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ Typically this will be denoted using an existing representation scheme
+such as <a href="http://www.heppnetz.de/ontologies/goodrelations/v1.html#PriceSpecification">gr:PriceSpecification</a> but the range is left open to allow applications to specialize it (e.g. to remunerationInGBP).
+</td></tr>
+
+ </tbody>
+</table>
+</section>
+
+</section> <!-- end of Class Role-->
+
+
+<!-- Class Post -->
+<section id="class-post">
+<h4 id="org:Post"><span class="secno">5.3.6 </span>Class: Post</h4>
+<p>
+A Post represents some position within an organization that
+ exists independently of the person or persons filling it. Posts
+ may be used to represent situations where a person is a member
+ of an organization ex officio (for example the Secretary of
+ State for Scotland is part of UK Cabinet by virtue of being
+ Secretary of State for Scotland, not as an individual person). A
+ post can be held by multiple people and hence can be treated as
+ a organization in its own right.
+</p>
+<table class="definition">
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#Post">org:Post</a></th></tr></thead>
+</table>
+
+<!-- Property holds -->
+<section>
+<h5 id="org:holds">Property: holds</h5>
+<p>Indicates a Post held by some Agent.</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#holds">org:holds</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain:</td><td> <a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Post">org:Post</a></td></tr>
+ <tr><td class="prop">subPropertyOf:</td><td> <a href="#org:memberOf">org:memberOf</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ Inverse of <a href="#org:heldBy">org:heldBy</a>.
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property heldBy -->
+<section>
+<h5 id="org:heldBy">Property: heldBy</h5>
+<p>Indicates an Agent which holds a Post.</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#heldBy">org:heldBy</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain:</td><td><a href="#org:Post">org:Post</a></td></tr>
+ <tr><td class="prop">Range:</td><td> <a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+ <tr><td class="prop">subPropertyOf:</td><td> <a href="#org:hasMember">org:hasMember</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ Inverse of <a href="#org:holds">org:holds</a>.
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property postIn -->
+<section>
+<h5 id="org:postIn">Property: postIn</h5>
+<p>Indicates the Organization in which the Post exists.</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#postIn">org:postIn</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain:</td><td><a href="#org:Post">org:Post</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ Inverse of <a href="#org:hasPost">org:hasPost</a>.
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property hasPost -->
+<section>
+<h5 id="org:hasPost">Property: hasPost</h5>
+<p>Indicates a Post which exists within the Organization.</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasPost">org:hasPost</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Post">org:Post</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ Inverse of <a href="#org:postIn">org:postIn</a>.
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+</section> <!-- end of Class Post -->
+
+<!-- Property reportsTo -->
+<section id="property-reportsto">
+<h4 id="org:reportsTo"><span class="secno">5.3.7 </span>Property: reportsTo</h4>
+<p>
+ Indicates a reporting relationship as might be depicted on an
+organizational chart. It can be used to indicate a reporting
+ relationship directly between Agents or between Posts that
+ Agents could hold.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#reportsTo">org:reportsTo</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain:</td><td><code>owl:unionOf</code>(<a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a>
+ <a href="#org:Post">org:Post</a>) </td></tr>
+ <tr><td class="prop">Range:</td><td><code>owl:unionOf</code>(<a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a>
+ <a href="#org:Post">org:Post</a>) </td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ The precise semantics of the reporting
+relationship will vary by organization but is intended to encompass both
+ direct supervisory relationships (e.g. carrying objective and salary
+setting authority) and more general reporting or accountability
+relationships (e.g. so called <em>dotted line</em> reporting).
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+
+</section> <!-- end of Membership, roles, posts and reporting -->
+
+
+<!-- LOCATION -->
+<section id="location">
+<h3><span class="secno">5.4 </span>Location</h3>
+
+
+<!-- Class Site -->
+<section id="class-site">
+<h4 id="org:Site"><span class="secno">5.4.1 </span>Class: Site</h4>
+<p>
+An office or other premise at which the organization is located.
+Many organizations are spread across multiple sites and many sites will
+host multiple locations.
+</p>
+<table class="definition">
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#Site">org:Site</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Usage note:</td><td>
+ In most cases a Site will be a physical
+location. However, we don't exclude the possibility of non-physical
+sites such as a virtual office with an associated post box and phone
+reception service. Extensions may provide sub-classes to denote
+particular types of site.
+</td></tr>
+</tbody>
+</table>
+
+<!-- Property siteAddress -->
+<section>
+<h5 id="org:siteAddress">Property: siteAddress</h5>
+<p>
+Indicates an addess for the site in a suitable encoding. Use of a well
+known address encoding such as the vCard
+[<cite><a class="bibref" href="#bib-VCARD">VCARD</a></cite>] vocabulary is encouraged
+but the range is left open to allow other encodings to be used. The
+address may include email, telephone, and geo-location information and
+is not restricted to a physical address.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#siteAddress">org:siteAddress</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:Site">org:Site</a></td></tr>
+
+ </tbody>
+</table>
+</section>
+
+<!-- Property hasSite -->
+<section>
+<h5 id="org:hasSite">Property: hasSite</h5>
+<p>
+ Indicates a site at which the Organization has some presence even if
+ only indirect (e.g. virtual office or a professional service which is
+acting as the registered address for a company).
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasSite">org:hasSite</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Site">org:Site</a></td></tr>
+ <tr><td class="prop">inverseOf:</td><td><a href="#org:siteOf">org:siteOf</a></td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property siteOf -->
+<section>
+<h5 id="org:siteOf">Property: siteOf</h5>
+<p>
+ Indicates an Organization which has some presence at the given site.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#siteOf">org:siteOf</a></th></tr></thead>
+ <tbody>
+
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:Site">org:Site</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">inverseOf:</td><td><a href="#org:hasSite">org:hasSite</a></td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property hasPrimarySite -->
+<section>
+<h5 id="org:hasPrimarySite">Property: hasPrimarySite</h5>
+<p>
+ Indicates a primary site for the Organization, this is the default
+means by which an Organization can be contacted and is not necessarily
+the formal headquarters.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasPrimarySite">org:hasPrimarySite</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Site">org:Site</a></td></tr>
+ <tr><td class="prop">subPropertyOf:</td><td><a href="#org:hasSite">org:hasSite</a></td></tr>
+ </tbody>
+</table>
+</section>
+
+
+<!-- Property hasRegisteredSite -->
+<section>
+<h5 id="org:hasRegisteredSite">Property: hasRegisteredSite</h5>
+<p>
+ Indicates the legally registered site for the organization, in many
+legal jurisdictions there is a requirement that FormalOrganizations such
+ as Companies or Charities have such a primary designed site.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasRegisteredSite">org:hasRegisteredSite</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Site">org:Site</a></td></tr>
+ <tr><td class="prop">subPropertyOf:</td><td><a href="#org:hasPrimarySite">org:hasPrimarySite</a></td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property basedAt -->
+<section>
+<h5 id="org:basedAt">Property: basedAt</h5>
+<p>
+ Indicates the site at which a person is based. We do not restrict the possibility that a person is based at multiple sites.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#basedAt">org:basedAt</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Person">foaf:Person</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Site">org:Site</a></td></tr>
+ </tbody>
+</table>
+</section>
+</section> <!-- end of Class Site-->
+
+
+<!-- Property location -->
+<section id="property-location">
+<h4 id="org:location"><span class="secno">5.4.2 </span>Property: location</h4>
+<p>
+ Gives a location description for a person within the organization, for example a <em>Mail Stop</em> for internal posting purposes.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#location">org:location</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Person">foaf:Person</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2001/XMLSchema#String">xsd:string</a></td></tr>
+ </tbody>
+</table>
+</section>
+
+</section> <!-- End of LOCATION section -->
+
+
+<!-- Projects and other activities -->
+<section id="projects-and-other-activities">
+<h3><span class="secno">5.5 </span>Projects and other activities</h3>
+<!-- Class OrganizationalCollaboration -->
+<section id="class-organizationalcollaboration">
+ <h4 id="org:OrganizationalCollaboration"><span class="secno">5.5.1 </span>Class: OrganizationalCollaboration</h4>
+ <p>
+ A collaboration between two or more Organizations such as a project.
+ It meets the criteria for being an Organization in that it has an
+ identity and defining purpose independent of its particular members but
+ is neither a formally recognized legal entity nor a sub-unit within some
+ larger organization. Might typically have a shorter lifetime than the
+ Organizations within it, but not necessarily.
+ </p>
+ <table class="definition">
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#OrganizationalCollaboration">org:OrganizationalCollaboration</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">subClassOf:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ All members are <a href="#org:Organization">org:Organization</a>s rather than individuals and those Organizations can play particular roles within the venture. Alternative names: <em>Project</em>, <em>Venture</em>, <em>Endeavour</em>, <em>Consortium</em>
+ </td></tr>
+ </tbody>
+ </table>
+</section> <!-- End of OrganizationalCollaboration class -->
+
+</section> <!-- End of Projects and other activities -->
+
+
+<!-- Historical information -->
+<section id="historical-information">
+<h3><span class="secno">5.6 </span>Historical information</h3>
+
+<!-- Class ChangeEvent -->
+<section id="class-changeevent">
+<h4 id="org:ChangeEvent"><span class="secno">5.6.1 </span>Class: ChangeEvent</h4>
+<p>
+Represents an event which resulted in a major change to an
+organization such as a merger or complete restructuring. It is intended
+for situations where the resulting organization is sufficiently distinct
+from the original organizations that it has a distinct identity and
+distinct URI.
+</p>
+<table class="definition">
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">subClassOf:</td><td> <a href="http://www.w3.org/TR/prov-o/#Activity">prov:Activity</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+Extension vocabularies should define sub-classes of this
+to denote particular categories of event. The time period over which
+the event occurred should be expressed using
+<a href="http://www.w3.org/TR/prov-o/#startedAtTime">prov:startedAtTime</a>
+and
+<a href="http://www.w3.org/TR/prov-o/#endedAtTime">prov:endedAtTime</a>.
+A textual description of the event may be given by <a href="http://dublincore.org/documents/dcmi-terms/#terms-description">dct:description</a>.
+</td></tr>
+</tbody>
+</table>
+
+<!-- Property originalOrganization -->
+<section>
+<h5 id="org:originalOrganization">Property: originalOrganization</h5>
+<p>
+ Indicates one or more organizations that existed before the change
+event. Depending on the event they may or may not have continued to
+exist after the event.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#originalOrganization">org:originalOrganization</a></th></tr></thead>
+ <tbody>
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:ChangeEvent">org:ChangeEvent</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">inverseOf:</td><td><a href="#org:changedBy">org:changedBy</a></td></tr>
+ <tr><td class="prop">subpropertyOf:</td><td><a href="http://www.w3.org/TR/prov-o/#used">prov:used</a></td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property changedBy -->
+<section>
+<h5 id="org:changedBy">Property: changedBy</h5>
+<p>
+Indicates a change event which resulted in a change to this
+organization.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#changedBy">org:changedBy</a></th></tr></thead>
+ <tbody>
+
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:ChangeEvent">org:ChangeEvent</a></td></tr>
+ <tr><td class="prop">inverseOf:</td><td><a href="#org:originalOrganization">org:originalOrganization</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ Depending on the event the organization may or may not
+have continued to exist after the event.
+</td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property resultedFrom -->
+<section>
+<h5 id="org:resultedFrom">Property: resultedFrom</h5>
+<p>
+Indicates an event which resulted in (led to, generated) this
+organization.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#resultedFrom">org:resultedFrom</a></th></tr></thead>
+ <tbody>
+
+
+ <tr><td class="prop">Domain:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:ChangeEvent">org:ChangeEvent</a></td></tr>
+ <tr><td class="prop">subpropertyOf:</td><td><a href="http://www.w3.org/TR/prov-o/#wasGeneratedBy">prov:wasGeneratedBy</a></td></tr>
+ <tr><td class="prop">inverseOf:</td><td><a href="#org:resultingOrganization">org:resultingOrganization</a></td></tr>
+ </tbody>
+</table>
+</section>
+
+<!-- Property resultingOrganization -->
+<section>
+<h5 id="org:resultingOrganization">Property: resultingOrganization</h5>
+<p>
+Indicates an organization which was created or changed as a result of the event.
+</p>
+
+<table class="definition">
+ <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#resultingOrganization">org:resultingOrganization</a></th></tr></thead>
+ <tbody>
+ <tr><td class="prop">Domain:</td><td><a href="#org:ChangeEvent">org:ChangeEvent</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">inverseOf:</td><td><a href="#org:resultedFrom">org:resultedFrom</a></td></tr>
+ </tbody>
+</table>
+</section>
+
+<h4 id="wasDerivedFromAxiom">Property chain axiom</h4>
+<p>
+In addition the ontology defines the following relationship between
+<a href="#org:resultedFrom">org:resultedFrom</a>, <a href="#org:originalOrganization">org:originalOrganization</a>
+and <a href="http://www.w3.org/TR/prov-o/#wasDerivedFrom">prov:wasDerivedFrom</a>
+:
+</p><pre class="code"> SubObjectPropertyOf( ObjectPropertyChain( org:resultedFrom org:originalOrganization ) prov:wasDerivedFrom )
+</pre>
+
+</section> <!-- end of Class Role-->
+
+</section> <!-- end of Section Historical-->
+
+</section> <!-- end of ontology reference section -->
+
+<!-- ACK -->
+<section class="appendix" id="change-history">
+
+<!-- Change history -->
+
+<!--OddPage--><h2><span class="secno">A. </span>Change history</h2>
+
+<p>Changes since <a href="http://www.w3.org/TR/2012/WD-vocab-org-20121023/"><abbr title="World Wide Web Consortium">W3C</abbr>
+ Working Draft 23 October 2012 (Last Call)</a>:
+
+</p><ul>
+ <li>Added explicit declarations that <a href="#org:member">org:member</a> and <a href="#org:organization">org:organization</a> are functional properties. This is a clarification rather than an intended change of semantics.</li>
+ <li>Removed assertion that <a href="#org:Post">org:Post</a> is a sub
+ class of <a href="#org:Organization">org:Organization</a>, adding
+ an informative note that ORG applications are still free to declare
+ entities as being instances of both classes.</li>
+ <li>Added <a href="#wasDerivedFromAxiom">property chain axiom</a>
+ for <a href="http://www.w3.org/TR/prov-o/#wasDerivedFrom">prov:wasDerivedFrom</a>.</li>
+ <li>Removed the range constraint
+ on <a href="#org:siteAddress">org:siteAddress</a> to allow other
+ encodings than VCard to be used.</li>
+ <li>Added a statement
+ that <a href="#org:Organization">org:Organization</a> is equivalent
+ to the foaf:Organization class. This statement was present in the
+ ontology itself at the time of last call but not sufficiently clear
+ in this document.</li>
+ <li>Removed informative comment that the org:reportsTo graph is
+ acyclic, this is not necessarily the case.</li>
+</ul>
+
+<p>Changes since <a href="http://www.w3.org/TR/2012/WD-vocab-org-20120405/"><abbr title="World Wide Web Consortium">W3C</abbr> Working Draft 05 April 2012</a>:
+
+</p><ul>
+ <li>Modified <a href="#org:ChangeEvent">org:ChangeEvent</a>, <a href="#org:originalOrganization">org:originalOrganization</a> and
+<a href="#org:resultedFrom">org:resultedFrom</a> to extend the PROV-O
+vocabulary instead of OPMV.</li>
+ <li>Added <a href="#org:Post">org:Post</a> and associated properties.</li>
+ <li>Corrected description of <a href="#org:hasSubOrganiation">org:hasSubOrganiation</a>
+ and <a href="#org:subOrganizationOf">org:subOrganizationOf</a>.</li>
+ <li>Corrected domain of <a href="#org:remuneration">org:remuneration</a> to match ontology.</li>
+ <li>Corrected domain/range of <a href="#org:hasMember">org:hasMember</a> to match ontology.</li>
+ <li>Added missing entry for <a href="#org:memberOf">org:memberOf</a> to match
+ ontology.</li>
+ <li>Rephrasing and restructuring throughout the document to improve clarity.</li>
+</ul>
+
+
+<p>Changes since previous version 0.3 <a href="http://www.epimorphics.com/public/vocabulary/org-20100609.html">2010-06-09</a>:</p>
+<ul>
+ <li>Added <a href="#org:identifier">org:identifier</a> to support generic use of organization identifier schemes, including local and national schemes.</li>
+</ul>
+
+<p>Changes since previous version 0.2 <a href="http://www.epimorphics.com/public/vocabulary/org-20100607.html">2010-06-07</a>:</p>
+<ul>
+ <li>Added <a href="#org:changedBy">org:changedBy</a> and <a href="#org:resultingOrganization">org:resultingOrganization</a> as inverses to
+ the OMPV compatible properties and added a note on use of inverses.</li>
+</ul>
+
+<p>Changes since previous version 0.1 <a href="http://www.epimorphics.com/public/vocabulary/org-20100528.html">2010-05-28</a>:</p>
+<ul>
+ <li>Rephrased the introduction to clarify scoping of the ontology.</li>
+ <li>Made <a href="#org:Organization">org:Organization</a> equivalent to <code>foaf:Organization</code> following clarifying discussions with Dan Brickley.</li>
+ <li>Added <a href="#org:hasMember">org:hasMember</a> as an inverse of <a href="#org:memberOf">org:memberOf</a> in order to be able to declare the equivalent to <code>foaf:member</code>, thanks to Dan Brickley for the suggestion.</li>
+ <li>Made <a href="#org:unitOf">org:unitOf</a>/<a href="#org:hasUnit">org:hasUnit</a> sub properties of <a href="#org:subOrganizationOf">org:subOrganizationOf</a>/<a href="#org:hasSubOrganization">org:hasSubOrganization</a>, thanks to Dave Challis for prompting this clarification.
+ </li><li>Added <a href="#org:transitiveSubOrganizationOf">org:transitiveSubOrganizationOf</a>, thanks to Damian Steer for the suggestion.</li>
+ <li>Fixed range statements for <a href="#org:role">org:role</a> and <a href="#org:organization">org:organization</a> to correspond to the documentation and intent, thanks to Bernard Vatant for spotting that problem.</li>
+ <li>Modified description of <a href="#org:memberOf">org:memberOf</a> to clarify that the notion of membership is very broad and not meant to be limited to formal notions of membership.</li>
+ <li>Clarified the description of <a href="#org:FormalOrganization">org:FormalOrganization</a>.
+ </li><li>Fixed bug in restriction definition for <a href="#org:OrganizationalCollaboration">org:OrganizationalCollaboration</a>, thanks to Start Williams for point out the problem.</li>
+ <li>Reversed <a href="#org:resultingOrganization">org:resultingOrganization</a> to <a href="#org:resultedFrom">org:resultedFrom</a> for compatibility with OPMV, thanks to Jeni Tennison for pointing out the problem.</li>
+ <li>Changed labels for has* properties to read as nouns, leaving URIs unchanged.</li>
+ <li>Added <code>rdfs:isDefinedBy</code> declarations, thanks to Kingsley Idehen for pointing out the lack of those.</li>
+ <li>Clarified license terms, thanks to Dan Brickley for pointing out the lack.</li>
+</ul>
+
+</section>
+<section class="appendix" id="acknowledgements">
+<!--OddPage--><h2><span class="secno">B. </span>Acknowledgements</h2>
+<p>This ontology was originally developed for use by data.gov.uk as part of the UK Linked Data Kernel project
+under the leadership and guidance of John Sheridan (The National Archives).
+Jeni Tennison provided immensely useful feedback and suggestions on the first draft,
+which greatly improved its design. The work also took inspiration from a
+number of other ontologies, particularly the thoughtfully designed
+<a href="http://www.london-gazette.co.uk/ontology/organisation.owl">Gazette Organization ontology</a>
+and <a href="http://proton.semanticweb.org/">Proton-top</a>.
+</p>
+<p>
+The editor gratefully acknowledges comments and support from the
+Government Linked Data Working Group - particularly to Daniel Vila for
+transcribing the original documentation into <abbr title="World Wide Web Consortium">W3C</abbr> format and to Bart
+van Leeuwen for feedback and discussions that resulted in the addition
+of <code>org:Post</code>. </p>
+
+<p>The modelling of <code>org:Post</code> is
+closely based on the work of Jeni Tennison on modelling UK Government.
+</p>
+
+</section>
+
+
+<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">C. </span>References</h2><section id="normative-references"><h3><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-OWL-TIME">[OWL-TIME]</dt><dd>Feng Pan; Jerry R. Hobbs. <a href="http://www.w3.org/TR/2006/WD-owl-time-20060927"><cite>Time Ontology in OWL.</cite></a> 27 September 2006. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2006/WD-owl-time-20060927">http://www.w3.org/TR/2006/WD-owl-time-20060927</a>
+</dd><dt id="bib-OWL2-PRIMER">[OWL2-PRIMER]</dt><dd>Pascal Hitzler; Markus Krötzsch; Bijan Parsia; Peter F. Patel-Schneider; Sebastian Rudolph. <a href="http://www.w3.org/TR/2009/REC-owl2-primer-20091027/"><cite>OWL 2 Web Ontology Language:Primer.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-primer-20091027/">http://www.w3.org/TR/2009/REC-owl2-primer-20091027/</a>
+</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo, Satya Sahoo, Deborah McGuinness, <cite><a href="http://www.w3.org/TR/2012/WD-prov-o-20120724/">PROV-O: The PROV Ontology</a></cite>, W3C Working Draft 24 July 2012. URL: <a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a>
+</dd><dt id="bib-RDF-CONCEPTS">[RDF-CONCEPTS]</dt><dd>Graham Klyne; Jeremy J. Carroll. <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210"><cite>Resource Description Framework (RDF): Concepts and Abstract Syntax.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210">http://www.w3.org/TR/2004/REC-rdf-concepts-20040210</a>
+</dd><dt id="bib-RDF-SCHEMA">[RDF-SCHEMA]</dt><dd>Dan Brickley; Ramanathan V. Guha. <a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210"><cite>RDF Vocabulary Description Language 1.0: RDF Schema.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210">http://www.w3.org/TR/2004/REC-rdf-schema-20040210</a>
+</dd><dt id="bib-RDF-SPARQL-QUERY">[RDF-SPARQL-QUERY]</dt><dd>Andy Seaborne; Eric Prud'hommeaux. <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115"><cite>SPARQL Query Language for RDF.</cite></a> 15 January 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115">http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115</a>
+</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
+</dd><dt id="bib-SKOS-REFERENCE">[SKOS-REFERENCE]</dt><dd>Sean Bechhofer; Alistair Miles. <a href="http://www.w3.org/TR/2009/REC-skos-reference-20090818/"><cite>SKOS Simple Knowledge Organization System Reference.</cite></a> 18 August 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-skos-reference-20090818/">http://www.w3.org/TR/2009/REC-skos-reference-20090818/</a>
+</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd>David Beckett; Tim Berners-Lee. <a href="http://www.w3.org/TeamSubmission/turtle/"><cite>Turtle: Terse RDF Triple Language.</cite></a> January 2008. W3C Team Submission. URL: <a href="http://www.w3.org/TeamSubmission/turtle/">http://www.w3.org/TeamSubmission/turtle/</a>
+</dd><dt id="bib-VCARD">[VCARD]</dt><dd>R. Iannella; et al. <cite><a href="http://www.w3.org/TR/vcard-rdf/">Representing vCard Objects in RDF</a></cite>, January 2010. W3C Member Sumission 20 January 2010. URL: <a href="http://www.w3.org/Submission/2010/SUBM-vcard-rdf-20100120">http://www.w3.org/Submission/2010/SUBM-vcard-rdf-20100120</a>
+</dd></dl></section><section id="informative-references"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-DC11">[DC11]</dt><dd>Dublin Core metadata initiative. <a href="http://dublincore.org/documents/dcmi-terms/"><cite>Dublin Core metadata element set, version 1.1.</cite></a> July 1999. Dublin Core recommendation. URL: <a href="http://dublincore.org/documents/dcmi-terms/">http://dublincore.org/documents/dcmi-terms/</a>
+</dd><dt id="bib-FOAF">[FOAF]</dt><dd>Dan Brickley, Libby Miller. <a href="http://xmlns.com/foaf/spec/"><cite>FOAF Vocabulary Specification 0.98.</cite></a> 9 August 2010. URL: <a href="http://xmlns.com/foaf/spec/">http://xmlns.com/foaf/spec/</a>
+</dd><dt id="bib-GOOD-RELATIONS">[GOOD-RELATIONS]</dt><dd>Martin Hepp, <cite><a href="http://www.heppnetz.de/ontologies/goodrelations/v1.html">GoodRelations Language Reference</a></cite>, Version 1.0, 1 October 2011, URL: <a href="http://www.heppnetz.de/ontologies/goodrelations/v1.html">http://www.heppnetz.de/ontologies/goodrelations/v1.html</a>
+</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/"><cite>Constraints of the PROV Data Model</cite></a>. 12 March 2013, W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</a>
+</dd></dl></section></section></body></html>