final edits in response to Richard's review
authorDave Reynolds <dave@epimorphics.com>
Sat, 06 Oct 2012 17:51:02 +0100
changeset 217 e5420d8a200f
parent 216 1b7eb22b1c01
child 218 751155c13429
final edits in response to Richard's review
org/img/diagram.png
org/index.html
org/respec-ref.js
org/vocab/org.ttl
Binary file org/img/diagram.png has changed
--- a/org/index.html	Fri Oct 05 16:49:35 2012 +0100
+++ b/org/index.html	Sat Oct 06 17:51:02 2012 +0100
@@ -60,8 +60,8 @@
 <section class="introductory">
 
 <h2>Introduction</h2>
-<p>This document describes a core ontology for organizational
-  structures (ORG), aimed
+<p>This document describes a core ontology (ORG) for organizational
+  structures, aimed
 at supporting linked data publishing of organizational information across
 a number of domains. It is designed to allow domain-specific extensions to add classification
 of organizations and roles, as well as extensions to support neighbouring information
@@ -69,9 +69,9 @@
 
 <p>This document does not prescribe any particular method of deploying
   data expressed in ORG. ORG is applicable in many contexts including
-  RDF accessible via SPARQL endpoints, embedded in HTML pages as RDFa,
-  or serialized as e.g. RDF/XML or Turtle. The examples in this
-  document use Turtle in the interests of readability.</p>
+  RDF accessible via SPARQL endpoints, embedded in HTML pages,
+  or serialized as an RDF/XML or Turtle. The examples in this
+  document use Turtle [[!TURTLE]] in the interests of readability.</p>
 
 </section>
 
@@ -92,14 +92,13 @@
   <ul>
     <li>notion of an organization</li>
     <li>decomposition into sub-organizations and units</li>
-    <li>posts within an organization</li>
-    <li>purpose of an organization</li>
+    <li>purpose and classification of organizations</li>
   </ul>
   </li>
   <li><a href="#reporting_structure">reporting structure</a>
     <ul>
       <li>people reporting structure within an organization</li>
-      <li>roles, posts, relationship between person and organization</li>
+      <li>roles, posts, and the relationship between people and organizations</li>
     </ul>
   </li>
   <li><a href="#location_information">location information</a>
@@ -127,6 +126,12 @@
   controlled vocabularies to use for these concepts.
 </p>
 
+<p>A pictorial illustration of the main classes and relationships in
+  ORG is shown below. All terms are within the
+  ORG namespace (<code>http://www.w3.org/ns/org#</code>) unless an explicit prefix is
+  given. The namespaces for all referenced vocabularies are giving
+  in the section on <a href="#ns">Namespaces</a>.
+
 <img src="img/diagram.png" alt="Diagram depicting core classes and relationships">
 
 <section class="informative">
@@ -176,13 +181,13 @@
 
 <p>We distinguish a particular subclass of
   organization  <a href="#org:FormalOrganization">org:FormalOrganization</a>
-  which are recognized in the world at large, in 
+  to indicate organizations that are recognized in the world at large, in 
   particular in legal jurisdictions, with associated rights and 
   responsibilities. Examples include a Corporation, Charity, Government or
   Church.</p>
 
 <p>The ontology then supports the notion of organizations being
-  composed of other organizations some hierarchy. The
+  composed of other organizations in some hierarchy. The
   relations <a href="#org:subOrganizationOf">org:subOrganizationOf</a>
   and  <a href="#org:hasSubOrganization">org:hasSubOrganization</a>
   establish these hierarchical links. </p>
@@ -202,7 +207,6 @@
 <p>Note that the containment hierarchy is completely open. For
    example, <a href="#org:FormalOrganization">org:FormalOrganization</a>s are free to contain
    other <a href="#org:FormalOrganization">org:FormalOrganization</a>s.</p>
-   large corporations).</p>
 
 <h4>Organizational hierarchy</h4>
 
@@ -216,7 +220,8 @@
 
 <p>Such hierarchies are specific to the particular organization, or class of
   organization being modelled. Profiles of ORG may include
