--- a/org/index.html Sun Sep 30 21:29:08 2012 +0100
+++ b/org/index.html Mon Oct 01 09:21:48 2012 +0100
@@ -2,7 +2,7 @@
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<title>An organization ontology</title>
- <meta name="description" content="Best Practices for Publishing Linked Data" />
+ <meta name="description" content="An organization ontology" />
<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 type="text/javascript" src="respec-ref.js" class="remove"></script>
@@ -67,7 +67,8 @@
<!-- INTRODUCTION -->
<section class="informative">
<h2>Introduction</h2>
-<p>This document describes a core ontology for organizational structures, aimed
+<p>This document describes a core ontology for organizational
+ structures (ORG), aimed
at supporting linked-data publishing of organizational information across
a number of domains. It is designed to allow domain-specific extensions to add classification
of organzations and roles, as well as extensions to support neighbouring information
@@ -152,7 +153,7 @@
ontology for organizational information and then let developers extend
and specialize it to particular domains. </p>
-<p>The ontology gives minimal terms to support representation of:</p>
+<p>The ontology gives terms to support representation of:</p>
<ul>
<li>organizational structure
<ul>
@@ -229,7 +230,7 @@
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 of maintenance of those relationships.
+ of maintenance of those relationships.
Particular applications of the ontology may adopt a profile in which only certain directions are asserted in the
data and leave it up to clients to apply any inverseOf reasoning they require.</p>
@@ -324,8 +325,8 @@
<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>
+is expected that profiles of this
+vocabulary will constrain the range of <code>org:purpose</code>. Alternative names: <em>remit</em>, <em>responsibility</em> (esp. if applied to OrganizationalUnits such as Government Departments).</td></tr>
</tbody>
</table>
</section>
@@ -337,7 +338,7 @@
<p>Indicates a classification for this Organization within some
classification scheme. </p>
<p>Note that it also permissible for applications to define
- sub-classes of <code>org:Organization</code> as means to represent
+ sub-classes of <code>org:Organization</code> as a means to represent
orgnanizational categories.</p>
<table class="definition">
@@ -359,8 +360,7 @@
<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>
+ be used to used to uniquely identify the organization.</p>
<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#identifier">org:identifier</a></th></tr></thead>
@@ -369,8 +369,8 @@
<tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
<tr><td class="prop">subPropertyOf:</td><td> <a href="http://www.w3.org/2004/02/skos/core#notation">skos:notation</a></td></tr>
<tr><td class="prop">Usage note:</td><td>
- The org
-ontology is neutral to which schemes are used. The particular identifier
+ Many different national and international identier schemes are available from other
+ vocabularies. The ORG ontology is neutral to which schemes are used. The particular identifier
scheme should be indicated by the datatype of the identifier value.
Using datatypes to distinguish the notation scheme used is consistent
with recommended best practice for <code>skos:notation</code> of which this property is a specialization.
@@ -652,9 +652,9 @@
given, independently of the people within that
structure then <code>org:Post</code> is the appropriate
representation to choose. In cases where the aim is to record
- the people who make up the organization
- then <code>org:Membership</code> is appropriate, especially if the
- duration of the membership is to be represented.</p>
+ the people who make up the organization and those memberships are
+ likely to be annotated (e.g. with duration of the membership)
+ then <code>org:Membership</code> is appropriate.</p>
<p>We can state a formal relationship between these
representations in the form of entailment rules. We express these
@@ -693,8 +693,7 @@
[] a org:Membership;
org:member ?agent ;
org:organization ?org;
- org:role ?role .
- ?role org:roleProperty ?roleprop .
+ org:role [ org:roleProperty ?roleprop ] .
}
</pre>
@@ -712,15 +711,15 @@
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, <code>org:hasMember</code>.
+ nuanced relationships to the organization.
</p>
<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#memberOf">org:memberOf</a></th></tr></thead>
<tbody>
<tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
+ <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#hasMember">org:hasMember</a></td></tr>
</tbody>
</table>
</section>
@@ -739,6 +738,7 @@
<tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
<tr><td class="prop">Range:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
<tr><td class="prop">Equivalent property:</td><td><a href="http://xmlns.com/foaf/0.1/member">foaf:member</a></td></tr>
+ <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#memberOf">org:memberOf</a></td></tr>
<tr><td class="prop">Usage note:</td><td>
Provided for compatibility with <code>foaf:member</code>.
</td></tr>
@@ -833,7 +833,7 @@
<p>
Indicates the Role that the Agent plays in a Membership
relationship with an Organization. Can also be used on
- a <code>org:Post</code> to indicate the role than any holder
+ a <code>org:Post</code> to indicate the role that any holder
of the Post plays.
</p>
@@ -887,27 +887,6 @@
</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#Role">org:Role</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- Typically this will be denoted using an existing representation scheme
-such as <code>gr:PriceSpecification</code> but the range is left open to allow applications to specialize it (e.g. to remunerationInGBP).
-</td></tr>
-
- </tbody>
-</table>
-</section>
-
-
</section> <!-- end of Class Membership-->
<!-- Class Role -->
@@ -955,6 +934,27 @@
</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#Role">org:Role</a></td></tr>
+ <tr><td class="prop">Usage note:</td><td>
+ Typically this will be denoted using an existing representation scheme
+such as <code>gr:PriceSpecification</code> but the range is left open to allow applications to specialize it (e.g. to remunerationInGBP).
+</td></tr>
+
+ </tbody>
+</table>
</section>
</section> <!-- end of Class Role-->
@@ -1057,9 +1057,9 @@
<h3 id="Property:_reportsTo">Property: reportsTo</h3>
<p>
Indicates a reporting relationship as might be depicted on an
-organizational chart. I can be used to indicate a reporting
+organizational chart. It can be used to indicate a reporting
relationship directly between Agents or between Posts that
- Agents could hold
+ Agents could hold.
</p>
<table class="definition">
@@ -1297,7 +1297,7 @@
<p>
Represents an event which resulted in a major change to an
organization such as a merger or complete restructuring. It is intended
-for situations where the resulting organization is sufficient distinct
+for situations where the resulting organization is sufficiently distinct
from the original organizations that it has a distinct identity and
distinct URI.
</p>
@@ -1424,7 +1424,7 @@
and <code>org:subOrganizationOf</code>.</li>
<li>Corrected domain of <code>org:remuneration</code> to match ontology.</li>
<li>Corrected domain/range of <code>org:hasMember</code> to match ontology.</li>
- <li>Added misssing entry for <code>org:memberOf</code> to match
+ <li>Added missing entry for <code>org:memberOf</code> to match
ontology.</li>
<li>Rephrasing and reordering throughout the document to improve clarity.</li>
</ul>