Binary file org/img/diagram.png has changed
--- a/org/index.html Thu Oct 11 16:32:33 2012 +0200
+++ b/org/index.html Wed Oct 17 15:00:04 2012 +0100
@@ -82,11 +82,11 @@
<h2>Overview of ontology</h2>
<p>This ontology is designed to enable publication of information on
- organizations and organizational structure including governmental
+ organizations and organizational structures including governmental
organizations. It is intended to provide a generic, reusable core
ontology that can be extended or specialized for use in particular situations.</p>
-<p>The ontology gives terms to support representation of:</p>
+<p>The ontology gives terms to support the representation of:</p>
<ul>
<li><a href="#organizational_structure">organizational structure</a>
<ul>
@@ -97,7 +97,7 @@
</li>
<li><a href="#reporting_structure">reporting structure</a>
<ul>
- <li>people reporting structure within an organization</li>
+ <li>membership and reporting structure within an organization</li>
<li>roles, posts, and the relationship between people and organizations</li>
</ul>
</li>
@@ -128,9 +128,11 @@
<p>A pictorial illustration of the main classes and relationships in
ORG is shown below. All terms are within the
- ORG namespace (<code>http://www.w3.org/ns/org#</code>) unless an explicit prefix is
+ ORG namespace (<code>http://www.w3.org/ns/org#</code>, preferred
+ prefix <em>org:</em>) unless an explicit prefix is
given. The namespaces for all referenced vocabularies are giving
- in the section on <a href="#ns">Namespaces</a>.
+ in the section on <a href="#ns">Namespaces</a>.
+ </p>
<img src="img/diagram.png" alt="Diagram depicting core classes and relationships">
@@ -156,6 +158,7 @@
org:postIn <http://reference.data.gov.uk/id/department/co/unit/cabinet-office-communications> ;
org:heldBy <#person161> .
</pre>
+
</section>
</section>
@@ -179,12 +182,12 @@
set of people belonging to it. An organization may itself be able to
act as an agent.</p>
-<p>We distinguish a particular subclass of
+<p>We distinguish a particular sub-class of
organization <a href="#org:FormalOrganization">org:FormalOrganization</a>
to indicate organizations that are recognized in the world at large, in
particular in legal jurisdictions, with associated rights and
- responsibilities. Examples include a Corporation, Charity, Government or
- Church.</p>
+ responsibilities. Examples include a corporation, charity, government or
+ church.</p>
<p>The ontology then supports the notion of organizations being
composed of other organizations in some hierarchy. The
@@ -193,7 +196,7 @@
establish these hierarchical links. </p>
<p>In some cases the sub-organization can be regarded as standalone -
- for example a complete, legally recognized, business may be part of a larger group or holding
+ for example a legally recognized business may be part of a larger group or holding
company. In other cases it is useful to refer to departments or
organizational units such as <emphasis>the IT department</emphasis>
which only have meaning within the context of the containing
@@ -202,7 +205,7 @@
called <a href="#org:OrganizationalUnit">org:OrganizationalUnit</a>. For
convenience it also provides the relations <a href="#org:hasUnit">org:hasUnit</a>
and <a href="#org:unitOf">org:unitOf</a> which are specializations
- of the generic sub-organization links<p>
+ of the generic sub-organization links.<p>
<p>Note that the containment hierarchy is completely open. For
example, <a href="#org:FormalOrganization">org:FormalOrganization</a>s are free to contain
@@ -229,27 +232,28 @@
<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
+For example in UK legislation there are defined notions of Partnership, Limited Company 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>
+Alternatively organizations can be classified by the service they
+ provide (e.g. educational, manufacturing, legal service etc).</p>
<p>ORG is neutral with respect to such choices.
It is anticipated that profiles will either introduce
- subclasses of <a href="#org:Organization">org:Organization</a> or
+ sub-classes of <a href="#org:Organization">org:Organization</a> or
define a classification scheme for organizations. To support the
latter the ontology supplies a
property <a href="#org:classification">org:classification</a> which
can be used the classify an organization using a SKOS
[[!SKOS-REFERENCE]] concept scheme.</p>
-<p>Which of these mechanisms to use depends on situation. If the classification is not intrinsic to the organization
+<p>Which of these mechanisms to use depends on the situation. If the classification is not intrinsic to the organization
but simply some way to group organizations, for example as part of a
directory, then <a href="#org:classification">org:classification</a> should be used. If the
classification is a reflection of the intrinsic nature of the
organization and affects other properties then the sub-class
approach should be used.
- For example, only Charities have CharityNumbers so it would be better to represent a
- Charity as a subClassOf <a href="#org:FormalOrganization">org:FormalOrganization</a> rather
+ For example, only charities have charity numbers so it would be better to represent a
+ charity as a sub-class of <a href="#org:FormalOrganization">org:FormalOrganization</a> rather
than via a taxonomic labelling.</p>
</section>
@@ -271,8 +275,8 @@
<p>
This simplest representation provided by ORG is to directly state that
-some individual (represented as a <a href="http://xmlns.com/foaf/spec/#term_Agent">foaf:Agent</a>) is <a href="#org:memberOf">org:memberOf</a> of an organization. To represent
-specific roles that the person plays then ORG profiles may define
+some individual (represented as a <a href="http://xmlns.com/foaf/spec/#term_Agent">foaf:Agent</a>) is <a href="#org:memberOf">org:memberOf</a> an organization. To represent
+specific roles that the person plays, ORG profiles may define
sub-properties of <a href="#org:memberOf">org:memberOf</a>. In particular, the notion
of a leader or head of a organization is so common that ORG provides a
built in property specialization of <a href="#org:memberOf">org:memberOf</a>, namely
@@ -288,9 +292,9 @@
<p>However, in general it is advantageous to have an explicit
representation of the organizational role that the person fulfils (e.g.
-for publication of responsibilities associated with the role), this is supported
+for publication of responsibilities associated with the role). This is supported
by the <a href="#org:Role">org:Role</a> class. The situation of an Agent fulfilling that role within an organization
-is then expressed through instances of the <a href="#org:Membership">org:Membership</a> n-ary relation. This also
+is then expressed through instances of the <a href="#org:Membership">org:Membership</a> n-ary relationship. 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>
@@ -300,7 +304,7 @@
skos:prefLabel "Example Ltd".
eg:ctoRole a org:Role;
- rdfs:label "CTO".
+ skos:prefLabel "CTO".
[] a org:Membership;
org:member <http://example.com/people#jo>;
@@ -334,7 +338,7 @@
org:roleProperty eg:ctoOf.
eg:ctoOf a owl:ObjectProperty, rdf:Property;
- rdfs:label "CTO";
+ skos:prefLabel "CTO";
rdfs:subPropertyOf org:memberOf.
<http://example.com/people#jo>
@@ -380,11 +384,12 @@
<p>A post can have an associated <a href="#org:Role">org:Role</a>.</p>
-<h4>Relationship between Posts and Membership</h4>
+<h4>Relationship between Posts and Memberships</h4>
-<p>In many cases only one of Posts and Memberships is needed to model
- the situation and ORG profiles may specify that use of one of
- these is preferred. In cases where the structure of the organization is to be
+<p>
+ In many situations only one of Post or Membership is needed, and ORG
+ profiles may specify that use of one of the two is preferred.
+ In cases where the structure of the organization is to be
given, independently of the people within that
structure, then <a href="#org:Post">org:Post</a> is the appropriate
representation to choose. In cases where the aim is to record
@@ -393,7 +398,7 @@
then <a href="#org:Membership">org:Membership</a> is appropriate.</p>
<p>We can state a formal relationship between these
- representations in the form of two more entailment rules:</p>
+ representations in the form of two entailment rules:</p>
<pre class="code">
CONSTRUCT {
@@ -422,14 +427,17 @@
<section id="location_information" class="informative">
<h3>Location information</h3>
-<p>ORG represents information on locations at which organizations exist
- through the notion an <a href="#org:Site">org:Site</a>, which can be
- linked to an organization via <a href="#org:siteOf">org:siteOf</a>
- and <a href="#org:hasSite">org:hasSite</a>. We can distinguish
- primary sites (<a href="#org:hasPrimarySite">org:hasPrimarySite</a>)
- and provide a specialization of
- that (<a href="#org:hasRegisteredSite">org:hasRegisteredSite</a>)
- indicate a legally registered site for the organization.</p>
+<p>ORG provides
+<a href="#org:Site">org:Site</a> to represent locations at which organizations exist. The
+relations <a href="#org:siteOf">org:siteOf</a> and <a href="#org:hasSite">org:hasSite</a> establish links between a
+<a href="#org:Site">org:Site</a> and an organization. We distinguish a
+primary site
+(<a href="#org:hasPrimarySite">org:hasPrimarySite</a>)
+to indicate the default means by which an
+organization can be contacted, and a registered site
+(<a href="#org:hasRegisteredSite">org:hasRegisteredSite</a>)
+to indicate a legally registered site for the
+organization.</p>
<p>The ontology
provides <a href="#org:siteAddress">org:siteAddress</a> to define
@@ -671,7 +679,7 @@
<!-- Property hasSubOrganization -->
<section>
<h3 id="org:hasSubOrganization">Property: hasSubOrganization</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>Represents hierarchical containment of Organizations or OrganizationalUnits; 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#hasSubOrganization">org:hasSubOrganization</a></th></tr></thead>
@@ -774,8 +782,8 @@
<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.
+responsibilities. Examples include a corporation, charity, government or
+ church.
</p>
<table class="definition">
<thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#FormalOrganization">org:FormalOrganization</a></th></tr></thead>
@@ -815,7 +823,7 @@
<!-- Property hasUnit -->
<section>
<h3 id="org:hasUnit">Property: hasUnit</h3>
-<p>Indicates a unit which is part of this Organization, e.g. a Department within a larger FormalOrganization.</p>
+<p>Indicates a unit which is part of this Organization, e.g. a Department within a larger Organization.</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>
@@ -834,7 +842,7 @@
<section>
<h3 id="org:unitOf">Property: unitOf</h3>
<p>Indicates an Organization of which this Unit is a part, e.g. a
-Department within a larger FormalOrganization.</p>
+Department within a larger Organization.</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>
@@ -942,7 +950,7 @@
<!--tr><td class="prop">subClassOf:</td><td> <a href="#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
+ Represents an n-ary relationship between an Agent, an Organization and a
Role. It is possible to directly indicate membership, independent of the
specific Role, through use of the <a href="#org:memberOf">org:memberOf</a> property.
</td></tr>
@@ -1078,7 +1086,7 @@
<section>
<h3 id="org:roleProperty">Property: roleProperty</h3>
<p>
- This is a metalevel property which is used to annotate an <a href="#org:Role">org:Role</a> instance with a sub-property of <a href="#org:memberOf">org:memberOf</a>
+ This is a metalevel property which is used to annotate a <a href="#org:Role">org:Role</a> instance with a sub-property of <a href="#org:memberOf">org:memberOf</a>
that can be used to directly indicate the role for ease of query.
</p>
@@ -1267,7 +1275,7 @@
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
+reception service. Extensions may provide sub-classes to denote
particular types of site.
</td></tr>
</tbody>
@@ -1277,8 +1285,7 @@
<section>
<h3 id="org: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
+ Indicates a VCard [[!VCARD]] for the site. This can include email, telephone, and
geo-location details as well as an address.
</p>
@@ -1623,7 +1630,7 @@
</p>
<p>
The editor gratefully acknowledges comments and support from the
-Government Linked Data Working group - particularly to Daniel Vila for
+Government Linked Data Working Group - particularly to Daniel Vila for
transcribing the original documentation into W3C format and to Bart
van Leeuwen for feedback and discussions that resulted in the addition
of <code>org:Post</code>. </p>
--- a/org/static.html Thu Oct 11 16:32:33 2012 +0200
+++ b/org/static.html Wed Oct 17 15:00:04 2012 +0100
@@ -500,7 +500,7 @@
pre.sh_sourceCode .sh_attribute { color: #006400; }
</style><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8"></head>
-<body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">An organization ontology</h1><h2 id="w3c-editor-s-draft-06-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft 06 October 2012</h2><dl><dt>This version:</dt><dd><a href="https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html">https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/vocab-org/">http://www.w3.org/TR/vocab-org/</a></dd><dt>Latest editor's draft:</dt><dd><a href="https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html">https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html</a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2012/WD-vocab-org-20120405/">http://www.w3.org/TR/2012/WD-vocab-org-20120405/</a></dd><dt>Editor:</dt><dd><span>Dave Reynolds</span>, <a href="http://www.epimorphics.com/">Epimorphics Ltd.</a></dd>
+<body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">An organization ontology</h1><h2 id="w3c-editor-s-draft-17-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft 17 October 2012</h2><dl><dt>This version:</dt><dd><a href="https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html">https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/vocab-org/">http://www.w3.org/TR/vocab-org/</a></dd><dt>Latest editor's draft:</dt><dd><a href="https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html">https://dvcs.w3.org/hg/gld/raw-file/default/org/index.html</a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2012/WD-vocab-org-20120405/">http://www.w3.org/TR/2012/WD-vocab-org-20120405/</a></dd><dt>Editor:</dt><dd><span>Dave Reynolds</span>, <a href="http://www.epimorphics.com/">Epimorphics Ltd.</a></dd>
</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2012 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr></div>
<div id="abstract" class="introductory section"><h2>Abstract</h2>
@@ -548,11 +548,11 @@
<!--OddPage--><h2><span class="secno">1. </span>Overview of ontology</h2><p><em>This section is non-normative.</em></p>
<p>This ontology is designed to enable publication of information on
- organizations and organizational structure including governmental
+ organizations and organizational structures including governmental
organizations. It is intended to provide a generic, reusable core
ontology that can be extended or specialized for use in particular situations.</p>
-<p>The ontology gives terms to support representation of:</p>
+<p>The ontology gives terms to support the representation of:</p>
<ul>
<li><a href="#organizational_structure">organizational structure</a>
<ul>
@@ -563,7 +563,7 @@
</li>
<li><a href="#reporting_structure">reporting structure</a>
<ul>
- <li>people reporting structure within an organization</li>
+ <li>membership and reporting structure within an organization</li>
<li>roles, posts, and the relationship between people and organizations</li>
</ul>
</li>
@@ -594,13 +594,15 @@
<p>A pictorial illustration of the main classes and relationships in
ORG is shown below. All terms are within the
- ORG namespace (<code>http://www.w3.org/ns/org#</code>) unless an explicit prefix is
+ ORG namespace (<code>http://www.w3.org/ns/org#</code>, preferred
+ prefix <em>org:</em>) unless an explicit prefix is
given. The namespaces for all referenced vocabularies are giving
- in the section on <a href="#ns">Namespaces</a>.
+ in the section on <a href="#ns">Namespaces</a>.
+ </p>
<img src="img/diagram.png" alt="Diagram depicting core classes and relationships">
-</p><div class="informative section" id="example-1">
+<div class="informative section" id="example-1">
<h3 id="example"><span class="secno">1.1 </span>Example</h3><p><em>This section is non-normative.</em></p>
<p>This example illustrates a small fragment of the organizational
structure of the UK Cabinet Office:</p>
@@ -621,6 +623,7 @@
org:postIn <http://reference.data.gov.uk/id/department/co/unit/cabinet-office-communications> ;
org:heldBy <#person161> .
</pre>
+
</div>
</div>
@@ -644,12 +647,12 @@
set of people belonging to it. An organization may itself be able to
act as an agent.</p>
-<p>We distinguish a particular subclass of
+<p>We distinguish a particular sub-class of
organization <a href="#org:FormalOrganization">org:FormalOrganization</a>
to indicate organizations that are recognized in the world at large, in
particular in legal jurisdictions, with associated rights and
- responsibilities. Examples include a Corporation, Charity, Government or
- Church.</p>
+ responsibilities. Examples include a corporation, charity, government or
+ church.</p>
<p>The ontology then supports the notion of organizations being
composed of other organizations in some hierarchy. The
@@ -658,7 +661,7 @@
establish these hierarchical links. </p>
<p>In some cases the sub-organization can be regarded as standalone -
- for example a complete, legally recognized, business may be part of a larger group or holding
+ for example a legally recognized business may be part of a larger group or holding
company. In other cases it is useful to refer to departments or
organizational units such as <emphasis>the IT department</emphasis>
which only have meaning within the context of the containing
@@ -667,7 +670,7 @@
called <a href="#org:OrganizationalUnit">org:OrganizationalUnit</a>. For
convenience it also provides the relations <a href="#org:hasUnit">org:hasUnit</a>
and <a href="#org:unitOf">org:unitOf</a> which are specializations
- of the generic sub-organization links</p><p>
+ of the generic sub-organization links.</p><p>
</p><p>Note that the containment hierarchy is completely open. For
example, <a href="#org:FormalOrganization">org:FormalOrganization</a>s are free to contain
@@ -694,27 +697,28 @@
<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
+For example in UK legislation there are defined notions of Partnership, Limited Company 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>
+Alternatively organizations can be classified by the service they
+ provide (e.g. educational, manufacturing, legal service etc).</p>
<p>ORG is neutral with respect to such choices.
It is anticipated that profiles will either introduce
- subclasses of <a href="#org:Organization">org:Organization</a> or
+ sub-classes of <a href="#org:Organization">org:Organization</a> or
define a classification scheme for organizations. To support the
latter the ontology supplies a
property <a href="#org:classification">org:classification</a> which
can be used the classify an organization using a SKOS
[<cite><a class="bibref" rel="biblioentry" href="#bib-SKOS-REFERENCE">SKOS-REFERENCE</a></cite>] concept scheme.</p>
-<p>Which of these mechanisms to use depends on situation. If the classification is not intrinsic to the organization
+<p>Which of these mechanisms to use depends on the situation. If the classification is not intrinsic to the organization
but simply some way to group organizations, for example as part of a
directory, then <a href="#org:classification">org:classification</a> should be used. If the
classification is a reflection of the intrinsic nature of the
organization and affects other properties then the sub-class
approach should be used.
- For example, only Charities have CharityNumbers so it would be better to represent a
- Charity as a subClassOf <a href="#org:FormalOrganization">org:FormalOrganization</a> rather
+ For example, only charities have charity numbers so it would be better to represent a
+ charity as a sub-class of <a href="#org:FormalOrganization">org:FormalOrganization</a> rather
than via a taxonomic labelling.</p>
</div>
@@ -736,8 +740,8 @@
<p>
This simplest representation provided by ORG is to directly state that
-some individual (represented as a <a href="http://xmlns.com/foaf/spec/#term_Agent">foaf:Agent</a>) is <a href="#org:memberOf">org:memberOf</a> of an organization. To represent
-specific roles that the person plays then ORG profiles may define
+some individual (represented as a <a href="http://xmlns.com/foaf/spec/#term_Agent">foaf:Agent</a>) is <a href="#org:memberOf">org:memberOf</a> an organization. To represent
+specific roles that the person plays, ORG profiles may define
sub-properties of <a href="#org:memberOf">org:memberOf</a>. In particular, the notion
of a leader or head of a organization is so common that ORG provides a
built in property specialization of <a href="#org:memberOf">org:memberOf</a>, namely
@@ -753,9 +757,9 @@
<p>However, in general it is advantageous to have an explicit
representation of the organizational role that the person fulfils (e.g.
-for publication of responsibilities associated with the role), this is supported
+for publication of responsibilities associated with the role). This is supported
by the <a href="#org:Role">org:Role</a> class. The situation of an Agent fulfilling that role within an organization
-is then expressed through instances of the <a href="#org:Membership">org:Membership</a> n-ary relation. This also
+is then expressed through instances of the <a href="#org:Membership">org:Membership</a> n-ary relationship. 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>
@@ -765,7 +769,7 @@
skos:prefLabel "Example Ltd".
eg:ctoRole a org:Role;
- rdfs:label "CTO".
+ skos:prefLabel "CTO".
[] a org:Membership;
org:member <http://example.com/people#jo>;
@@ -798,7 +802,7 @@
org:roleProperty eg:ctoOf.
eg:ctoOf a owl:ObjectProperty, rdf:Property;
- rdfs:label "CTO";
+ skos:prefLabel "CTO";
rdfs:subPropertyOf org:memberOf.
<http://example.com/people#jo>
@@ -843,11 +847,12 @@
<p>A post can have an associated <a href="#org:Role">org:Role</a>.</p>
-<h4 id="relationship-between-posts-and-membership">Relationship between Posts and Membership</h4>
+<h4 id="relationship-between-posts-and-memberships">Relationship between Posts and Memberships</h4>
-<p>In many cases only one of Posts and Memberships is needed to model
- the situation and ORG profiles may specify that use of one of
- these is preferred. In cases where the structure of the organization is to be
+<p>
+ In many situations only one of Post or Membership is needed, and ORG
+ profiles may specify that use of one of the two is preferred.
+ In cases where the structure of the organization is to be
given, independently of the people within that
structure, then <a href="#org:Post">org:Post</a> is the appropriate
representation to choose. In cases where the aim is to record
@@ -856,7 +861,7 @@
then <a href="#org:Membership">org:Membership</a> is appropriate.</p>
<p>We can state a formal relationship between these
- representations in the form of two more entailment rules:</p>
+ representations in the form of two entailment rules:</p>
<pre class="code">CONSTRUCT {
?agent org:memberOf ?org.
@@ -883,14 +888,17 @@
<div id="location_information" class="informative section">
<h3><span class="secno">2.3 </span>Location information</h3><p><em>This section is non-normative.</em></p>
-<p>ORG represents information on locations at which organizations exist
- through the notion an <a href="#org:Site">org:Site</a>, which can be
- linked to an organization via <a href="#org:siteOf">org:siteOf</a>
- and <a href="#org:hasSite">org:hasSite</a>. We can distinguish
- primary sites (<a href="#org:hasPrimarySite">org:hasPrimarySite</a>)
- and provide a specialization of
- that (<a href="#org:hasRegisteredSite">org:hasRegisteredSite</a>)
- indicate a legally registered site for the organization.</p>
+<p>ORG provides
+<a href="#org:Site">org:Site</a> to represent locations at which organizations exist. The
+relations <a href="#org:siteOf">org:siteOf</a> and <a href="#org:hasSite">org:hasSite</a> establish links between a
+<a href="#org:Site">org:Site</a> and an organization. We distinguish a
+primary site
+(<a href="#org:hasPrimarySite">org:hasPrimarySite</a>)
+to indicate the default means by which an
+organization can be contacted, and a registered site
+(<a href="#org:hasRegisteredSite">org:hasRegisteredSite</a>)
+to indicate a legally registered site for the
+organization.</p>
<p>The ontology
provides <a href="#org:siteAddress">org:siteAddress</a> to define
@@ -1134,7 +1142,7 @@
<!-- Property hasSubOrganization -->
<div class="section">
<h5 id="org:hasSubOrganization">Property: hasSubOrganization</h5>
-<p>Represents hierarchical containment of Organizations or Organizational Units; indicates an organization which is a sub-part or child of this organization.</p>
+<p>Represents hierarchical containment of Organizations or OrganizationalUnits; 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#hasSubOrganization">org:hasSubOrganization</a></th></tr></thead>
@@ -1237,8 +1245,8 @@
<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.
+responsibilities. Examples include a corporation, charity, government or
+ church.
</p>
<table class="definition">
<thead><tr><th>RDFS Class:</th><th><a href="http://www.w3.org/ns/org#FormalOrganization">org:FormalOrganization</a></th></tr></thead>
@@ -1278,7 +1286,7 @@
<!-- Property hasUnit -->
<div class="section">
<h5 id="org:hasUnit">Property: hasUnit</h5>
-<p>Indicates a unit which is part of this Organization, e.g. a Department within a larger FormalOrganization.</p>
+<p>Indicates a unit which is part of this Organization, e.g. a Department within a larger Organization.</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>
@@ -1297,7 +1305,7 @@
<div class="section">
<h5 id="org:unitOf">Property: unitOf</h5>
<p>Indicates an Organization of which this Unit is a part, e.g. a
-Department within a larger FormalOrganization.</p>
+Department within a larger Organization.</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>
@@ -1405,7 +1413,7 @@
<!--tr><td class="prop">subClassOf:</td><td> <a href="#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
+ Represents an n-ary relationship between an Agent, an Organization and a
Role. It is possible to directly indicate membership, independent of the
specific Role, through use of the <a href="#org:memberOf">org:memberOf</a> property.
</td></tr>
@@ -1541,7 +1549,7 @@
<div class="section">
<h5 id="org:roleProperty">Property: roleProperty</h5>
<p>
- This is a metalevel property which is used to annotate an <a href="#org:Role">org:Role</a> instance with a sub-property of <a href="#org:memberOf">org:memberOf</a>
+ This is a metalevel property which is used to annotate a <a href="#org:Role">org:Role</a> instance with a sub-property of <a href="#org:memberOf">org:memberOf</a>
that can be used to directly indicate the role for ease of query.
</p>
@@ -1729,7 +1737,7 @@
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
+reception service. Extensions may provide sub-classes to denote
particular types of site.
</td></tr>
</tbody>
@@ -1739,8 +1747,7 @@
<div class="section">
<h5 id="org:siteAddress">Property: siteAddress</h5>
<p>
- Indicates a VCard (using the http://www.w3.org/TR/vcard-rdf/
-vocabulary) for the site. This can include email, telephone, and
+ Indicates a VCard [<cite><a class="bibref" rel="biblioentry" href="#bib-VCARD">VCARD</a></cite>] for the site. This can include email, telephone, and
geo-location details as well as an address.
</p>
@@ -2085,7 +2092,7 @@
</p>
<p>
The editor gratefully acknowledges comments and support from the
-Government Linked Data Working group - particularly to Daniel Vila for
+Government Linked Data Working Group - particularly to Daniel Vila for
transcribing the original documentation into <acronym title="World Wide Web Consortium">W3C</acronym> format and to Bart
van Leeuwen for feedback and discussions that resulted in the addition
of <code>org:Post</code>. </p>