-  sub-classes of <a href="#org:OrganizationalUnit">org:OrganizationalUnit</a> to
+  sub-classes
+  of <a href="#org:Organization">org:Organization</a> and <a href="#org:OrganizationalUnit">org:OrganizationalUnit</a> to
   represent such structures and specialize or restrict the use
   of <a href="#org:hasSubOrganization">org:hasSubOrganization</a> to match the desired hierarchy.</p>
 
@@ -266,7 +271,7 @@
 
 <p>
 This simplest representation provided by ORG is to directly state that
-some individual (represented as a <code>foaf:Agent</code>) is <a href="#org:memberOf">org:memberOf</a> of an organization. To represent
+some individual (represented as a <a href="http://xmlns.com/foaf/spec/#term_Agent">foaf:Agent</a>) is <a href="#org:memberOf">org:memberOf</a> of an organization. To represent
 specific roles that the person plays then ORG profiles may define
 sub-properties of <a href="#org:memberOf">org:memberOf</a>. In particular, the notion
 of a leader or head of a organization is so common that ORG provides a
@@ -305,6 +310,20 @@
                       time:inXSDDateTime "2009-11-01T09:00:00Z"^^xsd:dateTime]].
 </pre>
 
+<p>The relationship between this full n-ary relationship and the 
+  direct <a href="#org:memberOf">org:memberOf</a> property can be expressed
+  as an entailment rule, using SPARQL Construct [[!RDF-SPARQL-QUERY]]:</p>
+
+<pre class="code">
+CONSTRUCT {
+    ?agent   org:memberOf  ?org.
+} WHERE {
+  [] a org:Membership;
+    org:member       ?agent;
+    org:organization ?org.
+}
+</pre>
+
 <p>Since this representation can be a little less convenient to query and
 explore via linked data browsing tools the core allows both explicit roles and
 simple direct relations to be used simultaneously. The relationship between
@@ -322,8 +341,22 @@
   eg:ctoOf &lt;http://example.com/org#id&gt;. 
 </pre>
 
-<p>In practice we anticipate tool chains generating the <a href="#org:Membership">org:Membership</a> instances
-and a simple closure rule being used to add any corresponding
+<p>The semantics of <a href="#org:roleProperty">org:roleProperty</a> can be expressed
+  using a second closure rule:</p>
+
+<pre class="code">
+CONSTRUCT {
+    ?agent   ?roleprop  ?org.
+} WHERE {
+  [] a org:Membership;
+    org:member       ?agent;
+    org:organization ?org;
+    org:role         [ org:roleProperty ?roleprop ].
+}
+</pre>
+
+<p>Tool chains may generate <a href="#org:Membership">org:Membership</a> instances
+  and then apply this closure rule to add any corresponding
   short-cut specializations of <a href="#org:memberOf">org:memberOf</a>.</p>
 
 <h4>Posts</h4>
@@ -353,15 +386,14 @@
   the situation and ORG profiles may specify that use of one of
   these is preferred. In cases where the structure of the organization is to be
   given, independently of the people within that
-  structure then <a href="#org:Post">org:Post</a> is the appropriate
+  structure, then <a href="#org:Post">org:Post</a> is the appropriate
   representation to choose. In cases where the aim is to record
   the people who make up the organization and those memberships are
   likely to be annotated (e.g. with duration of the membership)
   then <a href="#org:Membership">org:Membership</a> is appropriate.</p>
 
 <p>We can state a formal relationship between these
-  representations in the form of entailment rules. We express these
-  as a sequence of SPARQL Construct operations:</p>
+  representations in the form of two more entailment rules:</p>
 
 <pre class="code">
 CONSTRUCT {
@@ -370,15 +402,9 @@
   ?agent org:holds  ?post.
   ?post  org:postIn ?org.
 }
+</pre>
 
-CONSTRUCT {
-    ?agent   org:memberOf  ?org.
-} WHERE {
-  [] a org:Membership;
-    org:member       ?agent;
-    org:organization ?org.
-}
-
+<pre class="code">
 CONSTRUCT {
   [] a org:Membership;
     org:member       ?agent;
@@ -389,15 +415,6 @@
   ?post  org:postIn ?org.
   ?post  org:role   ?role.
 }
