--- a/org/index.html Thu Feb 09 11:58:18 2012 -0500
+++ b/org/index.html Thu Feb 09 20:44:56 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,47 @@
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>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,19 +145,94 @@
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">
-</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>
+<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> :catalog
+ a dcat:Catalog ;
+ dct:title "Imaginary catalog" ;
+ rdfs:label "Imaginary catalog" ;
+ foaf:homepage <<a href="http://example.org/catalog" class="external free" title="http://example.org/catalog" rel="nofollow">http://example.org/catalog</a>> ;
+ dct:publisher :transparency-office ;
+ dcat:themes :themes ;
+ dct:language "en"^^xsd:language ;
+ dcat:dataset :dataset/001 ;
+ .
+</pre>
+<p>The publisher of the catalog has the relative URI :transparency-office. Further description of the publisher can be provided as in the following example:
+</p>
+<pre> :transparency-office
+ a foaf:Agent ;
+ rdfs:label "Transparency Office" ;
+ .
+</pre>
+<p>The catalog classify its datasets according to a set of domains represented by the relative URI :themes. SKOS can be used to describe the domains used:
+</p>
+<pre> :themes
+ a skos:ConceptScheme ;
+ skos:prefLabel "A set of domains to classify documents" ;
+ .
+</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 :dataset/001. A possible description of it using dcat is shown below:
+</p>
+<pre> :dataset/001
+ a dcat:Dataset ;
+ dct:title "Imaginary dataset" ;
+ dcat:keyword "accountability","transparency" ,"payments" ;
+ dcat:theme :themes/accountability ;
+ dct:issued "2011-12-05"^^xsd:date ;
+ dct:updated "2011-12-05"^^xsd:date ;
+ dct:publisher :agency/finance-ministry ;
+ dct:accrualPeriodicity "every six months" ;
+ dct:language "en"^^xsd:language ;
+ dcat:Distribution :dataset/001/csv ;
+ .
+</pre>
+<p>Notice that this dataset is classified under the domain represented by the relative URI :themes/accountability. This should be part of the domains set identified by the URI :themes that was used to describe the catalog domains. An example SKOS description
+</p>
+<pre> :themes/accountability
+ a skos:Concept ;
+ skos:inScheme :themes ;
+ skos:prefLabel "Accountability" ;
+ .
+</pre>
+<p>The dataset can be downloaded in CSV format via the distribution represented by :dataset/001/csv.
+</p>
+<pre> :dataset/001/csv
+ a dcat:Distribution ;
+ dcat:accessURL <<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>> ;
+ dct:title "CSV distribution of imaginary dataset 001" ;
+ 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, :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> :record/001
+ a dcat:CatalogRecord ;
+ foaf:primaryTopic :dataset/001 ;
+ dct:issued "2011-12-11"^^xsd:date ;
+ .
+ :catalog
+ dcat:record :record/001 ;
+ .
+</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>
@@ -125,138 +263,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> -> <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> -> <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> -> <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> -> *)</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> -> <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> -> <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> -> <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> ->, 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> -> <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>
+<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>
-<h3>Formal organizations</h3>
+<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
@@ -273,7 +518,7 @@
</section>
<section>
-<h3>Organizational hierarchy</h3>
+<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>
@@ -289,7 +534,7 @@
</section>
<section>
-<h3>Organizational classification</h3>
+<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,6 +556,7 @@
</section>
</section>
+<!-- End of section Organizational structure -->
<!-- Reporting relationships and roles -->
<section>