* Commit changes of Daniel.
authorbkaempge
Wed, 22 Feb 2012 22:43:58 +0100
changeset 105 1235277b97ce
parent 104 4a811896d99f (current diff)
parent 103 5ea9bf9eb486 (diff)
child 106 9e0e2df8f5f7
* Commit changes of Daniel.
--- a/bp/index.html	Wed Feb 22 22:38:07 2012 +0100
+++ b/bp/index.html	Wed Feb 22 22:43:58 2012 +0100
@@ -53,8 +53,9 @@
 <p>
 <a href="http://www.w3.org/DesignIssues/LinkedData.html" title="Linked Data - Design Issues">Linked Data</a> addresses key requirements of open government by providing a family of international standards for the publication, dissemination and reuse of structured data.
 </p>
+</section>
 
-
+<section>
 <h3>Scope - Bernadette</h3>
 
 <p>
@@ -70,6 +71,9 @@
 Finally, in publishing Linked Open Data, it is not necessary to implement everything decribed herein. Instead, each Best Practice should be considered as a possible measure that may be implemented towards the goal of providing as rich and dynamic an experience as possible via a Web browser and Linked Data client. 
 </p>
 
+</section>
+
+<section>
 <h3>Motivation</h3>
 The best practices provided here are provide a methodical approach for the creation, publication and dissemination of government Linked Data, including:
 <ul>
@@ -81,9 +85,12 @@
 <p class='issue'>Does it make sense to base the GLD life cycle on one of the general LD life cycles? See <a href="https://www.w3.org/2011/gld/track/issues/15">ISSUE-15</a></p>
 </section>
 
+<section>
 <h3>Brief History of Open Government Linked Data - Bernadette</h3>
 
+</section>
 
+</section>
 <!--    PROCUREMENT   -->
 <section>
 <h3>Procurement - Bernadette</h3>
@@ -217,7 +224,7 @@
 
 <!--    VOCABULARY SELECTION   -->
 <section>
-<h3>Vocabulary Selection -  Boris</h3>
+<h3>Vocabulary Selection - Boris</h3>
 <p class='responsible'>Michael Hausenblas (DERI), Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (UPM),  Daniel Vila-Suero (UPM), George Thomas (Health & Human Services, US), John Erickson (RPI), Biplav Srivastava (IBM)</p>
 <p>
 The group will provide advice on how governments should select RDF vocabulary terms (URIs), including advice as to when they should mint their own. This advice will take into account issues of stability, security, and long-term maintenance commitment, as well as other factors that may arise during the group's work.
@@ -378,17 +385,44 @@
 </section>
 
 
-<!--    URI CONSTRUCTION   -->
+<!-- << URI CONSTRUCTION   -->
 <section>
 <h3>URI Construction - Boris</h3>
 <p class='responsible'>Ghislain Atemezing (INSTITUT TELECOM), Michael Hausenblas (DERI), Boris Villazon-Terrazas (UPM), Daniel Vila (UPM), John Erickson (RPI), Martin Alvarez (CTIC)</p>
 <p>
-This section specifies how to create good URIs for use in government linked data. Inputs include <a href="http://www.w3.org/TR/cooluris/" title="Cool URIs for the Semantic Web">Cool URIs for the Semantic Web</a>, <a href="http://www.cabinetoffice.gov.uk/media/308995/public_sector_uri.pdf">Designing URI Sets for the UK Public Sector</a> (PDF), and <a href="http://data.gov.uk/resources/uris" title="Creating URIs | data.gov.uk">Creating URIs</a> (data.gov.uk). Guidance will be produced not only for minting URIs for governmental entities, such as schools or agencies, but also for vocabularies, concepts, and datasets.
+This section specifies how to create good URIs for use in government linked data. Inputs include 
+<ul>
+	<li><a href="http://www.w3.org/TR/cooluris/" title="Cool URIs for the Semantic Web">Cool URIs for the Semantic Web</a></li>
+	<li><a href="http://www.cabinetoffice.gov.uk/media/308995/public_sector_uri.pdf">Designing URI Sets for the UK Public Sector</a> (PDF)</li>
+	<li><a href="http://data.gov.uk/resources/uris" title="Creating URIs | data.gov.uk">Creating URIs</a> (data.gov.uk).</li>
+</ul>
+Guidance will be produced not only for minting URIs for governmental entities, such as schools or agencies, but also for vocabularies, concepts, and datasets.
 </p>
 
-<p class="todo">Integrate Wiki <a href="http://www.w3.org/2011/gld/wiki/223_Best_Practices_URI_Construction">content</a>.</p>
+<section> 
+<h4>Definitions and General Principles</h4>
+<p>The Web makes use of the URI (Uniform Resource Identifiers) as a single global identification system. The global scope of URIs promotes large-scale "network effects". There are many benefits to participating in the existing network of URIs, including linking, caching, and indexing by search engines. This section aims at providing recommendations on how to create good URIs for use in government linked data:</p>
+<p class="highlight"><b>Identify with URIs</b><br>
+To benefit from and increase the value of the World Wide Web, data publishers SHOULD provide URIs as identifiers for their resources.
+</p>
 </section>
 
+<section> 
+<h4>Best Practices Checklist<h4>
+</section>
+
+<section> 
+<h4>Representation of Resources<h4>
+</section>
+
+<section> 
+<h4>Working Notes<h4>
+</section>
+
[email protected]@ TODO: include references
+<!-- <p class="todo">Integrate Wiki <a href="http://www.w3.org/2011/gld/wiki/223_Best_Practices_URI_Construction">content</a>.</p> -->
+</section> <!-- URI CONSTRUCTION >> -->
+
 
 <!--    VERSIONING   -->
 <section>
@@ -437,17 +471,164 @@
 </section>
 
 
-<!--    STABILITY   -->
+<!--  << STABILITY   -->
 <section>
 <h3>Stability - Boris</h3>
 <p class='responsible'>Anne Washington (GMU), Ron Reck</p>
+
+<section> <!-- << STABILITY.overview -->
+<h4>Overview</h4>
+<p>This section will focus how to publish data so that others can rely on it being available in perpetuity, persistently archived if necessary.</p>
+
+<h5>Definition</h5>
+<p><i>The scope, limits and explanation of stability.</i></p>
+<p>The following definition describes stability of LOD.</p>
 <p>
-This section specifies how to publish data so that others can rely on it being available in perpetuity, persistently archived if necessary.
+<b>Stability.</b> <u>Stable</u> LOD is persistent, predictable and machine accessible from externally visible locations. 
 </p>
+<ul>
+	<li>Persistent = Information accessible for an unbounded period of time.</li>
+	<li>Predictable = Names and information follow a logical format.</li>
+	<li>Stable location = Externally visible locations are consistent in name, and availability.</li>
+	<li>Other things that impact stability
+		<ul>
+			<li>legacy = earlier naming schemes, formats, data storage devices</li>
+			<li>steward = people who are committed to consistently maintain specific datasets, either individuals or roles in organizations</li>
+			<li>provenance = the sources that establish a context for the production and/or use of an artifact. See <a href="http://www.w3.org/2011/prov/wiki/Main_Page" target="_blank">W3C Provenance working group</a></li>
+		</ul>
+	</li>
+</ul>
 
-<p class="todo">Integrate Wiki <a href="http://www.w3.org/2011/gld/wiki/225_Best_Practices_for_Stability">content</a>.</p>
+<h5>Goals</h5>
+<p><i>The purpose of having a best practice for stability</i></p>
+<p>The length of time information is available is inherently connected to the value placed upon it. 
+If information is deemed valuable, it is likely to persist for a longer period of time. 
+Value, which can change over time, is always determined based on a cost-benefit relationship; 
+Any benefit derived from information is reduced by the cost(s) associated with using it. 
+Increasing stability requires the adoption of a strategy to allocate limited resources for achieving a goal. 
+Goals drive data providers' criteria to make a selection of what is best preserved.</b>
+<p>We believe that <b>preservation of content</b> is the main goal for stability, possible goals include:</p>
+<ol type="1">
+	<li><b>Preservation of content.</b> It might be important to have raw data available for analysis ad infinitum. This means the overall objective is to preserve only the scientific content.</li>
+	<li><b>Preservation of access.</b> It might be important to have information available immediately at all times.</li>
+	<li><b>Conservation.</b> From a historical perspective one could seek to preserve all information in the format and modality in which it was originally conveyed. The most demanding is conservation of the full look and feel of the publication.</li>
+</ol>
 
