Difference between revisions of "Organisational Structure"

From OpenOrg
Jump to: navigation, search
(Example)
Line 1: Line 1:
 
Organisational structure should primarily be modelled using the [http://www.epimorphics.com/public/vocabulary/org.html org ontology], with types from the [http://vocab.org/aiiso AIISO] as appropriate.
 
Organisational structure should primarily be modelled using the [http://www.epimorphics.com/public/vocabulary/org.html org ontology], with types from the [http://vocab.org/aiiso AIISO] as appropriate.
 +
 +
== Namespaces ==
 +
 +
http://prefix.cc/org,rdfs,aiiso,xtypes.xml
  
 
== Types ==
 
== Types ==
  
Your main institution should be of type org:FormalOrganization and aiiso:Institution.
+
Your main organisation should be of type org:FormalOrganization  
  
 
== URIs ==
 
== URIs ==
Line 15: Line 19:
 
It is better to assign a team a unique ID and use that. This will avoid pain and confusion when the organisation restructures.
 
It is better to assign a team a unique ID and use that. This will avoid pain and confusion when the organisation restructures.
  
== Sub-units ==
+
== Sub-units and organisations ==
 +
 
 +
Organisation should have a org:hasSubOrganization relationship with units and sub-organisations.
 +
 
 +
Sub-units may be included to any degree of detail, but it is strongly recommended that the minimum should be that all units referenced in other parts of the open linked data for the organisation should be listed in the organogram document
 +
 
 +
Generally sub parts will have type org:OrganizationalUnit. However they may be org:FormalOrganization instead, if that sub-organisation is recognised as a (legal?) organisation in its own right.
 +
 
 +
=== Example ===
 +
 
 +
<pre><rdf:RDF …>
 +
 
 +
  ... license etc ...
 +
 
 +
  <rdf:Description rdf:about="....main org URI...">
 +
    <rdf:type rdf:resource="http://www.w3.org/ns/org#FormalOrganization"/>
 +
    <rdfs:label>Example Org</rdfs:label>
 +
    <org:hasSubOrganization rdf:resource='..../orgpart-001'>
 +
    <org:hasSubOrganization rdf:resource='..../orgpart-002'>
 +
    <org:hasSubOrganization rdf:resource='..../orgpart-003'>
 +
  </rdf:Description>
 +
 
 +
  <rdf:Description rdf:about="..../orgpart-001">
 +
    <rdf:type rdf:resource="http://www.w3.org/ns/org#OrganizationalUnit"/>
 +
    <rdfs:label>Sales Division</rdfs:label>
 +
  </rdf:Description>
 +
 
 +
</rdf:RDF>
 +
</pre>
 +
 
 +
== Sub-Organisations who manage their own org data ==
  
Sub-units should have org:subOrganizationOf and org:hasSubOrganization relationships with their containing unit.
+
Collegiate institutions, or other organisations which are part of the main organisations may devolve URI definition and org description to their respective sub parts.  
  
Sub-units may be included to any degree of detail, but it is strongly recommended that all units referenced in other parts of the open linked data for the org. should be listed in the organogram document
+
In this case a source of additional information about the college should be indicated using an rdfs:seeAlso to link them to their
 +
 
 +
  <rdf:Description rdf:about="..../college-001">
 +
    <rdf:type rdf:resource="http://www.w3.org/ns/org#FormalOrganization" />
 +
    <rdf:type rdf:resource="http://purl.org/vocab/aiiso/schema#College" />
 +
    <rdfs:label>St. Malaclypse College</rdfs:label>
 +
    <rdfs:seeAlso rdf:resource="http://data.malaclypse.example.edu/orgchart.rdf" />
 +
  </rdf:Description>
 +
  <rdf:Description rdf:about="http://data.malaclypse.example.edu/orgchart.rdf">
 +
    <rdf:type xtypes:Document-RDFSerialisation
  
 
== Universities ==
 
== Universities ==
Line 38: Line 81:
 
For more details see http://vocab.org/aiiso/schema but the rule of thumb is that if it's ''called'' a faculty by your university then it's type aiiso:Faculty.
 
For more details see http://vocab.org/aiiso/schema but the rule of thumb is that if it's ''called'' a faculty by your university then it's type aiiso:Faculty.
  
If your institution is collegiate, then each college should be of both type org:FormalOrganization and aiiso:College.
+
If your institution is collegiate, then each college should be of both type org:FormalOrganization and aiiso:College.  
  
== Example ==
+
 
 +
 
 +
=== Example ===
  
 
<pre><rdf:RDF …>
 
<pre><rdf:RDF …>
Line 47: Line 92:
  
 
   <rdf:Description rdf:about="....main org URI...">
 
   <rdf:Description rdf:about="....main org URI...">
     <rdf:type rdf:resource="http://www.w3.org/ns/org#FormalOrganization"/>
+
     <rdf:type rdf:resource="http://www.w3.org/ns/org#FormalOrganization" />
     <rdfs:label>Example Org</rdfs:label>
+
    <rdf:type rdf:resource="http://purl.org/vocab/aiiso/schema#Institution" />
     <org:hasSubOrganization rdf:resource='..../orgpart-001'>
+
     <rdfs:label>Example University</rdfs:label>
     <org:hasSubOrganization rdf:resource='..../orgpart-002'>
+
     <org:hasSubOrganization rdf:resource='..../college-001'>
     <org:hasSubOrganization rdf:resource='..../orgpart-003'>
+
     <org:hasSubOrganization rdf:resource='..../unit-001'>
 +
  </rdf:Description>
 +
 
 +
  <rdf:Description rdf:about="..../college-001">
 +
     <rdf:type rdf:resource="http://www.w3.org/ns/org#FormalOrganization" />
 +
    <rdf:type rdf:resource="http://purl.org/vocab/aiiso/schema#College" />
 +
    <rdfs:label>St. Malaclypse College</rdfs:label>
 
   </rdf:Description>
 
   </rdf:Description>
  
   <rdf:Description rdf:about="..../orgpart-001">
+
   <rdf:Description rdf:about="..../unit-001">
     <rdfs:label>Sales Division</rdfs:label>
+
    <rdf:type rdf:resource="http://www.w3.org/ns/org#OrganizationalUnit" />
 +
     <rdfs:label>Waste Services</rdfs:label>
 
   </rdf:Description>
 
   </rdf:Description>
  
 
</rdf:RDF>
 
</rdf:RDF>
 
</pre>
 
</pre>
 +
 +
nb. It may be that not all Organizational Units of an academic institution require an aiiso: type.
 +
 +
= Inference =
 +
 +
From the above schema other predicates and classes from FOAF, AIISO and ORG should be possible to infer. Keeping the above list to a minimum makes basic consumption easier. There's nothing to stop you adding additional predicates and classes but they should be in addition, not as alternatives.

Revision as of 15:06, 14 December 2010

Organisational structure should primarily be modelled using the org ontology, with types from the AIISO as appropriate.

Namespaces

http://prefix.cc/org,rdfs,aiiso,xtypes.xml

Types

Your main organisation should be of type org:FormalOrganization

URIs

It is recommended that you put no structural information in the URI.

BAD: http://id.example.org/org/divisions/my-div/my-sub-div/team-3

GOOD: http://id.example.org/orgunit/team-2342

It is better to assign a team a unique ID and use that. This will avoid pain and confusion when the organisation restructures.

Sub-units and organisations

Organisation should have a org:hasSubOrganization relationship with units and sub-organisations.

Sub-units may be included to any degree of detail, but it is strongly recommended that the minimum should be that all units referenced in other parts of the open linked data for the organisation should be listed in the organogram document

Generally sub parts will have type org:OrganizationalUnit. However they may be org:FormalOrganization instead, if that sub-organisation is recognised as a (legal?) organisation in its own right.

Example

<rdf:RDF …>

  ... license etc ...

  <rdf:Description rdf:about="....main org URI...">
    <rdf:type rdf:resource="http://www.w3.org/ns/org#FormalOrganization"/>
    <rdfs:label>Example Org</rdfs:label>
    <org:hasSubOrganization rdf:resource='..../orgpart-001'>
    <org:hasSubOrganization rdf:resource='..../orgpart-002'>
    <org:hasSubOrganization rdf:resource='..../orgpart-003'>
  </rdf:Description>

  <rdf:Description rdf:about="..../orgpart-001">
    <rdf:type rdf:resource="http://www.w3.org/ns/org#OrganizationalUnit"/>
    <rdfs:label>Sales Division</rdfs:label>
  </rdf:Description>

</rdf:RDF>

Sub-Organisations who manage their own org data

Collegiate institutions, or other organisations which are part of the main organisations may devolve URI definition and org description to their respective sub parts.

In this case a source of additional information about the college should be indicated using an rdfs:seeAlso to link them to their

 <rdf:Description rdf:about="..../college-001">
   <rdf:type rdf:resource="http://www.w3.org/ns/org#FormalOrganization" />
   <rdf:type rdf:resource="http://purl.org/vocab/aiiso/schema#College" />
   <rdfs:label>St. Malaclypse College</rdfs:label>
   <rdfs:seeAlso rdf:resource="http://data.malaclypse.example.edu/orgchart.rdf" />
 </rdf:Description>
 <rdf:Description rdf:about="http://data.malaclypse.example.edu/orgchart.rdf">
   <rdf:type xtypes:Document-RDFSerialisation

Universities

The top level of a university should be type aiiso:Institution in addition to org:FormalOrganization.

For other parts of a university structure add the following types, as appropriate:

aiiso:Center, aiiso:College, aiiso:Department, aiiso:Divison, aiiso:Faculty, aiiso:Institute, aiiso:ResearchGroup, aiiso:School.

For more details see http://vocab.org/aiiso/schema but the rule of thumb is that if it's called a faculty by your university then it's type aiiso:Faculty.

If your institution is collegiate, then each college should be of both type org:FormalOrganization and aiiso:College.


Example

<rdf:RDF …>

  ... license etc ...

  <rdf:Description rdf:about="....main org URI...">
    <rdf:type rdf:resource="http://www.w3.org/ns/org#FormalOrganization" />
    <rdf:type rdf:resource="http://purl.org/vocab/aiiso/schema#Institution" />
    <rdfs:label>Example University</rdfs:label>
    <org:hasSubOrganization rdf:resource='..../college-001'>
    <org:hasSubOrganization rdf:resource='..../unit-001'>
  </rdf:Description>

  <rdf:Description rdf:about="..../college-001">
    <rdf:type rdf:resource="http://www.w3.org/ns/org#FormalOrganization" />
    <rdf:type rdf:resource="http://purl.org/vocab/aiiso/schema#College" />
    <rdfs:label>St. Malaclypse College</rdfs:label>
  </rdf:Description>

  <rdf:Description rdf:about="..../unit-001">
    <rdf:type rdf:resource="http://www.w3.org/ns/org#OrganizationalUnit" />
    <rdfs:label>Waste Services</rdfs:label>
  </rdf:Description>

</rdf:RDF>

nb. It may be that not all Organizational Units of an academic institution require an aiiso: type.

Inference

From the above schema other predicates and classes from FOAF, AIISO and ORG should be possible to infer. Keeping the above list to a minimum makes basic consumption easier. There's nothing to stop you adding additional predicates and classes but they should be in addition, not as alternatives.