Static snapshot of second proposed last draft
authorDave Reynolds <dave@epimorphics.com>
Sat, 06 Oct 2012 18:10:07 +0100
changeset 218 751155c13429
parent 217 e5420d8a200f
child 219 85312d579fee
Static snapshot of second proposed last draft
org/static.html
--- a/org/static.html	Sat Oct 06 17:51:02 2012 +0100
+++ b/org/static.html	Sat Oct 06 18:10:07 2012 +0100
@@ -500,16 +500,15 @@
 pre.sh_sourceCode .sh_attribute { color: #006400; }
 
 </style><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8"></head>
-<body style="display: inherit; "><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-editor-s-draft-01-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft 01 October 2012</h2><dl><dt>This version:</dt><dd><a href="https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html">https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html</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="https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html">https://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-20120405/">http://www.w3.org/TR/2012/WD-vocab-org-20120405/</a></dd><dt>Editor:</dt><dd><span>Dave Reynolds</span>, <a href="http://www.epimorphics.com/">Epimorphics Ltd.</a></dd>
+<body style="display: inherit; "><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-editor-s-draft-06-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft 06 October 2012</h2><dl><dt>This version:</dt><dd><a href="https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html">https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html</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="https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html">https://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-20120405/">http://www.w3.org/TR/2012/WD-vocab-org-20120405/</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> © 2012 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <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>
 
-
 <div id="abstract" class="introductory section"><h2>Abstract</h2>
 
 <p> This document describes a core ontology for organizational structures, aimed
-at supporting linked-data publishing of organizational information across
+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 organzations and roles, as well as extensions to support neighbouring information
+of organizations and roles, as well as extensions to support neighbouring information
 such as organizational activities.
 </p>
 </div><div id="sotd" class="introductory section"><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 <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p>
@@ -517,132 +516,63 @@
     developed <a href="http://www.epimorphics.com/public/vocabulary/org.html">
     and published</a> outside of <acronym title="World Wide Web Consortium">W3C</acronym>, 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 an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:[email protected]">[email protected]</a> (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-gld-wg/">archives</a>). All feedback is welcome.</p><p>Publication as an Editor's Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> 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 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="undefined" 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 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">2. </span>Conformance</a></li><li class="tocline"><a href="#namespaces-1" class="tocxref"><span class="secno">3. </span>Namespaces</a></li><li class="tocline"><a href="#overview-of-ontology" class="tocxref"><span class="secno">4. </span>Overview of ontology</a></li><li class="tocline"><a href="#notes-on-style" class="tocxref"><span class="secno">5. </span>Notes on style</a></li><li class="tocline"><a href="#organizational-structure" class="tocxref"><span class="secno">6. </span>Organizational structure</a><ul class="toc"><li class="tocline"><a href="#class--organization" class="tocxref"><span class="secno">6.1 </span>Class: Organization</a><ul class="toc"><li class="tocline"><a href="#property--suborganizationof" class="tocxref"><span class="secno">6.1.1 </span>Property: subOrganizationOf</a></li><li class="tocline"><a href="#property--transitivesuborganizationof" class="tocxref"><span class="secno">6.1.2 </span>Property: transitiveSubOrganizationOf</a></li><li class="tocline"><a href="#property--hassuborganization" class="tocxref"><span class="secno">6.1.3 </span>Property: hasSubOrganization</a></li><li class="tocline"><a href="#property--purpose" class="tocxref"><span class="secno">6.1.4 </span>Property: purpose</a></li><li class="tocline"><a href="#property--classification" class="tocxref"><span class="secno">6.1.5 </span>Property: classification</a></li><li class="tocline"><a href="#property--identifier" class="tocxref"><span class="secno">6.1.6 </span>Property: identifier</a></li><li class="tocline"><a href="#property--linkedto" class="tocxref"><span class="secno">6.1.7 </span>Property: linkedTo</a></li></ul></li><li class="tocline"><a href="#class--formalorganization" class="tocxref"><span class="secno">6.2 </span>Class: FormalOrganization</a></li><li class="tocline"><a href="#class--organizationalunit" class="tocxref"><span class="secno">6.3 </span>Class: OrganizationalUnit</a><ul class="toc"><li class="tocline"><a href="#property--hasunit" class="tocxref"><span class="secno">6.3.1 </span>Property: hasUnit</a></li><li class="tocline"><a href="#property--unitof" class="tocxref"><span class="secno">6.3.2 </span>Property: unitOf</a></li></ul></li><li class="tocline"><a href="#notes-on-formal-organizations" class="tocxref"><span class="secno">6.4 </span>Notes on formal organizations</a></li><li class="tocline"><a href="#notes-on-organizational-hierarchy" class="tocxref"><span class="secno">6.5 </span>Notes on organizational hierarchy</a></li><li class="tocline"><a href="#notes-on-organizational-classification" class="tocxref"><span class="secno">6.6 </span>Notes on organizational classification</a></li></ul></li><li class="tocline"><a href="#membership--roles--posts-and-reporting" class="tocxref"><span class="secno">7. </span>Membership, roles, posts and reporting</a><ul class="toc"><li class="tocline"><a href="#discussion" class="tocxref"><span class="secno">7.1 </span>Discussion</a></li><li class="tocline"><a href="#property--memberof" class="tocxref"><span class="secno">7.2 </span>Property: memberOf</a></li><li class="tocline"><a href="#property--hasmember" class="tocxref"><span class="secno">7.3 </span>Property: hasMember</a></li><li class="tocline"><a href="#property--headof" class="tocxref"><span class="secno">7.4 </span>Property: headOf</a></li><li class="tocline"><a href="#class--membership" class="tocxref"><span class="secno">7.5 </span>Class: Membership</a><ul class="toc"><li class="tocline"><a href="#property--member" class="tocxref"><span class="secno">7.5.1 </span>Property: member</a></li><li class="tocline"><a href="#property--organization" class="tocxref"><span class="secno">7.5.2 </span>Property: organization</a></li><li class="tocline"><a href="#property--role" class="tocxref"><span class="secno">7.5.3 </span>Property: role</a></li><li class="tocline"><a href="#property--hasmembership" class="tocxref"><span class="secno">7.5.4 </span>Property: hasMembership</a></li><li class="tocline"><a href="#property--memberduring" class="tocxref"><span class="secno">7.5.5 </span>Property: memberDuring</a></li></ul></li><li class="tocline"><a href="#class--role" class="tocxref"><span class="secno">7.6 </span>Class: Role</a><ul class="toc"><li class="tocline"><a href="#property--roleproperty" class="tocxref"><span class="secno">7.6.1 </span>Property: roleProperty</a></li><li class="tocline"><a href="#property--remuneration" class="tocxref"><span class="secno">7.6.2 </span>Property: remuneration</a></li></ul></li><li class="tocline"><a href="#class--post" class="tocxref"><span class="secno">7.7 </span>Class: Post</a><ul class="toc"><li class="tocline"><a href="#property--holds" class="tocxref"><span class="secno">7.7.1 </span>Property: holds</a></li><li class="tocline"><a href="#property--heldby" class="tocxref"><span class="secno">7.7.2 </span>Property: heldBy</a></li><li class="tocline"><a href="#property--postin" class="tocxref"><span class="secno">7.7.3 </span>Property: postIn</a></li><li class="tocline"><a href="#property--haspost" class="tocxref"><span class="secno">7.7.4 </span>Property: hasPost</a></li></ul></li><li class="tocline"><a href="#property--reportsto" class="tocxref"><span class="secno">7.8 </span>Property: reportsTo</a></li></ul></li><li class="tocline"><a href="#location" class="tocxref"><span class="secno">8. </span>Location</a><ul class="toc"><li class="tocline"><a href="#class--site" class="tocxref"><span class="secno">8.1 </span>Class: Site</a><ul class="toc"><li class="tocline"><a href="#property--siteaddress" class="tocxref"><span class="secno">8.1.1 </span>Property: siteAddress</a></li><li class="tocline"><a href="#property--hassite" class="tocxref"><span class="secno">8.1.2 </span>Property: hasSite</a></li><li class="tocline"><a href="#property--siteof" class="tocxref"><span class="secno">8.1.3 </span>Property: siteOf</a></li><li class="tocline"><a href="#property--hasprimarysite" class="tocxref"><span class="secno">8.1.4 </span>Property: hasPrimarySite</a></li><li class="tocline"><a href="#property--hasregisteredsite" class="tocxref"><span class="secno">8.1.5 </span>Property: hasRegisteredSite</a></li><li class="tocline"><a href="#property--basedat" class="tocxref"><span class="secno">8.1.6 </span>Property: basedAt</a></li></ul></li><li class="tocline"><a href="#property--location" class="tocxref"><span class="secno">8.2 </span>Property: location</a></li></ul></li><li class="tocline"><a href="#projects-and-other-activities" class="tocxref"><span class="secno">9. </span>Projects and other activities</a><ul class="toc"><li class="tocline"><a href="#class--organizationalcollaboration" class="tocxref"><span class="secno">9.1 </span>Class: OrganizationalCollaboration</a></li></ul></li><li class="tocline"><a href="#historical-information" class="tocxref"><span class="secno">10. </span>Historical information</a><ul class="toc"><li class="tocline"><a href="#class--changeevent" class="tocxref"><span class="secno">10.1 </span>Class: ChangeEvent</a><ul class="toc"><li class="tocline"><a href="#property--originalorganization" class="tocxref"><span class="secno">10.1.1 </span>Property: originalOrganization</a></li><li class="tocline"><a href="#property--changedby" class="tocxref"><span class="secno">10.1.2 </span>Property: changedBy</a></li><li class="tocline"><a href="#property--resultedfrom" class="tocxref"><span class="secno">10.1.3 </span>Property: resultedFrom</a></li><li class="tocline"><a href="#property--resultingorganization" class="tocxref"><span class="secno">10.1.4 </span>Property: resultingOrganization</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="#acknowledgments" class="tocxref"><span class="secno">B. </span>Acknowledgments</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></div>