-</section>
+<h5>Success Factors</h5>
+<p>ORGANIZATIONAL CONSIDERATIONS Without internal stability from the data stewards, any external technology stability is a challenge. These following are some organization characteristics for stable data.</p>
+<ul>
+	<li>Consistent human skills</li>
+	<li>Consistent infrastructure</li>
+	<li>Data related to organizational values or business needs</li>
+	<li>Internal champion or consistent business process</li>
+	<li>Internal politics on variation names do not impact external locations</li>
+</ul>
+<p>Mark metadata based on its intended audience</p>
+<ul>
+	<li>Internal-audience : management of the process</li>
+	<li>External-audience : final state, or no-update needed.</li>
+</ul>
+</section> <!-- STABILITY.overview >> -->
+
+<section> <!-- << STABILITY.examples -->
+<h4>Examples</h4>
+<p><i>These are a few representative samples to generate discussion and comment. Additional suggestions are encouraged.</i></p>
+<p>These examples were discussed on the <a href="http://lists.w3.org/Archives/Public/public-gld-wg/" target="_blank">public-gld email listserv</a></p>
+
+<p><b>Technical examples</b>  What existing examples can we point to? (Need international ones...)</p>
+<ol type="1">
+	<li>Internet Archive - <a href="http:www.archive.org">http:www.archive.org</a></li>
+</ol>
+
+<p><b>Institutional examples</b> Who has the incentive to provide stable persistent data? Some real possibilities and some metaphors for discussion.</p>
+<ol type="1">
+	<li>Archives
+		<ol type="i">
+			<li>Third party entities that document provenance and provide access</li>
+		</ol>
+	</li>
+	<li>Estate Lawyer
+		<ol type="i">
+			<li>Someone responsible for tracking down heirs for an inheritance</li>
+		</ol>
+	</li>
+	<li>Private Foundation
+		<ol type="i">
+			<li>A philanthropic entity who is interested in the value proposition of stability and acts as archive</li>
+		</ol>
+	</li>
+	<li>Government
+		<ol type="i">
+			<li>A government organization which has the funds to steward others' data</li>
+		</ol>
+	</li>
+	<li>Internet organization
+		<ol type="i">
+			<li>A global open organization like W3C or IKAN</li>
+		</ol>
+	</li>
+</ol>
+</section> <!-- STABILITY.examples >> -->
+
+<section> <!-- << STABILITY.Properties -->
+<h4>Properties</h4>
+<p><i>These are characteristics that influence the stability or longevity. Many of these properties are not unique to LOD, yet they influence data cost and therefore data value.</i></p>
+<ul>
+	<li><b><u>Integrity.</u></b>Provide checksums of downloads so that consumers can be assured that they have received the entire dataset. Data that is unreliable should not used for critical decisions and is therefore of less value than data that is deemed complete. Possible checksum types include MD5 and SHA.</li>
+	<li><b><u>Consistency.</u></b>Any design of a data format should recognize that change is necessary and will happen. Recognition that change is enviable while providing a mechanism for embracing modification increases continuity and longevity.
+	The following types of changes can be anticipated. Therefore, data design should be made to accommodate them:
+	<ol type="1">
+		<li>The person who published the data changes jobs - For <u>Contact Consistency</u> - Any support contact information should be published using a data steward so that the inherent transition of responsibility does not introduce inconsistency to consumers.</li>
+		<li>Departments, Agencies and Governments are reorganized - For <u>File Naming and Data Consistency</u> - Discourage the use of the originating source as component in the name of the data file, or the URIs it contains.The information can appropriately be contained within the file as metadata.</li>
+		<li>IT infrastructure overhaul - <u>For File Naming Consistency</u> - Discourage the use of the server or system as component in the name of the data file.</li>
+		<li>Merger/acquisition - For <u>Data Consistency</u> - Discourage the use of branding as it inherently and needlessly increases cost for new owners while providing no value at all to consumers.</li>
+		<li>Primary stakeholder loses interest in the data - As above For <u>Data Consistency</u> - Discourage the use of branding as it inherently increase cost for new owners.</li>
+	</ol>	
+	</li>
+<li><b><u>Data Repository Consistency.</u></b>As new data is produced, old data becomes legacy data. Consumers of data will write programs to automate processing of legacy data and the number of changes in format directly effects the cost incurred by data consumers. Data providers should carefully consider whether the benefit of the change exceeds the incurred cost of modifying ingestion procedures. Even changing formats between different serializations has a cost to consumers as they need to anticipate and provide for the change. Data providers should consider lifecycle workflow and when at all possible they should modify legacy data themselves so that all provided data is consistent and each consumer will not be required to perform exactly the same data conversion task to create a homogeneous data repository.</li>
+
+<li><b><u>Manageability.</u></b>
+	<ul>
+		<li><b><u>Discrete</u></b> It is best to have a greater number of small files rather than fewer larger files. Smaller files reduce the cost on consumers. Files should be comprised of meaningful discrete units based on a time period, locality or other logical unit.</li>
+		<li><b><u>File names</u></b> Files should be meaningfully named without using non-printable characters.</li>
+		<li><b><u>Archive structure</u></b> Data archives should be nested in least a single directory. The directory name should be unique to accommodate multiple archives to be uncompressed without introducing collisions.</li>
+	</ul>
+</li>
+<li><b><u>Organization.</u></b>The minimum metadata accompanying each data offering should include:
+	<ol type="1">
+		<li>Serialization type (such as NTriples or RDF/XML)</li>
+		<li>Publisher</li>
+		<li>Creation Date</li>
+		<li>Modification Date</li>
+		<li>Version</li>
+		<li>Email address for data steward</li>
+	</ol>
+</li>
+<li><b><u>Complexity.</u></b>All serializations are equal to a back-end system, therefore providers should serialize RDF in either
+	<ul>
+		<li>turtle - The turtle serialization minimizes the disk space expenditure while also increasing human readability.</li>
+		<li>NTriples - The NTriples serialization increases integrity in that re-ordering will have no effect on semantics, and damaged lines only effect the assertion on those lines. NTriples also increases flexibility because files can be split into smaller files as long as the division happen at the end of the line.</li>
+	</ul>
+</li>
+<li><b><u>Diskspace Resource.</u></b>Different serializations represent the same semantics but require varying amounts of characters (diskspace). While Turtle provides the most concise serialization and is arguably the easiest for humans to read. Turtle does not provide the integrity that NTriples does because NTriples can be reordered or split up based on size or line count without effecting the integrity of the dataset. In general NTriples will provide the greatest overall stability for LOD. Compression of data should be done using either GZIP or ZIP, do not choose to adopt other compression approaches just because they are "free". The maximum data compression should be chosen.</li>
+</ul>
+</section> <!--  STABILITY.Properties >> -->
+
+<section> <!-- << STABILITY.Interconnections -->
+<h4>Interconnections</h4>
+<p><i>Ways that this best practice is connected to others.</i></p>
+<p><b>STABIILTY, URL, and URIs.</b> The identifiers used in LOD are a possible point of failure, therefore use URIs that dereference under DNS that you control or that have greatest likeliness to persist. Use URI's according to the best practices stated <b>elsewhere in this document</b> increases value. Other strategies for maximizing the longevity of URI's include:</p>
+<ol type="1">
+	<li>PURLs (Persistent Uniform Resource Locators) <a href="http://purl.oclc.org/docs/index.html" target="_blank">purl.oclc.org</a></li>
+	<li>Handle System <a href="http://www.handle.net/" target="_blank">http://www.handle.net/</a> and its commercial cousin <a href="http://www.doi.org/" target="_blank">Digital Object Identifier</a></li>
+</ol>
+<p><b>Vocabulary Choices Effect Value</b> When LOD uses or references vocabularies or vocabulary items it is a point of frailty, which therefore can effect cost. Vocabulary use according to the best practices stated <b>elsewhere in this document</b> increases value.</p>
+</section> <!-- STABILITY.Interconnections >> -->
+
+<!-- <p class="todo">Integrate Wiki <a href="http://www.w3.org/2011/gld/wiki/225_Best_Practices_for_Stability">content</a>.</p> -->
[email protected]@ TODO: Include references
+
+</section> <!-- STABILITY >> -->
 
 
 <!--   SOURCE DATA   -->
@@ -532,4 +713,4 @@
 </p>
 </section>
 </body>
-</html>
\ No newline at end of file
+</html>
--- a/bp/local-style.css	Wed Feb 22 22:38:07 2012 +0100
+++ b/bp/local-style.css	Wed Feb 22 22:43:58 2012 +0100
@@ -59,6 +59,12 @@
 padding: 10px;
 }
 
+.highlight {
+border: 3px solid #005a9c;
+margin: 5 5 5 20px;
+padding: 10px;
+}
+
 
 ol.prereq li {
 padding-bottom: 10px;
--- a/bp/respec-config.js	Wed Feb 22 22:38:07 2012 +0100
+++ b/bp/respec-config.js	Wed Feb 22 22:43:58 2012 +0100
@@ -1,7 +1,7 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
     specStatus:           "ED",
-    publishDate:          "2012-02-06",
+    publishDate:          "2012-02-16",
     //copyrightStart:       "2010",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/
@@ -34,7 +34,7 @@
     editors:  [
         { name: "Michael Hausenblas", url: "http://sw-app.org/mic.xhtml#i", company: "DERI", companyURL: "http://www.deri.ie" },
 		{ name: "Bernadette Hyland", url: "https://twitter.com/bernhyland",  company: "3 Round Stones", companyURL: "http://3roundstones.com/"},
-		{ name: "Boris Villaz&oacute;n-Terrazas", url: "http://boris.villazon.terrazas.name",  company: "OEG-UPM", companyURL: "http://www.oeg-upm.net"}
+		{ name: "Boris Villaz&oacute;n-Terrazas", url: "http://boris.villazon.terrazas.name",  company: "OEG, UPM", companyURL: "http://www.oeg-upm.net"}
     ],
 
     // authors, add as many as you like. 
Binary file org/img/diagram.png has changed
--- a/org/index.html	Wed Feb 22 22:38:07 2012 +0100
+++ b/org/index.html	Wed Feb 22 22:43:58 2012 +0100
@@ -9,6 +9,31 @@
 	<script type="text/javascript"src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
 	<script src="respec-ref.js"></script>
 	<script src="respec-config.js"></script>
+	 <style type="text/css">
+	  table {
+	    border-collapse:collapse;
+	  }
+	  td, th {
+	    border:1px solid black;
+	    padding:1em;
+	  }  
+	  table#namespaces td {
+	    font-family: monospace;
+	  }
+	  table.definition {
+	    width:100%;
+	  }
+	  table.definition td.prop {
+	    width:10em;
+	  }
+          pre {
+		padding: 1em;
+		border: 1px dashed #2f6fab;
+		color: black;
+		background-color: #f9f9f9;
+		line-height: 1.1em;
+	 }
+	</style>
 	<link rel="stylesheet" type="text/css" href="local-style.css" />
 </head>
 <body>
@@ -38,9 +63,49 @@
 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. 
 </section>
 
+
 <!--    INTRODUCTION    -->
+<section class="informative">
+<h2>Introduction</h2>
+<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>
+
+</section>
+
+
+<section id="conformance">
+<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>
+</ul>
+</section>
+
+<!-- Namespaces -->
 <section>
-<h2>Introduction</h2>
+<h2 id="ns">Namespaces</h2>
+<p>The namespace for ORG is <code>http://www.w3.org/ns/org#</code>. However,
+it should be noted that ORG extends and uses terms from other vocabularies. A full set of alphabetically ordered namespaces and prefixes used in this
+document is shown in the table below.</p>
+<!-- Alphabetically ordered-->
+<table id="namespaces">
+  <thead><tr><th>Prefix</th><th>Namespace</th></tr></thead>
+  <tbody>
+    
+    <tr><td>foaf</td><td>http://xmlns.com/foaf/0.1/</td></tr>
+    <tr><td>gr</td><td>http://purl.org/goodrelations/v1#</td></tr>  
+    <tr><td>opmv</td><td>http://purl.org/net/opmv/ns#</td></tr> 
+    <tr><td>org</td><td>http://www.w3.org/ns/org#</td></tr>
+    <tr><td>owlTime</td><td>http://www.w3.org/2006/time#</td></tr>
+    <tr><td>rdf</td><td>http://www.w3.org/1999/02/22-rdf-syntax-ns#</td></tr>
+    <tr><td>skos</td><td>http://www.w3.org/2004/02/skos/core#</td></tr>
+    <tr><td>vcard</td><td>http://www.w3.org/2006/vcard/ns#</td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Overview of ontology -->
+<section class="informative">
+<h3>Overview of ontology</h3>
+
 
 <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.