-
-CONSTRUCT {
-    ?agent   ?roleprop  ?org.
-} WHERE {
-  [] a org:Membership;
-    org:member       ?agent;
-    org:organization ?org;
-    org:role         [ org:roleProperty ?roleprop ].
-}
 </pre>
 
 </section>
@@ -405,14 +422,14 @@
 <section id="location_information"  class="informative">
 <h3>Location information</h3>
 
-<p>ORG allows information on locations at which organizations exist
-  through the notion an <a href="#org:Site">org:Site</a> which can be
+<p>ORG represents information on locations at which organizations exist
+  through the notion an <a href="#org:Site">org:Site</a>, which can be
   linked to an organization via <a href="#org:siteOf">org:siteOf</a>
   and <a href="#org:hasSite">org:hasSite</a>. We can distinguish
   primary sites (<a href="#org:hasPrimarySite">org:hasPrimarySite</a>)
-  and specialization of
-  that <a href="#org:hasRegisteredSite">org:hasRegisteredSite</a>
-  which indicates a legally registered site for the organization.</p>
+  and provide a specialization of
+  that (<a href="#org:hasRegisteredSite">org:hasRegisteredSite</a>)
+  indicate a legally registered site for the organization.</p>
 
 <p>The ontology
   provides <a href="#org:siteAddress">org:siteAddress</a> to define
@@ -425,12 +442,14 @@
 
 <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 
+When Organizations change substantially (not simply a change of personnel or internal structure),
+for example a merger to create a new organization, then the new Organization 
 will typically be denoted by a new URI. In that case we need some
   vocabulary to describe that change over time 
  and the relationship between the original and resulting resources. 
- The Event mechanism here gives a generic hook for this, building upon
+ORG provides <a href="#org:ChangeEvent">org:ChangeEvent</a> and
+  associated properties as a
+  foundation for this, building upon
   the PROV-O Provenance Vocabulary [[!PROV-O]].</p>
 
 <h5>Note</h5>
@@ -513,17 +532,20 @@
 document is shown in the table below.</p>
 <!-- Alphabetically ordered-->
 <table id="namespaces">
-  <thead><tr><th>Prefix</th><th>Namespace</th></tr></thead>
+  <thead><tr><th>Prefix</th><th>Namespace</th><th>Reference</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>time</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>
+    <tr><td>foaf</td><td><a href="http://xmlns.com/foaf/0.1/">http://xmlns.com/foaf/0.1/</a></td><td>[[FOAF]]</td></tr>
+    <tr><td>gr</td><td><a href="http://purl.org/goodrelations/v1">http://purl.org/goodrelations/v1#</a></td><td>[[GOOD-RELATIONS]]</td></tr>  
+    <tr><td>prov</td><td><a href="http://www.w3.org/ns/prov">http://www.w3.org/ns/prov#</a></td><td>[[!PROV-O]]</td></tr> 
+    <tr><td>org</td><td><a href="http://www.w3.org/ns/org">http://www.w3.org/ns/org#</a></td><td></td></tr>
+    <tr><td>owl</td><td><a href="http://www.w3.org/2002/07/owl">http://www.w3.org/2002/07/owl#</a></td><td>[[!OWL2-PRIMER]]</td></tr>
+    <tr><td>time</td><td><a href="http://www.w3.org/2006/time">http://www.w3.org/2006/time#</a></td><td>[[!OWL-TIME]]</td></tr>
+    <tr><td>rdf</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns">http://www.w3.org/1999/02/22-rdf-syntax-ns#</a></td><td>[[!RDF-CONCEPTS]]</td></tr>
+    <tr><td>rdfs</td><td><a href="http://www.w3.org/2000/01/rdf-schema">http://www.w3.org/2000/01/rdf-schema#</a></td><td>[[!RDF-SCHEMA]]</td></tr>
+    <tr><td>skos</td><td><a href="http://www.w3.org/2004/02/skos/core">http://www.w3.org/2004/02/skos/core#</a></td><td>[[!SKOS-REFERENCE]]</td></tr>
+    <tr><td>vcard</td><td><a href="http://www.w3.org/2006/vcard/ns#">http://www.w3.org/2006/vcard/ns#</a></td><td>[[!VCARD]]</td></tr>
+    <tr><td>dct</td><td><a href="http://purl.org/dc/terms/">http://purl.org/dc/terms/</a></td><td>[[DC11]]</td></tr>
   </tbody>
 </table>
 </section>