+<p>This document was published by the <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:[email protected]">[email protected]</a> (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-gld-wg/">archives</a>). All feedback is welcome.</p><p>Publication as an Editor's Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> 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 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="undefined" 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 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" class="section"><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></div>
 
 
 
-<div class="introductory section">
-<h2 id="scope">Scope</h2>
-
-<p>
-This document is aimed at assisting government IT managers, procurement officers, Web developers, vendors, and researchers who are interested in publishing open government data using <acronym title="World Wide Web Consortium">W3C</acronym> standards.  The benefits of using international standards for data exchange is to significantly increase interoperability of data.
-</p>
-</div>
-
 
 <!--    INTRODUCTION    -->
-<div class="informative section" id="introduction">
-<!--OddPage--><h2><span class="secno">1. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
-<p>This document describes a core ontology for organizational
-  structures (ORG), aimed
-at supporting linked-data publishing of organizational information across
+
+<div class="introductory section">
+
+<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 organzations and roles, as well as extensions to support neighbouring information
+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 as RDFa,
-  or serialized as e.g. RDF/XML or Turtle. The examples in this
-  document use Turtle in the interests of readability.</p>
+  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" rel="biblioentry" href="#bib-TURTLE">TURTLE</a></cite>] in the interests of readability.</p>
 
 </div>
 
 
-<div id="conformance" class="section"><!--OddPage--><h2><span class="secno">2. </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" rel="biblioentry" 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 instead of ones defined
- in this vocabulary that could reasonably be used.</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:
-</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 URI sets 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>
-</ul>
-<p></p>
+<!-- Overview of ontology -->
 
-</div>
+<div class="informative section" id="overview-of-ontology">
+<!--OddPage--><h2><span class="secno">1. </span>Overview of ontology</h2><p><em>This section is non-normative.</em></p>
 
-<!-- Namespaces -->
-<div id="namespaces-1" class="section">
-<!--OddPage--><h2 id="ns"><span class="secno">3. </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></tr></thead>
-  <tbody>
-    
-    <tr><td>foaf</td><td>http://xmlns.com/foaf/0.1/</td></tr>
-    <tr><td>gr</td><td>http://purl.org/goodrelations/v1#</td></tr>  
-    <tr><td>opmv</td><td>http://purl.org/net/opmv/ns#</td></tr> 
-    <tr><td>org</td><td>http://www.w3.org/ns/org#</td></tr>
-    <tr><td>owlTime</td><td>http://www.w3.org/2006/time#</td></tr>
-    <tr><td>rdf</td><td>http://www.w3.org/1999/02/22-rdf-syntax-ns#</td></tr>
-    <tr><td>skos</td><td>http://www.w3.org/2004/02/skos/core#</td></tr>
-    <tr><td>vcard</td><td>http://www.w3.org/2006/vcard/ns#</td></tr>
-  </tbody>
-</table>
-</div>
-
-<!-- Overview of ontology -->
-<div class="informative section" id="overview-of-ontology">
-<!--OddPage--><h2><span class="secno">4. </span>Overview of ontology</h2><p><em>This section is non-normative.</em></p>
-
-
-<p>This ontology was original motivated by a need to publish information
-relating to government organizational structure as part of
-  the <em>data.gov.uk</em> initiative.
-The approach adopted was to develop a small, generic, reusable core
-ontology for organizational information and then let developers extend
-and specialize it to particular domains. </p> 
+<p>This ontology is designed to enable publication of information on
+  organizations and organizational structure 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 representation of:</p>
 <ul>
-  <li>organizational structure
+  <li><a href="#organizational_structure">organizational structure</a>
   <ul>
     <li>notion of an organization</li>
     <li>decomposition into sub-organizations and units</li>
-    <li>posts within an organization</li>
-    <li>purpose of an organization</li>
+    <li>purpose and classification of organizations</li>
   </ul>
   </li>
-  <li>reporting structure
+  <li><a href="#reporting_structure">reporting structure</a>
     <ul>
       <li>people reporting structure within an organization</li>
-      <li>roles, relationship between person and organization</li>
+      <li>roles, posts, and the relationship between people and organizations</li>
     </ul>
   </li>
-  <li>location information
+  <li><a href="#location_information">location information</a>
     <ul>
      <li>sites or buildings, locations within sites</li>
     </ul>
   </li>