@@ -82,22 +147,97 @@
 sub-class structures or classification schemes as required. 
 </p>
 
-<section>
-<h3>Overview of ontology</h3>
-
 <img src="img/diagram.png" alt="Diagram dipicting core classes and relationships">
 
+
+
+<h2 id="example">Example</h2>
+<p>This example provides a quick overview of how dcat might be used to an organization </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>
+-->
 </section>
 
-<section>
-<h3>Namespace</h3>
-
-  <p>The namespace for the ontology is: 
-  	<a href="http://www.w3.org/ns/org#">http://www.w3.org/ns/org#</a>
-  </p>
-</section>
-
-<section>
+<section class="informative">
 <h3>Design notes</h3>
 
   <p>For background to the approach taken in developing the ontology see: 
@@ -106,7 +246,7 @@
 </section>
 
 
-<section>
+<section class="informative">
 <h3>Notes on style</h3>
 
 <p><em>Use of inverses:</em> authorities differ on whether providing pairs of inverse relationships between
@@ -125,138 +265,245 @@
 and "foo of" to improve readability in linked data viewers.</p>
 </section>
 
-</section>
 <!--    Organizational structure   -->
 <section>
 <h2>Organizational structure</h2>
 
-<dl>
-<dt><em>Class:</em> <code>org:Organization</code> (subClassOf  <code>foaf:Agent</code>)</dt>
-<dd>Represents a collection of people organized together into a 
+<!-- Class Organization -->
+<section>
+<h2 id="Class:_Organization">Class: Organization</h2>
+<p>Represents a collection of people organized together into a 
 community or other social, commercial or political structure. The group 
 has some common purpose or reason for existence which goes beyond the 
 set of people belonging to it and can act as an Agent. Organizations are
- often decomposable into hierarchical structures.  It is recommended 
+ often decomposable into hierarchical structures. </p>
+<table class="definition">
+  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></th></tr></thead>
+  <tbody>
+     <tr><td class="prop">subClassOf:</td><td> <a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> It is recommended 
 that SKOS lexical labels should be used to label the Organization. In 
-particular <code>skos:prefLabel</code> for the primary (e.g. legally recognized name), <code>skos:altLabel</code> for alternative names (trading names, colloquial names) and <code>skos:notation</code> to denote codes from a code list. Alternative names: <em>Collective</em> <em>Body</em> <em>Org</em> <em>Group</em></dd>
-</dl>
-
-<p> </p>
-
-
-<dl>
-<dt><em>Class:</em> <code>org:FormalOrganization</code> (subClassOf  <code>org:Organization</code>, <code>foaf:Organization</code>; superClassOf <code>gr:BusinessEntity</code>)</dt>
-<dd>An Organization which is recognized in the world at large, in 
-particular in legal jurisdictions, with associated rights and 
-responsibilities. Examples include a Corporation, Charity, Government or
- Church. Note that this is a super class of <code>gr:BusinessEntity</code> and it is recommended to use the GoodRelations vocabulary to denote Business classifications such as DUNS or NAICS.</dd>
-</dl>
-
-<p> </p>
-
-<dl>
-<dt><em>Class:</em> <code>org:OrganizationalUnit</code> (subClassOf  <code>org:Organization</code>)</dt>
-<dd>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. Units can be large and complex containing other Units and even 
-FormalOrganizations. Alternative names: <em>OU</em> <em>Unit</em> <em>Department</em></dd>
-</dl>
-
-<p> </p>
+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>
 
-<dl>
-<dt><em>Property:</em> <code>org:subOrganizationOf</code>  (<code>org:Organization</code> -&gt; <code>org:Organization</code>)</dt>
-<dd>Represents hierarchical containment of Organizations or 
-Organizational Units; indicates an organization which is a sub-part or 
-child of this organization.  Inverse of <code>org:hasSubOrganization</code>. Alternative names: subOrgOf</dd>
-</dl>
-
-<p> </p>
-
-<dl>
-  <dt><em>Property:</em> <code>org:transitiveSubOrganizationOf</code>  (<code>org:Organization</code> -&gt; <code>org:Organization</code>, Transitive super property of <code>org:subOrganizationOf</code>)</dt>
-<dd>The transitive closure of subOrganizationOf, giving a representation
- of all organizations that contain this one. Note that technically this 
-is a super property of the transitive closure so it could contain 
-additional assertions but such usage is discouraged.</dd>
-</dl>
+   
+  </tbody>
+</table>
 
-<p> </p>
-
-<dl>
-<dt><em>Property:</em> <code>org:hasSubOrganization</code>  (<code>org:Organization</code> -&gt; <code>org:Organization</code>)</dt>
-<dd>Represents hierarchical containment of Organizations or 
-OrganizationalUnits; indicates an Organization which contains this 
-Organization. Inverse of <code>org:subOrganizationOf</code>. Alternative names: hasSubOrg</dd>
-</dl>
+<!-- Property subOrganizationOf -->
+<section>
+<h3 id="Property:_subOrganizationOf">Property: subOrganizationOf</h3>
+<p>Represents hierarchical containment of Organizations or Organizational Units; indicates an organization which is a sub-part or child of this organization.</p>
 
-<p> </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>
+  </tbody>
+</table>
+</section>
 
-<dl>
-<dt><em>Property:</em> <code>org:purpose</code>  (<code>org:Organization</code> -&gt; *)</dt>
-<dd>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. It is recommended that the purpose be denoted by a controlled 
+<!-- Property transitiveSubOrganizationOf -->
+<section>
+<h3 id="Property:_transitiveSubOrganizationOf">Property: transitiveSubOrganizationOf</h3>
+<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#transitiveSubOrganizationOf">org:transitiveSubOrganizationOf</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Domain and Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Transitive super property of:</td><td><a href="http://www.w3.org/ns/org#subOrganizationOf">org:subOrganizationOf</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> The transitive closure of subOrganizationOf, giving a representation of all organizations that contain this one. Note that technically this is a super property of the transitive closure so it could contain additional assertions but such usage is discouraged.</td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Property hasSubOrganization -->
+<section>
+<h3 id="Property:_hasSubOrganization">Property: hasSubOrganization</h3>
+<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#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>
+  </tbody>
+</table>
+</section>
+
+<!-- Property purpose -->
+<section>
+<h3 id="Property:_purpose">Property: purpose</h3>
+<p>Indicates the purpose of this Organization. There can be many purposes at different levels of abstraction but the nature of an organization is to have a reason for existence and this property is a means to document that reason. An Organization may have multiple purposes.</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#purpose">org:purpose</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> It is recommended that the purpose be denoted by a controlled 
 term or code list, ideally a <code>skos:Concept</code>. However, the 
 range is left open to allow for other types of descriptive schemes. It 
 is expected that 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).</dd>
-</dl>
-
-<p> </p>
-
-<dl>
-  <dt><em>Property:</em> <code>org:hasUnit</code>  (<code>org:Organization</code> -&gt; <code>org:OrganizationalUnit</code>, subPropertyOf <code>hasSubOrganization</code>)</dt>
-<dd>Indicates a unit which is part of this Organization, e.g. a Department within a larger FormalOrganization. Inverse of <code>org:unitOf</code>.</dd>
-</dl>
-
-<p> </p>
-
-<dl>
-  <dt><em>Property:</em> <code>org:unitOf</code>  (<code>org:OrganizationalUnit</code> -&gt; <code>org:Organization</code>, subPropertyOf <code>subOrganizationOf</code>)</dt>
-<dd>Indicates an Organization of which this Unit is a part, e.g. a 
-Department within a larger FormalOrganization. This is the inverse of <code>org:hasUnit</code>.</dd>
-</dl>
+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>
+</section>
 
-<p> </p>
+<!-- Property hasUnit -->
+<section>
+<h3 id="Property:_hasUnit">Property: hasUnit</h3>
+<p>Indicates a unit which is part of this Organization, e.g. a Department within a larger FormalOrganization.</p>
 
-<dl>
-<dt><em>Property:</em> <code>org:classification</code>  (<code>org:Organization</code> -&gt; <code>skos:Concept</code>)</dt>
-<dd>Indicates a classification for this Organization within some 
-classification scheme. Extension vocabularies may wish to specialize 
-this property to have a range corresponding to a specific <code>skos:ConceptScheme</code>.
- This property is under discussion and may be revised or removed - in 
+<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>
+</section>
+
+<!-- Property unitOf -->
+<section>
+<h3 id="Property:_unitOf">Property: unitOf</h3>
+<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>
+</section>
+
+<!-- Property classification -->
+<section>
+<h3 id="Property:_classification">Property: classification</h3>
+<p>Indicates a classification for this Organization within some 
+classification scheme. 
+<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.</dd>
-</dl>
-
-<p> </p>
+hierarchy in an extension vocabulary.</p>
 
-<dl>
-<dt><em>Property:</em> <code>org:identifier</code>  (<code>org:Organization</code> -&gt;, subPropertyOf <code>skos:notation</code>)</dt>
-<dd>Gives an identifier, such as a company registration number, that can
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#classification">org:classification</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+     Extension vocabularies may wish to specialize 
+this property to have a range corresponding to a specific <code>skos:ConceptScheme</code>
+</td></tr>
+  </tbody>
+</table>
+</section>
+
+
+<!-- Property identifier -->
+<section>
+<h3 id="Property:_identifier">Property: identifier</h3>
+<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. The org 
+national and international identier schemes are available.</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#identifier">org:identifier</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <tr><td class="prop">subPropertyOf:</td><td> <a href="http://www.w3.org/2004/02/skos/core#notation">skos:notation</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+      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.</dd>
-</dl>
-
-<p> </p>
+with recommended best practice for <code>skos:notation</code> of which this property is a specialization.
+</td></tr>
+  </tbody>
+</table>
+</section>
 