@@ -761,7 +783,9 @@
      <tr><td class="prop">subClassOf:</td><td> <a href="#org:Organization">org:Organization</a></td></tr>
     <tr><td class="prop">Usage note:</td><td> 
 
-	Note that this is a super class of <code>gr:BusinessEntity</code> and it is recommended to use the GoodRelations vocabulary to denote Business classifications such as DUNS or NAICS.
+	Note that this is a super class
+	of <a href="http://www.heppnetz.de/ontologies/goodrelations/v1.html#BusinessEntity">gr:BusinessEntity</a> 
+and it is recommended to use the GoodRelations vocabulary to denote Business classifications such as DUNS or NAICS.
 </td></tr>
 </tbody>
 </table>
@@ -878,7 +902,7 @@
      <tr><td class="prop">Equivalent property:</td><td><a href="http://xmlns.com/foaf/0.1/member">foaf:member</a></td></tr>
      <tr><td class="prop">inverseOf:</td><td><a href="#org:memberOf">org:memberOf</a></td></tr>
      <tr><td class="prop">Usage note:</td><td> 
-     Provided for compatibility with <code>foaf:member</code>.
+     Provided for compatibility with <a href="http://xmlns.com/foaf/spec/#term_member">foaf:member</a>.
 </td></tr>
   </tbody>
 </table>
@@ -1088,7 +1112,7 @@
      <tr><td class="prop">Domain:</td><td><a href="#org:Role">org:Role</a></td></tr>
      <tr><td class="prop">Usage note:</td><td> 
     Typically this will be denoted using an existing representation scheme 
-such as <code>gr:PriceSpecification</code> but the range is left open to allow applications to specialize it (e.g. to remunerationInGBP).
+such as <a href="http://www.heppnetz.de/ontologies/goodrelations/v1.html#PriceSpecification">gr:PriceSpecification</a> but the range is left open to allow applications to specialize it (e.g. to remunerationInGBP).
 </td></tr> 
     
   </tbody>
@@ -1130,7 +1154,7 @@
     <tr><td class="prop">Range:</td><td><a href="#org:Post">org:Post</a></td></tr>
      <tr><td class="prop">subPropertyOf:</td><td> <a href="#org:memberOf">org:memberOf</a></td></tr>
     <tr><td class="prop">Usage note:</td><td> 
-     Inverse of <a href="#org:heldBy">org:heldBy</a></code>.
+     Inverse of <a href="#org:heldBy">org:heldBy</a>.
 </td></tr>
   </tbody>
 </table>
@@ -1148,7 +1172,7 @@
     <tr><td class="prop">Range:</td><td> <a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
      <tr><td class="prop">subPropertyOf:</td><td> <a href="#org:hasMember">org:hasMember</a></td></tr>
     <tr><td class="prop">Usage note:</td><td> 
-     Inverse of <a href="#org:holds">org:holds</a></code>.
+     Inverse of <a href="#org:holds">org:holds</a>.
 </td></tr>
   </tbody>
 </table>
@@ -1165,7 +1189,7 @@
     <tr><td class="prop">Domain:</td><td><a href="#org:Post">org:Post</a></td></tr>
     <tr><td class="prop">Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
     <tr><td class="prop">Usage note:</td><td> 
-     Inverse of <a href="#org:hasPost">org:hasPost</a></code>.
+     Inverse of <a href="#org:hasPost">org:hasPost</a>.
 </td></tr>
   </tbody>
 </table>
@@ -1182,7 +1206,7 @@
     <tr><td class="prop">Domain:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
     <tr><td class="prop">Range:</td><td><a href="#org:Post">org:Post</a></td></tr>
     <tr><td class="prop">Usage note:</td><td> 
-     Inverse of <a href="#org:postIn">org:postIn</a></code>.
+     Inverse of <a href="#org:postIn">org:postIn</a>.
 </td></tr>
   </tbody>
 </table>
@@ -1433,12 +1457,15 @@
 <table class="definition">
   <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></th></tr></thead>
   <tbody>