-  <li>organizational history (merger, renaming, repurposing)</li>
+  <li><a href="#organizational_history">organizational history (merger, renaming)</a></li>
 </ul>
 
 <p>This coverage corresponds to the type of information typically
@@ -662,11 +592,16 @@
   controlled vocabularies to use for these concepts.
 </p>
 
-<img src="img/diagram.png" alt="Diagram dipicting core classes and relationships">
+<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>) unless an explicit prefix is
+  given. The namespaces for all referenced vocabularies are giving
+  in the section on <a href="#ns">Namespaces</a>.
 
+<img src="img/diagram.png" alt="Diagram depicting core classes and relationships">
 
-
-<h2 id="example">Example</h2>
+</p><div class="informative section" 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>
 
@@ -686,283 +621,59 @@
     org:postIn &lt;http://reference.data.gov.uk/id/department/co/unit/cabinet-office-communications&gt; ;
     org:heldBy &lt;#person161&gt; .
  </pre>
-
-</div>
-
-<div class="informative section" id="notes-on-style">
-<!--OddPage--><h2><span class="secno">5. </span>Notes on style</h2><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>
-</div>
-
-<!--    Organizational structure   -->
-<div id="organizational-structure" class="section">
-<!--OddPage--><h2><span class="secno">6. </span>Organizational structure</h2>
-
-<!-- Class Organization -->
-<div id="class--organization" class="section">
-<h3 id="Class:_Organization"><span class="secno">6.1 </span>Class: Organization</h3>
-<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>RDF 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">Usage note:</td><td> It is recommended 
-that SKOS lexical labels should be used to label the Organization. In 
-particular <code>skos:prefLabel</code> for the primary (e.g. legally
-	recognized name), <code>skos:altLabel</code> for alternative
-	names (trading names, colloquial names)
-	and <code>skos:notation</code> to denote codes from a code
-	list. Alternative names: <em>Collective</em>, <em>Body</em>, <em>Group</em>.</td></tr>
-  </tbody>
-</table>
-
-<!-- Property subOrganizationOf -->
-<div id="property--suborganizationof" class="section">
-<h4 id="Property:_subOrganizationOf"><span class="secno">6.1.1 </span>Property: subOrganizationOf</h4>
-<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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td> Inverse of <code>org:hasSubOrganization</code>. </td></tr>
-  </tbody>
-</table>
 </div>
 
-<!-- Property transitiveSubOrganizationOf -->
-<div id="property--transitivesuborganizationof" class="section">
-<h4 id="Property:_transitiveSubOrganizationOf"><span class="secno">6.1.2 </span>Property: transitiveSubOrganizationOf</h4>
-<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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-    <tr><td class="prop">Transitive super property of:</td><td><a href="http://www.w3.org/ns/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>
-</div>
-
-<!-- Property hasSubOrganization -->
-<div id="property--hassuborganization" class="section">
-<h4 id="Property:_hasSubOrganization"><span class="secno">6.1.3 </span>Property: hasSubOrganization</h4>
-<p>Represents hierarchical containment of Organizations or Organizational Units; 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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td> Inverse of <code>org:subOrganizationOf</code>.</td></tr>
-  </tbody>
-</table>
-</div>
-
-<!-- Property purpose -->
-<div id="property--purpose" class="section">
-<h4 id="Property:_purpose"><span class="secno">6.1.4 </span>Property: purpose</h4>
-<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="http://www.w3.org/ns/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 <code>skos:Concept</code>. 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 <code>org:purpose</code>. Alternative names: <em>remit</em>, <em>responsibility</em> (esp. if applied to OrganizationalUnits such as Government Departments).</td></tr>
-  </tbody>
-</table>
-</div>
-
-
-<!-- Property classification -->
-<div id="property--classification" class="section">
-<h4 id="Property:_classification"><span class="secno">6.1.5 </span>Property: classification</h4>
-<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 <code>org:Organization</code> as a means to represent
-  orgnanizational 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="http://www.w3.org/ns/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 <code>skos:ConceptScheme</code>
-</td></tr>
-  </tbody>
-</table>
 </div>
 
 
-<!-- Property identifier -->
-<div id="property--identifier" class="section">
-<h4 id="Property:_identifier"><span class="secno">6.1.6 </span>Property: identifier</h4>
-<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="http://www.w3.org/ns/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 identier 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 <code>skos:notation</code> of which this property is a specialization.
-</td></tr>
-  </tbody>
-</table>
-</div>
-
-<!-- Property linkedTo -->
-<div id="property--linkedto" class="section">
-<h4 id="Property:_linkedTo"><span class="secno">6.1.7 </span>Property: linkedTo</h4>
-<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="http://www.w3.org/ns/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>
-</div>
-
-</div> <!-- end of Class Organization-->
-
-<!-- Class FormalOrganization -->
-<div id="class--formalorganization" class="section">
-<h3 id="Class:_FormalOrganization"><span class="secno">6.2 </span>Class: FormalOrganization</h3>
-<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>RDF 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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td> 
-
-	Note that this is a super class of <code>gr:BusinessEntity</code> and it is recommended to use the GoodRelations vocabulary to denote Business classifications such as DUNS or NAICS.
-</td></tr>
-</tbody>
-</table>
-
-</div>  <!-- end of Class FormalOrganization-->
-
+<!-- Descriptive section -->
 
-<!-- Class OrganizationalUnit -->
-<div id="class--organizationalunit" class="section">
-<h3 id="Class:_OrganizationalUnit"><span class="secno">6.3 </span>Class: OrganizationalUnit</h3>
-<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>RDF 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="http://www.w3.org/ns/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 -->
-<div id="property--hasunit" class="section">
-<h4 id="Property:_hasUnit"><span class="secno">6.3.1 </span>Property: hasUnit</h4>
-<p>Indicates a unit which is part of this Organization, e.g. a Department within a larger FormalOrganization.</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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#OrganizationalUnit">org:OrganizationalUnit</a></td></tr>
-     <tr><td class="prop">subPropertyOf:</td><td> <a href="http://www.w3.org/ns/org#hasSubOrganization">org:hasSubOrganization</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td> 
-     Inverse of <code>org:unitOf</code>.
-</td></tr>
-  </tbody>
-</table>
-</div>
+<div id="description" class="section">
 
-<!-- Property unitOf -->
-<div id="property--unitof" class="section">
-<h4 id="Property:_unitOf"><span class="secno">6.3.2 </span>Property: unitOf</h4>
-<p>Indicates an Organization of which this Unit is a part, e.g. a 
-Department within a larger FormalOrganization.</p>
+<!--OddPage--><h2><span class="secno">2. </span>Description and commentary</h2>
 
-<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="http://www.w3.org/ns/org#OrganizationalUnit">org:OrganizationalUnit</a></td></tr>
-     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-     <tr><td class="prop">subPropertyOf:</td><td> <a href="http://www.w3.org/ns/org#subOrganizationOf">org:subOrganizationOf</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td> 
-     This is the inverse of <code>org:hasUnit</code>.
-</td></tr>
-  </tbody>
-</table>
-</div>
+<div id="organizational_structure" class="informative section">
+<h3><span class="secno">2.1 </span>Organizational structure</h3><p><em>This section is non-normative.</em></p>
 