-<dl>
-<dt><em>Property:</em> <code>org:linkedTo</code>  (<code>org:Organization</code> -&gt; <code>org:Organization</code>)</dt>
-<dd>Indicates an arbitrary relationship between two organizations. 
-Specializations of this can be used to, for example, denote funding or 
-supply chain relationships.</dd>
-</dl>
+<!-- Property linkedTo -->
+<section>
+<h3 id="Property:_linkedTo">Property: linkedTo</h3>
+<p>Indicates an arbitrary relationship between two organizations.</p>
 
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#linkedTo">org:linkedTo</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Domain and Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Usage note:</td>
+	<td> 
+		Specializations of this can be used to, for example, denote funding or supply chain relationships.    
+	</td>
+    </tr>
+  </tbody>
+</table>
+</section>
+
+</section> <!-- end of Class Organization-->
+
+<!-- Class FormalOrganization -->
 <section>
-<h3>Formal organizations</h3>
+<h2 id="Class:_FormalOrganization">Class: FormalOrganization</h2>
+<p>
+ An Organization which is recognized in the world at large, in 
+particular in legal jurisdictions, with associated rights and 
+responsibilities. Examples include a Corporation, Charity, Government or
+ Church.
+</p>
+<table class="definition">
+  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#FormalOrganization">org:FormalOrganization</a></th></tr></thead>
+  <tbody>
+     <tr><td class="prop">subClassOf:</td><td> <a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+
+	Note that this is a super class of <code>gr:BusinessEntity</code> and it is recommended to use the GoodRelations vocabulary to denote Business classifications such as DUNS or NAICS.
+</td></tr>
+</tbody>
+</table>
+
+</section>  <!-- end of Class FormalOrganization-->
+
+
+<!-- Class OrganizationalUnit -->
+<section>
+<h2 id="Class:_OrganizationalUnit">Class: OrganizationalUnit</h2>
+<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.
+</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>
+</td></tr>
+</tbody>
+</table>
+
+</section> <!-- end of Class OrganizationalUnit-->
+
+<section class="informative">
+<h3>Notes on formal organizations</h3>
 <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
@@ -272,8 +519,8 @@
    whether this distinction useful in practice.</p>
 </section>
 
-<section>
-<h3>Organizational hierarchy</h3>
+<section class="informative">
+<h3>Notes on organizational hierarchy</h3>
 
 <p>In many organizations there is a hierarchy of unit structures. For example we might see a containment hierarchy like:</p>
 
@@ -288,8 +535,8 @@
 specializing <code>org:hasSubOrganization</code> and/or using <code>owl:allValuesFrom</code> restrictions on the new subclasses.</p>
 </section>
 
-<section>
-<h3>Organizational classification</h3>
+<section class="informative">
+<h3>Notes on organizational classification</h3>
 
 <p>In a number of circumstances we wish to classify organizations. There are many approaches that could be 
 taken for this. It can be based on the legal structure under which the organization operates.
@@ -311,132 +558,272 @@
 </section>	
 </section>
 
+<!-- End of section Organizational structure -->
 
 <!--    Reporting relationships and roles   -->
 <section>
 <h3>Reporting relationships and roles</h3>
-<dl>
-<dt><em>Property:</em> <code>org:memberOf</code> (<code>foaf:Agent</code> -&gt; <code>org:Organization</code>)</dt>
-<dd>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. Has an optional inverse, `org:hasmember`.</dd>
-</dl>
-
-<p> </p>
 
-<dl>
-  <dt><em>Property:</em> <code>org:hasMember</code> (<code>org:Organization</code> -&gt; <code>foaf:Agent</code>, equivalent property to <code>foaf:member</code>)</dt>
-<dd>Indicates a person who is a member of the subject Organization. 
-Inverse of `org:memberOf`, see that property for further clarification. 
-Provided for compatibility with `foaf:member`.</dd>
-</dl>
-
-<p> </p>
 
-<dl>
-<dt><em>Property:</em> <code>org:reportsTo</code> (<code>foaf:Agent</code> -&gt; <code>foaf:Agent</code>)</dt>
-<dd>Indicates a reporting relationship as might be depicted on an 
-organizational chart. 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).</dd>
-</dl>
+<!-- Class Membership -->
+<section>
+<h2 id="Class:_Membership">Class: Membership</h2>
+<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> 
 
-<p> </p>
+	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>
 
-<dl>
-<dt><em>Class:</em> <code>org:Role</code> subClassOf <code>skos:Concept</code></dt>
-<dd>Denotes a role that a Person or other Agent can take in an 
+
+<!-- Property member -->
+<section>
+<h3 id="Property:_member">Property: member</h3>
+<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>
+</section>
+
+
+
+<!-- Property organization -->
+<section>
+<h3 id="Property:_organization">Property: organization</h3>
+<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>
+</section>
+
+<!-- Property role -->
+<section>
+<h3 id="Property:_role">Property: role</h3>
+<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>
+</section>
+
+<!-- Property hasMembership -->
+<section>
+<h3 id="Property:_hasMembership">Property: hasMembership</h3>
+<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>
+</section>
+
+<!-- Property memberDuring -->
+<section>
+<h3 id="Property:_memberDuring">Property: memberDuring</h3>
+<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>
+</section>
+
+<!-- Property remuneration -->
+<section>
+<h3 id="Property:_remuneration">Property: remuneration</h3>
+<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#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>
+</section>
+
+
+</section>  <!-- end of Class Membership-->
+
+<!-- Class Role -->
+<section>
+<h2 id="Class:_Role">Class: Role</h2>
+<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>. It is 
+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.</dd>
-</dl>
-
-<p> </p>
-
-<dl>
-<dt><em>Class:</em> <code>org:Membership</code></dt>
-<dd>Indicates the nature of an Agent's membership of an organization. 
-Represents an n-ary relation between an Agent, an Organzation and a 
-Role. It is possible to directly indicate membership, independent of the
- specific Role, through use of the <code>org:memberOf</code> property.</dd>
-</dl>
-
-<p> </p>
-
-<dl>
-<dt><em>Property:</em> <code>org:member</code> (<code>org:Membership</code> -&gt; <code>foaf:Agent</code>)</dt>
-<dd>Indicates the Person (or other Agent including Organization) involved in the Membership relationship. Inverse of <code>org:hasMembership</code></dd>
-</dl>
-
-<p> </p>
-
-<dl>
-<dt><em>Property:</em> <code>org:organization</code> (<code>org:Membership</code> -&gt; <code>org:Organization</code>)</dt>
-<dd>Indicates Organization in which the Agent is a member.</dd>
-</dl>
+Role, such as a Salary band, may be added by extension vocabularies.
+</td></tr>
+</tbody>
+</table>
 
-<p> </p>
-
-<dl>
-<dt><em>Property:</em> <code>org:role</code> (<code>org:Membership</code> -&gt; <code>org:Role</code>)</dt>
-<dd>Indicates the Role that the Agent plays in a Membership relationship with an Organization.</dd>
-</dl>
-
-<p> </p>
+<!-- Property roleProperty -->
+<section>
+<h3 id="Property:_roleProperty">Property: roleProperty</h3>
+<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>
 
-<dl>
-<dt><em>Property:</em> <code>org:hasMembership</code> (<code>foaf:Agent</code> -&gt; <code>org:Membership</code>)</dt>
-<dd>Indicates a membership relationship that the Agent plays. Inverse of <code>org:member</code>.</dd>
-</dl>
-
-<p> </p>
-
-<dl>
-<dt><em>Property:</em> <code>org:memberDuring</code> (<code>org:Membership</code> -&gt; <code>owlTime:Interval</code>)</dt>
-<dd>Optional property to indicate the interval for which the membership is/was valid.</dd>
-</dl>
-
-<p> </p>
-
-<dl>
-<dt><em>Property:</em> <code>org:roleProperty</code> (<code>org:Role</code> -&gt; <code>rdf:Property</code>)</dt>
-<dd>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. The 
+<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>.</dd>
-</dl>
-
-<p> </p>
+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>
+</section>
 
-<dl>
-<dt><em>Property:</em> <code>org:headOf</code> (<code>foaf:Agent</code> -&gt; <code>org:Organization</code>) subPropertyOf <code>org:memberOf</code></dt>
-<dd>Indicates that a person (or other agent) is the leader or formal 
-head of the Organization. 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.</dd>
-</dl>
+</section>  <!-- end of Class Role-->
 
-<p> </p>
 
-<dl>
-<dt><em>Property:</em> <code>org:remuneration</code> (<code>org:Membership</code> -&gt;)</dt>
-<dd>Indicates a salary or other reward associated with the role. 
-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).</dd>
-</dl>
+<!-- Property hasMember -->
+<section>
+<h3 id="Property:_hasMember">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>
+</section>
+
+<!-- Property reportsTo -->
 <section>
+<h3 id="Property:_reportsTo">Property: reportsTo</h3>
+<p>
+	Indicates a reporting relationship as might be depicted on an 
+organizational chart.
+</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>
+</section>
+
+
+<!-- Property headOf -->
+<section>
+<h3 id="Property:_headOf">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>
+</section>
+
+<section class="informative">
 <h3>Discussion</h3>
 
 <p>In some applications then it is sufficient to represent the role of an individual
@@ -495,93 +882,199 @@
 <h2>Location</h2>
 
 
-<dl>
-<dt><em>Class:</em> <code>org:Site</code></dt>
-<dd>An office or other premise at which the organization is located. 
+<!-- Class Site -->
+<section>
+<h2 id="Class:_Site">Class: Site</h2>
+<p>
+An office or other premise at which the organization is located. 
 Many organizations are spread across multiple sites and many sites will 
-host multiple locations. In most cases a Site will be a physical 
+host multiple locations. 
+</p>
+<table class="definition">
+  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Site">org:Site</a></th></tr></thead>
+  <tbody>
+    
+    <tr><td class="prop">Usage note:</td><td> 
+ In most cases a Site will be a physical 
 location. However, we don't exclude the possibility of non-physical 
 sites such as a virtual office with an associated post box and phone 
 reception service. Extensions may provide subclasses to denote 
-particular types of site.</dd>
-</dl>
-
-<p> </p>
-
-<dl>
-<dt><em>Property:</em> <code>org:siteAddress</code>  (<code>org:Site</code> -&gt; <code>vcard:VCard</code>)</dt>
-<dd>Indicates a VCard (using the http://www.w3.org/TR/vcard-rdf/ 
-vocabulary) for the site. This can include email, telephone, and 
-geo-location details as well as an address.</dd>
-</dl>
-
-<p> </p>
-
-<dl>
-<dt><em>Property:</em> <code>org:hasSite</code>  (<code>org:Organization</code> -&gt; <code>org:Site</code>)</dt>
-<dd>Indicates a site at which the Organization has some presence even if
- only indirect (e.g. virtual office or a professional service which is 
-acting as the registered address for a company). Inverse of <code>org:siteOf</code>.</dd>
-</dl>
-
-<p> </p>
-
-<dl>
-<dt><em>Property:</em> <code>org:siteOf</code>  (<code>org:Site</code> -&gt; <code>org:Organization</code>)</dt>
-<dd>Indicates an Organization which has some presence at the given site. This is the inverse of <code>org:hasSite</code>.</dd>
-</dl>
-
-<p> </p>
+particular types of site.
+</td></tr>
+</tbody>
+</table>
 
