Static version of proposal Last Call ORG for review
authorDave Reynolds <dave@epimorphics.com>
Mon, 01 Oct 2012 09:44:58 +0100
changeset 205 cbe0644b17e1
parent 204 2b6f7a0d0794
child 206 9d49239dda2b
Static version of proposal Last Call ORG for review
org/static.html
--- a/org/static.html	Mon Oct 01 09:21:48 2012 +0100
+++ b/org/static.html	Mon Oct 01 09:44:58 2012 +0100
@@ -1,9 +1,14 @@
-<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML+RDFa 1.1//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd'>
+<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
 <html lang="en" dir="ltr">
 <head>
 	<title>An organization ontology</title>
-	<meta name="description" content="Best Practices for Publishing Linked Data" /> 
-	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+	<meta name="description" content="An organization ontology">
+	<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+	
+	
+	
+		
+	
 	 <style type="text/css">
 	  table {
 	    border-collapse:collapse;
@@ -29,7 +34,6 @@
 		line-height: 1.1em;
 	 }
 	</style>
-	<link rel="stylesheet" type="text/css" href="local-style.css">
 <style type="text/css">
 /*****************************************************************
  * ReSpec CSS
@@ -495,12 +499,12 @@
 pre.sh_sourceCode .sh_paren { color: red; }
 pre.sh_sourceCode .sh_attribute { color: #006400; }
 
-</style><link charset="utf-8" type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD"></head>
-<body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" width="72" height="48"></a></p><h1 class="title" id="title">An organization ontology</h1><h2 id="w3c-working-draft-05-april-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 05 April 2012</h2><dl><dt>This 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>Latest published version:</dt><dd><a href="http://www.w3.org/TR/vocab-org/">http://www.w3.org/TR/vocab-org/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/gld/raw-file/default/org/static.html">http://dvcs.w3.org/hg/gld/raw-file/default/org/static.html</a></dd><dt>Editor:</dt><dd><span>Dave Reynolds</span>, <a href="http://www.epimorphics.com/">Epimorphics Ltd.</a></dd>
+</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>
 </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 class="introductory section" id="abstract"><h2>Abstract</h2>
+<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
@@ -509,8 +513,11 @@
 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>
-This ontology was originally 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 with this publication is now on the Recommendation Track, being further developed as necessary by the GLD Working Group.
-<p>This document was published by the <a href="http://www.w3.org/2011/gld/">Government Linked Data (GLD) Working Group</a> as a First Public Working Draft. This document is intended to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. 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-comments/">archives</a>). All feedback is welcome.</p><p>Publication as a Working 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="http://www.w3.org/2004/01/pp-impl/47663/status" 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 class="section" id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#introduction"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a class="tocxref" href="#conformance"><span class="secno">2. </span>Conformance</a></li><li class="tocline"><a class="tocxref" href="#namespaces-1"><span class="secno">3. </span>Namespaces</a></li><li class="tocline"><a class="tocxref" href="#overview-of-ontology"><span class="secno">4. </span>Overview of ontology</a></li><li class="tocline"><a class="tocxref" href="#design-notes"><span class="secno">5. </span>Design notes</a></li><li class="tocline"><a class="tocxref" href="#notes-on-style"><span class="secno">6. </span>Notes on style</a></li><li class="tocline"><a class="tocxref" href="#organizational-structure"><span class="secno">7. </span>Organizational structure</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#class--organization"><span class="secno">7.1 </span>Class: Organization</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#property--suborganizationof"><span class="secno">7.1.1 </span>Property: subOrganizationOf</a></li><li class="tocline"><a class="tocxref" href="#property--transitivesuborganizationof"><span class="secno">7.1.2 </span>Property: transitiveSubOrganizationOf</a></li><li class="tocline"><a class="tocxref" href="#property--hassuborganization"><span class="secno">7.1.3 </span>Property: hasSubOrganization</a></li><li class="tocline"><a class="tocxref" href="#property--purpose"><span class="secno">7.1.4 </span>Property: purpose</a></li><li class="tocline"><a class="tocxref" href="#property--hasunit"><span class="secno">7.1.5 </span>Property: hasUnit</a></li><li class="tocline"><a class="tocxref" href="#property--unitof"><span class="secno">7.1.6 </span>Property: unitOf</a></li><li class="tocline"><a class="tocxref" href="#property--classification"><span class="secno">7.1.7 </span>Property: classification</a></li><li class="tocline"><a class="tocxref" href="#property--identifier"><span class="secno">7.1.8 </span>Property: identifier</a></li><li class="tocline"><a class="tocxref" href="#property--linkedto"><span class="secno">7.1.9 </span>Property: linkedTo</a></li></ul></li><li class="tocline"><a class="tocxref" href="#class--formalorganization"><span class="secno">7.2 </span>Class: FormalOrganization</a></li><li class="tocline"><a class="tocxref" href="#class--organizationalunit"><span class="secno">7.3 </span>Class: OrganizationalUnit</a></li><li class="tocline"><a class="tocxref" href="#notes-on-formal-organizations"><span class="secno">7.4 </span>Notes on formal organizations</a></li><li class="tocline"><a class="tocxref" href="#notes-on-organizational-hierarchy"><span class="secno">7.5 </span>Notes on organizational hierarchy</a></li><li class="tocline"><a class="tocxref" href="#notes-on-organizational-classification"><span class="secno">7.6 </span>Notes on organizational classification</a></li></ul></li><li class="tocline"><a class="tocxref" href="#reporting-relationships-and-roles"><span class="secno">8. </span>Reporting relationships and roles</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#class--membership"><span class="secno">8.1 </span>Class: Membership</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#property--member"><span class="secno">8.1.1 </span>Property: member</a></li><li class="tocline"><a class="tocxref" href="#property--organization"><span class="secno">8.1.2 </span>Property: organization</a></li><li class="tocline"><a class="tocxref" href="#property--role"><span class="secno">8.1.3 </span>Property: role</a></li><li class="tocline"><a class="tocxref" href="#property--hasmembership"><span class="secno">8.1.4 </span>Property: hasMembership</a></li><li class="tocline"><a class="tocxref" href="#property--memberduring"><span class="secno">8.1.5 </span>Property: memberDuring</a></li><li class="tocline"><a class="tocxref" href="#property--remuneration"><span class="secno">8.1.6 </span>Property: remuneration</a></li></ul></li><li class="tocline"><a class="tocxref" href="#class--role"><span class="secno">8.2 </span>Class: Role</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#property--roleproperty"><span class="secno">8.2.1 </span>Property: roleProperty</a></li></ul></li><li class="tocline"><a class="tocxref" href="#property--hasmember"><span class="secno">8.3 </span>Property: hasMember</a></li><li class="tocline"><a class="tocxref" href="#property--reportsto"><span class="secno">8.4 </span>Property: reportsTo</a></li><li class="tocline"><a class="tocxref" href="#property--headof"><span class="secno">8.5 </span>Property: headOf</a></li><li class="tocline"><a class="tocxref" href="#discussion"><span class="secno">8.6 </span>Discussion</a></li></ul></li><li class="tocline"><a class="tocxref" href="#location"><span class="secno">9. </span>Location</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#class--site"><span class="secno">9.1 </span>Class: Site</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#property--siteaddress"><span class="secno">9.1.1 </span>Property: siteAddress</a></li><li class="tocline"><a class="tocxref" href="#property--hassite"><span class="secno">9.1.2 </span>Property: hasSite</a></li><li class="tocline"><a class="tocxref" href="#property--siteof"><span class="secno">9.1.3 </span>Property: siteOf</a></li><li class="tocline"><a class="tocxref" href="#property--hasprimarysite"><span class="secno">9.1.4 </span>Property: hasPrimarySite</a></li><li class="tocline"><a class="tocxref" href="#property--hasregisteredsite"><span class="secno">9.1.5 </span>Property: hasRegisteredSite</a></li><li class="tocline"><a class="tocxref" href="#property--basedat"><span class="secno">9.1.6 </span>Property: basedAt</a></li></ul></li><li class="tocline"><a class="tocxref" href="#property--location"><span class="secno">9.2 </span>Property: location</a></li></ul></li><li class="tocline"><a class="tocxref" href="#projects-and-other-activities"><span class="secno">10. </span>Projects and other activities</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#class--organizationalcollaboration"><span class="secno">10.1 </span>Class: OrganizationalCollaboration</a></li></ul></li><li class="tocline"><a class="tocxref" href="#historical-information"><span class="secno">11. </span>Historical information</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#class--changeevent"><span class="secno">11.1 </span>Class: ChangeEvent</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#property--originalorganization"><span class="secno">11.1.1 </span>Property: originalOrganization</a></li><li class="tocline"><a class="tocxref" href="#property--changedby"><span class="secno">11.1.2 </span>Property: changedBy</a></li><li class="tocline"><a class="tocxref" href="#property--resultedfrom"><span class="secno">11.1.3 </span>Property: resultedFrom</a></li><li class="tocline"><a class="tocxref" href="#property--resultingorganization"><span class="secno">11.1.4 </span>Property: resultingOrganization</a></li></ul></li></ul></li><li class="tocline"><a class="tocxref" href="#change-history"><span class="secno">A. </span>Change history</a></li><li class="tocline"><a class="tocxref" href="#acknowledgments"><span class="secno">B. </span>Acknowledgments</a></li><li class="tocline"><a class="tocxref" href="#references"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#normative-references"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></div>
+This ontology was originally
+    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>
 
 
 
@@ -520,30 +527,67 @@
 <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>
-<p>
-Readers of this document are expected to be familiar with delivery of content via the Web, and to have a general familiarity with the technologies involved, but are not required to have a background in semantic technologies or previous experience with Linked Data. Data stewards, curators, database administrators and other personnel involved in Open Government initiatives are encouraged to read this Linked Open Data Best Practices document. 
-</p></div>
+</div>
 
 
 <!--    INTRODUCTION    -->
-<div id="introduction" class="informative section">
+<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 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 simply because of Turtle's readability.</p>
+<p>This document describes a core ontology for organizational
+  structures (ORG), 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
+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>
 
 </div>
 
 
-<div class="section" id="conformance"><!--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 title="must" class="rfc2119">must</em>, <em title="must not" class="rfc2119">must not</em>, <em title="required" class="rfc2119">required</em>, <em title="should" class="rfc2119">should</em>, <em title="should not" class="rfc2119">should not</em>, <em title="recommended" class="rfc2119">recommended</em>, <em title="may" class="rfc2119">may</em>, and <em title="optional" class="rfc2119">optional</em> in this specification are to be interpreted as described in [<cite><a href="#bib-RFC2119" rel="biblioentry" class="bibref">RFC2119</a></cite>].</p>
+<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>
 
-<ul>
-<li><i>ORG compliance</i> means that a provider uses a subset of the ORG vocabulary when publishing catalog and dataset metadata. This is likely to be the common case.</li>
-<li><i>ORG conformance</i> means that a provider uses the entire ORG vocabulary when publishing catalog and dataset metadata.</li>
+<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>
+
 </div>
 
 <!-- Namespaces -->
-<div class="section" id="namespaces-1">
+<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
@@ -566,33 +610,38 @@
 </div>
 
 <!-- Overview of ontology -->
-<div id="overview-of-ontology" class="informative section">
+<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.
-We felt that the best approach was to develop a small, generic, reusable core
+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>The ontology gives minimal basic terms to support representation of:</p>
+<p>The ontology gives terms to support representation of:</p>
 <ul>
-  <li>organizational structure</li>
-    <ul>
-      <li>notion of an organization</li>
-      <li>decomposition into sub-organizations and units</li>
-      <li>purpose of an organization</li>
-    </ul>
-  <li>reporting structure</li>
+  <li>organizational structure
+  <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>
+  </ul>
+  </li>
+  <li>reporting structure
     <ul>
       <li>people reporting structure within an organization</li>
       <li>roles, relationship between person and organization</li>
     </ul>
-  <li>location information</li>
+  </li>
+  <li>location information
     <ul>
      <li>sites or buildings, locations within sites</li>
     </ul>
+  </li>
   <li>organizational history (merger, renaming, repurposing)</li>
 </ul>
 
@@ -607,7 +656,10 @@
 type, organization purpose or roles. Different domains will have different
 requirements for classification of such concepts. Instead the ontology 
 provides just the core base concepts needed to allow extensions to add specific
-sub-class structures or classification schemes as required. 
+sub-class structures or classification schemes as required. Users of
+  the ontology are encouraged to define <strong>profiles</strong>
+  which strengthen interoperability by specifying particular
+  controlled vocabularies to use for these concepts.
 </p>
 
 <img src="img/diagram.png" alt="Diagram dipicting core classes and relationships">
@@ -615,108 +667,37 @@
 
 
 <h2 id="example">Example</h2>
-<p>This example provides a quick overview of how dcat might be used to an organization </p>
+<p>This example illustrates a small fragment of the organizational
+  structure of the UK Cabinet Office:</p>
 
-<p>@@@ TODO.jse: Actually provide an example @@@</p>
-<!--
-<p>First, the catalog description:
-</p>
-<pre>  &nbsp;:catalog
-       a dcat:Catalog&nbsp;;
-       dct:title "Imaginary catalog"&nbsp;;
-       rdfs:label "Imaginary catalog"&nbsp;;
-       foaf:homepage &lt;<a href="http://example.org/catalog" class="external free" title="http://example.org/catalog" rel="nofollow">http://example.org/catalog</a>&gt;&nbsp;;
-       dct:publisher&nbsp;:transparency-office&nbsp;;
-       dcat:themes&nbsp;:themes&nbsp;;
-       dct:language "en"^^xsd:language&nbsp;;
-       dcat:dataset&nbsp;:dataset/001&nbsp;;
-       .
-</pre>
-<p>The publisher of the catalog has the relative URI&nbsp;:transparency-office. Further description of the publisher can be provided as in the following example:
-</p>
-<pre>  &nbsp;:transparency-office
-       a foaf:Agent&nbsp;;
-       rdfs:label "Transparency Office"&nbsp;;
-       .
-</pre>
-<p>The catalog classify its datasets according to a set of domains represented by the relative URI&nbsp;:themes. SKOS can be used to describe the domains used:
-</p>
-<pre>  &nbsp;:themes
-       a skos:ConceptScheme&nbsp;;
-       skos:prefLabel "A set of domains to classify documents"&nbsp;;
-   .
-</pre>
-<p>The catalog connect to each of its datasets via dcat:dataset. In the example above, an example dataset was mentioned with the relative URI&nbsp;:dataset/001. A possible description of it using dcat is shown below:
-</p>
-<pre>  &nbsp;:dataset/001
-       a       dcat:Dataset&nbsp;;
-       dct:title "Imaginary dataset"&nbsp;;
-       dcat:keyword "accountability","transparency" ,"payments"&nbsp;;
-       dcat:theme&nbsp;:themes/accountability&nbsp;;
-       dct:issued "2011-12-05"^^xsd:date&nbsp;;
-       dct:updated "2011-12-05"^^xsd:date&nbsp;;
-       dct:publisher&nbsp;:agency/finance-ministry&nbsp;;
-       dct:accrualPeriodicity "every six months"&nbsp;;
-       dct:language "en"^^xsd:language&nbsp;;
-       dcat:Distribution&nbsp;:dataset/001/csv&nbsp;;
-       .
-</pre>
-<p>Notice that this dataset is classified under the domain represented by the relative URI&nbsp;:themes/accountability. This should be part of the domains set identified by the URI&nbsp;:themes that was used to describe the catalog domains. An example SKOS description
-</p>
-<pre>   &nbsp;:themes/accountability 
-        a skos:Concept&nbsp;;
-        skos:inScheme&nbsp;:themes&nbsp;;
-        skos:prefLabel "Accountability"&nbsp;;
-        .
-</pre>
-<p>The dataset can be downloaded in CSV format via the distribution represented by&nbsp;:dataset/001/csv.
-</p>
-<pre>  &nbsp;:dataset/001/csv
-       a dcat:Distribution&nbsp;;
-       dcat:accessURL &lt;<a href="http://www.example.org/files/001.csv" class="external free" title="http://www.example.org/files/001.csv" rel="nofollow">http://www.example.org/files/001.csv</a>&gt;&nbsp;;
-       dct:title "CSV distribution of imaginary dataset 001"&nbsp;;
-       dct:format [
-            a dct:IMT; 
-            rdf:value "text/csv"; 
-            rdfs:label "CSV"
-       ]
-       .
-</pre>
-<p>Finally, if the catalog publisher decides to keep metadata describing its records (i.e. the records containing metadata describing the datasets) dcat:CatalogRecord can be used. For example,&nbsp;:dataset/001 was issued on 2011-12-05. however, its description on Imaginary Catalog was added on 2011-12-11. This can be represented by dcat:
-</p>
-<pre>  &nbsp;:record/001
-       a dcat:CatalogRecord&nbsp;;
-       foaf:primaryTopic&nbsp;:dataset/001&nbsp;;
-       dct:issued "2011-12-11"^^xsd:date&nbsp;;
-   .
-  &nbsp;:catalog
-       dcat:record&nbsp;:record/001&nbsp;;
-   .
-</pre>
-<a name="Encoding_of_property_values" id="Encoding_of_property_values"></a><h2> <span class="mw-headline"> Encoding of property values </span></h2>
-<ul><li> Values like "unknown" or "unspecified" should never be used, and if present in the original database should be filtered for publishing. Instead, the property should simply be omitted.
-</li><li> @@@ policy for using resources vs. literals
-</li></ul>
--->
-</div>
+<pre>&lt;http://reference.data.gov.uk/id/department/co&gt; 
+    rdf:type org:Organization , central-government:Department;
+    skos:prefLabel "Cabinet Office" ;
+    org:hasUnit &lt;http://reference.data.gov.uk/id/department/co/unit/cabinet-office-communications&gt; .
+    
+&lt;http://reference.data.gov.uk/id/department/co/unit/cabinet-office-communications&gt; 
+    rdf:type org:OrganizationalUnit ;
+    skos:prefLabel "Cabinet Office Communications" ;
+    org:unitOf  &lt;http://reference.data.gov.uk/id/department/co&gt; ;
+    org:hasPost &lt;http://reference.data.gov.uk/id/department/co/post/246&gt; .
 
-<div id="design-notes" class="informative section">
-<!--OddPage--><h2><span class="secno">5. </span>Design notes</h2><p><em>This section is non-normative.</em></p>
-
-  <p>For background to the approach taken in developing the ontology see: 
-    <a href="http://www.epimorphics.com/web/category/category/developers/organization-ontology">blog notes</a></p>
+&lt;http://reference.data.gov.uk/id/department/co/post/246&gt; 
+    skos:prefLabel "Deputy Director, Deputy Prime Minister's Spokesperson/Head of Communications" . 
+    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>
 
-<div id="notes-on-style" class="informative section">
-<!--OddPage--><h2><span class="secno">6. </span>Notes on style</h2><p><em>This section is non-normative.</em></p>
-
-<p><em>Use of inverses:</em> authorities differ on whether providing pairs of inverse relationships between
+<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 storage or use of run-time inference.
+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>
 
@@ -729,12 +710,12 @@
 </div>
 
 <!--    Organizational structure   -->
-<div class="section" id="organizational-structure">
-<!--OddPage--><h2><span class="secno">7. </span>Organizational structure</h2>
+<div id="organizational-structure" class="section">
+<!--OddPage--><h2><span class="secno">6. </span>Organizational structure</h2>
 
 <!-- Class Organization -->
-<div class="section" id="class--organization">
-<h3 id="Class:_Organization"><span class="secno">7.1 </span>Class: Organization</h3>
+<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 
@@ -746,30 +727,34 @@
      <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>Org</em> <em>Group</em>.</td></tr>
-
-   
+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 class="section" id="property--suborganizationof">
-<h4 id="Property:_subOrganizationOf"><span class="secno">7.1.1 </span>Property: subOrganizationOf</h4>
-<p>Represents hierarchical containment of Organizations or Organizational Units; indicates an organization which is a sub-part or child of this organization.</p>
+<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>. Alternative names: subOrgOf.</td></tr>
+    <tr><td class="prop">Usage note:</td><td> Inverse of <code>org:hasSubOrganization</code>. </td></tr>
   </tbody>
 </table>
 </div>
 
 <!-- Property transitiveSubOrganizationOf -->
-<div class="section" id="property--transitivesuborganizationof">
-<h4 id="Property:_transitiveSubOrganizationOf"><span class="secno">7.1.2 </span>Property: transitiveSubOrganizationOf</h4>
-<p>Represents hierarchical containment of Organizations or Organizational Units; indicates an organization which is a sub-part or child of this organization.</p>
+<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>
@@ -782,22 +767,22 @@
 </div>
 
 <!-- Property hasSubOrganization -->
-<div class="section" id="property--hassuborganization">
-<h4 id="Property:_hasSubOrganization"><span class="secno">7.1.3 </span>Property: hasSubOrganization</h4>
-<p>Represents hierarchical containment of Organizations or OrganizationalUnits; indicates an Organization which contains this Organization.</p>
+<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>. Alternative names: hasSubOrg.</td></tr>
+    <tr><td class="prop">Usage note:</td><td> Inverse of <code>org:subOrganizationOf</code>.</td></tr>
   </tbody>
 </table>
 </div>
 
 <!-- Property purpose -->
-<div class="section" id="property--purpose">
-<h4 id="Property:_purpose"><span class="secno">7.1.4 </span>Property: purpose</h4>
+<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">
@@ -807,59 +792,21 @@
     <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 specializations or application profiles of this 
-vocabulary will constrain the range of the purpose. Alternative names: <em>remit</em> <em>responsibility</em> (esp. if applied to OrganizationalUnits such as Government Departments).</td></tr>
-  </tbody>
-</table>
-</div>
-
-<!-- Property hasUnit -->
-<div class="section" id="property--hasunit">
-<h4 id="Property:_hasUnit"><span class="secno">7.1.5 </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>
+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 unitOf -->
-<div class="section" id="property--unitof">
-<h4 id="Property:_unitOf"><span class="secno">7.1.6 </span>Property: unitOf</h4>
-<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="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>
 
 <!-- Property classification -->
-<div class="section" id="property--classification">
-<h4 id="Property:_classification"><span class="secno">7.1.7 </span>Property: classification</h4>
+<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 class="todo">@@TODO: Make clear what is the status of this property</p>
-This property is under discussion and may be revised or removed - in 
-many cases organizations are best categorized by defining a sub-class 
-hierarchy in an extension vocabulary.<p></p>
+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>
@@ -877,11 +824,10 @@
 
 
 <!-- Property identifier -->
-<div class="section" id="property--identifier">
-<h4 id="Property:_identifier"><span class="secno">7.1.8 </span>Property: identifier</h4>
+<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. Many different 
-national and international identier schemes are available.</p>
+ 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>
@@ -890,8 +836,8 @@
     <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> 
-      The org 
-ontology is neutral to which schemes are used. The particular identifier
+       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.
@@ -901,8 +847,8 @@
 </div>
 
 <!-- Property linkedTo -->
-<div class="section" id="property--linkedto">
-<h4 id="Property:_linkedTo"><span class="secno">7.1.9 </span>Property: linkedTo</h4>
+<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">
@@ -921,8 +867,8 @@
 </div> <!-- end of Class Organization-->
 
 <!-- Class FormalOrganization -->
-<div class="section" id="class--formalorganization">
-<h3 id="Class:_FormalOrganization"><span class="secno">7.2 </span>Class: FormalOrganization</h3>
+<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 
@@ -944,46 +890,79 @@
 
 
 <!-- Class OrganizationalUnit -->
-<div class="section" id="class--organizationalunit">
-<h3 id="Class:_OrganizationalUnit"><span class="secno">7.3 </span>Class: OrganizationalUnit</h3>
+<div id="class--organizationalunit" class="section">
+<h3 id="Class:_OrganizationalUnit"><span class="secno">6.3 </span>Class: OrganizationalUnit</h3>
 <p>
-An Organization such University Support Unit which is part of some 
-larger FormalOrganization and only has full recognition within the 
-context of that FormalOrganization, it is not a Legal Entity in its own 
-right.
+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 ot	her Units and even 
-FormalOrganizations. Alternative names: <em>OU</em> <em>Unit</em> <em>Department</em>
+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>
+
+<!-- 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>
+
+<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> <!-- end of Class OrganizationalUnit-->
 
-<div id="notes-on-formal-organizations" class="informative section">
-<h3><span class="secno">7.4 </span>Notes on formal organizations</h3><p><em>This section is non-normative.</em></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 <code>org:OrganizationalUnit</code>.  The distinction between
-   an externally recognized organization and one which only has
-   meaning in the context of a larger organization is a common one
-   which we support to simplify the mapping to existing practice. Note
+   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). We invite feedback from users of the ontology as to
-   whether this distinction useful in practice.</p>
+   large corporations).</p>
 </div>
 
-<div id="notes-on-organizational-hierarchy" class="informative section">
-<h3><span class="secno">7.5 </span>Notes on organizational hierarchy</h3><p><em>This section is non-normative.</em></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>In many organizations there is a hierarchy of unit structures. For example we might see a containment hierarchy like:</p>
 
@@ -993,13 +972,15 @@
       Function
 </pre>
 
-<p>The intention is that this would be added in custom extensions since they are specific to the 
-organization at hand. This can easily be done by subclassing <code>org:OrganizationalUnit</code>, 
-specializing <code>org:hasSubOrganization</code> and/or using <code>owl:allValuesFrom</code> restrictions on the new subclasses.</p>
+<p>Such hierarchies are specific to the organization, or class of
+  organization being modelled. Profiles of ORG may include
+  sub-classes of <code>org:OrganizationalUnit</code> to
+  represent such structures and specialize or restrict the use
+  of <code>org:hasSubOrganization</code> to match the desired hierarchy.</p>
 </div>
 
-<div id="notes-on-organizational-classification" class="informative section">
-<h3><span class="secno">7.6 </span>Notes on organizational classification</h3><p><em>This section is non-normative.</em></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>
 
 <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.
@@ -1008,293 +989,65 @@
 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 applications to particular domains will introduce
-subclasses of <code>org:Organization</code> to reflect the domain requirements. </p>
+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>Note that the core supports labelling an organization according to some 
-external classification scheme through use of the <code>org:classification</code> property. 
-This is appropriate for cases where the labelling is not intrinsic to the organization
- and doesn't affect other aspects of the modelling. 
- This is not always appropriate. 
+<p>Which of these mechanisms to use depends on the nature of the
+  profile. 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
+  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 FormalOrganization rather than via a taxonomic labelling.</p>
+ Charity as a subClassOf <code>org:FormalOrganization</code> rather
+  than via a taxonomic labelling.</p>
 </div>	
 </div>
 
 <!-- End of section Organizational structure -->
 
 <!--    Reporting relationships and roles   -->
-<div class="section" id="reporting-relationships-and-roles">
-<!--OddPage--><h2><span class="secno">8. </span>Reporting relationships and roles</h2>
-
-
-<!-- Class Membership -->
-<div class="section" id="class--membership">
-<h3 id="Class:_Membership"><span class="secno">8.1 </span>Class: Membership</h3>
-<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>
-  <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> 
-
-	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.
-</td></tr>
-</tbody>
-</table>
-
-
-<!-- Property member -->
-<div class="section" id="property--member">
-<h4 id="Property:_member"><span class="secno">8.1.1 </span>Property: member</h4>
-<p>
-	Indicates the Person (or other Agent including Organization) involved in the Membership relationship.
-</p>
-
-<table class="definition">
-  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#member">org:member</a></th></tr></thead>
-  <tbody>
-   
-    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/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>
-</td></tr>
-  </tbody>
-</table>
-</div>
-
-
-
-<!-- Property organization -->
-<div class="section" id="property--organization">
-<h4 id="Property:_organization"><span class="secno">8.1.2 </span>Property: organization</h4>
-<p>
-	Indicates Organization in which the Agent is a member.
-</p>
-
-<table class="definition">
-  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#organization">org:organization</a></th></tr></thead>
-  <tbody>
-   
-    <tr><td class="prop">Domain:</td><td><a href="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>
-  </tbody>
-</table>
-</div>
-
-<!-- Property role -->
-<div class="section" id="property--role">
-<h4 id="Property:_role"><span class="secno">8.1.3 </span>Property: role</h4>
-<p>
-	Indicates the Role that the Agent plays in a Membership relationship with an Organization.
-</p>
-
-<table class="definition">
-  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#role">org:role</a></th></tr></thead>
-  <tbody>
-   
-    <tr><td class="prop">Domain:</td><td><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#Role">org:Role</a></td></tr>
-    
-  </tbody>
-</table>
-</div>
-
-<!-- Property hasMembership -->
-<div class="section" id="property--hasmembership">
-<h4 id="Property:_hasMembership"><span class="secno">8.1.4 </span>Property: hasMembership</h4>
-<p>
-	Indicates a membership relationship that the Agent plays.
-</p>
-
-<table class="definition">
-  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasMembership">org:hasMembership</a></th></tr></thead>
-  <tbody>
-   
-    <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
-     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td> 
-      Inverse of <code>org:member</code>.
-</td></tr>
-  </tbody>
-</table>
-</div>
-
-<!-- Property memberDuring -->
-<div class="section" id="property--memberduring">
-<h4 id="Property:_memberDuring"><span class="secno">8.1.5 </span>Property: memberDuring</h4>
-<p>
-	Optional property to indicate the interval for which the membership is/was valid.
-</p>
-
-<table class="definition">
-  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#memberDuring">org:memberDuring</a></th></tr></thead>
-  <tbody>
-   
-   
-     <tr><td class="prop">Domain:</td><td><a href="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>
-    
-  </tbody>
-</table>
-</div>
-
-<!-- Property remuneration -->
-<div class="section" id="property--remuneration">
-<h4 id="Property:_remuneration"><span class="secno">8.1.6 </span>Property: remuneration</h4>
-<p>
-	Indicates a salary or other reward associated with the role. 
-</p>
+<div id="membership--roles--posts-and-reporting" class="section">
+<!--OddPage--><h2><span class="secno">7. </span>Membership, roles, posts and reporting</h2>
 
-<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#Membership">org:Membership</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).
-</td></tr> 
-    
-  </tbody>
-</table>
-</div>
-
-
-</div>  <!-- end of Class Membership-->
+<div class="informative section" id="discussion">
+<h3><span class="secno">7.1 </span>Discussion</h3><p><em>This section is non-normative.</em></p>
 
-<!-- Class Role -->
-<div class="section" id="class--role">
-<h3 id="Class:_Role"><span class="secno">8.2 </span>Class: Role</h3>
-<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>. 
-</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>
-  <tbody>
-     <tr><td class="prop">subClassOf:</td><td> <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td> 
-It is 
-common for roles to be arranged in some taxonomic structure and we use 
-SKOS to represent that. The normal SKOS lexical properties should be 
-used when labelling the Role. Additional descriptive properties for the 
-Role, such as a Salary band, may be added by extension vocabularies.
-</td></tr>
-</tbody>
-</table>
+<p>ORG provides a number of ways to represent the relationship between
+  people and organizations, together with the internal reporting
+  structure of an organization. Experience with early versions of the
+  ontology demonstrated that there is no "one size that fits
+  all". In some cases a very simple direct representation is preferred
+  for ease of consumption. In other cases a more complex
+  representation is needed to capture the nuances of the situation.
+  An ORG profile may specify that a particular subset of these
+  mechanisms be used.</p>
 
-<!-- Property roleProperty -->
-<div class="section" id="property--roleproperty">
-<h4 id="Property:_roleProperty"><span class="secno">8.2.1 </span>Property: roleProperty</h4>
-<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>
- that can be used to directly indicate the role for easy of query.
-</p>
+<h4 id="direct-membership-relation">Direct membership relation</h4>
 
-<table class="definition">
-  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#roleProperty">org:roleProperty</a></th></tr></thead>
-  <tbody>
-   
-    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Role">org:Role</a></td></tr>
-    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property">rdf:Property</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td> 
-      The 
-intended semantics is a Membership relation involving the Role implies 
-the existence of a direct property relationship through an inference 
-rule of the form:  <code>{ [] org:member ?p; org:organization ?o; org:role [org:roleProperty ?r] } -&gt; {?p ?r ?o}</code>
-</td></tr>
-  </tbody>
-</table>
-</div>
-
-</div>  <!-- end of Class Role-->
-
-
-<!-- Property hasMember -->
-<div class="section" id="property--hasmember">
-<h3 id="Property:_hasMember"><span class="secno">8.3 </span>Property: hasMember</h3>
 <p>
-	Indicates a person who is a member of the subject Organization. 
-Inverse of `org:memberOf`, 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://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">Equivalent property:</td><td><a href="http://xmlns.com/foaf/0.1/member">foaf:member</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td> 
-     Provided for compatibility with `foaf:member`.
-</td></tr>
-  </tbody>
-</table>
-</div>
-
-<!-- Property reportsTo -->
-<div class="section" id="property--reportsto">
-<h3 id="Property:_reportsTo"><span class="secno">8.4 </span>Property: reportsTo</h3>
-<p>
-	Indicates a reporting relationship as might be depicted on an 
-organizational chart.
-</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
+specific roles that the person plays then ORG profiles may define
+sub-properties of <code>org:memberOf</code>. 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>
 
-<table class="definition">
-  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#reportsTo">org:reportsTo</a></th></tr></thead>
-  <tbody>
-    <tr><td class="prop">Domain and 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> 
-     The precise semantics of the reporting 
-relationship will vary by organization but is intended to encompass both
- direct supervisory relationships (e.g. carrying objective and salary 
-setting authority) and more general reporting or accountability 
-relationships (e.g. so called <em>dotted line</em> reporting).
-</td></tr>
-  </tbody>
-</table>
-</div>
-
+<p>For example:</p>
 
-<!-- Property headOf -->
-<div class="section" id="property--headof">
-<h3 id="Property:_headOf"><span class="secno">8.5 </span>Property: headOf</h3>
-<p>
-	Indicates that a person (or other agent) is the leader or formal 
-head of the Organization.
-</p>
+<pre class="code">&lt;http://example.com/people#ceo&gt; 
+  org:headOf    &lt;http://example.com/org#id&gt; . 
+</pre>
 
-<table class="definition">
-  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#headOf">org:headOf</a></th></tr></thead>
-  <tbody>
-    <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
-     <tr><td class="prop">Range:</td><td><a href="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">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.
-</td></tr>
-  </tbody>
-</table>
-</div>
+<h4 id="membership-n-ary-relationship">Membership n-ary relationship</h4>
 
-<div id="discussion" class="informative section">
-<h3><span class="secno">8.6 </span>Discussion</h3><p><em>This section is non-normative.</em></p>
-
-<p>In some applications then it is sufficient to represent the role of an individual
-within an Organization by specializations of <code>org:memberOf</code>, as in the 
-builtin example <code>org:headOf</code>.</p>
-
-<p>However, in general it is advantageous to have an explicit representation of the organizational role (e.g. 
-to enable advertising of a post or for publication of salary ranges associated with the role), this is supported
+<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
 makes it possible to annotate the relationship with qualifying information such as duration, salary,
@@ -1334,20 +1087,476 @@
 </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>
+and a simple closure rule being used to add any corresponding
+  short-cut specializations of <code>org:memberOf</code>.</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
+  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
+  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
+  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>
+
+<h4 id="relationship-between-posts-and-membership">Relationship between Posts and Membership</h4>
+
+<p>In many cases only one of Posts and Memberships is needed to model
+  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
+  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>
+
+<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>
+
+<pre class="code">CONSTRUCT {
+  ?agent  org:memberOf ?org .
+} WHERE {
+  ?agent org:holds  ?post .
+  ?post  org:postIn ?org .
+}
+
+CONSTRUCT {
+    ?agent   org:memberOf  ?org .
+} WHERE {
+  [] a org:Membership;
+    org:member       ?agent ;
+    org:organization ?org .
+}
+
+CONSTRUCT {
+  [] a org:Membership;
+    org:member       ?agent ;
+    org:organization ?org;
+    org:role         ?role .
+} WHERE {
+  ?agent org:holds  ?post .
+  ?post  org:postIn ?org .
+  ?post  org:role   ?role .
+}
+
+CONSTRUCT {
+    ?agent   ?roleprop  ?org .
+} WHERE {
+  [] a org:Membership;
+    org:member       ?agent ;
+    org:organization ?org;
+    org:role         [ org:roleProperty ?roleprop ] .
+}
+</pre>
+
 </div>
 
+<!-- Property memberOf -->
+<div id="property--memberof" class="section">
+<h3 id="Property:_memberOf"><span class="secno">7.2 </span>Property: memberOf</h3>
+<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
+	organization. Extensions can specialize this relationship to
+	indicate particular roles within the organization or more
+	nuanced relationships to the organization.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#memberOf">org:memberOf</a></th></tr></thead>
+  <tbody>
+     <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+     <tr><td class="prop">Range:</td><td><a href="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>
+  </tbody>
+</table>
 </div>
 
+<!-- Property hasMember -->
+<div id="property--hasmember" class="section">
+<h3 id="Property:_hasMember"><span class="secno">7.3 </span>Property: hasMember</h3>
+<p>
+	Indicates a person who is a member of the subject Organization. 
+Inverse of <code>org:memberOf</code>, 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">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">Usage note:</td><td> 
+     Provided for compatibility with <code>foaf:member</code>.
+</td></tr>
+  </tbody>
+</table>
+</div>
+
+<!-- Property headOf -->
+<div id="property--headof" class="section">
+<h3 id="Property:_headOf"><span class="secno">7.4 </span>Property: headOf</h3>
+<p>
+	Indicates that a person (or other agent) is the leader or formal 
+head of the Organization.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#headOf">org:headOf</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+     <tr><td class="prop">Range:</td><td><a href="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">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.
+</td></tr>
+  </tbody>
+</table>
+</div>
+
+<!-- Class Membership -->
+<div id="class--membership" class="section">
+<h3 id="Class:_Membership"><span class="secno">7.5 </span>Class: Membership</h3>
+<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>
+  <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> 
+
+	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.
+</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>
+<p>
+	Indicates the Person (or other Agent including Organization) involved in the Membership relationship.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#member">org:member</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/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>
+</td></tr>
+  </tbody>
+</table>
+</div>
+
+
+
+<!-- Property organization -->
+<div id="property--organization" class="section">
+<h4 id="Property:_organization"><span class="secno">7.5.2 </span>Property: organization</h4>
+<p>
+	Indicates the organization in which the Agent is a member.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#organization">org:organization</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="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>
+  </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>
+<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
+	of the Post plays.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#role">org:role</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><code>owl:unionOf</code>(<a href="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>
+    
+  </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>
+<p>
+	Indicates a membership relationship that the Agent plays.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasMembership">org:hasMembership</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+      Inverse of <code>org:member</code>.
+</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>
+<p>
+	Optional property to indicate the interval for which the membership is/was valid.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#memberDuring">org:memberDuring</a></th></tr></thead>
+  <tbody>
+   
+   
+     <tr><td class="prop">Domain:</td><td><a href="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>
+    
+  </tbody>
+</table>
+</div>
+
+</div>  <!-- end of Class Membership-->
+
+<!-- Class Role -->
+<div id="class--role" class="section">
+<h3 id="Class:_Role"><span class="secno">7.6 </span>Class: Role</h3>
+<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>. 
+</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>
+  <tbody>
+     <tr><td class="prop">subClassOf:</td><td> <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+It is 
+common for roles to be arranged in some taxonomic structure and we use 
+SKOS to represent that. The normal SKOS lexical properties should be 
+used when labelling the Role. Additional descriptive properties for the 
+Role, such as a Salary band, may be added by extension vocabularies.
+</td></tr>
+</tbody>
+</table>
+
+<!-- Property roleProperty -->
+<div id="property--roleproperty" class="section">
+<h4 id="Property:_roleProperty"><span class="secno">7.6.1 </span>Property: roleProperty</h4>
+<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>
+ that can be used to directly indicate the role for ease of query.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#roleProperty">org:roleProperty</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Role">org:Role</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property">rdf:Property</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+      The 
+intended semantics is that a Membership relation involving the Role implies 
+the existence of a direct property relationship through an inference 
+rule of the form:  <code>{ [] org:member ?a; org:organization ?o; org:role [org:roleProperty ?r] } -&gt; {?a ?r ?o}</code>
+</td></tr>
+  </tbody>
+</table>
+</div>
+
+<!-- Property remuneration -->
+<div id="property--remuneration" class="section">
+<h4 id="Property:_remuneration"><span class="secno">7.6.2 </span>Property: remuneration</h4>
+<p>
+	Indicates a salary or other reward associated with the role. 
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#remuneration">org:remuneration	</a></th></tr></thead>
+  <tbody>
+     <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/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).
+</td></tr> 
+    
+  </tbody>
+</table>
+</div>
+
+</div>  <!-- end of Class Role-->
+
+
+<!-- Class Post -->
+<div id="class--post" class="section">
+<h3 id="Class:_Post"><span class="secno">7.7 </span>Class: Post</h3>
+<p>
+A Post represents some position within an organization that
+      exists independently of the person or persons filling it. Posts
+      may be used to represent situations where a person is a member
+      of an organization ex officio (for example the Secretary of
+      State for Scotland is part of UK Cabinet by virtue of being
+      Secretary of State for Scotland, not as an individual person). A
+      post can be held by multiple people and hence can be treated as
+      a organization in its own right.
+</p>
+<table class="definition">
+  <thead><tr><th>RDF 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>
+</tbody>
+</table>
+
+<!-- Property holds -->
+<div id="property--holds" class="section">
+<h4 id="Property:_holds"><span class="secno">7.7.1 </span>Property: holds</h4>
+<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">Usage note:</td><td> 
+     Inverse of <code>org:heldBy</code>.
+</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>
+<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">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">Usage note:</td><td> 
+     Inverse of <code>org:holds</code>.
+</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>
+<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">Usage note:</td><td> 
+     Inverse of <code>org:hasPost</code>.
+</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>
+<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">Usage note:</td><td> 
+     Inverse of <code>org:postIn</code>.
+</td></tr>
+  </tbody>
+</table>
+</div>
+
+</div> <!-- end of Class Post -->
+
+<!-- Property reportsTo -->
+<div id="property--reportsto" class="section">
+<h3 id="Property:_reportsTo"><span class="secno">7.8 </span>Property: reportsTo</h3>
+<p>
+	Indicates a reporting relationship as might be depicted on an 
+organizational chart. It can be used to indicate a reporting
+	relationship directly between Agents or between Posts that
+	Agents could hold.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#reportsTo">org:reportsTo</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Domain:</td><td><code>owl:unionOf</code>(<a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a>
+    <a href="http://www.w3.org/ns/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>
+    <tr><td class="prop">Usage note:</td><td> 
+     The precise semantics of the reporting 
+relationship will vary by organization but is intended to encompass both
+ direct supervisory relationships (e.g. carrying objective and salary 
+setting authority) and more general reporting or accountability 
+relationships (e.g. so called <em>dotted line</em> reporting).
+</td></tr>
+  </tbody>
+</table>
+</div>
+
+
+</div>  <!-- end of Membership, roles, posts and reporting -->
+
 
 <!--    LOCATION   -->
-<div class="section" id="location">
-<!--OddPage--><h2><span class="secno">9. </span>Location</h2>
+<div id="location" class="section">
+<!--OddPage--><h2><span class="secno">8. </span>Location</h2>
 
 
 <!-- Class Site -->
-<div class="section" id="class--site">
-<h3 id="Class:_Site"><span class="secno">9.1 </span>Class: Site</h3>
+<div id="class--site" class="section">
+<h3 id="Class:_Site"><span class="secno">8.1 </span>Class: Site</h3>
 <p>
 An office or other premise at which the organization is located. 
 Many organizations are spread across multiple sites and many sites will 
@@ -1368,8 +1577,8 @@
 </table>
 
 <!-- Property siteAddress -->
-<div class="section" id="property--siteaddress">
-<h4 id="Property:_siteAddress"><span class="secno">9.1.1 </span>Property: siteAddress</h4>
+<div id="property--siteaddress" class="section">
+<h4 id="Property:_siteAddress"><span class="secno">8.1.1 </span>Property: siteAddress</h4>
 <p>
 	Indicates a VCard (using the http://www.w3.org/TR/vcard-rdf/ 
 vocabulary) for the site. This can include email, telephone, and 
@@ -1388,8 +1597,8 @@
 </div>
 
 <!-- Property hasSite -->
-<div class="section" id="property--hassite">
-<h4 id="Property:_hasSite"><span class="secno">9.1.2 </span>Property: hasSite</h4>
+<div id="property--hassite" class="section">
+<h4 id="Property:_hasSite"><span class="secno">8.1.2 </span>Property: hasSite</h4>
 <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 
@@ -1408,8 +1617,8 @@
 </div>
 
 <!-- Property siteOf -->
-<div class="section" id="property--siteof">
-<h4 id="Property:_siteOf"><span class="secno">9.1.3 </span>Property: siteOf</h4>
+<div id="property--siteof" class="section">
+<h4 id="Property:_siteOf"><span class="secno">8.1.3 </span>Property: siteOf</h4>
 <p>
 	Indicates an Organization which has some presence at the given site. 
 </p>
@@ -1427,8 +1636,8 @@
 </div>
 
 <!-- Property hasPrimarySite -->
-<div class="section" id="property--hasprimarysite">
-<h4 id="Property:_hasPrimarySite"><span class="secno">9.1.4 </span>Property: hasPrimarySite</h4>
+<div id="property--hasprimarysite" class="section">
+<h4 id="Property:_hasPrimarySite"><span class="secno">8.1.4 </span>Property: hasPrimarySite</h4>
 <p>
 	Indicates a primary site for the Organization, this is the default 
 means by which an Organization can be contacted and is not necessarily 
@@ -1448,8 +1657,8 @@
 
 
 <!-- Property hasRegisteredSite -->
-<div class="section" id="property--hasregisteredsite">
-<h4 id="Property:_hasRegisteredSite"><span class="secno">9.1.5 </span>Property: hasRegisteredSite</h4>
+<div id="property--hasregisteredsite" class="section">
+<h4 id="Property:_hasRegisteredSite"><span class="secno">8.1.5 </span>Property: hasRegisteredSite</h4>
 <p>
 	Indicates the legally registered site for the organization, in many 
 legal jurisdictions there is a requirement that FormalOrganizations such
@@ -1468,8 +1677,8 @@
 </div>
 
 <!-- Property basedAt -->
-<div class="section" id="property--basedat">
-<h4 id="Property:_basedAt"><span class="secno">9.1.6 </span>Property: basedAt</h4>
+<div id="property--basedat" class="section">
+<h4 id="Property:_basedAt"><span class="secno">8.1.6 </span>Property: basedAt</h4>
 <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>
@@ -1480,7 +1689,6 @@
    
     <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">subPropertyOf:</td><td><a href="http://www.w3.org/ns/org#hasPrimarySite">org:hasPrimarySite</a></td></tr>
   </tbody>
 </table>
 </div>
@@ -1488,8 +1696,8 @@
 
 
 <!-- Property location -->
-<div class="section" id="property--location">
-<h3 id="Property:_location"><span class="secno">9.2 </span>Property: location</h3>
+<div id="property--location" class="section">
+<h3 id="Property:_location"><span class="secno">8.2 </span>Property: location</h3>
 <p>
 	Gives a location description for a person within the organization, for example a <em>Mail Stop</em> for internal posting purposes.
 </p>
@@ -1508,11 +1716,11 @@
 
 
 <!--   Projects and other activities   -->
-<div class="section" id="projects-and-other-activities">
-<!--OddPage--><h2><span class="secno">10. </span>Projects and other activities</h2>
+<div id="projects-and-other-activities" class="section">
+<!--OddPage--><h2><span class="secno">9. </span>Projects and other activities</h2>
 <!-- Class OrganizationalCollaboration -->
-<div class="section" id="class--organizationalcollaboration">
-	<h3 id="Class:_OrganizationalCollaboration"><span class="secno">10.1 </span>Class: OrganizationalCollaboration</h3>
+<div id="class--organizationalcollaboration" class="section">
+	<h3 id="Class:_OrganizationalCollaboration"><span class="secno">9.1 </span>Class: OrganizationalCollaboration</h3>
 	<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 
@@ -1526,7 +1734,7 @@
 	  <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> 
-	 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 <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>
 	</td></tr>
 	</tbody>
 	</table>
@@ -1536,25 +1744,25 @@
 
 
 <!--   Historical information   -->
-<div class="section" id="historical-information">
-<!--OddPage--><h2><span class="secno">11. </span>Historical information</h2>
+<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 resouces. 
+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>
 
 <!-- Class ChangeEvent -->
-<div class="section" id="class--changeevent">
-<h3 id="Class:_ChangeEvent"><span class="secno">11.1 </span>Class: ChangeEvent</h3>
+<div id="class--changeevent" class="section">
+<h3 id="Class:_ChangeEvent"><span class="secno">10.1 </span>Class: ChangeEvent</h3>
 <p>
 Represents an event which resulted in a major change to an 
 organization such as a merger or complete restructuring. It is intended 
-for situations where the resulting organization is sufficient distinct 
+for situations where the resulting organization is sufficiently distinct 
 from the original organizations that it has a distinct identity and 
 distinct URI. 
 </p>
@@ -1565,15 +1773,15 @@
     <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 `opmv:wasGeneratedAt`, a 
-description should be given by `dct:description`.
+which the event occurred should be given by <code>opmv:wasGeneratedAt</code>, a 
+description should be given by <code>dct:description</code>.
 </td></tr>
 </tbody>
 </table>
 
 <!-- Property originalOrganization -->
-<div class="section" id="property--originalorganization">
-<h4 id="Property:_originalOrganization"><span class="secno">11.1.1 </span>Property: originalOrganization</h4>
+<div id="property--originalorganization" class="section">
+<h4 id="Property:_originalOrganization"><span class="secno">10.1.1 </span>Property: originalOrganization</h4>
 <p>
 	Indicates one or more organizations that existed before the change 
 event. Depending on the event they may or may not have continued to 
@@ -1589,16 +1797,16 @@
      <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 `org:Organization` 
-as an `opmv:Artifact`, which is consistent with the OPM model.
+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>
   </tbody>
 </table>
 </div>
 
 <!-- Property changedBy -->
-<div class="section" id="property--changedby">
-<h4 id="Property:_changedBy"><span class="secno">11.1.2 </span>Property: changedBy</h4>
+<div id="property--changedby" class="section">
+<h4 id="Property:_changedBy"><span class="secno">10.1.2 </span>Property: changedBy</h4>
 <p>
 Indicates a change event which resulted in a change to this 
 organization. 
@@ -1621,8 +1829,8 @@
 </div>
 
 <!-- Property resultedFrom -->
-<div class="section" id="property--resultedfrom">
-<h4 id="Property:_resultedFrom"><span class="secno">11.1.3 </span>Property: resultedFrom</h4>
+<div id="property--resultedfrom" class="section">
+<h4 id="Property:_resultedFrom"><span class="secno">10.1.3 </span>Property: resultedFrom</h4>
 <p>
 Indicates an event which resulted in (led to, generated) this 
 organization.
@@ -1639,16 +1847,16 @@
      <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 `org:Organization` 
-as an `opmv:Artifact`, which is consistent with the OPM model.
+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>
   </tbody>
 </table>
 </div>
 
 <!-- Property resultingOrganization -->
-<div class="section" id="property--resultingorganization">
-<h4 id="Property:_resultingOrganization"><span class="secno">11.1.4 </span>Property: resultingOrganization</h4>
+<div id="property--resultingorganization" class="section">
+<h4 id="Property:_resultingOrganization"><span class="secno">10.1.4 </span>Property: resultingOrganization</h4>
 <p>
 Indicates an organization which was created or changed as a result of the event.
 </p>
@@ -1668,11 +1876,25 @@
 
 </div>  <!-- end of Section Historical-->
 <!--    ACK   -->
-<div id="change-history" class="appendix section">
+<div class="appendix section" id="change-history">
 
 <!--    Change history   -->
 
 <!--OddPage--><h2><span class="secno">A. </span>Change history</h2>
+<p>Changes since <a href="http://www.w3.org/TR/2012/WD-vocab-org-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
+  ontology.</li>
+  <li>Rephrasing and reordering 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>
@@ -1702,11 +1924,8 @@
 </ul>
 
 </div>
-<div id="acknowledgments" class="appendix section">
+<div class="appendix section" id="acknowledgments">
 <!--OddPage--><h2><span class="secno">B. </span>Acknowledgments</h2>
-<p>
-The editors are very thankful for comments and suggestions ...
-</p>
 <p>This ontology was originally developed 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,
@@ -1715,9 +1934,20 @@
 <a href="http://www.london-gazette.co.uk/ontology/organisation.owl">Gazette Organization ontology</a>
 and <a href="http://proton.semanticweb.org/">Proton-top</a>.
 </p>
+<p>
+The editor gratefully acknowledges comments and support from the
+Government Linked Data Working group - particularly to Daniel Vila for
+transcribing the original documentation into <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
+closely based on the work of Jeni Tennison on modelling UK Government.
+</p>
 
 </div>
 
 
-<div class="appendix section" id="references"><!--OddPage--><h2><span class="secno">C. </span>References</h2><div class="section" id="normative-references"><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 class="section" id="informative-references"><h3><span class="secno">C.2 </span>Informative references</h3><p>No informative references.</p></div></div></body></html>
\ No newline at end of file
+<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>