-</div> <!-- end of Class OrganizationalUnit-->
+<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>
 
-<div class="informative section" id="notes-on-formal-organizations">
-<h3><span class="secno">6.4 </span>Notes on formal organizations</h3><p><em>This section is non-normative.</em></p>
-<p>Note that the subclass hierarchy
-   below <code>org:Organization</code> is not a full covering. There
-   can be <code>org:Organization</code>s which are in
-   neither <code>org:FormalOrganization</code>
-   nor in <code>org:OrganizationalUnit</code>.  Note also
-   that the containment hierarchy is completely open
-   - <code>org:FormalOrganization</code>s are free to contain
-   other <code>org:FormalOrganization</code>s (e.g. subsidiaries of
-   large corporations).</p>
-</div>
+<p>We distinguish a particular subclass 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>
 
-<div class="informative section" id="notes-on-organizational-hierarchy">
-<h3><span class="secno">6.5 </span>Notes on organizational hierarchy</h3><p><em>This section is non-normative.</em></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 complete, 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>
+
+<h4 id="organizational-hierarchy">Organizational hierarchy</h4>
 
 <p>In many organizations there is a hierarchy of unit structures. For example we might see a containment hierarchy like:</p>
 
@@ -972,15 +683,14 @@
       Function
 </pre>
 
-<p>Such hierarchies are specific to the organization, or class of
+<p>Such hierarchies are specific to the particular organization, or class of
   organization being modelled. Profiles of ORG may include
-  sub-classes of <code>org:OrganizationalUnit</code> to
+  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 <code>org:hasSubOrganization</code> to match the desired hierarchy.</p>
-</div>
+  of <a href="#org:hasSubOrganization">org:hasSubOrganization</a> to match the desired hierarchy.</p>
 
-<div class="informative section" id="notes-on-organizational-classification">
-<h3><span class="secno">6.6 </span>Notes on organizational classification</h3><p><em>This section is non-normative.</em></p>
+<h4 id="organizational-classification">Organizational classification</h4>
 
 <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.
@@ -988,33 +698,29 @@
 that can be used as a basis for classification.
 Alternatively organizations can be classified by the service they provide (e.g. Educational, Manufacturing, LegalService etc).</p>
 
-<p>The core organization ontology is neutral with respect to such choices.
-It is anticipated that profiles will either introduce
-subclasses of <code>org:Organization</code> or define a classification
-  scheme to use with the <code>org:classification</code>
-  property. </p>
+<p>ORG is neutral with respect to such choices.
+  It is anticipated that profiles will either introduce
+  subclasses 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" rel="biblioentry" href="#bib-SKOS-REFERENCE">SKOS-REFERENCE</a></cite>] concept scheme.</p>
 
-<p>Which of these mechanisms to use depends on the nature of the
-  profile. If the classification is not intrinsic to the organization
+<p>Which of these mechanisms to use depends on 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  <code>org:classification</code> should be used. If the
+  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 CharityNumbers so it would be better to represent a 
- Charity as a subClassOf <code>org:FormalOrganization</code> rather
+ Charity as a subClassOf <a href="#org:FormalOrganization">org:FormalOrganization</a> rather
   than via a taxonomic labelling.</p>
-</div>	
+
 </div>
 
-<!-- End of section Organizational structure -->
-
-<!--    Reporting relationships and roles   -->
-<div id="membership--roles--posts-and-reporting" class="section">
-<!--OddPage--><h2><span class="secno">7. </span>Membership, roles, posts and reporting</h2>
-
-<div class="informative section" id="discussion">
-<h3><span class="secno">7.1 </span>Discussion</h3><p><em>This section is non-normative.</em></p>
+<div id="reporting_structure" class="informative section">
+<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
@@ -1030,17 +736,17 @@
 
 <p>
 This simplest representation provided by ORG is to directly state that
-some individual (represented as a <code>foaf:Agent</code>) is <code>org:memberOf</code> of an organization. To represent
+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> of an organization. To represent
 specific roles that the person plays then ORG profiles may define
-sub-properties of <code>org:memberOf</code>. In particular, the notion
+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 <code>org:memberOf</code>, namely
-<code>org:headOf</code> for this purpose.</p>
+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">&lt;http://example.com/people#ceo&gt; 
-  org:headOf    &lt;http://example.com/org#id&gt; . 
+  org:headOf    &lt;http://example.com/org#id&gt;. 
 </pre>
 
 <h4 id="membership-n-ary-relationship">Membership n-ary relationship</h4>
@@ -1048,68 +754,94 @@
 <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 <code>org:Role</code> class. The situation of an Agent fulfilling that role within an organization
-is then expressed through instances of the <code>org:Membership</code> n-ary relation. This also
+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 relation. 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">&lt;http://example.com/org#id&gt; a org:FormalOrganization;
-    skos:prefLabel "Example Ltd" .
+    skos:prefLabel "Example Ltd".
 
 eg:ctoRole a org:Role;
-    rdfs:label "CTO" .
+    rdfs:label "CTO".
         
 [] a org:Membership;
-    org:member &lt;http://example.com/people#jo&gt; ;
-    org:organization &lt;http://example.com/org#id&gt; ;
+    org:member &lt;http://example.com/people#jo&gt;;
+    org:organization &lt;http://example.com/org#id&gt;;
     org:role eg:ctoRole;
-    org:memberDuring [a owlTime:Interval; owlTime:hasBeginning [
-                      owlTime:inXSDDateTime "2009-11-01T09:00:00Z"^^xsd:dateTime]] .
+    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" rel="biblioentry" 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
+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 <code>org:roleProperty</code> annotation. Thus we might extend the above example with:</p>
+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 .
+    org:roleProperty eg:ctoOf.
     
-eg:ctoOf a owl:ObjectProperty, rdf:Property ;
-    rdfs:label "CTO" ;
-    rdfs:subPropertyOf org:memberOf .
+eg:ctoOf a owl:ObjectProperty, rdf:Property;
+    rdfs:label "CTO";
+    rdfs:subPropertyOf org:memberOf.
         
 &lt;http://example.com/people#jo&gt; 
-  eg:ctoOf &lt;http://example.com/org#id&gt; . 
+  eg:ctoOf &lt;http://example.com/org#id&gt;. 
 </pre>
 
-<p>In practice we antipate tool chains generating the <code>org:Membership</code> instances
-and a simple closure rule being used to add any corresponding
-  short-cut specializations of <code>org:memberOf</code>.</p>
+<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>The third representation that is provided by ORG is that of
-  a <code>org:Post</code> which represents some position in the
+  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 <code>org:Post</code> can exist without someone holding that
-  post. In contrast, a <code>org:Membership</code> represents the relationship between
+</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>A <code>org:Post</code> is also defined as a sub-class
-  of <code>org:Organization</code> to allow for cases where a Post is
+<p>A <a href="#org:Post">org:Post</a> is also defined as a sub-class
+  of <a href="#org:Organization">org:Organization</a> to allow for cases where a Post is
   actually held by a group of people (whether as a timeshare, as a
   team or as a formal group such as a committee). </p>
 