-<dl>
-<dt><em>Property:</em> <code>org:hasPrimarySite</code>  (<code>org:Organization</code> -&gt; <code>org:Site</code>) subPropertyOf <code>org:hasSite</code></dt>
-<dd>Indicates a primary site for the Organization, this is the default 
-means by which an Organization can be contacted and is not necessarily 
-the formal headquarters.</dd>
-</dl>
-
-<p> </p>
-
-<dl>
-<dt><em>Property:</em> <code>org:hasRegisteredSite</code>  (<code>org:FormalOrganization</code> -&gt; <code>org:Site</code>) subPropertyOf <code>org:hasPrimarySite</code></dt>
-<dd>Indicates the legally registered site for the organization, in many 
-legal jurisdictions there is a requirement that FormalOrganizations such
- as Companies or Charities have such a primary designed site.</dd>
-</dl>
+<!-- Property siteAddress -->
+<section>
+<h3 id="Property:_siteAddress">Property: siteAddress</h3>
+<p>
+	Indicates a VCard (using the http://www.w3.org/TR/vcard-rdf/ 
+vocabulary) for the site. This can include email, telephone, and 
+geo-location details as well as an address.
+</p>
 
-<p> </p>
-
-<dl>
-<dt><em>Property:</em> <code>org:basedAt</code>  (<code>foaf:Person</code> -&gt; <code>org:Site</code>)</dt>
-<dd>Indicates the site at which a person is based. We do not restrict the possibility that a person is based at multiple sites.</dd>
-</dl>
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#siteAddress">org:siteAddress</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2006/vcard/ns#VCard">vcard:VCard</a></td></tr>
+    
+  </tbody>
+</table>
+</section>
 
-<p> </p>
+<!-- Property hasSite -->
+<section>
+<h3 id="Property:_hasSite">Property: hasSite</h3>
+<p>
+	Indicates a site at which the Organization has some presence even if
+ only indirect (e.g. virtual office or a professional service which is 
+acting as the registered address for a company).
+</p>
 
-<dl>
-<dt><em>Property:</em> <code>org:location</code>  (<code>foaf:Person</code> -&gt; xsd:string)</dt>
-<dd>Gives a location description for a person within the organization, for example a <em>Mail Stop</em> for internal posting purposes.</dd>
-</dl>
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasSite">org:hasSite</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
+    <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#siteOf">org:siteOf</a></td></tr>
+  </tbody>
+</table>
+</section>
 
+<!-- Property siteOf -->
+<section>
+<h3 id="Property:_siteOf">Property: siteOf</h3>
+<p>
+	Indicates an Organization which has some presence at the given site. 
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#siteOf">org:siteOf</a></th></tr></thead>
+  <tbody>
+   
+    
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#hasSite">org:hasSite</a></td></tr>
+  </tbody>
+</table>
 </section>
+
+<!-- Property hasPrimarySite -->
+<section>
+<h3 id="Property:_hasPrimarySite">Property: hasPrimarySite</h3>
+<p>
+	Indicates a primary site for the Organization, this is the default 
+means by which an Organization can be contacted and is not necessarily 
+the formal headquarters.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasPrimarySite">org:hasPrimarySite</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
+    <tr><td class="prop">subPropertyOf:</td><td><a href="http://www.w3.org/ns/org#hasSite">org:hasSite</a></td></tr>
+  </tbody>
+</table>
 </section>
 
 
+<!-- Property hasRegisteredSite -->
+<section>
+<h3 id="Property:_hasRegisteredSite">Property: hasRegisteredSite</h3>
+<p>
+	Indicates the legally registered site for the organization, in many 
+legal jurisdictions there is a requirement that FormalOrganizations such
+ as Companies or Charities have such a primary designed site.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasRegisteredSite">org:hasRegisteredSite</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
+    <tr><td class="prop">subPropertyOf:</td><td><a href="http://www.w3.org/ns/org#hasPrimarySite">org:hasPrimarySite</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Property basedAt -->
+<section>
+<h3 id="Property:_basedAt">Property: basedAt</h3>
+<p>
+	Indicates the site at which a person is based. We do not restrict the possibility that a person is based at multiple sites.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#basedAt">org:basedAt</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Person">foaf:Person</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="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>
+</section>
+</section>  <!-- end of Class Site-->
+
+
+<!-- Property location -->
+<section>
+<h3 id="Property:_location">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>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#location">org:location</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Person">foaf:Person</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2001/XMLSchema#String">xsd:string</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+</section> <!--   End of LOCATION section -->
+
+
 <!--   Projects and other activities   -->
 <section>
 <h3>Projects and other activities</h3>
+<!-- Class OrganizationalCollaboration -->
+<section>
+	<h2 id="Class:_OrganizationalCollaboration">Class: OrganizationalCollaboration</h2>
+	<p>
+	A collaboration between two or more Organizations such as a project.
+	 It meets the criteria for being an Organization in that it has an 
+	identity and defining purpose independent of its particular members but 
+	is neither a formally recognized legal entity nor a sub-unit within some
+	 larger organization. Might typically have a shorter lifetime than the 
+	Organizations within it, but not necessarily.
+	</p>
+	<table class="definition">
+	  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#OrganizationalCollaboration">org:OrganizationalCollaboration</a></th></tr></thead>
+	  <tbody>
+	     <tr><td class="prop">subClassOf:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+	    <tr><td class="prop">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>
+	</td></tr>
+	</tbody>
+	</table>
+</section> <!-- End of OrganizationalCollaboration class -->
 
-<dl>
-<dt><em>Class:</em> <code>org:OrganizationalCollaboration</code> (subClassOf  <code>org:Organization</code>)</dt>
-<dd>A collaboration between two or more Organizations such as a project.
- It meets the criteria for being an Organization in that it has an 
-identity and defining purpose independent of its particular members but 
-is neither a formally recognized legal entity nor a sub-unit within some
- larger organization. Might typically have a shorter lifetime than the 
-Organizations within it, but not necessarily. 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></dd>
-</dl>
+</section> <!--   End of Projects and other activities   -->
 
-<h2 id="historical">6. Historical information</h2>
+
+<!--   Historical information   -->
+<section>
+<h2>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. 
@@ -592,56 +1085,125 @@
 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>
 
-<dl>
-<dt><em>Class:</em> <code>org:ChangeEvent</code> (subClassOf <code>opmv:Process)</code></dt>
-<dd>Represents an event which resulted in a major change to an 
+<!-- Class ChangeEvent -->
+<section>
+<h2 id="Class:_ChangeEvent">Class: ChangeEvent</h2>
+<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 
 from the original organizations that it has a distinct identity and 
