--- a/org/index.html Fri Oct 05 14:16:48 2012 +0100
+++ b/org/index.html Fri Oct 05 16:44:10 2012 +0100
@@ -58,6 +58,7 @@
<!-- INTRODUCTION -->
<section class="introductory">
+
<h2>Introduction</h2>
<p>This document describes a core ontology for organizational
structures (ORG), aimed
@@ -98,7 +99,7 @@
<li><a href="#reporting_structure">reporting structure</a>
<ul>
<li>people reporting structure within an organization</li>
- <li>roles, relationship between person and organization</li>
+ <li>roles, posts, relationship between person and organization</li>
</ul>
</li>
<li><a href="#location_information">location information</a>
@@ -106,7 +107,7 @@
<li>sites or buildings, locations within sites</li>
</ul>
</li>
- <li><a href="#organizational_history">organizational history (merger, renaming, repurposing)</a></li>
+ <li><a href="#organizational_history">organizational history (merger, renaming)</a></li>
</ul>
<p>This coverage corresponds to the type of information typically
@@ -128,6 +129,7 @@
<img src="img/diagram.png" alt="Diagram depicting core classes and relationships">
+<section class="informative">
<h3 id="example">Example</h3>
<p>This example illustrates a small fragment of the organizational
structure of the UK Cabinet Office:</p>
@@ -149,6 +151,7 @@
org:postIn <http://reference.data.gov.uk/id/department/co/unit/cabinet-office-communications> ;
org:heldBy <#person161> .
</pre>
+</section>
</section>
@@ -162,21 +165,46 @@
<section id="organizational_structure" class="informative">
<h3>Organizational structure</h3>
-<section class="informative">
-<h3>Notes on formal organizations</h3>
-<p>Note that the subclass hierarchy
- below <a href="#org:Organization">org:Organization</a> is not a full covering. There
- can be <a href="#org:Organization">org:Organization</a>s which are in
- neither <a href="#org:FormalOrganization">org:FormalOrganization</a>
- nor in <a href="#org:OrganizationalUnit">org:OrganizationalUnit</a>. Note also
- that the containment hierarchy is completely open
- - <a href="#org:FormalOrganization">org:FormalOrganization</a>s are free to contain
- other <a href="#org:FormalOrganization">org:FormalOrganization</a>s (e.g. subsidiaries of
+<p>The core class in the ontology
+ is <a href="#org:Organization">org:Organization</a> which is
+ intended to be applicable to a very broad range of organizations. It
+ represents a collection of people organized together into a
+ community or other social, commercial or political structure. The group
+ has some common purpose or reason for existence which goes beyond the
+ set of people belonging to it. An organization may itself be able to
+ act as an agent.</p>
+
+<p>We distinguish a particular subclass of
+ organization <a href="#org:FormalOrganization">org:FormalOrganization</a>
+ which 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
+ relations <a href="#org:subOrganizationOf">org:subOrganizationOf</a>
+ and <a href="#org:hasSubOrganization">org:hasSubOrganization</a>
+ establish these hierarchical links. </p>
+
+<p>In some cases the sub-organization can be regarded as standalone -
+ for example a complete, legally recognized, business may be part of a larger group or holding
+ company. In other cases it is useful to refer to departments or
+ organizational units such as <emphasis>the IT department</emphasis>
+ which only have meaning within the context of the containing
+ organization. The ontology supports that situation through a specialization
+ of <a href="#org:Organization">org:Organization</a>
+ called <a href="#org:OrganizationalUnit">org:OrganizationalUnit</a>. For
+ convenience it also provides the relations <a href="#org:hasUnit">org:hasUnit</a>
+ and <a href="#org:unitOf">org:unitOf</a> which are specializations
+ of the generic sub-organization links<p>
+
+<p>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>
-</section>
-<section class="informative">
-<h3>Notes on organizational hierarchy</h3>
+<h4>Organizational hierarchy</h4>
<p>In many organizations there is a hierarchy of unit structures. For example we might see a containment hierarchy like:</p>
@@ -186,15 +214,13 @@
Function
</pre>
-<p>Such hierarchies are specific to the organization, or class of
+<p>Such hierarchies are specific to the particular organization, or class of
organization being modelled. Profiles of ORG may include
sub-classes of <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>
-</section>
-<section class="informative">
-<h3>Notes on organizational classification</h3>
+<h4>Organizational classification</h4>
<p>In a number of circumstances we wish to classify organizations. There are many approaches that could be
taken for this. It can be based on the legal structure under which the organization operates.
@@ -202,14 +228,16 @@
that can be used as a basis for classification.
Alternatively organizations can be classified by the service they provide (e.g. Educational, Manufacturing, LegalService etc).</p>
-<p>The core organization ontology is neutral with respect to such choices.
-It is anticipated that profiles will either introduce
-subclasses of <a href="#org:Organization">org:Organization</a> or define a classification
- scheme to use with the <a href="#org:classification">org:classification</a>
- property. </p>
+<p>ORG is neutral with respect to such choices.
+ It is anticipated that profiles will either introduce
+ subclasses of <a href="#org:Organization">org:Organization</a> or
+ define a classification scheme for organizations. To support the
+ latter the ontology supplies a
+ property <a href="#org:classification">org:classification</a> which
+ can be used the classify an organization using a SKOS
+ [[!SKOS-REFERENCE]] concept scheme.</p>
-<p>Which of these mechanisms to use depends on the nature of the
- profile. If the classification is not intrinsic to the organization
+<p>Which of these mechanisms to use depends on situation. If the classification is not intrinsic to the organization
but simply some way to group organizations, for example as part of a
directory, then <a href="#org:classification">org:classification</a> should be used. If the
classification is a reflection of the intrinsic nature of the
@@ -218,24 +246,206 @@
For example, only Charities have CharityNumbers so it would be better to represent a
Charity as a subClassOf <a href="#org:FormalOrganization">org:FormalOrganization</a> rather
than via a taxonomic labelling.</p>
-</section>
</section>
<section id="reporting_structure" class="informative">
-<h3>Reporting structure</h3>
+<h3>Membership and Reporting structure</h3>
+
+<p>ORG provides a number of ways to represent the relationship between
+ people and organizations, together with the internal reporting
+ structure of an organization. Experience with early versions of the
+ ontology demonstrated that there is no "one size that fits
+ all". In some cases a very simple direct representation is preferred
+ for ease of consumption. In other cases a more complex
+ representation is needed to capture the nuances of the situation.
+ An ORG profile may specify that a particular subset of these
+ mechanisms be used.</p>
+
+<h4>Direct membership relation</h4>
+
+<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
+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
+built in property specialization of <a href="#org:memberOf">org:memberOf</a>, namely
+<a href="#org:headOf">org:headOf</a> for this purpose.</p>
+
+<p>For example:</p>
+
+<pre class="code"><http://example.com/people#ceo>
+ org:headOf <http://example.com/org#id> .
+</pre>
+
+<h4>Membership n-ary relationship</h4>
+
+<p>However, in general it is advantageous to have an explicit
+ representation of the organizational role that the person fulfils (e.g.
+for publication of responsibilities associated with the role), this is supported
+by the <a href="#org:Role">org:Role</a> class. The situation of an Agent fulfilling that role within an organization
+is then expressed through instances of the <a href="#org:Membership">org:Membership</a> n-ary 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"><http://example.com/org#id> a org:FormalOrganization;
+ skos:prefLabel "Example Ltd" .
+
+eg:ctoRole a org:Role;
+ rdfs:label "CTO" .
+
+[] a org:Membership;
+ org:member <http://example.com/people#jo> ;
+ org:organization <http://example.com/org#id> ;
+ org:role eg:ctoRole;
+ org:memberDuring [a 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 <a href="#org:roleProperty">org:roleProperty</a> annotation. Thus we might extend the above example with:</p>
+
+<pre class="code">eg:ctoRole a org:Role;
+ org:roleProperty eg:ctoOf .
+
+eg:ctoOf a owl:ObjectProperty, rdf:Property ;
+ rdfs:label "CTO" ;
+ rdfs:subPropertyOf org:memberOf .
+
+<http://example.com/people#jo>
+ eg:ctoOf <http://example.com/org#id> .
+</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
+ short-cut specializations of <a href="#org:memberOf">org:memberOf</a>.</p>
+
+<h4>Posts</h4>
+
+<p>The third representation that is provided by ORG is that of
+ a <a href="#org:Post">org:Post</a> which represents some position in the
+ organization that may or may not be currently filled. Posts enable
+ reporting structures and organization charts to be represented
+ independently of the individuals holding those posts. Posts can
+ report to other Posts.<p>
+
+<p>So a <a href="#org:Post">org:Post</a> can exist without someone holding that
+ post. In contrast, a <a href="#org:Membership">org:Membership</a> represents the relationship between
+ a particular individual (Agent) and the organization and does not
+ exist unless there is an Agent to partake of the relationship.</p>
+
+<p>A <a href="#org:Post">org:Post</a> is also defined as a sub-class
+ of <a href="#org:Organization">org:Organization</a> to allow for cases where a Post is
+ actually held by a group of people (whether as a timeshare, as a
+ team or as a formal group such as a committee). </p>
+
+<p>A post can have an associated <a href="#org:Role">org:Role</a>.</p>
+
+<h4>Relationship between Posts and Membership</h4>
+
+<p>In many cases only one of Posts and Memberships is needed to model
+ the situation and ORG profiles may specify that use of one of
+ these is preferred. In cases where the structure of the organization is to be
+ given, independently of the people within that
+ structure then <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>
+
+<pre class="code">
+CONSTRUCT {
+ ?agent org:memberOf ?org .
+} WHERE {
+ ?agent org:holds ?post .
+ ?post org:postIn ?org .
+}
+
+CONSTRUCT {
+ ?agent org:memberOf ?org .
+} WHERE {
+ [] a org:Membership;
+ org:member ?agent ;
+ org:organization ?org .
+}
+
+CONSTRUCT {
+ [] a org:Membership;
+ org:member ?agent ;
+ org:organization ?org;
+ org:role ?role .
+} WHERE {
+ ?agent org:holds ?post .
+ ?post org:postIn ?org .
+ ?post org:role ?role .
+}
+
+CONSTRUCT {
+ ?agent ?roleprop ?org .
+} WHERE {
+ [] a org:Membership;
+ org:member ?agent ;
+ org:organization ?org;
+ org:role [ org:roleProperty ?roleprop ] .
+}
+</pre>
+
</section>
<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
+ 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>
+
+<p>The ontology
+ provides <a href="#org:siteAddress">org:siteAddress</a> to define
+ the address of a site using the vCard [[!VCARD]] vocabulary.</p>
+
</section>
<section id="organizational_history" class="informative">
<h3>Organizational history</h3>
+
+<p>Any aspect of organizational structure is subject to change over time.
+For the most part this should be handled by an external mechanism such as named graphs.
+When Organizations change substantially (not simply a change of personnel or internal structure,
+for example a merger to create a new organization) then the new Organization
+will typically be denoted by a new URI. In that case we need some
+ vocabulary to describe that change over time
+ and the relationship between the original and resulting resources.
+ The Event mechanism here gives a generic hook for this, building upon
+ the PROV-O Provenance Vocabulary [[!PROV-O]].</p>
+
+<h5>Note</h5>
+
+<p>In earlier versions of this ontology
+ the <a href="http://open-biomed.sourceforge.net/opmv/ns">OPMV
+ Provenance Vocabulary</a> was used.
+ We believe that the PROV-O terms used here are equivalent to the corresponding
+ OPMV terms previously used and that this change does not affect the
+ semantics of the ontology. </p>
+
</section>
<section class="informative">
-<h3>Notes on style</h3>
+<h3>Notes on modelling style</h3>
<p><em>Use of inverses:</em> designers differ on whether providing pairs of inverse relationships between
concepts is good practice compared to declaring each relationship in just one direction. In this design we
@@ -262,8 +472,9 @@
<ul>
<li>it uses terms (classes and properties) from ORG in a way consistent with
their semantics as declared in this specification;</li>
-<li>it does <strong>not</strong> use terms from other vocabularies instead of ones defined
- in this vocabulary that could reasonably be used.</li>
+<li>it does <strong>not</strong> use terms from other vocabularies <strong>instead</strong> of ones defined
+ in this vocabulary that could reasonably be used (use of such
+ terms <strong>in addition</strong> to ORG terms is permissible).</li>
</ul>
</p>
@@ -277,15 +488,18 @@
<p>An <strong>ORG profile</strong> is a specification for data
interchange that adds additional constraints to ORG. Additional
constraints in a profile <em class="rfc2119" title="may">may</em>
- include:
+ include (but are not limited to):
<ul>
<li>a minimum set of required terms;</li>
<li>classes and properties for additional terms not covered in ORG;</li>
-<li>controlled vocabularies or URI sets as acceptable values for
+<li>controlled vocabularies or controlled sets of URIs to use as acceptable values for
properties;</li>
<li>guidance on use of pairs of inverse properties (such as selecting only one
member of the pair to be included, or requiring that both
- members be explicitly included).</li>
+ members be explicitly included);</li>
+<li>guidance on choice of modelling approach for roles
+ (see <a href="#reporting_structure">Membership and Reporting
+ structure</a>).</li>
</ul>
</p>
@@ -317,8 +531,63 @@
<!-- Ontology section -->
-<!-- <section id="description" class="informative"> -->
-<1-- </section> <!-- end of ontology section -->
+<section id="ontology_reference">
+<h2>Ontology Reference</h2>
+
+<section id="ontology_index">
+<h3>Index of classes and properties</h3>
+
+<p><strong>Classes:</strong>
+ | <a href="#org:ChangeEvent">ChangeEvent</a>
+ | <a href="#org:FormalOrganization">FormalOrganization</a>
+ | <a href="#org:Membership">Membership</a>
+ | <a href="#org:OrganizationalCollaboration">OrganizationalCollaboration</a>
+ | <a href="#org:OrganizationalUnit">OrganizationalUnit</a>
+ | <a href="#org:Organization">Organization</a>
+ | <a href="#org:Post">Post</a>
+ | <a href="#org:Role">Role</a>
+ | <a href="#org:Site">Site</a> |
+</p>
+
+<p><strong>Properties:</strong>
+ | <a href="#org:basedAt">basedAt</a>
+ | <a href="#org:changedBy">changedBy</a>
+ | <a href="#org:classification">classification</a>
+ | <a href="#org:hasMember">hasMember</a>
+ | <a href="#org:hasMembership">hasMembership</a>
+ | <a href="#org:hasPost">hasPost</a>
+ | <a href="#org:hasPrimarySite">hasPrimarySite</a>
+ | <a href="#org:hasRegisteredSite">hasRegisteredSite</a>
+ | <a href="#org:hasSite">hasSite</a>
+ | <a href="#org:hasSubOrganization">hasSubOrganization</a>
+ | <a href="#org:hasUnit">hasUnit</a>
+ | <a href="#org:headOf">headOf</a>
+ | <a href="#org:heldBy">heldBy</a>
+ | <a href="#org:holds">holds</a>
+ | <a href="#org:identifier">identifier</a>
+ | <a href="#org:linkedTo">linkedTo</a>
+ | <a href="#org:location">location</a>
+ | <a href="#org:memberDuring">memberDuring</a>
+ | <a href="#org:memberOf">memberOf</a>
+ | <a href="#org:member">member</a>
+ | <a href="#org:organization">organization</a>
+ | <a href="#org:originalOrganization">originalOrganization</a>
+ | <a href="#org:postIn">postIn</a>
+ | <a href="#org:purpose">purpose</a>
+ | <a href="#org:remuneration">remuneration </a>
+ | <a href="#org:reportsTo">reportsTo</a>
+ | <a href="#org:resultedFrom">resultedFrom</a>
+ | <a href="#org:resultingOrganization">resultingOrganization</a>
+ | <a href="#org:role">role</a>
+ | <a href="#org:roleProperty">roleProperty</a>
+ | <a href="#org:siteAddress">siteAddress</a>
+ | <a href="#org:siteOf">siteOf</a>
+ | <a href="#org:subOrganizationOf">subOrganizationOf</a>
+ | <a href="#org:transitiveSubOrganizationOf">transitiveSubOrganizationOf</a>
+ | <a href="#org:unitOf">unitOf</a> |
+</p>
+
+</section>
<!-- Organizational structure -->
<section>
@@ -333,7 +602,7 @@
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>
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></th></tr></thead>
<tbody>
<tr><td class="prop">subClassOf:</td><td> <a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
<tr><td class="prop">Usage note:</td><td> It is recommended
@@ -487,7 +756,7 @@
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>
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#FormalOrganization">org:FormalOrganization</a></th></tr></thead>
<tbody>
<tr><td class="prop">subClassOf:</td><td> <a href="#org:Organization">org:Organization</a></td></tr>
<tr><td class="prop">Usage note:</td><td>
@@ -510,7 +779,7 @@
regarded as a legal entity in its own right.
</p>
<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#OrganizationalUnit">org:OrganizationalUnit</a></th></tr></thead>
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#OrganizationalUnit">org:OrganizationalUnit</a></th></tr></thead>
<tbody>
<tr><td class="prop">subClassOf:</td><td> <a href="#org:Organization">org:Organization</a></td></tr>
<tr><td class="prop">Usage note:</td><td>
@@ -567,158 +836,6 @@
<section>
<h2>Membership, roles, posts and reporting</h2>
-<section class="informative">
-<h3>Discussion</h3>
-
-<p>ORG provides a number of ways to represent the relationship between
- people and organizations, together with the internal reporting
- structure of an organization. Experience with early versions of the
- ontology demonstrated that there is no "one size that fits
- all". In some cases a very simple direct representation is preferred
- for ease of consumption. In other cases a more complex
- representation is needed to capture the nuances of the situation.
- An ORG profile may specify that a particular subset of these
- mechanisms be used.</p>
-
-<h4>Direct membership relation</h4>
-
-<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
-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
-built in property specialization of <a href="#org:memberOf">org:memberOf</a>, namely
-<a href="#org:headOf">org:headOf</a> for this purpose.</p>
-
-<p>For example:</p>
-
-<pre class="code"><http://example.com/people#ceo>
- org:headOf <http://example.com/org#id> .
-</pre>
-
-<h4>Membership n-ary relationship</h4>
-
-<p>However, in general it is advantageous to have an explicit
- representation of the organizational role that the person fulfils (e.g.
-for publication of responsibilities associated with the role), this is supported
-by the <a href="#org:Role">org:Role</a> class. The situation of an Agent fulfilling that role within an organization
-is then expressed through instances of the <a href="#org:Membership">org:Membership</a> n-ary 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"><http://example.com/org#id> a org:FormalOrganization;
- skos:prefLabel "Example Ltd" .
-
-eg:ctoRole a org:Role;
- rdfs:label "CTO" .
-
-[] a org:Membership;
- org:member <http://example.com/people#jo> ;
- org:organization <http://example.com/org#id> ;
- org:role eg:ctoRole;
- org:memberDuring [a 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 <a href="#org:roleProperty">org:roleProperty</a> annotation. Thus we might extend the above example with:</p>
-
-<pre class="code">eg:ctoRole a org:Role;
- org:roleProperty eg:ctoOf .
-
-eg:ctoOf a owl:ObjectProperty, rdf:Property ;
- rdfs:label "CTO" ;
- rdfs:subPropertyOf org:memberOf .
-
-<http://example.com/people#jo>
- eg:ctoOf <http://example.com/org#id> .
-</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
- short-cut specializations of <a href="#org:memberOf">org:memberOf</a>.</p>
-
-<h4>Posts</h4>
-
-<p>The third representation that is provided by ORG is that of
- a <a href="#org:Post">org:Post</a> which represents some position in the
- organization that may or may not be currently filled. Posts enable
- reporting structures and organization charts to be represented
- independently of the individuals holding those posts. Posts can
- report to other Posts.<p>
-
-<p>So a <a href="#org:Post">org:Post</a> can exist without someone holding that
- post. In contrast, a <a href="#org:Membership">org:Membership</a> represents the relationship between
- a particular individual (Agent) and the organization and does not
- exist unless there is an Agent to partake of the relationship.</p>
-
-<p>A <a href="#org:Post">org:Post</a> is also defined as a sub-class
- of <a href="#org:Organization">org:Organization</a> to allow for cases where a Post is
- actually held by a group of people (whether as a timeshare, as a
- team or as a formal group such as a committee). </p>
-
-<p>A post can have an associated <a href="#org:Role">org:Role</a>.</p>
-
-<h4>Relationship between Posts and Membership</h4>
-
-<p>In many cases only one of Posts and Memberships is needed to model
- the situation and ORG profiles may specify that use of one of
- these is preferred. In cases where the structure of the organization is to be
- given, independently of the people within that
- structure then <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>
-
-<pre class="code">
-CONSTRUCT {
- ?agent org:memberOf ?org .
-} WHERE {
- ?agent org:holds ?post .
- ?post org:postIn ?org .
-}
-
-CONSTRUCT {
- ?agent org:memberOf ?org .
-} WHERE {
- [] a org:Membership;
- org:member ?agent ;
- org:organization ?org .
-}
-
-CONSTRUCT {
- [] a org:Membership;
- org:member ?agent ;
- org:organization ?org;
- org:role ?role .
-} WHERE {
- ?agent org:holds ?post .
- ?post org:postIn ?org .
- ?post org:role ?role .
-}
-
-CONSTRUCT {
- ?agent ?roleprop ?org .
-} WHERE {
- [] a org:Membership;
- org:member ?agent ;
- org:organization ?org;
- org:role [ org:roleProperty ?roleprop ] .
-}
-</pre>
-
-</section>
<!-- Property memberOf -->
<section>
@@ -796,7 +913,7 @@
Indicates the nature of an Agent's membership of an organization.
</p>
<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></th></tr></thead>
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></th></tr></thead>
<tbody>
<!--tr><td class="prop">subClassOf:</td><td> <a href="#org:Organization">org:Organization</a></td></tr-->
<tr><td class="prop">Usage note:</td><td>
@@ -920,7 +1037,7 @@
organization use an instance of <a href="#org:Membership">org:Membership</a>.
</p>
<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Role">org:Role</a></th></tr></thead>
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#Role">org:Role</a></th></tr></thead>
<tbody>
<tr><td class="prop">subClassOf:</td><td> <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
<tr><td class="prop">Usage note:</td><td>
@@ -995,7 +1112,7 @@
a organization in its own right.
</p>
<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Post">org:Post</a></th></tr></thead>
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#Post">org:Post</a></th></tr></thead>
<tbody>
<tr><td class="prop">subClassOf:</td><td> <a href="#org:Organization">org:Organization</a></td></tr>
</tbody>
@@ -1119,7 +1236,7 @@
host multiple locations.
</p>
<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Site">org:Site</a></th></tr></thead>
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#Site">org:Site</a></th></tr></thead>
<tbody>
<tr><td class="prop">Usage note:</td><td>
@@ -1286,7 +1403,7 @@
Organizations within it, but not necessarily.
</p>
<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#OrganizationalCollaboration">org:OrganizationalCollaboration</a></th></tr></thead>
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#OrganizationalCollaboration">org:OrganizationalCollaboration</a></th></tr></thead>
<tbody>
<tr><td class="prop">subClassOf:</td><td><a href="#org:Organization">org:Organization</a></td></tr>
<tr><td class="prop">Usage note:</td><td>
@@ -1303,15 +1420,6 @@
<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 resources.
-The Event mechanism here gives a generic hook for this, building upon the
-<a href="http://open-biomed.sourceforge.net/opmv/ns">OPMV Provenance Vocabulary</a>.</p>
-
<!-- Class ChangeEvent -->
<section>
<h2 id="org:ChangeEvent">Class: ChangeEvent</h2>
@@ -1323,7 +1431,7 @@
distinct URI.
</p>
<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></th></tr></thead>
+ <thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></th></tr></thead>
<tbody>
<tr><td class="prop">subClassOf:</td><td> <a href="http://purl.org/net/opmv/ns#Process">opmv:Process</a></td></tr>
<tr><td class="prop">Usage note:</td><td>
@@ -1429,8 +1537,10 @@
</section> <!-- end of Class Role-->
+</section> <!-- end of Section Historical-->
-</section> <!-- end of Section Historical-->
+</section> <!-- end of ontology reference section -->
+
<!-- ACK -->
<section class="appendix">
--- a/org/respec-ref.js Fri Oct 05 14:16:48 2012 +0100
+++ b/org/respec-ref.js Fri Oct 05 16:44:10 2012 +0100
@@ -9,7 +9,9 @@
berjon.biblio["VOID-GUIDE"] = "<cite><a href=\"http://www.w3.org/TR/void/\">Describing Linked Datasets with the VoID Vocabulary</a></cite>, K. Alexander, R. Cyganiak, M. Hausenblas, and J. Zhao, W3C Interest Group Note 03 March 2011. URL: http://www.w3.org/TR/void/";
berjon.biblio["RDFA-CORE-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/rdfa-1.1\">RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 02 June 2011. URL: http://www.w3.org/profile/rdfa-1.1";
berjon.biblio["XHTML-RDFA-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/html-rdfa-1.1\">HTML+RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 24 May 2011. URL: http://www.w3.org/profile/html-rdfa-1.1";
- 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["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>";
// process the document before anything else is done
var refs = document.querySelectorAll('adef') ;