-<p>A post can have an associated <code>org:Role</code>.</p>
+<p>A post can have an associated <a href="#org:Role">org:Role</a>.</p>
 
 <h4 id="relationship-between-posts-and-membership">Relationship between Posts and Membership</h4>
 
@@ -1117,64 +849,491 @@
   the situation and ORG profiles may specify that use of one of
   these is preferred. In cases where the structure of the organization is to be
   given, independently of the people within that
-  structure then <code>org:Post</code> is the appropriate
+  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 <code>org:Membership</code> is appropriate.</p>
+  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 entailment rules. We express these
-  as a sequence of SPARQL Construct operations:</p>
+  representations in the form of two more entailment rules:</p>
 
 <pre class="code">CONSTRUCT {
-  ?agent  org:memberOf ?org .
+  ?agent  org:memberOf ?org.
 } WHERE {
-  ?agent org:holds  ?post .
-  ?post  org:postIn ?org .
+  ?agent org:holds  ?post.
+  ?post  org:postIn ?org.
 }
+</pre>
 
-CONSTRUCT {
-    ?agent   org:memberOf  ?org .
-} WHERE {
-  [] a org:Membership;
-    org:member       ?agent ;
-    org:organization ?org .
-}
-
-CONSTRUCT {
+<pre class="code">CONSTRUCT {
   [] a org:Membership;
-    org:member       ?agent ;
+    org:member       ?agent;
     org:organization ?org;
-    org:role         ?role .
+    org:role         ?role.
 } WHERE {
-  ?agent org:holds  ?post .
-  ?post  org:postIn ?org .
-  ?post  org:role   ?role .
-}
-
-CONSTRUCT {
-    ?agent   ?roleprop  ?org .
-} WHERE {
-  [] a org:Membership;
-    org:member       ?agent ;
-    org:organization ?org;
-    org:role         [ org:roleProperty ?roleprop ] .
+  ?agent org:holds  ?post.
+  ?post  org:postIn ?org.
+  ?post  org:role   ?role.
 }
 </pre>
 
 </div>
 
+<div id="location_information" class="informative section">
+<h3><span class="secno">2.3 </span>Location information</h3><p><em>This section is non-normative.</em></p>
+
+<p>ORG represents information on locations at which organizations exist
+  through the notion an <a href="#org:Site">org:Site</a>, which can be
+  linked to an organization via <a href="#org:siteOf">org:siteOf</a>
+  and <a href="#org:hasSite">org:hasSite</a>. We can distinguish
+  primary sites (<a href="#org:hasPrimarySite">org:hasPrimarySite</a>)
+  and provide a specialization of
+  that (<a href="#org:hasRegisteredSite">org:hasRegisteredSite</a>)
+  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 the vCard [<cite><a class="bibref" rel="biblioentry" href="#bib-VCARD">VCARD</a></cite>] vocabulary.</p>
+
+</div>
+
+<div id="organizational_history" class="informative section">
+<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" rel="biblioentry" href="#bib-PROV-O">PROV-O</a></cite>].</p>
+
+<h5 id="note">Note</h5>
+
+<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>
+
+</div>
+
+<div class="informative section" 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>
+</div>
+
+</div> <!-- End of descriptive section -->
+
+<div id="conformance" class="section"><!--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" rel="biblioentry" 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>
+
+</div>
+
+<!-- Namespaces -->
+<div id="namespaces-1" class="section">
+<!--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" rel="biblioentry" 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" rel="biblioentry" 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" rel="biblioentry" 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" rel="biblioentry" 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" rel="biblioentry" 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" rel="biblioentry" 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" rel="biblioentry" 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" rel="biblioentry" 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" rel="biblioentry" 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" rel="biblioentry" href="#bib-DC11">DC11</a></cite>]</td></tr>
+  </tbody>
+</table>
+</div>
+
+
+<!-- Ontology section -->
+
+<div id="ontology_reference" class="section"> 
+<!--OddPage--><h2><span class="secno">5. </span>Ontology Reference</h2>
+
+<div id="ontology_index" class="section">
+<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>
+
+</div>
+
+<!--    Organizational structure   -->
+<div id="organizational-structure" class="section">
+<h3><span class="secno">5.2 </span>Organizational structure</h3>
+
+<!-- Class Organization -->
+<div id="class--organization" class="section">
+<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">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 -->
+<div class="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>
+</div>
+
+<!-- Property transitiveSubOrganizationOf -->
+<div class="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>
+</div>
+
+<!-- Property hasSubOrganization -->
+<div class="section">
+<h5 id="org:hasSubOrganization">Property: hasSubOrganization</h5>
+<p>Represents hierarchical containment of Organizations or Organizational Units; 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>
+</div>
+
+<!-- Property purpose -->
+<div class="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>
+</div>
+
+
+<!-- Property classification -->
+<div class="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>
+</div>
+
+
+<!-- Property identifier -->
+<div class="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>
+</div>
+
+<!-- Property linkedTo -->
+<div class="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>
+</div>
+
+</div> <!-- end of Class Organization-->
+
+<!-- Class FormalOrganization -->
+<div id="class--formalorganization" class="section">
+<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>
+
+</div>  <!-- end of Class FormalOrganization-->
+
+
+<!-- Class OrganizationalUnit -->
+<div id="class--organizationalunit" class="section">
+<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 -->
+<div class="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 FormalOrganization.</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>
+</div>
+
+<!-- Property unitOf -->
+<div class="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 FormalOrganization.</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>
+</div>
+
+</div> <!-- end of Class OrganizationalUnit-->
+
+</div>
+
+<!-- End of section Organizational structure -->
+
+<!--    Reporting relationships and roles   -->
+<div id="membership--roles--posts-and-reporting" class="section">
+<h3><span class="secno">5.3 </span>Membership, roles, posts and reporting</h3>
+
+
 <!-- Property memberOf -->
 <div id="property--memberof" class="section">
-<h3 id="Property:_memberOf"><span class="secno">7.2 </span>Property: memberOf</h3>
+<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 indended to cover related concepts such as
-	affilliation or other involvement in the
+	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.
@@ -1184,29 +1343,29 @@
   <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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-     <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#hasMember">org:hasMember</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>
 </div>
 
 <!-- Property hasMember -->
 <div id="property--hasmember" class="section">
-<h3 id="Property:_hasMember"><span class="secno">7.3 </span>Property: hasMember</h3>
+<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 <code>org:memberOf</code>, see that property for further clarification. 
+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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <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="http://www.w3.org/ns/org#memberOf">org:memberOf</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 <code>foaf:member</code>.
+     Provided for compatibility with <a href="http://xmlns.com/foaf/spec/#term_member">foaf:member</a>.
 </td></tr>
   </tbody>
 </table>
@@ -1214,7 +1373,7 @@
 
 <!-- Property headOf -->
 <div id="property--headof" class="section">