-distinct URI. Extension vocabularies should define sub-classes of this 
+distinct URI. 
+</p>
+<table class="definition">
+  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></th></tr></thead>
+  <tbody>
+     <tr><td class="prop">subClassOf:</td><td> <a href="http://purl.org/net/opmv/ns#Process">opmv:Process</a></td></tr>
+    <tr><td class="prop">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`.</dd>
-</dl>
-
-<p> </p>
-
-<dl>
-<dt><em>Property:</em> <code>org:originalOrganization</code> (<code>org:ChangeEvent</code> -&gt; <code>org:Organization</code>) subPropertyOf opmv:used</dt>
-<dd>Indicates one or more organizations that existed before the change 
-event. Depending on the event they may or may not have continued to 
-exist after the event. Inverse of `org:changedBy`. Note that in 
-specializing the OPMV vocabulary we are treating an `org:Organization` 
-as an `opmv:Artifact`, which is consistent with the OPM model.</dd>
-</dl>
-
-<p> </p>
+description should be given by `dct:description`.
+</td></tr>
+</tbody>
+</table>
 
-<dl>
-<dt><em>Property:</em> <code>org:changedBy</code> (<code>org:Organization</code> -&gt; <code>org:ChangeEvent</code>)</dt>
-<dd>Indicates a change event which resulted in a change to this 
-organization. Depending on the event the organization may or may not 
-have continued to exist after the event. Inverse of 
-`org:originalOrganzation`.</dd>
-</dl>
-
-<p> </p>
+<!-- Property originalOrganization -->
+<section>
+<h3 id="Property:_originalOrganization">Property: originalOrganization</h3>
+<p>
+	Indicates one or more organizations that existed before the change 
+event. Depending on the event they may or may not have continued to 
+exist after the event.
+</p>
 
-<dl>
-<dt><em>Property:</em> <code>org:resultedFrom</code> (<code>org:Organization</code> -&gt; <code>org:ChangeEvent</code>) subPropertyOf opmv:wasGeneratedBy</dt>
-<dd>Indicates an event which resulted in (led to, generated) this 
-organization. Inverse of `org:resultingOrganization`. Note that in 
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#originalOrganization">org:originalOrganization</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
+     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#changedBy">org:changedBy</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+      Note that in 
 specializing the OPMV vocabulary we are treating an `org:Organization` 
-as an `opmv:Artifact`, which is consistent with the OPM model.</dd>
-</dl>
-
-<dl>
-<dt><em>Property:</em> <code>org:resultingOrganization</code> (<code>org:ChangeEvent</code> -&gt; <code>org:Organization</code>)</dt>
-<dd>Indicates an organization which was created or changed as a result of the event. Inverse of `org:resultedFrom`.</dd>
-</dl>
+as an `opmv:Artifact`, which is consistent with the OPM model.
+</td></tr>
+  </tbody>
+</table>
 </section>
 
+<!-- Property changedBy -->
+<section>
+<h3 id="Property:_changedBy">Property: changedBy</h3>
+<p>
+Indicates a change event which resulted in a change to this 
+organization. 
+</p>
 
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#changedBy">org:changedBy</a></th></tr></thead>
+  <tbody>
+   
+    
+     <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
+     <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#originalOrganzation">org:originalOrganzation</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+     Depending on the event the organization may or may not 
+have continued to exist after the event.
+</td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Property resultedFrom -->
+<section>
+<h3 id="Property:_resultedFrom">Property: resultedFrom</h3>
+<p>
+Indicates an event which resulted in (led to, generated) this 
+organization.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#resultedFrom">org:resultedFrom</a></th></tr></thead>
+  <tbody>
+   
+    
+     <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
+     <tr><td class="prop">subpropertyOf:</td><td><a href="http://purl.org/net/opmv/ns#wasGeneratedBy">opmv:wasGeneratedBy</a></td></tr>
+     <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#resultingOrganization">org:resultingOrganization</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+    Note that in 
+specializing the OPMV vocabulary we are treating an `org:Organization` 
+as an `opmv:Artifact`, which is consistent with the OPM model.
+</td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Property resultingOrganization -->
+<section>
+<h3 id="Property:_resultingOrganization">Property: resultingOrganization</h3>
+<p>
+Indicates an organization which was created or changed as a result of the event.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#resultingOrganization">org:resultingOrganization</a></th></tr></thead>
+  <tbody>
+     <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
+     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#resultedFrom">org:resultedFrom</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+</section>  <!-- end of Class Role-->
+
+
+</section>  <!-- end of Section Historical-->
 <!--    ACK   -->
 <section class="appendix">
 
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/org/index.html~	Wed Feb 22 22:43:58 2012 +0100
@@ -0,0 +1,1257 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.1//EN"
+                      "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+	<title>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" />
+	<script type="text/javascript"src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+	<script src="respec-ref.js"></script>
+	<script src="respec-config.js"></script>
+	 <style type="text/css">
+	  table {
+	    border-collapse:collapse;
+	  }
+	  td, th {
+	    border:1px solid black;
+	    padding:1em;
+	  }  
+	  table#namespaces td {
+	    font-family: monospace;
+	  }
+	  table.definition {
+	    width:100%;
+	  }
+	  table.definition td.prop {
+	    width:10em;
+	  }
+          pre {
+		padding: 1em;
+		border: 1px dashed #2f6fab;
+		color: black;
+		background-color: #f9f9f9;
+		line-height: 1.1em;
+	 }
+	</style>
+	<link rel="stylesheet" type="text/css" href="local-style.css" />
+</head>
+<body>
+
+
+<section id="abstract">
+
+<p> This document describes a core ontology for organizational structures, aimed
+at supporting linked-data publishing of organizational information across
+a number of domains. It is designed to allow domain-specific extensions to add classification
+of organzations and roles, as well as extensions to support neighbouring information
+such as organizational activities.
+</p>
+</section>
+
+<section id="sotd">
+
+</section>
+
+<section class="introductory">
+<h2>Scope</h2>
+
+<p>
+This document is aimed at assisting government IT managers, procurement officers, Web developers, vendors, and researchers who are interested in publishing open government data using W3C 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. 
+</section>
+
+
+<!--    INTRODUCTION    -->
+<section class="informative">
+<h2>Introduction</h2>
+<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>
+
+</section>
+
+
+<section id="conformance">
+<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>
+</ul>
+</section>
+
+<!-- Namespaces -->
+<section>
+<h2 id="ns">Namespaces</h2>
+<p>The namespace for ORG is <code>http://www.w3.org/ns/org#</code>. However,
+it should be noted that ORG extends and uses terms from other vocabularies. A full set of alphabetically ordered namespaces and prefixes used in this
+document is shown in the table below.</p>
+<!-- Alphabetically ordered-->
+<table id="namespaces">
+  <thead><tr><th>Prefix</th><th>Namespace</th></tr></thead>
+  <tbody>
+    
+    <tr><td>foaf</td><td>http://xmlns.com/foaf/0.1/</td></tr>
+    <tr><td>gr</td><td>http://purl.org/goodrelations/v1#</td></tr>  
+    <tr><td>opmv</td><td>http://purl.org/net/opmv/ns#</td></tr> 
+    <tr><td>org</td><td>http://www.w3.org/ns/org#</td></tr>
+    <tr><td>owlTime</td><td>http://www.w3.org/2006/time#</td></tr>
+    <tr><td>skos</td><td>http://www.w3.org/2004/02/skos/core#</td></tr>
+    <tr><td>vcard</td><td>http://www.w3.org/2006/vcard/ns#</td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Overview of ontology -->
+<section class="informative">
+<h3>Overview of ontology</h3>
+
+
+<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
+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>
+<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>
+    <ul>
+      <li>people reporting structure within an organization</li>
+      <li>roles, relationship between person and organization</li>
+    </ul>
+  <li>location information</li>
+    <ul>
+     <li>sites or buildings, locations within sites</li>
+    </ul>
+  <li>organizational history (merger, renaming, repurposing)</li>
+</ul>
+
+<p>This coverage corresponds to the type of information typically
+   found in organizational charts. As such it does not offer a
+   complete representation for all the nuances of organizational
+   control structures and flows of accountability and empowerment.
+   Developers are encouraged to create extension vocabularies for such
+   purposes, building upon this generic foundation.</p>
+
+<p>The ontology does not provide category structures for organization
+type, organization purpose or roles. Different domains will have different
+requirements for classification of such concepts. Instead the ontology 
+provides just the core base concepts needed to allow extensions to add specific
+sub-class structures or classification schemes as required. 
+</p>
+
+<img src="img/diagram.png" alt="Diagram dipicting core classes and relationships">
+
+
+
+<h2 id="example">Example</h2>
+<p>This example provides a quick overview of how dcat might be used to an organization </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>
+-->
+</section>
+
+<section class="informative">
+<h3>Design notes</h3>
+
+  <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>
+
+</section>
+
+
+<section class="informative">
+<h3>Notes on style</h3>
+
+<p><em>Use of inverses:</em> authorities 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.
+Particular applications of the ontology may adopt a profile in which only certain directions are asserted in the
+  data and leave it up to clients to apply any inverseOf reasoning they require.</p>
+
+<p><em>Naming:</em> some designers prefer to name properties by nouns which describe the object
+of the property, others prefer to treat property names as names of the link and use a pattern 
+to indicate the direction of the link. Here we adopt the latter approach for those properties
+which are relational and especially when the direction is ambiguous.
+We use the URI pattern <code>org:hasFoo/org:fooOf</code> for this but simplify the labels to "foo" 
+and "foo of" to improve readability in linked data viewers.</p>
+</section>
+
+<!--    Organizational structure   -->
+<section>
+<h2>Organizational structure</h2>
+
+<!-- Class Organization -->
+<section>
+<h2 id="Class:_Organization">Class: Organization</h2>
+<p>Represents a collection of people organized together into a 
+community or other social, commercial or political structure. The group 
+has some common purpose or reason for existence which goes beyond the 
+set of people belonging to it and can act as an Agent. Organizations are
+ often decomposable into hierarchical structures. </p>
+<table class="definition">
+  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></th></tr></thead>
+  <tbody>
+     <tr><td class="prop">subClassOf:</td><td> <a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> It is recommended 
+that SKOS lexical labels should be used to label the Organization. In 
+particular <code>skos:prefLabel</code> for the primary (e.g. legally recognized name), <code>skos:altLabel</code> for alternative names (trading names, colloquial names) and <code>skos:notation</code> to denote codes from a code list. Alternative names: <em>Collective</em> <em>Body</em> <em>Org</em> <em>Group</em>.</td></tr>
+
+   
+  </tbody>
+</table>
+
+<!-- Property subOrganizationOf -->
+<section>
+<h3 id="Property:_subOrganizationOf">Property: subOrganizationOf</h3>
+<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#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>
+  </tbody>
+</table>
+</section>
+
+<!-- Property transitiveSubOrganizationOf -->
+<section>
+<h3 id="Property:_transitiveSubOrganizationOf">Property: transitiveSubOrganizationOf</h3>
+<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#transitiveSubOrganizationOf">org:transitiveSubOrganizationOf</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Domain and Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Transitive super property of:</td><td><a href="http://www.w3.org/ns/org#subOrganizationOf">org:subOrganizationOf</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> The transitive closure of subOrganizationOf, giving a representation of all organizations that contain this one. Note that technically this is a super property of the transitive closure so it could contain additional assertions but such usage is discouraged.</td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Property hasSubOrganization -->
+<section>
+<h3 id="Property:_hasSubOrganization">Property: hasSubOrganization</h3>
+<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#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>
+  </tbody>
+</table>
+</section>
+
+<!-- Property purpose -->
+<section>
+<h3 id="Property:_purpose">Property: purpose</h3>
+<p>Indicates the purpose of this Organization. There can be many purposes at different levels of abstraction but the nature of an organization is to have a reason for existence and this property is a means to document that reason. An Organization may have multiple purposes.</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#purpose">org:purpose</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> It is recommended that the purpose be denoted by a controlled 
+term or code list, ideally a <code>skos:Concept</code>. However, the 
+range is left open to allow for other types of descriptive schemes. It 
+is expected that 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>
+</section>
+
+<!-- Property hasUnit -->
+<section>
+<h3 id="Property:_hasUnit">Property: hasUnit</h3>
+<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>
+</section>
+
+<!-- Property unitOf -->
+<section>
+<h3 id="Property:_unitOf">Property: unitOf</h3>
+<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>
+</section>
+
+<!-- Property classification -->
+<section>
+<h3 id="Property:_classification">Property: classification</h3>
+<p>Indicates a classification for this Organization within some 
+classification scheme. 
+<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>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#classification">org:classification</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+     Extension vocabularies may wish to specialize 
+this property to have a range corresponding to a specific <code>skos:ConceptScheme</code>
+</td></tr>
+  </tbody>
+</table>
+</section>
+
+
+<!-- Property identifier -->
+<section>
+<h3 id="Property:_identifier">Property: identifier</h3>
+<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>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#identifier">org:identifier</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <tr><td class="prop">subPropertyOf:</td><td> <a href="http://www.w3.org/2004/02/skos/core#notation">skos:notation</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+      The org 
+ontology is neutral to which schemes are used. The particular identifier
+ scheme should be indicated by the datatype of the identifier value.  
+Using datatypes to distinguish the notation scheme used is consistent 
+with recommended best practice for <code>skos:notation</code> of which this property is a specialization.
+</td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Property linkedTo -->
+<section>
+<h3 id="Property:_linkedTo">Property: linkedTo</h3>
+<p>Indicates an arbitrary relationship between two organizations.</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#linkedTo">org:linkedTo</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Domain and Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Usage note:</td>
+	<td> 
+		Specializations of this can be used to, for example, denote funding or supply chain relationships.    
+	</td>
+    </tr>
+  </tbody>
+</table>
+</section>
+
+</section> <!-- end of Class Organization-->
+
+<!-- Class FormalOrganization -->
+<section>
+<h2 id="Class:_FormalOrganization">Class: FormalOrganization</h2>
+<p>
+ An Organization which is recognized in the world at large, in 
+particular in legal jurisdictions, with associated rights and 
+responsibilities. Examples include a Corporation, Charity, Government or
+ Church.
+</p>
+<table class="definition">
+  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#FormalOrganization">org:FormalOrganization</a></th></tr></thead>
+  <tbody>
+     <tr><td class="prop">subClassOf:</td><td> <a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+
+	Note that this is a super class of <code>gr:BusinessEntity</code> and it is recommended to use the GoodRelations vocabulary to denote Business classifications such as DUNS or NAICS.
+</td></tr>
+</tbody>
+</table>
+
+</section>  <!-- end of Class FormalOrganization-->
+
+
+<!-- Class OrganizationalUnit -->
+<section>
+<h2 id="Class:_OrganizationalUnit">Class: OrganizationalUnit</h2>
+<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.
+</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>
+</td></tr>
+</tbody>
+</table>
+
+</section> <!-- end of Class OrganizationalUnit-->
+
+<section class="informative">
+<h3>Notes on formal organizations</h3>
+<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
+   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>
+</section>
+
+<section class="informative">
+<h3>Notes on organizational hierarchy</h3>
+
+<p>In many organizations there is a hierarchy of unit structures. For example we might see a containment hierarchy like:</p>
+
+<pre class="code">Corporation
+  BusinessUnit
+    Division
+      Function
+</pre>
+
+<p>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>
+</section>
+
+<section class="informative">
+<h3>Notes on organizational classification</h3>
+
+<p>In a number of circumstances we wish to classify organizations. There are many approaches that could be 
+taken for this. It can be based on the legal structure under which the organization operates.
+For example in UK legislation there are defined notions of Partnership, Limited Company (public, private) etc
+that can be used as a basis for classification.
+Alternatively organizations can be classified by the service they provide (e.g. Educational, Manufacturing, LegalService etc).</p>
+
+<p>The core organization ontology is neutral with respect to such choices.
+It is anticipated that applications to particular domains will introduce
+subclasses of <code>org:Organization</code> to reflect the domain requirements. </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. 
+ 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>
+</section>	
+</section>
+
+<!-- End of section Organizational structure -->
+
+<!--    Reporting relationships and roles   -->
+<section>
+<h3>Reporting relationships and roles</h3>
+
+
+<!-- Class Membership -->
+<section>
+<h2 id="Class:_Membership">Class: Membership</h2>
+<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 -->
+<section>
+<h3 id="Property:_member">Property: member</h3>
+<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>
+</section>
+
+
+
+<!-- Property organization -->
+<section>
+<h3 id="Property:_organization">Property: organization</h3>
+<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>
+</section>
+
+<!-- Property role -->
+<section>
+<h3 id="Property:_role">Property: role</h3>
+<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>
+</section>
+
+<!-- Property hasMembership -->
+<section>
+<h3 id="Property:_hasMembership">Property: hasMembership</h3>
+<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>
+</section>
+
+<!-- Property memberDuring -->
+<section>
+<h3 id="Property:_memberDuring">Property: memberDuring</h3>
+<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>
+</section>
+
+<!-- Property remuneration -->
+<section>
+<h3 id="Property:_remuneration">Property: remuneration</h3>
+<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#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>
+</section>
+
+
+</section>  <!-- end of Class Membership-->
+
+<!-- Class Role -->
+<section>
+<h2 id="Class:_Role">Class: Role</h2>
+<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 -->
+<section>
+<h3 id="Property:_roleProperty">Property: roleProperty</h3>
+<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>
+
+<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>
+</section>
+
+</section>  <!-- end of Class Role-->
+
+
+<!-- Property hasMember -->
+<section>
+<h3 id="Property:_hasMember">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>
+</section>
+
+<!-- Property reportsTo -->
+<section>
+<h3 id="Property:_reportsTo">Property: reportsTo</h3>
+<p>
+	Indicates a reporting relationship as might be depicted on an 
+organizational chart.
+</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>
+</section>
+
+
+<!-- Property headOf -->
+<section>
+<h3 id="Property:_headOf">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>
+</section>
+
+<section class="informative">
+<h3>Discussion</h3>
+
+<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
+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,
+reference to the employment contract and so forth.</p>
+
+<p>For example:</p>
+
+<pre class="code">&lt;http://www.epimorphics.com/public/org#epimorphics&gt; a org:FormalOrganization;
+    skos:prefLabel "Epimorphics Ltd" .
+
+eg:ctoRole a org:Role;
+    rdfs:label "CTO" .
+        
+[] a org:Membership;
+    org:member &lt;http://www.amberdown.net/rdf/foaf.rdf#der&gt; ;
+    org:organization &lt;http://www.epimorphics.com/public/org#epimorphics&gt; ;
+    org:role eg:ctoRole;
+    org:memberDuring [a owlTime:Interval; owlTime:hasBeginning [
+                      owlTime:inXSDDateTime "2009-11-01T09:00:00Z"^^xsd:dateTime]] .
+</pre>
+
+<p>Since this representation can be a little less convenient to query and
+explore via linked-data browsing tools the core allows both explicit roles and
+simple direct relations to be used simultaneously. The relationship between
+the Role resource and the corresponding property can be indicated through 
+the <code>org:roleProperty</code> annotation. Thus we might extend the above example with:</p>
+
+<pre class="code">eg:ctoRole a org:Role;
+    org:roleProperty eg:ctoOf .
+    
+eg:ctoOf a owl:ObjectProperty, rdf:Property ;
+    rdfs:label "CTO" ;
+    rdfs:subPropertyOf org:memberOf .
+        
+&lt;http://www.amberdown.net/rdf/foaf.rdf#der&gt; 
+  eg:ctoOf &lt;http://www.epimorphics.com/public/org#epimorphics&gt; . 
+</pre>
+
+<p>In practice we antipate tool chains generating the <code>org:Membership</code> instances
+and a simple closure rule being used to add any corresponding short-cut specializations of <code>org:memberOf</code>.</p>
+</section>
+
+</section>
+
+
+<!--    LOCATION   -->
+<section>
+<h2>Location</h2>
+
+
+<!-- Class Site -->
+<section>
+<h2 id="Class:_Site">Class: Site</h2>
+<p>
+An office or other premise at which the organization is located. 
+Many organizations are spread across multiple sites and many sites will 
+host multiple locations. 
+</p>
+<table class="definition">
+  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Site">org:Site</a></th></tr></thead>
+  <tbody>
+    
+    <tr><td class="prop">Usage note:</td><td> 
+ In most cases a Site will be a physical 
+location. However, we don't exclude the possibility of non-physical 
+sites such as a virtual office with an associated post box and phone 
+reception service. Extensions may provide subclasses to denote 
+particular types of site.
+</td></tr>
+</tbody>
+</table>
+
+<!-- Property siteAddress -->
+<section>
+<h3 id="Property:_siteAddress">Property: siteAddress</h3>
+<p>
+	Indicates a VCard (using the http://www.w3.org/TR/vcard-rdf/ 
+vocabulary) for the site. This can include email, telephone, and 
+geo-location details as well as an address.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#siteAddress">org:siteAddress</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2006/vcard/ns#VCard">vcard:VCard</a></td></tr>
+    
+  </tbody>
+</table>
+</section>
+
+<!-- Property hasSite -->
+<section>
+<h3 id="Property:_hasSite">Property: hasSite</h3>
+<p>
+	Indicates a site at which the Organization has some presence even if
+ only indirect (e.g. virtual office or a professional service which is 
+acting as the registered address for a company).
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasSite">org:hasSite</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
+    <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#siteOf">org:siteOf</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Property siteOf -->
+<section>
+<h3 id="Property:_siteOf">Property: siteOf</h3>
+<p>
+	Indicates an Organization which has some presence at the given site. 
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#siteOf">org:siteOf</a></th></tr></thead>
+  <tbody>
+   
+    
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#hasSite">org:hasSite</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Property hasPrimarySite -->
+<section>
+<h3 id="Property:_hasPrimarySite">Property: hasPrimarySite</h3>
+<p>
+	Indicates a primary site for the Organization, this is the default 
+means by which an Organization can be contacted and is not necessarily 
+the formal headquarters.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasPrimarySite">org:hasPrimarySite</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
+    <tr><td class="prop">subPropertyOf:</td><td><a href="http://www.w3.org/ns/org#hasSite">org:hasSite</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+
+<!-- Property hasRegisteredSite -->
+<section>
+<h3 id="Property:_hasRegisteredSite">Property: hasRegisteredSite</h3>
+<p>
+	Indicates the legally registered site for the organization, in many 
+legal jurisdictions there is a requirement that FormalOrganizations such
+ as Companies or Charities have such a primary designed site.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasRegisteredSite">org:hasRegisteredSite</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
+    <tr><td class="prop">subPropertyOf:</td><td><a href="http://www.w3.org/ns/org#hasPrimarySite">org:hasPrimarySite</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Property basedAt -->
+<section>
+<h3 id="Property:_basedAt">Property: basedAt</h3>
+<p>
+	Indicates the site at which a person is based. We do not restrict the possibility that a person is based at multiple sites.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#basedAt">org:basedAt</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Person">foaf:Person</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="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>
+</section>
+</section>  <!-- end of Class Site-->
+
+
+<!-- Property location -->
+<section>
+<h3 id="Property:_location">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>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#location">org:location</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Person">foaf:Person</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2001/XMLSchema#String">xsd:string</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+</section> <!--   End of LOCATION section -->
+
+
+<!--   Projects and other activities   -->
+<section>
+<h3>Projects and other activities</h3>
+<!-- Class OrganizationalCollaboration -->
+<section>
+	<h2 id="Class:_OrganizationalCollaboration">Class: OrganizationalCollaboration</h2>
+	<p>
+	A collaboration between two or more Organizations such as a project.
+	 It meets the criteria for being an Organization in that it has an 
+	identity and defining purpose independent of its particular members but 
+	is neither a formally recognized legal entity nor a sub-unit within some
+	 larger organization. Might typically have a shorter lifetime than the 
+	Organizations within it, but not necessarily.
+	</p>
+	<table class="definition">
+	  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#OrganizationalCollaboration">org:OrganizationalCollaboration</a></th></tr></thead>
+	  <tbody>
+	     <tr><td class="prop">subClassOf:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+	    <tr><td class="prop">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>
+	</td></tr>
+	</tbody>
+	</table>
+</section> <!-- End of OrganizationalCollaboration class -->
+
+</section> <!--   End of Projects and other activities   -->
+
+
+<!--   Historical information   -->
+<section>
+<h2>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. 
+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 -->
+<section>
+<h2 id="Class:_ChangeEvent">Class: ChangeEvent</h2>
+<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 
+from the original organizations that it has a distinct identity and 
+distinct URI. 
+</p>
+<table class="definition">
+  <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></th></tr></thead>
+  <tbody>
+     <tr><td class="prop">subClassOf:</td><td> <a href="http://purl.org/net/opmv/ns#Process">opmv:Process</a></td></tr>
+    <tr><td class="prop">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`.
+</td></tr>
+</tbody>
+</table>
+
+<!-- Property originalOrganization -->
+<section>
+<h3 id="Property:_originalOrganization">Property: originalOrganization</h3>
+<p>
+	Indicates one or more organizations that existed before the change 
+event. Depending on the event they may or may not have continued to 
+exist after the event.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#originalOrganization">org:originalOrganization</a></th></tr></thead>
+  <tbody>
+   
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
+     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#changedBy">org:changedBy</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+      Note that in 
+specializing the OPMV vocabulary we are treating an `org:Organization` 
+as an `opmv:Artifact`, which is consistent with the OPM model.
+</td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Property changedBy -->
+<section>
+<h3 id="Property:_changedBy">Property: changedBy</h3>
+<p>
+Indicates a change event which resulted in a change to this 
+organization. 
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#changedBy">org:changedBy</a></th></tr></thead>
+  <tbody>
+   
+    
+     <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
+     <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#originalOrganzation">org:originalOrganzation</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+     Depending on the event the organization may or may not 
+have continued to exist after the event.
+</td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Property resultedFrom -->
+<section>
+<h3 id="Property:_resultedFrom">Property: resultedFrom</h3>
+<p>
+Indicates an event which resulted in (led to, generated) this 
+organization.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#resultedFrom">org:resultedFrom</a></th></tr></thead>
+  <tbody>
+   
+    
+     <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
+     <tr><td class="prop">subpropertyOf:</td><td><a href="http://purl.org/net/opmv/ns#wasGeneratedBy">opmv:wasGeneratedBy</a></td></tr>
+     <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#resultingOrganization">org:resultingOrganization</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td> 
+    Note that in 
+specializing the OPMV vocabulary we are treating an `org:Organization` 
+as an `opmv:Artifact`, which is consistent with the OPM model.
+</td></tr>
+  </tbody>
+</table>
+</section>
+
+<!-- Property resultingOrganization -->
+<section>
+<h3 id="Property:_resultingOrganization">Property: resultingOrganization</h3>
+<p>
+Indicates an organization which was created or changed as a result of the event.
+</p>
+
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#resultingOrganization">org:resultingOrganization</a></th></tr></thead>
+  <tbody>
+     <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
+     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+     <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#resultedFrom">org:resultedFrom</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+</section>  <!-- end of Class Role-->
+
+
+</section>  <!-- end of Section Historical-->
+<!--    ACK   -->
+<section class="appendix">
+
+<!--    Change history   -->
+
+<h2>Change history</h2>
+<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>
+</ul>
+
+<p>Changes since previous version 0.2 <a href="http://www.epimorphics.com/public/vocabulary/org-20100607.html">2010-06-07</a>:</p>
+<ul>
+  <li>Added <code>org:changedBy</code> and <code>org:resultingOrganization</code> as inverses to
+      the OMPV compatible properties and added a note on use of inverses.</li>
+</ul>
+
+<p>Changes since previous version 0.1 <a href="http://www.epimorphics.com/public/vocabulary/org-20100528.html">2010-05-28</a>:</p>
+<ul>
+  <li>Rephrased the introduction to clarify scoping of the ontology.</li>
+  <li>Made <code>org:Organization</code> equivalent to <code>foaf:Organization</code> following clarifying discussions with Dan Brickley.</li>
+  <li>Added <code>org:hasMember</code> as an inverse of <code>org:memberOf</code> in order to be able to declare the equivalent to <code>foaf:member</code>, thanks to Dan Brickley for the suggestion.</li>
+  <li>Made <code>org:unitOf/hasUnit</code> sub properties of <code>org:subOrganizationOf/hasSubOrganization</code>, thanks to Dave Challis for prompting this clarification.
+  </li><li>Added <code>org:transitiveSubOrganizationOf</code>, thanks to Damian Steer for the suggestion.</li>
+  <li>Fixed range statements for <code>org:role</code> and <code>org:organization</code> to correspond to the documentation and intent, thanks to Bernard Vatant for spotting that problem.</li>
+  <li>Modified description of <code>org:memberOf</code> to clarify that the notion of membership is very broad and not meant to be limited to formal notions of membership.</li>
+  <li>Clarified the description of <code>org:FormalOrganization</code>.
+  </li><li>Fixed bug in restriction definition for <code>org:OrganizationalCollaboration</code>, thanks to Start Williams for point out the problem.</li>
+  <li>Reversed <code>org:resultingOrganization</code> to <code>org:resultedFrom</code> for compatibility with OPMV, thanks to Jeni Tennison for pointing out the problem.</li>
+  <li>Changed labels for has* properties to read as nouns, leaving URIs unchanged.</li>
+  <li>Added <code>rdfs:isDefinedBy</code> declarations, thanks to Kingsley Idehen for pointing out the lack of those.</li>
+  <li>Clarified license terms, thanks to Dan Brickley for pointing out the lack.</li>
+</ul>
+
+</section>
+<section class="appendix">
+<h2>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,
+which greatly improved its design. The work also took inspiration from a
+number of other ontologies, particularly the thoughtfully designed
+<a href="http://www.london-gazette.co.uk/ontology/organisation.owl">Gazette Organization ontology</a>
+and <a href="http://proton.semanticweb.org/">Proton-top</a>.
+</p>
+
+</section>
+</body>
+</html>
--- a/org/respec-config.js	Wed Feb 22 22:38:07 2012 +0100
+++ b/org/respec-config.js	Wed Feb 22 22:43:58 2012 +0100
@@ -1,7 +1,7 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
     specStatus:           "ED",