-     <tr><td class="prop">subClassOf:</td><td> <a href="http://purl.org/net/opmv/ns#Process">opmv:Process</a></td></tr>
+     <tr><td class="prop">subClassOf:</td><td> <a href="http://www.w3.org/TR/prov-o/#Activity">prov:Activity</a></td></tr>
     <tr><td class="prop">Usage note:</td><td> 
 Extension vocabularies should define sub-classes of this 
-to denote particular categories of event. The instant or interval at 
-which the event occurred should be given by <code>opmv:wasGeneratedAt</code>, a 
-description should be given by <code>dct:description</code>.
+to denote particular categories of event. The time period over which
+the event occurred should be expressed using 
+<a href="http://www.w3.org/TR/prov-o/#startedAtTime">prov:startedAtTime</a>
+and
+<a href="http://www.w3.org/TR/prov-o/#endedAtTime">prov:endedAtTime</a>.
+A textual description of the event may be given by <a href="http://dublincore.org/documents/dcmi-terms/#terms-description">dct:description</a>.
 </td></tr>
 </tbody>
 </table>
@@ -1459,11 +1486,7 @@
     <tr><td class="prop">Domain:</td><td><a href="#org:ChangeEvent">org:ChangeEvent</a></td></tr>
      <tr><td class="prop">Range:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
      <tr><td class="prop">inverseOf:</td><td><a href="#org:changedBy">org:changedBy</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td> 
-      Note that in 
-specializing the OPMV vocabulary we are treating an <a href="#org:Organization">org:Organization</a> 
-as an <code>opmv:Artifact</code>, which is consistent with the OPM model.
-</td></tr>
+     <tr><td class="prop">subpropertyOf:</td><td><a href="#org:changedBy">prov:used</a></td></tr>
   </tbody>
 </table>
 </section>
@@ -1507,13 +1530,8 @@
     
      <tr><td class="prop">Domain:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
      <tr><td class="prop">Range:</td><td><a href="#org:ChangeEvent">org:ChangeEvent</a></td></tr>
-     <tr><td class="prop">subpropertyOf:</td><td><a href="http://purl.org/net/opmv/ns#wasGeneratedBy">opmv:wasGeneratedBy</a></td></tr>
+     <tr><td class="prop">subpropertyOf:</td><td><a href="http://www.w3.org/TR/prov-o/#wasGeneratedBy">prov:wasGeneratedBy</a></td></tr>
      <tr><td class="prop">inverseOf:</td><td><a href="#org:resultingOrganization">org:resultingOrganization</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td> 
-    Note that in 
-specializing the OPMV vocabulary we are treating an <a href="#org:Organization">org:Organization</a> 
-as an <code>opmv:Artifact</code>, which is consistent with the OPM model.
-</td></tr>
   </tbody>
 </table>
 </section>
@@ -1550,6 +1568,9 @@
 <p>Changes since <a href="http://www.w3.org/TR/2012/WD-vocab-org-20120405/">W3C Working Draft 05 April 2012</a>:
 
 <ul>
+  <li>Modified <a href="#org:ChangeEvent">org:ChangeEvent</a>, <a href="#org:originalOrganization">org:originalOrganization</a> and
+<a href="#org:resultedFrom">org:resultedFrom</a> to extend the PROV-O
+vocabulary instead of OPMV.</li>
   <li>Added <a href="#org:Post">org:Post</a> and associated properties.</li>
   <li>Corrected description of <a href="#org:hasSubOrganiation">org:hasSubOrganiation</a>
   and <a href="#org:subOrganizationOf">org:subOrganizationOf</a>.</li>
@@ -1557,7 +1578,7 @@
   <li>Corrected domain/range of <a href="#org:hasMember">org:hasMember</a> to match ontology.</li>
   <li>Added missing entry for <a href="#org:memberOf">org:memberOf</a> to match
   ontology.</li>
-  <li>Rephrasing and reordering throughout the document to improve clarity.</li>
+  <li>Rephrasing and restructuring throughout the document to improve clarity.</li>
 </ul>
 
 
@@ -1591,7 +1612,7 @@
 
 </section>
 <section class="appendix">