-<h3 id="Property:_headOf"><span class="secno">7.4 </span>Property: headOf</h3>
+<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.
@@ -1224,11 +1383,11 @@
   <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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-      <tr><td class="prop">subPropertyOf:</td><td><a href="http://www.w3.org/ns/org#memberOf">org:memberOf</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>
     <tr><td class="prop">Usage note:</td><td> 
      This will normally mean that they are the root
- of the <code>org:reportsTo</code> (acyclic) graph, though an organization may have more than one head.
+ of the <a href="#org:reportsTo">org:reportsTo</a> (acyclic) graph, though an organization may have more than one head.
 </td></tr>
   </tbody>
 </table>
@@ -1236,27 +1395,27 @@
 
 <!-- Class Membership -->
 <div id="class--membership" class="section">
-<h3 id="Class:_Membership"><span class="secno">7.5 </span>Class: Membership</h3>
+<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>RDF class:</th><th><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></th></tr></thead>
+  <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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr-->
+     <!--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 relation between an Agent, an Organization and a 
 Role. It is possible to directly indicate membership, independent of the
- specific Role, through use of the <code>org:memberOf</code> property.
+ specific Role, through use of the <a href="#org:memberOf">org:memberOf</a> property.
 </td></tr>
 </tbody>
 </table>
 
 
 <!-- Property member -->
-<div id="property--member" class="section">
-<h4 id="Property:_member"><span class="secno">7.5.1 </span>Property: member</h4>
+<div class="section">
+<h5 id="org:member">Property: member</h5>
 <p>
 	Indicates the Person (or other Agent including Organization) involved in the Membership relationship.
 </p>
@@ -1265,10 +1424,10 @@
   <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="http://www.w3.org/ns/org#Membership">org:Membership</a></td></tr>
+    <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">Usage note:</td><td> 
-     Inverse of <code>org:hasMembership</code>
+     Inverse of <a href="#org:hasMembership">org:hasMembership</a>
 </td></tr>
   </tbody>
 </table>
@@ -1277,8 +1436,8 @@
 
 
 <!-- Property organization -->
-<div id="property--organization" class="section">
-<h4 id="Property:_organization"><span class="secno">7.5.2 </span>Property: organization</h4>
+<div class="section">
+<h5 id="org:organization">Property: organization</h5>
 <p>
 	Indicates the organization in which the Agent is a member.
 </p>
@@ -1287,19 +1446,19 @@
   <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="http://www.w3.org/ns/org#Membership">org:Membership</a></td></tr>
-     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <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>
   </tbody>
 </table>
 </div>
 
 <!-- Property role -->
-<div id="property--role" class="section">
-<h4 id="Property:_role"><span class="secno">7.5.3 </span>Property: role</h4>
+<div class="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 <code>org:Post</code> to indicate the role that any holder
+	a <a href="#org:Post">org:Post</a> to indicate the role that any holder
 	of the Post plays.
 </p>
 
@@ -1307,16 +1466,16 @@
   <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="http://www.w3.org/ns/org#Membership">org:Membership</a>  <a href="http://www.w3.org/ns/org#Post">org:Post</a>)</td></tr>
-     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Role">org:Role</a></td></tr>
+    <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>
 </div>
 
 <!-- Property hasMembership -->
-<div id="property--hasmembership" class="section">
-<h4 id="Property:_hasMembership"><span class="secno">7.5.4 </span>Property: hasMembership</h4>
+<div class="section">
+<h5 id="org:hasMembership">Property: hasMembership</h5>
 <p>
 	Indicates a membership relationship that the Agent plays.
 </p>
@@ -1326,17 +1485,17 @@
   <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="http://www.w3.org/ns/org#Membership">org:Membership</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 <code>org:member</code>.
+      Inverse of <a href="#org:member">org:member</a>.
 </td></tr>
   </tbody>
 </table>
 </div>
 
 <!-- Property memberDuring -->
-<div id="property--memberduring" class="section">
-<h4 id="Property:_memberDuring"><span class="secno">7.5.5 </span>Property: memberDuring</h4>
+<div class="section">
+<h5 id="org:memberDuring">Property: memberDuring</h5>
 <p>
 	Optional property to indicate the interval for which the membership is/was valid.
 </p>
@@ -1346,8 +1505,8 @@
   <tbody>
    
    
-     <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></td></tr>
-      <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2006/time#Interval">owlTime:Interval</a></td></tr>
+     <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>
@@ -1357,15 +1516,15 @@
 
 <!-- Class Role -->
 <div id="class--role" class="section">
-<h3 id="Class:_Role"><span class="secno">7.6 </span>Class: Role</h3>
+<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 <code>org:Membership</code>. 
+organization use an instance of <a href="#org:Membership">org:Membership</a>. 
 </p>
 <table class="definition">
-  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Role">org:Role</a></th></tr></thead>
+  <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> 
@@ -1379,10 +1538,10 @@
 </table>
 
 <!-- Property roleProperty -->
-<div id="property--roleproperty" class="section">
-<h4 id="Property:_roleProperty"><span class="secno">7.6.1 </span>Property: roleProperty</h4>
+<div class="section">
+<h5 id="org:roleProperty">Property: roleProperty</h5>
 <p>
-	This is a metalevel property which is used to annotate an <code>org:Role</code> instance with a sub-property of <code>org:memberOf</code>
+	This is a metalevel property which is used to annotate an <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>
 
@@ -1390,7 +1549,7 @@
   <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="http://www.w3.org/ns/org#Role">org:Role</a></td></tr>
+    <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 
@@ -1403,8 +1562,8 @@
 </div>
 
 <!-- Property remuneration -->
-<div id="property--remuneration" class="section">
-<h4 id="Property:_remuneration"><span class="secno">7.6.2 </span>Property: remuneration</h4>
+<div class="section">
+<h5 id="org:remuneration">Property: remuneration</h5>
 <p>
 	Indicates a salary or other reward associated with the role. 
 </p>
@@ -1412,10 +1571,10 @@
 <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="http://www.w3.org/ns/org#Role">org:Role</a></td></tr>
+     <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 <code>gr:PriceSpecification</code> but the range is left open to allow applications to specialize it (e.g. to remunerationInGBP).
+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>
@@ -1427,7 +1586,7 @@
 
 <!-- Class Post -->
 <div id="class--post" class="section">
-<h3 id="Class:_Post"><span class="secno">7.7 </span>Class: Post</h3>
+<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
@@ -1439,77 +1598,77 @@
       a organization in its own right.
 </p>
 <table class="definition">
-  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Post">org:Post</a></th></tr></thead>
+  <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#Post">org:Post</a></th></tr></thead>
   <tbody>
-     <tr><td class="prop">subClassOf:</td><td> <a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <tr><td class="prop">subClassOf:</td><td> <a href="#org:Organization">org:Organization</a></td></tr>
 </tbody>
 </table>
 
 <!-- Property holds -->
-<div id="property--holds" class="section">
-<h4 id="Property:_holds"><span class="secno">7.7.1 </span>Property: holds</h4>
+<div class="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="http://www.w3.org/ns/org#Post">org:Post</a></td></tr>
-     <tr><td class="prop">subPropertyOf:</td><td> <a href="http://www.w3.org/ns/org#memberOf">org:memberOf</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 <code>org:heldBy</code>.
+     Inverse of <a href="#org:heldBy">org:heldBy</a>.
 </td></tr>
   </tbody>
 </table>
 </div>
 
 <!-- Property heldBy -->