-    publishDate:          "2012-02-03",
+    publishDate:          "2012-02-17",
     //copyrightStart:       "2010",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/org/respec-config.js~	Wed Feb 22 22:43:58 2012 +0100
@@ -0,0 +1,96 @@
+var respecConfig = {
+    // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+    specStatus:           "ED",
+    publishDate:          "2012-02-03",
+    //copyrightStart:       "2010",
+
+    // the specification's short name, as in http://www.w3.org/TR/short-name/
+    shortName:            "gld-org",
+    //subtitle:             "",
+    // if you wish the publication date to be other than today, set this
+    // publishDate:  "2009-08-06",
+
+    // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+    // and its maturity status
+    //previousPublishDate:  "2011-06-26",
+    //previousMaturity:     "ED",
+    //previousDiffURI:      "http://dvcs.w3.org/hg/gld/bp/",
+    diffTool:             "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
+
+    // if there a publicly available Editor's Draft, this is the link
+    edDraftURI:           "http://dvcs.w3.org/hg/gld/org/",
+
+    // if this is a LCWD, uncomment and set the end of its review period
+    // lcEnd: "2009-08-05",
+
+    // if you want to have extra CSS, append them to this list
+    // it is recommended that the respec.css stylesheet be kept
+    extraCSS:             [
+        "http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"
+    ],
+
+    // editors, add as many as you like
+    // only "name" is required
+    editors:  [
+        { name: "Dave Reynolds", company: "Epimorphics Ltd.", companyURL: "http://www.epimorphics.com/" }
+    ],
+
+    // authors, add as many as you like. 
+    // This is optional, uncomment if you have authors as well as editors.
+    // only "name" is required. Same format as editors.
+
+    //authors:  [],
+
+    // name of the WG
+    wg:           "Government Linked Data Working Group",
+
+    // URI of the public WG page
+    wgURI:        "http://www.w3.org/2011/gld/",
+
+    // name of the public mailing to which comments are due
+    wgPublicList: "public-gld-wg",
+
+    // URI of the patent status for this WG, for Rec-track documents
+    // !!!! IMPORTANT !!!!
+    // This is important for Rec-track documents, do not copy a patent URI from a random
+    // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+    // Team Contact.
+    wgPatentURI:  "",
+    maxTocLevel: 3,
+    preProcess: [ preProc ]
+    //alternateFormats: [ {uri: "diff-20110507.html", label: "diff to previous version"} ],
+};
+
+function updateExample(doc, content) {
+  // perform transformations to make it render and prettier
+  content = content.replace(/<!--/, '');
+  content = content.replace(/-->/, '');
+  content = doc._esc(content);
+  content = content.replace(/\*\*\*\*([^*]*)\*\*\*\*/g, '<span class="diff">$1</span>') ;
+  return content ;
+}
+
+function updateDTD(doc, content) {
+  // perform transformations to
+  // make it render and prettier
+  content = '<pre class="dtd">' + doc._esc(content) + '</pre>';
+  content = content.replace(/!ENTITY % ([^ \t\r\n]*)/g, '!ENTITY <span class="entity">% $1</span>');
+  content = content.replace(/!ELEMENT ([^ \t$]*)/mg, '!ELEMENT <span class="element">$1</span>');
+  return content;
+}
+
+function updateSchema(doc, content) {
+  // perform transformations to
+  // make it render and prettier
+  content = '<pre class="dtd">' + doc._esc(content) + '</pre>';
+  content = content.replace(/&lt;xs:element\s+name=&quot;([^&]*)&quot;/g, '&lt;xs:element name="<span class="element" id="schema_element_$1">$1</span>"') ;
+  return content;
+}
+
+function updateTTL(doc, content) {
+  // perform transformations to
+  // make it render and prettier
+  content = '<pre class="sh_sourceCode">' + doc._esc(content) + '</pre>';
+  content = content.replace(/@prefix/g, '<span class="sh_keyword">@prefix</span>');
+  return content;
+}