-<h2>Acknowledgments</h2>
+<h2>Acknowledgements</h2>
 <p>This ontology was originally developed for use by data.gov.uk as part of the UK Linked Data Kernel project
 under the leadership and guidance of John Sheridan (The National Archives).
 Jeni Tennison provided immensely useful feedback and suggestions on the first draft,
@@ -1605,7 +1626,9 @@
 Government Linked Data Working group - particularly to Daniel Vila for
 transcribing the original documentation into W3C format and to Bart
 van Leeuwen for feedback and discussions that resulted in the addition
-of <code>org:Post</code>. The modelling of <code>org:Post</code> is
+of <code>org:Post</code>. </p>
+
+<p>The modelling of <code>org:Post</code> is
 closely based on the work of Jeni Tennison on modelling UK Government.
 </p>
 
--- a/org/respec-ref.js	Fri Oct 05 16:49:35 2012 +0100
+++ b/org/respec-ref.js	Sat Oct 06 17:51:02 2012 +0100
@@ -12,6 +12,7 @@
           berjon.biblio["RFC2616"] = "<cite><a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616.html\">Hypertext Transfer Protocol -- HTTP/1.1</a></cite>, R. Fielding; et al. June 1999. Internet RFC 2616. URL: http://www.w3.org/Protocols/rfc2616/rfc2616.html.";
 	  berjon.biblio["VCARD"] =  "R. Iannella; et al. <cite><a href=\"http://www.w3.org/TR/vcard-rdf/\">Representing vCard Objects in RDF</a></cite>, January 2010. W3C Member Sumission 20 January 2010. URL: <a href=\"http://www.w3.org/Submission/2010/SUBM-vcard-rdf-20100120\">http://www.w3.org/Submission/2010/SUBM-vcard-rdf-20100120</a>";
 	  berjon.biblio["PROV-O"] =  "Timothy Lebo, Satya Sahoo, Deborah McGuinness, <cite><a href=\"http://www.w3.org/TR/2012/WD-prov-o-20120724/\">PROV-O: The PROV Ontology</a></cite>, W3C Working Draft 24 July 2012. URL: <a href=\"http://www.w3.org/TR/prov-o/\">http://www.w3.org/TR/prov-o/</a>";
+	  berjon.biblio["GOOD-RELATIONS"] =  "Martin Hepp, <cite><a href=\"http://www.heppnetz.de/ontologies/goodrelations/v1.html\">GoodRelations Language Reference</a></cite>, Version 1.0, 1 October 2011,  URL: <a href=\"http://www.heppnetz.de/ontologies/goodrelations/v1.html\">http://www.heppnetz.de/ontologies/goodrelations/v1.html</a>";
 
                 // process the document before anything else is done
                 var refs = document.querySelectorAll('adef') ;
--- a/org/vocab/org.ttl	Fri Oct 05 16:49:35 2012 +0100
+++ b/org/vocab/org.ttl	Sat Oct 06 17:51:02 2012 +0100
@@ -10,19 +10,21 @@
 @prefix org:        <http://www.w3.org/ns/org#> .
 @prefix vcard:      <http://www.w3.org/2006/vcard/ns#> .
 @prefix opmv:       <http://purl.org/net/opmv/ns#> .
[email protected] prov:       <http://www.w3.org/ns/prov#> .
 @prefix :           <http://www.w3.org/ns/org#> .
 
 # -- Meta data -----------------------------------------------------------
 
 <http://www.w3.org/ns/org#>
     a owl:Ontology;
-    owl:versionInfo "0.5";
+    owl:versionInfo "0.6";
     rdfs:label "Core organization ontology"@en;
     rdfs:comment "Vocabulary for describing organizational structures, specializable to a broad variety of types of organization."@en;
     dct:created "2010-05-28"^^xsd:date;
     dct:modified "2010-06-09"^^xsd:date;
     dct:modified "2010-10-08"^^xsd:date;
     dct:modified "2012-09-30"^^xsd:date;
+    dct:modified "2012-10-06"^^xsd:date;
     dct:title "Core organization ontology"@en;
     dct:title "Ontologie des organisations"@fr;
     dct:contributor [foaf:mbox "[email protected]"; foaf:name "Dave Reynolds"];