-<div id="property--heldby" class="section">
-<h4 id="Property:_heldBy"><span class="secno">7.7.2 </span>Property: heldBy</h4>
+<div class="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="http://www.w3.org/ns/org#Post">org:Post</a></td></tr>
+    <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="http://www.w3.org/ns/org#hasMember">org:hasMember</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 <code>org:holds</code>.
+     Inverse of <a href="#org:holds">org:holds</a>.
 </td></tr>
   </tbody>
 </table>
 </div>
 
 <!-- Property postIn -->
-<div id="property--postin" class="section">
-<h4 id="Property:_postIn"><span class="secno">7.7.3 </span>Property: postIn</h4>
+<div class="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="http://www.w3.org/ns/org#Post">org:Post</a></td></tr>
-    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <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 <code>org:hasPost</code>.
+     Inverse of <a href="#org:hasPost">org:hasPost</a>.
 </td></tr>
   </tbody>
 </table>
 </div>
 
 <!-- Property hasPost -->
-<div id="property--haspost" class="section">
-<h4 id="Property:_hasPost"><span class="secno">7.7.4 </span>Property: hasPost</h4>
+<div class="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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Post">org:Post</a></td></tr>
+    <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 <code>org:postIn</code>.
+     Inverse of <a href="#org:postIn">org:postIn</a>.
 </td></tr>
   </tbody>
 </table>
@@ -1519,7 +1678,7 @@
 
 <!-- Property reportsTo -->
 <div id="property--reportsto" class="section">
-<h3 id="Property:_reportsTo"><span class="secno">7.8 </span>Property: reportsTo</h3>
+<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
@@ -1531,9 +1690,9 @@
   <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="http://www.w3.org/ns/org#Post">org:Post</a>) </td></tr>
+    <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="http://www.w3.org/ns/org#Post">org:Post</a>) </td></tr>
+    <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
@@ -1551,19 +1710,19 @@
 
 <!--    LOCATION   -->
 <div id="location" class="section">
-<!--OddPage--><h2><span class="secno">8. </span>Location</h2>
+<h3><span class="secno">5.4 </span>Location</h3>
 
 
 <!-- Class Site -->
 <div id="class--site" class="section">
-<h3 id="Class:_Site"><span class="secno">8.1 </span>Class: Site</h3>
+<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>RDF class:</th><th><a href="http://www.w3.org/ns/org#Site">org:Site</a></th></tr></thead>
+  <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> 
@@ -1577,8 +1736,8 @@
 </table>
 
 <!-- Property siteAddress -->
-<div id="property--siteaddress" class="section">
-<h4 id="Property:_siteAddress"><span class="secno">8.1.1 </span>Property: siteAddress</h4>
+<div class="section">
+<h5 id="org:siteAddress">Property: siteAddress</h5>
 <p>
 	Indicates a VCard (using the http://www.w3.org/TR/vcard-rdf/ 
 vocabulary) for the site. This can include email, telephone, and 
@@ -1589,7 +1748,7 @@
   <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="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
+    <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="http://www.w3.org/2006/vcard/ns#VCard">vcard:VCard</a></td></tr>
     
   </tbody>
@@ -1597,8 +1756,8 @@
 </div>
 
 <!-- Property hasSite -->
-<div id="property--hassite" class="section">
-<h4 id="Property:_hasSite"><span class="secno">8.1.2 </span>Property: hasSite</h4>
+<div class="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 
@@ -1609,16 +1768,16 @@
   <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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
-    <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#siteOf">org:siteOf</a></td></tr>
+    <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>
 </div>
 
 <!-- Property siteOf -->
-<div id="property--siteof" class="section">
-<h4 id="Property:_siteOf"><span class="secno">8.1.3 </span>Property: siteOf</h4>
+<div class="section">
+<h5 id="org:siteOf">Property: siteOf</h5>
 <p>
 	Indicates an Organization which has some presence at the given site. 
 </p>
@@ -1628,16 +1787,16 @@
   <tbody>
    
     
-    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
-    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-    <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#hasSite">org:hasSite</a></td></tr>
+    <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>
 </div>
 
 <!-- Property hasPrimarySite -->
-<div id="property--hasprimarysite" class="section">
-<h4 id="Property:_hasPrimarySite"><span class="secno">8.1.4 </span>Property: hasPrimarySite</h4>
+<div class="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 
@@ -1648,17 +1807,17 @@
   <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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
-    <tr><td class="prop">subPropertyOf:</td><td><a href="http://www.w3.org/ns/org#hasSite">org:hasSite</a></td></tr>
+    <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>
 </div>
 
 
 <!-- Property hasRegisteredSite -->
-<div id="property--hasregisteredsite" class="section">
-<h4 id="Property:_hasRegisteredSite"><span class="secno">8.1.5 </span>Property: hasRegisteredSite</h4>
+<div class="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
@@ -1669,16 +1828,16 @@
   <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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
-    <tr><td class="prop">subPropertyOf:</td><td><a href="http://www.w3.org/ns/org#hasPrimarySite">org:hasPrimarySite</a></td></tr>
+    <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>
 </div>
 
 <!-- Property basedAt -->
-<div id="property--basedat" class="section">
-<h4 id="Property:_basedAt"><span class="secno">8.1.6 </span>Property: basedAt</h4>
+<div class="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>
@@ -1688,7 +1847,7 @@
   <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/ns/org#Site">org:Site</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="#org:Site">org:Site</a></td></tr>
   </tbody>
 </table>
 </div>
@@ -1697,7 +1856,7 @@
 
 <!-- Property location -->
 <div id="property--location" class="section">
-<h3 id="Property:_location"><span class="secno">8.2 </span>Property: location</h3>
+<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>
@@ -1717,10 +1876,10 @@
 
 <!--   Projects and other activities   -->
 <div id="projects-and-other-activities" class="section">
-<!--OddPage--><h2><span class="secno">9. </span>Projects and other activities</h2>
+<h3><span class="secno">5.5 </span>Projects and other activities</h3>
 <!-- Class OrganizationalCollaboration -->
 <div id="class--organizationalcollaboration" class="section">
-	<h3 id="Class:_OrganizationalCollaboration"><span class="secno">9.1 </span>Class: OrganizationalCollaboration</h3>
+	<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 
@@ -1730,11 +1889,11 @@
 	Organizations within it, but not necessarily.
 	</p>
 	<table class="definition">
-	  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#OrganizationalCollaboration">org:OrganizationalCollaboration</a></th></tr></thead>
+	  <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="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+	     <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 <code>org:Organization</code>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>
+	 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>
@@ -1745,20 +1904,11 @@
 
 <!--   Historical information   -->
 <div id="historical-information" class="section">
-<!--OddPage--><h2><span class="secno">10. </span>Historical information</h2>
-
-<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 and we need some vocabulary to describe that change over time
-and the relationship between the original and resulting resources. 
-The Event mechanism here gives a generic hook for this, building upon the 
-<a href="http://open-biomed.sourceforge.net/opmv/ns">OPMV Provenance Vocabulary</a>.</p>
+<h3><span class="secno">5.6 </span>Historical information</h3>
 
 <!-- Class ChangeEvent -->
 <div id="class--changeevent" class="section">
