--- a/org/index.html~ Thu Mar 29 16:19:37 2012 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,1257 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.1//EN"
- "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>An organization ontology</title>
- <meta name="description" content="Best Practices for Publishing Linked Data" />
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <script type="text/javascript"src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
- <script src="respec-ref.js"></script>
- <script src="respec-config.js"></script>
- <style type="text/css">
- table {
- border-collapse:collapse;
- }
- td, th {
- border:1px solid black;
- padding:1em;
- }
- table#namespaces td {
- font-family: monospace;
- }
- table.definition {
- width:100%;
- }
- table.definition td.prop {
- width:10em;
- }
- pre {
- padding: 1em;
- border: 1px dashed #2f6fab;
- color: black;
- background-color: #f9f9f9;
- line-height: 1.1em;
- }
- </style>
- <link rel="stylesheet" type="text/css" href="local-style.css" />
-</head>
-<body>
-
-
-<section id="abstract">
-
-<p> This document describes a core ontology for organizational structures, aimed
-at supporting linked-data publishing of organizational information across
-a number of domains. It is designed to allow domain-specific extensions to add classification
-of organzations and roles, as well as extensions to support neighbouring information
-such as organizational activities.
-</p>
-</section>
-
-<section id="sotd">
-
-</section>
-
-<section class="introductory">
-<h2>Scope</h2>
-
-<p>
-This document is aimed at assisting government IT managers, procurement officers, Web developers, vendors, and researchers who are interested in publishing open government data using W3C standards. The benefits of using international standards for data exchange is to significantly increase interoperability of data.
-</p>
-<p>
-Readers of this document are expected to be familiar with delivery of content via the Web, and to have a general familiarity with the technologies involved, but are not required to have a background in semantic technologies or previous experience with Linked Data. Data stewards, curators, database administrators and other personnel involved in Open Government initiatives are encouraged to read this Linked Open Data Best Practices document.
-</section>
-
-
-<!-- INTRODUCTION -->
-<section class="informative">
-<h2>Introduction</h2>
-<p>This document does not prescribe any particular method of deploying data expressed in ORG. ORG is applicable in many contexts including RDF accessible via SPARQL endpoints, embedded in HTML pages as RDFa, or serialized as e.g. RDF/XML or Turtle. The examples in this document use Turtle simply because of Turtle's readability.</p>
-
-</section>
-
-
-<section id="conformance">
-<ul>
-<li><i>ORG compliance</i> means that a provider uses a subset of the ORG vocabulary when publishing catalog and dataset metadata. This is likely to be the common case.</li>
-<li><i>ORG conformance</i> means that a provider uses the entire ORG vocabulary when publishing catalog and dataset metadata.</li>
-</ul>
-</section>
-
-<!-- Namespaces -->
-<section>
-<h2 id="ns">Namespaces</h2>
-<p>The namespace for ORG is <code>http://www.w3.org/ns/org#</code>. However,
-it should be noted that ORG extends and uses terms from other vocabularies. A full set of alphabetically ordered namespaces and prefixes used in this
-document is shown in the table below.</p>
-<!-- Alphabetically ordered-->
-<table id="namespaces">
- <thead><tr><th>Prefix</th><th>Namespace</th></tr></thead>
- <tbody>
-
- <tr><td>foaf</td><td>http://xmlns.com/foaf/0.1/</td></tr>
- <tr><td>gr</td><td>http://purl.org/goodrelations/v1#</td></tr>
- <tr><td>opmv</td><td>http://purl.org/net/opmv/ns#</td></tr>
- <tr><td>org</td><td>http://www.w3.org/ns/org#</td></tr>
- <tr><td>owlTime</td><td>http://www.w3.org/2006/time#</td></tr>
- <tr><td>skos</td><td>http://www.w3.org/2004/02/skos/core#</td></tr>
- <tr><td>vcard</td><td>http://www.w3.org/2006/vcard/ns#</td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Overview of ontology -->
-<section class="informative">
-<h3>Overview of ontology</h3>
-
-
-<p>This ontology was original motivated by a need to publish information
-relating to government organizational structure as part of the <em>data.gov.uk</em> initiative.
-We felt that the best approach was to develop a small, generic, reusable core
-ontology for organizational information and then let developers extend
-and specialize it to particular domains. </p>
-
-<p>The ontology gives minimal basic terms to support representation of:</p>
-<ul>
- <li>organizational structure</li>
- <ul>
- <li>notion of an organization</li>
- <li>decomposition into sub-organizations and units</li>
- <li>purpose of an organization</li>
- </ul>
- <li>reporting structure</li>
- <ul>
- <li>people reporting structure within an organization</li>
- <li>roles, relationship between person and organization</li>
- </ul>
- <li>location information</li>
- <ul>
- <li>sites or buildings, locations within sites</li>
- </ul>
- <li>organizational history (merger, renaming, repurposing)</li>
-</ul>
-
-<p>This coverage corresponds to the type of information typically
- found in organizational charts. As such it does not offer a
- complete representation for all the nuances of organizational
- control structures and flows of accountability and empowerment.
- Developers are encouraged to create extension vocabularies for such
- purposes, building upon this generic foundation.</p>
-
-<p>The ontology does not provide category structures for organization
-type, organization purpose or roles. Different domains will have different
-requirements for classification of such concepts. Instead the ontology
-provides just the core base concepts needed to allow extensions to add specific
-sub-class structures or classification schemes as required.
-</p>
-
-<img src="img/diagram.png" alt="Diagram dipicting core classes and relationships">
-
-
-
-<h2 id="example">Example</h2>
-<p>This example provides a quick overview of how dcat might be used to an organization </p>
-
-<p>@@@ TODO.jse: Actually provide an example @@@</p>
-<!--
-<p>First, the catalog description:
-</p>
-<pre> :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 class="informative">
-<h3>Design notes</h3>
-
- <p>For background to the approach taken in developing the ontology see:
- <a href="http://www.epimorphics.com/web/category/category/developers/organization-ontology">blog notes</a></p>
-
-</section>
-
-
-<section class="informative">
-<h3>Notes on style</h3>
-
-<p><em>Use of inverses:</em> authorities differ on whether providing pairs of inverse relationships between
-concepts is good practice compared to declaring each relationship in just one direction. In this design we
-provide inverses for most relations (omitting attribute-like relations). This makes it easier to query
-the data in linked-data settings where a (non-symmetric) closed bounded description is often the
-default description of each resource. This does incur a cost in terms of storage or use of run-time inference.
-Particular applications of the ontology may adopt a profile in which only certain directions are asserted in the
- data and leave it up to clients to apply any inverseOf reasoning they require.</p>
-
-<p><em>Naming:</em> some designers prefer to name properties by nouns which describe the object
-of the property, others prefer to treat property names as names of the link and use a pattern
-to indicate the direction of the link. Here we adopt the latter approach for those properties
-which are relational and especially when the direction is ambiguous.
-We use the URI pattern <code>org:hasFoo/org:fooOf</code> for this but simplify the labels to "foo"
-and "foo of" to improve readability in linked data viewers.</p>
-</section>
-
-<!-- Organizational structure -->
-<section>
-<h2>Organizational structure</h2>
-
-<!-- Class Organization -->
-<section>
-<h2 id="Class:_Organization">Class: Organization</h2>
-<p>Represents a collection of people organized together into a
-community or other social, commercial or political structure. The group
-has some common purpose or reason for existence which goes beyond the
-set of people belonging to it and can act as an Agent. Organizations are
- often decomposable into hierarchical structures. </p>
-<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">subClassOf:</td><td> <a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
- <tr><td class="prop">Usage note:</td><td> It is recommended
-that SKOS lexical labels should be used to label the Organization. In
-particular <code>skos:prefLabel</code> for the primary (e.g. legally recognized name), <code>skos:altLabel</code> for alternative names (trading names, colloquial names) and <code>skos:notation</code> to denote codes from a code list. Alternative names: <em>Collective</em> <em>Body</em> <em>Org</em> <em>Group</em>.</td></tr>
-
-
- </tbody>
-</table>
-
-<!-- Property subOrganizationOf -->
-<section>
-<h3 id="Property:_subOrganizationOf">Property: subOrganizationOf</h3>
-<p>Represents hierarchical containment of Organizations or Organizational Units; indicates an organization which is a sub-part or child of this organization.</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#subOrganizationOf">org:subOrganizationOf</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain and Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Usage note:</td><td> Inverse of <code>org:hasSubOrganization</code>. Alternative names: subOrgOf.</td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property transitiveSubOrganizationOf -->
-<section>
-<h3 id="Property:_transitiveSubOrganizationOf">Property: transitiveSubOrganizationOf</h3>
-<p>Represents hierarchical containment of Organizations or Organizational Units; indicates an organization which is a sub-part or child of this organization.</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#transitiveSubOrganizationOf">org:transitiveSubOrganizationOf</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain and Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Transitive super property of:</td><td><a href="http://www.w3.org/ns/org#subOrganizationOf">org:subOrganizationOf</a></td></tr>
- <tr><td class="prop">Usage note:</td><td> The transitive closure of subOrganizationOf, giving a representation of all organizations that contain this one. Note that technically this is a super property of the transitive closure so it could contain additional assertions but such usage is discouraged.</td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property hasSubOrganization -->
-<section>
-<h3 id="Property:_hasSubOrganization">Property: hasSubOrganization</h3>
-<p>Represents hierarchical containment of Organizations or OrganizationalUnits; indicates an Organization which contains this Organization.</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasSubOrganization">org:hasSubOrganization</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain and Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Usage note:</td><td> Inverse of <code>org:subOrganizationOf</code>. Alternative names: hasSubOrg.</td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property purpose -->
-<section>
-<h3 id="Property:_purpose">Property: purpose</h3>
-<p>Indicates the purpose of this Organization. There can be many purposes at different levels of abstraction but the nature of an organization is to have a reason for existence and this property is a means to document that reason. An Organization may have multiple purposes.</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#purpose">org:purpose</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Usage note:</td><td> It is recommended that the purpose be denoted by a controlled
-term or code list, ideally a <code>skos:Concept</code>. However, the
-range is left open to allow for other types of descriptive schemes. It
-is expected that specializations or application profiles of this
-vocabulary will constrain the range of the purpose. Alternative names: <em>remit</em> <em>responsibility</em> (esp. if applied to OrganizationalUnits such as Government Departments).</td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property hasUnit -->
-<section>
-<h3 id="Property:_hasUnit">Property: hasUnit</h3>
-<p>Indicates a unit which is part of this Organization, e.g. a Department within a larger FormalOrganization.</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasUnit">org:hasUnit</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#OrganizationalUnit">org:OrganizationalUnit</a></td></tr>
- <tr><td class="prop">subPropertyOf:</td><td> <a href="http://www.w3.org/ns/org#hasSubOrganization">org:hasSubOrganization</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- Inverse of <code>org:unitOf</code>.
-</td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property unitOf -->
-<section>
-<h3 id="Property:_unitOf">Property: unitOf</h3>
-<p>Indicates an Organization of which this Unit is a part, e.g. a
-Department within a larger FormalOrganization.</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#unitOf">org:unitOf</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#OrganizationalUnit">org:OrganizationalUnit</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">subPropertyOf:</td><td> <a href="http://www.w3.org/ns/org#subOrganizationOf">org:subOrganizationOf</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- This is the inverse of <code>org:hasUnit</code>.
-</td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property classification -->
-<section>
-<h3 id="Property:_classification">Property: classification</h3>
-<p>Indicates a classification for this Organization within some
-classification scheme.
-<p class="todo">@@TODO: Make clear what is the status of this property</p>
-This property is under discussion and may be revised or removed - in
-many cases organizations are best categorized by defining a sub-class
-hierarchy in an extension vocabulary.</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#classification">org:classification</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- Extension vocabularies may wish to specialize
-this property to have a range corresponding to a specific <code>skos:ConceptScheme</code>
-</td></tr>
- </tbody>
-</table>
-</section>
-
-
-<!-- Property identifier -->
-<section>
-<h3 id="Property:_identifier">Property: identifier</h3>
-<p>Gives an identifier, such as a company registration number, that can
- be used to used to uniquely identify the organization. Many different
-national and international identier schemes are available.</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#identifier">org:identifier</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">subPropertyOf:</td><td> <a href="http://www.w3.org/2004/02/skos/core#notation">skos:notation</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- The org
-ontology is neutral to which schemes are used. The particular identifier
- scheme should be indicated by the datatype of the identifier value.
-Using datatypes to distinguish the notation scheme used is consistent
-with recommended best practice for <code>skos:notation</code> of which this property is a specialization.
-</td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property linkedTo -->
-<section>
-<h3 id="Property:_linkedTo">Property: linkedTo</h3>
-<p>Indicates an arbitrary relationship between two organizations.</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#linkedTo">org:linkedTo</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain and Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Usage note:</td>
- <td>
- Specializations of this can be used to, for example, denote funding or supply chain relationships.
- </td>
- </tr>
- </tbody>
-</table>
-</section>
-
-</section> <!-- end of Class Organization-->
-
-<!-- Class FormalOrganization -->
-<section>
-<h2 id="Class:_FormalOrganization">Class: FormalOrganization</h2>
-<p>
- An Organization which is recognized in the world at large, in
-particular in legal jurisdictions, with associated rights and
-responsibilities. Examples include a Corporation, Charity, Government or
- Church.
-</p>
-<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#FormalOrganization">org:FormalOrganization</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">subClassOf:</td><td> <a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
-
- Note that this is a super class of <code>gr:BusinessEntity</code> and it is recommended to use the GoodRelations vocabulary to denote Business classifications such as DUNS or NAICS.
-</td></tr>
-</tbody>
-</table>
-
-</section> <!-- end of Class FormalOrganization-->
-
-
-<!-- Class OrganizationalUnit -->
-<section>
-<h2 id="Class:_OrganizationalUnit">Class: OrganizationalUnit</h2>
-<p>
-An Organization such University Support Unit which is part of some
-larger FormalOrganization and only has full recognition within the
-context of that FormalOrganization, it is not a Legal Entity in its own
-right.
-</p>
-<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#OrganizationalUnit">org:OrganizationalUnit</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">subClassOf:</td><td> <a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
-Units can be large and complex containing ot her Units and even
-FormalOrganizations. Alternative names: <em>OU</em> <em>Unit</em> <em>Department</em>
-</td></tr>
-</tbody>
-</table>
-
-</section> <!-- end of Class OrganizationalUnit-->
-
-<section class="informative">
-<h3>Notes on formal organizations</h3>
-<p>Note that the subclass hierarchy
- below <code>org:Organization</code> is not a full covering. There
- can be <code>org:Organization</code>s which are in
- neither <code>org:FormalOrganization</code>
- nor <code>org:OrganizationalUnit</code>. The distinction between
- an externally recognized organization and one which only has
- meaning in the context of a larger organization is a common one
- which we support to simplify the mapping to existing practice. Note
- that the containment hierarchy is completely open
- - <code>org:FormalOrganization</code>s are free to contain
- other <code>org:FormalOrganization</code>s (e.g. subsidiaries of
- large corporations). We invite feedback from users of the ontology as to
- whether this distinction useful in practice.</p>
-</section>
-
-<section class="informative">
-<h3>Notes on organizational hierarchy</h3>
-
-<p>In many organizations there is a hierarchy of unit structures. For example we might see a containment hierarchy like:</p>
-
-<pre class="code">Corporation
- BusinessUnit
- Division
- Function
-</pre>
-
-<p>The intention is that this would be added in custom extensions since they are specific to the
-organization at hand. This can easily be done by subclassing <code>org:OrganizationalUnit</code>,
-specializing <code>org:hasSubOrganization</code> and/or using <code>owl:allValuesFrom</code> restrictions on the new subclasses.</p>
-</section>
-
-<section class="informative">
-<h3>Notes on organizational classification</h3>
-
-<p>In a number of circumstances we wish to classify organizations. There are many approaches that could be
-taken for this. It can be based on the legal structure under which the organization operates.
-For example in UK legislation there are defined notions of Partnership, Limited Company (public, private) etc
-that can be used as a basis for classification.
-Alternatively organizations can be classified by the service they provide (e.g. Educational, Manufacturing, LegalService etc).</p>
-
-<p>The core organization ontology is neutral with respect to such choices.
-It is anticipated that applications to particular domains will introduce
-subclasses of <code>org:Organization</code> to reflect the domain requirements. </p>
-
-<p>Note that the core supports labelling an organization according to some
-external classification scheme through use of the <code>org:classification</code> property.
-This is appropriate for cases where the labelling is not intrinsic to the organization
- and doesn't affect other aspects of the modelling.
- This is not always appropriate.
- For example, only Charities have CharityNumbers so it would be better to represent a
- Charity as a subClassOf FormalOrganization rather than via a taxonomic labelling.</p>
-</section>
-</section>
-
-<!-- End of section Organizational structure -->
-
-<!-- Reporting relationships and roles -->
-<section>
-<h3>Reporting relationships and roles</h3>
-
-
-<!-- Class Membership -->
-<section>
-<h2 id="Class:_Membership">Class: Membership</h2>
-<p>
-Indicates the nature of an Agent's membership of an organization.
-</p>
-<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></th></tr></thead>
- <tbody>
- <!--tr><td class="prop">subClassOf:</td><td> <a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr-->
- <tr><td class="prop">Usage note:</td><td>
-
- Represents an n-ary relation between an Agent, an Organization and a
-Role. It is possible to directly indicate membership, independent of the
- specific Role, through use of the <code>org:memberOf</code> property.
-</td></tr>
-</tbody>
-</table>
-
-
-<!-- Property member -->
-<section>
-<h3 id="Property:_member">Property: member</h3>
-<p>
- Indicates the Person (or other Agent including Organization) involved in the Membership relationship.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#member">org:member</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- Inverse of <code>org:hasMembership</code>
-</td></tr>
- </tbody>
-</table>
-</section>
-
-
-
-<!-- Property organization -->
-<section>
-<h3 id="Property:_organization">Property: organization</h3>
-<p>
- Indicates Organization in which the Agent is a member.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#organization">org:organization</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property role -->
-<section>
-<h3 id="Property:_role">Property: role</h3>
-<p>
- Indicates the Role that the Agent plays in a Membership relationship with an Organization.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#role">org:role</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Role">org:Role</a></td></tr>
-
- </tbody>
-</table>
-</section>
-
-<!-- Property hasMembership -->
-<section>
-<h3 id="Property:_hasMembership">Property: hasMembership</h3>
-<p>
- Indicates a membership relationship that the Agent plays.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasMembership">org:hasMembership</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- Inverse of <code>org:member</code>.
-</td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property memberDuring -->
-<section>
-<h3 id="Property:_memberDuring">Property: memberDuring</h3>
-<p>
- Optional property to indicate the interval for which the membership is/was valid.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#memberDuring">org:memberDuring</a></th></tr></thead>
- <tbody>
-
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2006/time#Interval">owlTime:Interval</a></td></tr>
-
- </tbody>
-</table>
-</section>
-
-<!-- Property remuneration -->
-<section>
-<h3 id="Property:_remuneration">Property: remuneration</h3>
-<p>
- Indicates a salary or other reward associated with the role.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#remuneration">org:remuneration </a></th></tr></thead>
- <tbody>
-
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Membership">org:Membership</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- Typically this will be denoted using an existing representation scheme
-such as <code>gr:PriceSpecification</code> but the range is left open to allow applications to specialize it (e.g. to remunerationInGBP).
-</td></tr>
-
- </tbody>
-</table>
-</section>
-
-
-</section> <!-- end of Class Membership-->
-
-<!-- Class Role -->
-<section>
-<h2 id="Class:_Role">Class: Role</h2>
-<p>
-Denotes a role that a Person or other Agent can take in an
-organization. Instances of this class describe the abstract role; to
-denote a specific instance of a person playing that role in a specific
-organization use an instance of <code>org:Membership</code>.
-</p>
-<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Role">org:Role</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">subClassOf:</td><td> <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
-It is
-common for roles to be arranged in some taxonomic structure and we use
-SKOS to represent that. The normal SKOS lexical properties should be
-used when labelling the Role. Additional descriptive properties for the
-Role, such as a Salary band, may be added by extension vocabularies.
-</td></tr>
-</tbody>
-</table>
-
-<!-- Property roleProperty -->
-<section>
-<h3 id="Property:_roleProperty">Property: roleProperty</h3>
-<p>
- This is a metalevel property which is used to annotate an <code>org:Role</code> instance with a sub-property of <code>org:memberOf</code>
- that can be used to directly indicate the role for easy of query.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#roleProperty">org:roleProperty</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Role">org:Role</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property">rdf:Property</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- The
-intended semantics is a Membership relation involving the Role implies
-the existence of a direct property relationship through an inference
-rule of the form: <code>{ [] org:member ?p; org:organization ?o; org:role [org:roleProperty ?r] } -> {?p ?r ?o}</code>
-</td></tr>
- </tbody>
-</table>
-</section>
-
-</section> <!-- end of Class Role-->
-
-
-<!-- Property hasMember -->
-<section>
-<h3 id="Property:_hasMember">Property: hasMember</h3>
-<p>
- Indicates a person who is a member of the subject Organization.
-Inverse of `org:memberOf`, see that property for further clarification.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasMember">org:hasMember</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Equivalent property:</td><td><a href="http://xmlns.com/foaf/0.1/member">foaf:member</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- Provided for compatibility with `foaf:member`.
-</td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property reportsTo -->
-<section>
-<h3 id="Property:_reportsTo">Property: reportsTo</h3>
-<p>
- Indicates a reporting relationship as might be depicted on an
-organizational chart.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#reportsTo">org:reportsTo</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain and range:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- The precise semantics of the reporting
-relationship will vary by organization but is intended to encompass both
- direct supervisory relationships (e.g. carrying objective and salary
-setting authority) and more general reporting or accountability
-relationships (e.g. so called <em>dotted line</em> reporting).
-</td></tr>
- </tbody>
-</table>
-</section>
-
-
-<!-- Property headOf -->
-<section>
-<h3 id="Property:_headOf">Property: headOf</h3>
-<p>
- Indicates that a person (or other agent) is the leader or formal
-head of the Organization.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#headOf">org:headOf</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">subPropertyOf:</td><td><a href="http://www.w3.org/ns/org#memberOf">org:memberOf</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- This will normally mean that they are the root
- of the <code>org:reportsTo</code> (acyclic) graph, though an organization may have more than one head.
-</td></tr>
- </tbody>
-</table>
-</section>
-
-<section class="informative">
-<h3>Discussion</h3>
-
-<p>In some applications then it is sufficient to represent the role of an individual
-within an Organization by specializations of <code>org:memberOf</code>, as in the
-builtin example <code>org:headOf</code>.</p>
-
-<p>However, in general it is advantageous to have an explicit representation of the organizational role (e.g.
-to enable advertising of a post or for publication of salary ranges associated with the role), this is supported
-by the <code>org:Role</code> class. The situation of an Agent fulfilling that role within an organization
-is then expressed through instances of the <code>org:Membership</code> n-ary relation. This also
-makes it possible to annotate the relationship with qualifying information such as duration, salary,
-reference to the employment contract and so forth.</p>
-
-<p>For example:</p>
-
-<pre class="code"><http://www.epimorphics.com/public/org#epimorphics> a org:FormalOrganization;
- skos:prefLabel "Epimorphics Ltd" .
-
-eg:ctoRole a org:Role;
- rdfs:label "CTO" .
-
-[] a org:Membership;
- org:member <http://www.amberdown.net/rdf/foaf.rdf#der> ;
- org:organization <http://www.epimorphics.com/public/org#epimorphics> ;
- org:role eg:ctoRole;
- org:memberDuring [a owlTime:Interval; owlTime:hasBeginning [
- owlTime:inXSDDateTime "2009-11-01T09:00:00Z"^^xsd:dateTime]] .
-</pre>
-
-<p>Since this representation can be a little less convenient to query and
-explore via linked-data browsing tools the core allows both explicit roles and
-simple direct relations to be used simultaneously. The relationship between
-the Role resource and the corresponding property can be indicated through
-the <code>org:roleProperty</code> annotation. Thus we might extend the above example with:</p>
-
-<pre class="code">eg:ctoRole a org:Role;
- org:roleProperty eg:ctoOf .
-
-eg:ctoOf a owl:ObjectProperty, rdf:Property ;
- rdfs:label "CTO" ;
- rdfs:subPropertyOf org:memberOf .
-
-<http://www.amberdown.net/rdf/foaf.rdf#der>
- eg:ctoOf <http://www.epimorphics.com/public/org#epimorphics> .
-</pre>
-
-<p>In practice we antipate tool chains generating the <code>org:Membership</code> instances
-and a simple closure rule being used to add any corresponding short-cut specializations of <code>org:memberOf</code>.</p>
-</section>
-
-</section>
-
-
-<!-- LOCATION -->
-<section>
-<h2>Location</h2>
-
-
-<!-- Class Site -->
-<section>
-<h2 id="Class:_Site">Class: Site</h2>
-<p>
-An office or other premise at which the organization is located.
-Many organizations are spread across multiple sites and many sites will
-host multiple locations.
-</p>
-<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#Site">org:Site</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Usage note:</td><td>
- In most cases a Site will be a physical
-location. However, we don't exclude the possibility of non-physical
-sites such as a virtual office with an associated post box and phone
-reception service. Extensions may provide subclasses to denote
-particular types of site.
-</td></tr>
-</tbody>
-</table>
-
-<!-- Property siteAddress -->
-<section>
-<h3 id="Property:_siteAddress">Property: siteAddress</h3>
-<p>
- Indicates a VCard (using the http://www.w3.org/TR/vcard-rdf/
-vocabulary) for the site. This can include email, telephone, and
-geo-location details as well as an address.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#siteAddress">org:siteAddress</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2006/vcard/ns#VCard">vcard:VCard</a></td></tr>
-
- </tbody>
-</table>
-</section>
-
-<!-- Property hasSite -->
-<section>
-<h3 id="Property:_hasSite">Property: hasSite</h3>
-<p>
- Indicates a site at which the Organization has some presence even if
- only indirect (e.g. virtual office or a professional service which is
-acting as the registered address for a company).
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasSite">org:hasSite</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
- <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#siteOf">org:siteOf</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property siteOf -->
-<section>
-<h3 id="Property:_siteOf">Property: siteOf</h3>
-<p>
- Indicates an Organization which has some presence at the given site.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#siteOf">org:siteOf</a></th></tr></thead>
- <tbody>
-
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#hasSite">org:hasSite</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property hasPrimarySite -->
-<section>
-<h3 id="Property:_hasPrimarySite">Property: hasPrimarySite</h3>
-<p>
- Indicates a primary site for the Organization, this is the default
-means by which an Organization can be contacted and is not necessarily
-the formal headquarters.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasPrimarySite">org:hasPrimarySite</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
- <tr><td class="prop">subPropertyOf:</td><td><a href="http://www.w3.org/ns/org#hasSite">org:hasSite</a></td></tr>
- </tbody>
-</table>
-</section>
-
-
-<!-- Property hasRegisteredSite -->
-<section>
-<h3 id="Property:_hasRegisteredSite">Property: hasRegisteredSite</h3>
-<p>
- Indicates the legally registered site for the organization, in many
-legal jurisdictions there is a requirement that FormalOrganizations such
- as Companies or Charities have such a primary designed site.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#hasRegisteredSite">org:hasRegisteredSite</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
- <tr><td class="prop">subPropertyOf:</td><td><a href="http://www.w3.org/ns/org#hasPrimarySite">org:hasPrimarySite</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property basedAt -->
-<section>
-<h3 id="Property:_basedAt">Property: basedAt</h3>
-<p>
- Indicates the site at which a person is based. We do not restrict the possibility that a person is based at multiple sites.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#basedAt">org:basedAt</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Person">foaf:Person</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Site">org:Site</a></td></tr>
- <tr><td class="prop">subPropertyOf:</td><td><a href="http://www.w3.org/ns/org#hasPrimarySite">org:hasPrimarySite</a></td></tr>
- </tbody>
-</table>
-</section>
-</section> <!-- end of Class Site-->
-
-
-<!-- Property location -->
-<section>
-<h3 id="Property:_location">Property: location</h3>
-<p>
- Gives a location description for a person within the organization, for example a <em>Mail Stop</em> for internal posting purposes.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#location">org:location</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://xmlns.com/foaf/0.1/Person">foaf:Person</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2001/XMLSchema#String">xsd:string</a></td></tr>
- </tbody>
-</table>
-</section>
-
-</section> <!-- End of LOCATION section -->
-
-
-<!-- Projects and other activities -->
-<section>
-<h3>Projects and other activities</h3>
-<!-- Class OrganizationalCollaboration -->
-<section>
- <h2 id="Class:_OrganizationalCollaboration">Class: OrganizationalCollaboration</h2>
- <p>
- A collaboration between two or more Organizations such as a project.
- It meets the criteria for being an Organization in that it has an
- identity and defining purpose independent of its particular members but
- is neither a formally recognized legal entity nor a sub-unit within some
- larger organization. Might typically have a shorter lifetime than the
- Organizations within it, but not necessarily.
- </p>
- <table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#OrganizationalCollaboration">org:OrganizationalCollaboration</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">subClassOf:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- All members are <code>org:Organization</code>s rather than individuals and those Organizations can play particular roles within the venture. Alternative names: <em>Project</em> <em>Venture</em> <em>Endeavour</em> <em>Consortium</em>
- </td></tr>
- </tbody>
- </table>
-</section> <!-- End of OrganizationalCollaboration class -->
-
-</section> <!-- End of Projects and other activities -->
-
-
-<!-- Historical information -->
-<section>
-<h2>Historical information</h2>
-
-<p>Any aspect of organizational structure is subject to change over time.
-For the most part this should be handled by an external mechanism such as named graphs.
-When Organizations change substantially (not simply a change of personnel or internal structure,
-for example a merger to create a new organization) then the new Organization
-will typically be denoted by a new URI and we need some vocabulary to describe that change over time
-and the relationship between the original and resulting resouces.
-The Event mechanism here gives a generic hook for this, building upon the
-<a href="http://open-biomed.sourceforge.net/opmv/ns">OPMV Provenance Vocabulary</a>.</p>
-
-<!-- Class ChangeEvent -->
-<section>
-<h2 id="Class:_ChangeEvent">Class: ChangeEvent</h2>
-<p>
-Represents an event which resulted in a major change to an
-organization such as a merger or complete restructuring. It is intended
-for situations where the resulting organization is sufficient distinct
-from the original organizations that it has a distinct identity and
-distinct URI.
-</p>
-<table class="definition">
- <thead><tr><th>RDF class:</th><th><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">subClassOf:</td><td> <a href="http://purl.org/net/opmv/ns#Process">opmv:Process</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
-Extension vocabularies should define sub-classes of this
-to denote particular categories of event. The instant or interval at
-which the event occurred should be given by `opmv:wasGeneratedAt`, a
-description should be given by `dct:description`.
-</td></tr>
-</tbody>
-</table>
-
-<!-- Property originalOrganization -->
-<section>
-<h3 id="Property:_originalOrganization">Property: originalOrganization</h3>
-<p>
- Indicates one or more organizations that existed before the change
-event. Depending on the event they may or may not have continued to
-exist after the event.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#originalOrganization">org:originalOrganization</a></th></tr></thead>
- <tbody>
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#changedBy">org:changedBy</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- Note that in
-specializing the OPMV vocabulary we are treating an `org:Organization`
-as an `opmv:Artifact`, which is consistent with the OPM model.
-</td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property changedBy -->
-<section>
-<h3 id="Property:_changedBy">Property: changedBy</h3>
-<p>
-Indicates a change event which resulted in a change to this
-organization.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#changedBy">org:changedBy</a></th></tr></thead>
- <tbody>
-
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
- <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#originalOrganzation">org:originalOrganzation</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- Depending on the event the organization may or may not
-have continued to exist after the event.
-</td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property resultedFrom -->
-<section>
-<h3 id="Property:_resultedFrom">Property: resultedFrom</h3>
-<p>
-Indicates an event which resulted in (led to, generated) this
-organization.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#resultedFrom">org:resultedFrom</a></th></tr></thead>
- <tbody>
-
-
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
- <tr><td class="prop">subpropertyOf:</td><td><a href="http://purl.org/net/opmv/ns#wasGeneratedBy">opmv:wasGeneratedBy</a></td></tr>
- <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#resultingOrganization">org:resultingOrganization</a></td></tr>
- <tr><td class="prop">Usage note:</td><td>
- Note that in
-specializing the OPMV vocabulary we are treating an `org:Organization`
-as an `opmv:Artifact`, which is consistent with the OPM model.
-</td></tr>
- </tbody>
-</table>
-</section>
-
-<!-- Property resultingOrganization -->
-<section>
-<h3 id="Property:_resultingOrganization">Property: resultingOrganization</h3>
-<p>
-Indicates an organization which was created or changed as a result of the event.
-</p>
-
-<table class="definition">
- <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/org#resultingOrganization">org:resultingOrganization</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/org#ChangeEvent">org:ChangeEvent</a></td></tr>
- <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/org#Organization">org:Organization</a></td></tr>
- <tr><td class="prop">inverseOf:</td><td><a href="http://www.w3.org/ns/org#resultedFrom">org:resultedFrom</a></td></tr>
- </tbody>
-</table>
-</section>
-
-</section> <!-- end of Class Role-->
-
-
-</section> <!-- end of Section Historical-->
-<!-- ACK -->
-<section class="appendix">
-
-<!-- Change history -->
-
-<h2>Change history</h2>
-<p>Changes since previous version 0.3 <a href="http://www.epimorphics.com/public/vocabulary/org-20100609.html">2010-06-09</a>:</p>
-<ul>
- <li>Added <code>org:identifier</code> to support generic use of organization identifier schemes, including local and national schemes.</li>
-</ul>
-
-<p>Changes since previous version 0.2 <a href="http://www.epimorphics.com/public/vocabulary/org-20100607.html">2010-06-07</a>:</p>
-<ul>
- <li>Added <code>org:changedBy</code> and <code>org:resultingOrganization</code> as inverses to
- the OMPV compatible properties and added a note on use of inverses.</li>
-</ul>
-
-<p>Changes since previous version 0.1 <a href="http://www.epimorphics.com/public/vocabulary/org-20100528.html">2010-05-28</a>:</p>
-<ul>
- <li>Rephrased the introduction to clarify scoping of the ontology.</li>
- <li>Made <code>org:Organization</code> equivalent to <code>foaf:Organization</code> following clarifying discussions with Dan Brickley.</li>
- <li>Added <code>org:hasMember</code> as an inverse of <code>org:memberOf</code> in order to be able to declare the equivalent to <code>foaf:member</code>, thanks to Dan Brickley for the suggestion.</li>
- <li>Made <code>org:unitOf/hasUnit</code> sub properties of <code>org:subOrganizationOf/hasSubOrganization</code>, thanks to Dave Challis for prompting this clarification.
- </li><li>Added <code>org:transitiveSubOrganizationOf</code>, thanks to Damian Steer for the suggestion.</li>
- <li>Fixed range statements for <code>org:role</code> and <code>org:organization</code> to correspond to the documentation and intent, thanks to Bernard Vatant for spotting that problem.</li>
- <li>Modified description of <code>org:memberOf</code> to clarify that the notion of membership is very broad and not meant to be limited to formal notions of membership.</li>
- <li>Clarified the description of <code>org:FormalOrganization</code>.
- </li><li>Fixed bug in restriction definition for <code>org:OrganizationalCollaboration</code>, thanks to Start Williams for point out the problem.</li>
- <li>Reversed <code>org:resultingOrganization</code> to <code>org:resultedFrom</code> for compatibility with OPMV, thanks to Jeni Tennison for pointing out the problem.</li>
- <li>Changed labels for has* properties to read as nouns, leaving URIs unchanged.</li>
- <li>Added <code>rdfs:isDefinedBy</code> declarations, thanks to Kingsley Idehen for pointing out the lack of those.</li>
- <li>Clarified license terms, thanks to Dan Brickley for pointing out the lack.</li>
-</ul>
-
-</section>
-<section class="appendix">
-<h2>Acknowledgments</h2>
-<p>
-The editors are very thankful for comments and suggestions ...
-</p>
-<p>This ontology was originally developed as part of the UK Linked Data Kernel project
-under the leadership and guidance of John Sheridan (The National Archives).
-Jeni Tennison provided immensely useful feedback and suggestions on the first draft,
-which greatly improved its design. The work also took inspiration from a
-number of other ontologies, particularly the thoughtfully designed
-<a href="http://www.london-gazette.co.uk/ontology/organisation.owl">Gazette Organization ontology</a>
-and <a href="http://proton.semanticweb.org/">Proton-top</a>.
-</p>
-
-</section>
-</body>
-</html>
--- a/org/respec-config.js Thu Mar 29 16:19:37 2012 +0100
+++ b/org/respec-config.js Thu Mar 29 16:42:06 2012 +0100
@@ -1,7 +1,7 @@
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
- publishDate: "2012-02-17",
+ specStatus: "FPWD",
+ publishDate: "2012-04-03",
//copyrightStart: "2010",
// the specification's short name, as in http://www.w3.org/TR/short-name/
--- a/org/respec-config.js~ Thu Mar 29 16:19:37 2012 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,96 +0,0 @@
-var respecConfig = {
- // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
- publishDate: "2012-02-03",
- //copyrightStart: "2010",
-
- // the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "gld-org",
- //subtitle: "",
- // if you wish the publication date to be other than today, set this
- // publishDate: "2009-08-06",
-
- // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
- // and its maturity status
- //previousPublishDate: "2011-06-26",
- //previousMaturity: "ED",
- //previousDiffURI: "http://dvcs.w3.org/hg/gld/bp/",
- diffTool: "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
-
- // if there a publicly available Editor's Draft, this is the link
- edDraftURI: "http://dvcs.w3.org/hg/gld/org/",
-
- // if this is a LCWD, uncomment and set the end of its review period
- // lcEnd: "2009-08-05",
-
- // if you want to have extra CSS, append them to this list
- // it is recommended that the respec.css stylesheet be kept
- extraCSS: [
- "http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"
- ],
-
- // editors, add as many as you like
- // only "name" is required
- editors: [
- { name: "Dave Reynolds", company: "Epimorphics Ltd.", companyURL: "http://www.epimorphics.com/" }
- ],
-
- // authors, add as many as you like.
- // This is optional, uncomment if you have authors as well as editors.
- // only "name" is required. Same format as editors.
-
- //authors: [],
-
- // name of the WG
- wg: "Government Linked Data Working Group",
-
- // URI of the public WG page
- wgURI: "http://www.w3.org/2011/gld/",
-
- // name of the public mailing to which comments are due
- wgPublicList: "public-gld-wg",
-
- // URI of the patent status for this WG, for Rec-track documents
- // !!!! IMPORTANT !!!!
- // This is important for Rec-track documents, do not copy a patent URI from a random
- // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
- // Team Contact.
- wgPatentURI: "",
- maxTocLevel: 3,
- preProcess: [ preProc ]
- //alternateFormats: [ {uri: "diff-20110507.html", label: "diff to previous version"} ],
-};
-
-function updateExample(doc, content) {
- // perform transformations to make it render and prettier
- content = content.replace(/<!--/, '');
- content = content.replace(/-->/, '');
- content = doc._esc(content);
- content = content.replace(/\*\*\*\*([^*]*)\*\*\*\*/g, '<span class="diff">$1</span>') ;
- return content ;
-}
-
-function updateDTD(doc, content) {
- // perform transformations to
- // make it render and prettier
- content = '<pre class="dtd">' + doc._esc(content) + '</pre>';
- content = content.replace(/!ENTITY % ([^ \t\r\n]*)/g, '!ENTITY <span class="entity">% $1</span>');
- content = content.replace(/!ELEMENT ([^ \t$]*)/mg, '!ELEMENT <span class="element">$1</span>');
- return content;
-}
-
-function updateSchema(doc, content) {
- // perform transformations to
- // make it render and prettier
- content = '<pre class="dtd">' + doc._esc(content) + '</pre>';
- content = content.replace(/<xs:element\s+name="([^&]*)"/g, '<xs:element name="<span class="element" id="schema_element_$1">$1</span>"') ;
- return content;
-}
-
-function updateTTL(doc, content) {
- // perform transformations to
- // make it render and prettier
- content = '<pre class="sh_sourceCode">' + doc._esc(content) + '</pre>';
- content = content.replace(/@prefix/g, '<span class="sh_keyword">@prefix</span>');
- return content;
-}