@@ -415,11 +417,11 @@
 # -- Historical information -----------------------------------------------------------
 
 org:ChangeEvent a owl:Class, rdfs:Class;
-    rdfs:subClassOf opmv:Process;
+    rdfs:subClassOf opmv:Process, prov:Activity;
     rdfs:label "Change Event"@en;
     rdfs:label "Évènement"@fr;
-    rdfs:comment """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 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`. """@en;    
-    rdfs:comment """Représente un Évènement impliquant un changement majeur dans l'Organisation, comme une fusion ou une restructuration. Prévu pour des situations ou l'organisation finale est suffisamment différente des Organisations originales pour qu'elle ait une identité et une URI distinctes. Des vocabulaires d'extension devraient définir des sous-classes de celle-ci pour annoter les différentes catégories d'Évènemenents. Le moment ou l'intervalle de l'Évènement devrait être indiqué avec `opmv:wasGeneratedAt`, et une description avec la classe `dct:description`. """@fr;
+    rdfs:comment """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 to denote particular categories of event. The instant or interval at which the event occurred should be given by `prov:startAtTime` and `prov:endedAtTime`, a description should be given by `dct:description`. """@en;    
+    rdfs:comment """Représente un Évènement impliquant un changement majeur dans l'Organisation, comme une fusion ou une restructuration. Prévu pour des situations ou l'organisation finale est suffisamment différente des Organisations originales pour qu'elle ait une identité et une URI distinctes. Des vocabulaires d'extension devraient définir des sous-classes de celle-ci pour annoter les différentes catégories d'Évènemenents. Le moment ou l'intervalle de l'Évènement devrait être indiqué avec `prov:startAtTime` et `prov:endedAtTime`, et une description avec la classe `dct:description`. """@fr;
     rdfs:isDefinedBy <http://www.w3.org/ns/org> ;
     .
 
@@ -428,9 +430,9 @@
     rdfs:label "organisation originelle"@fr;
     rdfs:domain org:ChangeEvent;
     rdfs:range  org:Organization;
-    rdfs:subPropertyOf opmv:used;
-    rdfs:comment """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."""@en;
-    rdfs:comment """Indique une ou plusieurs organisations qui ont existé avant un évènement de changement. Selon l'évènement, ces organisations ont pu continuer à exister ou non. Inverse de `org:changedBy`. Notez qu'en spécialisant le vocabulaire OPMV nous traitons `org:Organization` comme un `opmv:Artifact`, ce qui est cohérent avec le modèle OPM."""@fr;    
+    rdfs:subPropertyOf prov:used;
+    rdfs:comment """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`."""@en;
+    rdfs:comment """Indique une ou plusieurs organisations qui ont existé avant un évènement de changement. Selon l'évènement, ces organisations ont pu continuer à exister ou non. Inverse de `org:changedBy`. """@fr;    
     rdfs:isDefinedBy <http://www.w3.org/ns/org> ;
     .
 
@@ -452,9 +454,9 @@
     rdfs:label "issue de"@fr;
     rdfs:domain org:Organization;
     rdfs:range  org:ChangeEvent;
-    rdfs:subPropertyOf opmv:wasGeneratedBy;
-    rdfs:comment """Indicates an event which resulted in this organization. Note that in specializing the OPMV vocabulary we are treating an `org:Organization` as an `opmv:Artifact`, which is consistent with the OPM model. Inverse of `org:resultingOrganization`."""@en;
-    rdfs:comment """Indique un évènement dont est issue l'Organisation. Notez qu'en spécialisant le vocabulaire OPMV nous traitons `org:Organization` comme un `opmv:Artifact`, ce qui est cohérent avec le modèle OPM. Inverse de `org:resultingOrganization`."""@fr;    
+    rdfs:subPropertyOf prov:wasGeneratedBy;
+    rdfs:comment """Indicates an event which resulted in this organization. Inverse of `org:resultingOrganization`."""@en;
+    rdfs:comment """Indique un évènement dont est issue l'Organisation. Inverse de `org:resultingOrganization`."""@fr;    
     rdfs:isDefinedBy <http://www.w3.org/ns/org> ; 
     .