-<h3 id="Class:_ChangeEvent"><span class="secno">10.1 </span>Class: ChangeEvent</h3>
+<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 
@@ -1767,21 +1917,24 @@
 distinct URI. 
 </p>
 <table class="definition">
-  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></th></tr></thead>
+  <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://purl.org/net/opmv/ns#Process">opmv:Process</a></td></tr>
+     <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 instant or interval at 
-which the event occurred should be given by <code>opmv:wasGeneratedAt</code>, a 
-description should be given by <code>dct:description</code>.
+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 -->
-<div id="property--originalorganization" class="section">
-<h4 id="Property:_originalOrganization"><span class="secno">10.1.1 </span>Property: originalOrganization</h4>
+<div class="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 
@@ -1792,21 +1945,17 @@
   <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="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
-     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-     <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#changedBy">org:changedBy</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td> 
-      Note that in 
-specializing the OPMV vocabulary we are treating an <code>org:Organization</code> 
-as an <code>opmv:Artifact</code>, which is consistent with the OPM model.
-</td></tr>
+    <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="#org:changedBy">prov:used</a></td></tr>
   </tbody>
 </table>
 </div>
 
 <!-- Property changedBy -->
-<div id="property--changedby" class="section">
-<h4 id="Property:_changedBy"><span class="secno">10.1.2 </span>Property: changedBy</h4>
+<div class="section">
+<h5 id="org:changedBy">Property: changedBy</h5>
 <p>
 Indicates a change event which resulted in a change to this 
 organization. 
@@ -1817,9 +1966,9 @@
   <tbody>
    
     
-     <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
-     <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#originalOrganzation">org:originalOrganzation</a></td></tr>
+     <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.
@@ -1829,8 +1978,8 @@
 </div>
 
 <!-- Property resultedFrom -->
-<div id="property--resultedfrom" class="section">
-<h4 id="Property:_resultedFrom"><span class="secno">10.1.3 </span>Property: resultedFrom</h4>
+<div class="section">
+<h5 id="org:resultedFrom">Property: resultedFrom</h5>
 <p>
 Indicates an event which resulted in (led to, generated) this 
 organization.
@@ -1841,22 +1990,17 @@
   <tbody>
    
     
-     <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
-     <tr><td class="prop">subpropertyOf:</td><td><a href="http://purl.org/net/opmv/ns#wasGeneratedBy">opmv:wasGeneratedBy</a></td></tr>
-     <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#resultingOrganization">org:resultingOrganization</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td> 
-    Note that in 
-specializing the OPMV vocabulary we are treating an <code>org:Organization</code> 
-as an <code>opmv:Artifact</code>, which is consistent with the OPM model.
-</td></tr>
+     <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>
 </div>
 
 <!-- Property resultingOrganization -->
-<div id="property--resultingorganization" class="section">
-<h4 id="Property:_resultingOrganization"><span class="secno">10.1.4 </span>Property: resultingOrganization</h4>
+<div class="section">
+<h5 id="org:resultingOrganization">Property: resultingOrganization</h5>
 <p>
 Indicates an organization which was created or changed as a result of the event.
 </p>
@@ -1864,17 +2008,19 @@
 <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="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
-     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
-     <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#resultedFrom">org:resultedFrom</a></td></tr>
+     <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>
 </div>
 
 </div>  <!-- end of Class Role-->
 
+</div>  <!-- end of Section Historical-->
 
-</div>  <!-- end of Section Historical-->
+</div>  <!-- end of ontology reference section -->
+
 <!--    ACK   -->
 <div class="appendix section" id="change-history">
 
@@ -1884,49 +2030,52 @@
 <p>Changes since <a href="http://www.w3.org/TR/2012/WD-vocab-org-20120405/"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 05 April 2012</a>:
 
 </p><ul>
-  <li>Added <code>org:Post</code> and associated properties.</li>
-  <li>Corrected description of <code>org:hasSubOrganiation</code>
-  and <code>org:subOrganizationOf</code>.</li>
-  <li>Corrected domain of <code>org:remuneration</code> to match ontology.</li>
-  <li>Corrected domain/range of <code>org:hasMember</code> to match ontology.</li>
-  <li>Added missing entry for <code>org:memberOf</code> to match
+  <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 reordering throughout the document to improve clarity.</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 <code>org:identifier</code> to support generic use of organization identifier schemes, including local and national schemes.</li>
+  <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 <code>org:changedBy</code> and <code>org:resultingOrganization</code> as inverses to
+  <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 <code>org:Organization</code> equivalent to <code>foaf:Organization</code> following clarifying discussions with Dan Brickley.</li>
-  <li>Added <code>org:hasMember</code> as an inverse of <code>org:memberOf</code> in order to be able to declare the equivalent to <code>foaf:member</code>, thanks to Dan Brickley for the suggestion.</li>
-  <li>Made <code>org:unitOf/hasUnit</code> sub properties of <code>org:subOrganizationOf/hasSubOrganization</code>, thanks to Dave Challis for prompting this clarification.
-  </li><li>Added <code>org:transitiveSubOrganizationOf</code>, thanks to Damian Steer for the suggestion.</li>
-  <li>Fixed range statements for <code>org:role</code> and <code>org:organization</code> to correspond to the documentation and intent, thanks to Bernard Vatant for spotting that problem.</li>
-  <li>Modified description of <code>org:memberOf</code> 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 <code>org:FormalOrganization</code>.
-  </li><li>Fixed bug in restriction definition for <code>org:OrganizationalCollaboration</code>, thanks to Start Williams for point out the problem.</li>
-  <li>Reversed <code>org:resultingOrganization</code> to <code>org:resultedFrom</code> for compatibility with OPMV, thanks to Jeni Tennison for pointing out the problem.</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>
 
 </div>
-<div class="appendix section" id="acknowledgments">
-<!--OddPage--><h2><span class="secno">B. </span>Acknowledgments</h2>
-<p>This ontology was originally developed as part of the UK Linked Data Kernel project
+<div class="appendix section" 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
@@ -1939,15 +2088,26 @@
 Government Linked Data Working group - particularly to Daniel Vila for
 transcribing the original documentation into <acronym title="World Wide Web Consortium">W3C</acronym> format and to Bart
 van Leeuwen for feedback and discussions that resulted in the addition
-of <code>org:Post</code>. The modelling of <code>org:Post</code> is
+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>
 
 </div>
 
 
-<div id="references" class="appendix section"><!--OddPage--><h2><span class="secno">C. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography"><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></dl></div><div id="informative-references"
-		     class="section"><h3><span class="secno">C.2 </span>Informative
-      references</h3><p>No informative
-      references.</p></div></div></body></html>
+<div id="references" class="appendix section"><!--OddPage--><h2><span class="secno">C. </span>References</h2><div id="normative-references" class="section"><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. (Work in progress.) 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></div><div id="informative-references" class="section"><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></dl></div></div></body></html>