--- a/legal/index.html Thu Dec 13 09:21:11 2012 +0200
+++ b/legal/index.html Thu Dec 20 14:49:02 2012 +0000
@@ -56,6 +56,21 @@
font-style:italic;
font-weight:bold;
}
+
+ #vocIndex ul {
+ list-style-type:none;
+ display:block;
+ width: 90%;
+ margin: 0 auto;
+ border: 1px solid black;
+ padding: 1em;
+ background-color: #ccc;
+ }
+ #vocIndex ul li {
+ display:inline-block;
+ margin: 0 0.3em;
+ line-height:1.5em;
+ }
</style>
</head>
<body>
@@ -64,7 +79,7 @@
<p>This is a vocabulary for describing organizations that have gained legal entity status
through a formal registration process, typically in a national or regional register.
This document is a companion to the namespace document at <a href="http://www.w3.org/ns/regorg">http://www.w3.org/ns/regorg</a></p>
-<p class="editorsnote">NB. For this Ed Draft, see <a href="regorg20121107.rdf">regorg20121107.rdf</a></p>
+<p class="editorsnote">NB. For this Ed Draft, see <a href="regorg20121220.rdf">regorg20121220.rdf</a></p>
</section>
<section id="sotd">
@@ -84,7 +99,7 @@
It focuses solely on such organizations and excludes natural persons, virtual organizations
and other types of legal entity or 'agent' that are able to act. It should be seen as a specialization of the more
flexible and comprehensive Organization Ontology [[ORG]]. The relationship between the Registered
-Organization Vocabulary and the Organization Ontology is described <a href="#relOrg">below</a>.</p>
+Organization Vocabulary (RegOrg) and the Organization Ontology is described <a href="#relOrg">below</a>.</p>
<p>The Registered Organization Vocabulary includes classes and properties that are designed to capture the typical details recorded
by business registers and thereby facilitate information exchange between them,
although there is significant variation between business registers in what they record and
@@ -92,53 +107,92 @@
</section> <!-- intro -->
+<section id="ns" class="informative">
+<h2>Namespaces</h2>
+<p>The namespace for the Registered Organization vocabulary is <code>http://www.w3.org/ns/regorg#</code> and the preferred prefix is
+<code>rov</code>. A full set of namespaces and prefixes used in this document is shown in the table below.</p>
+<table id="namespaces">
+ <thead><tr><th>Prefix</th><th>Namespace</th></tr></thead>
+ <tbody>
+ <tr><td>adms</td><td>http://www.w3.org/ns/adms#</td></tr>
+ <tr><td>dcterms</td><td>http://purl.org/dc/terms/</td></tr>
+ <tr><td>org</td><td>http://www.w3.org/ns/org#</td></tr>
+ <tr><td>skos</td><td>http://www.w3.org/2004/02/skos/core#</td></tr>
+ <tr><td>xsd</td><td>http://www.w3.org/2001/XMLSchema#</td></tr>
+ </tbody>
+</table>
+</section> <!--end of namespaces-->
+
+
<section class="informative">
<h2 id="intro">Overview of the vocabulary</h2>
-<p>As already mentioned, the Registered Organisation Vocabulary aims to describe businesses as a legal entity. The key class is Legal Entity which represents a business that has at least one single legal entity, obtained thtough a formal registration process, like for example a VAT register. </p>
-<p>The Registered Organisation Vocabulary also includes two other classes, namely the Identifier class and the Code class. The Identifier class, captures the legal and other identifiers, while the Code class can be used to describe properties like company type, status and activity, that might be represented across national borders. </p>
-<p> The Registered Organization class is associated with the Identifier and Code classes through 2 properties, adms:identifier and org:classification respectively. These properties have sub-properties as depicted in the following diagram. for more information see <a href='#app13'>Note on identifier and classification properties </a> in the Appendix.
+<p>The key class is <code>rov:RegisteredOrganization</code> and it is this class that represents a single business that became a
+legal entity through a formal registration process. It is a sub class of <code>org:FormalOrganization</code> that covers
+any legal entity, however created. The sub class relationship allows us to use the Organization Ontology's <code>org:hasRegisteredSite</code> to link a registered business
+with the site of its registered address. The registration process varies between different jurisdictions; in some cases it's
+the tax authority that registers a business, in others a separate register exists and so on.</p>
+<p class="editorsnote">See <a href="http://www.w3.org/2011/gld/track/issues/45">Issue 45</a> concerning the alignment of addresses</p>
+<p>As well as defining the <code>rov:RegisteredOrganization</code> class, this
+vocabulary also makes use of classes defined elsewhere: the <code>adms:Identifier</code>
+class and the familiar <code>skos:Concept</code>. The Identifier class captures the legal and other identifiers, while the
+Concept class can be used to describe properties like company type, status and activity, that might be represented across national borders.</p>
+<p>The Registered Organization class is associated with the Identifier and Concept classes through 2 properties,
+<code>adms:identifier</code> and <code>org:classification</code> respectively. These have sub-properties with more specific semantics
+as depicted in the diagram and the following sections. <!--For more information see <a href='#app13'>Note on identifier and classification properties </a> in the Appendix.--></p>
<figure id="uml">
- <img src="regorg20121213.png" width="912" height="372" alt="The Registered Organization Vocabulary with RDF encodings" />
+ <img src="regorg20121220.png" width="662" height="362" alt="The Registered Organization Vocabulary with RDF encodings" />
<br/>
<figcaption>The Registered Organization Vocabulary with RDF encodings</figcaption>
</figure>
-
-<section id="index">
-<h3>Vocabulary index</h3>
+<p class="editorsnote"><a href="http://www.w3.org/2011/gld/track/issues/46">Issue-46</a> Should GLD vocabularies define conceptual models too?</p>
- <p><b>Classes:</b>
- <a href='#ref_rov_regorg'>rov:RegisteredOrganization</a>
- </p>
- <p><b>Properties:</b>
- <a href='#ref_rov_legalname'>rov:legalName</a>
- <a href='#ref_rov_alternativename'>rov:alternativeName</a>
- <a href='#ref_rov_companyType'>rov:companyType</a>
- <a href='#ref_rov_companystatus'>rov:companyStatus</a>
- <a href='#ref_rov_companyactivity'>rov:companyActivity</a>
- <a href='#ref_rov_registration'>rov:registration</a>
- <a href='#ref_rov_regaddress'>rov:registeredAddress</a>
- <a href='#ref_rov_regorgprop'>rov:registeredOrganization</a>
- </p>
+<section id="vocIndex">
+<h3>Vocabulary index</h3>
+<p>Normative definitions of each term in the vocabulary are provided in the <a href="#vocabDef">Vocabulary Definitions</a> section but for quick reference they are listed
+below.</p>
+<dl>
+ <dt>Classes:</dt>
+ <dd><ul><li><a href='#ref_rov_regorg'>rov:RegisteredOrganization</a></li></ul></dd>
+ <dt>Properties:</dt>
+ <dd><ul>
+ <li><a href='#ref_rov_legalname'>rov:legalName</a></li>
+ <li><a href='#ref_dct_alternativename'>dcterms:alternative</a></li>
+ <li><a href='#ref_rov_companyType'>rov:companyType</a></li>
+ <li><a href='#ref_rov_companystatus'>rov:companyStatus</a></li>
+ <li><a href='#ref_rov_companyactivity'>rov:companyActivity</a></li>
+ <li><a href='#ref_rov_registration'>rov:registration</a></li>
+<!-- <li><a href='#ref_rov_regaddress'>rov:registeredAddress</a></li> -->
+ <li><a href='#ref_rov_regorgprop'>rov:registeredOrganization</a></li></ul></dd>
+ </dl>
</section> <!--end of voc index-->
-<p class="editorsnote"><a href="http://www.w3.org/2011/gld/track/issues/46">Issue-46</a> Should GLD vocabularies define conceptual models too?</p>
-<p class="editorsnote"> Diagram is still under refinement </p>
-
</section> <!-- end of overview-->
<section class="informative">
<h2 id="usage">RegOrg Usage</h2>
+<!--<p>The benefit of using a vocabulary such as the Registered Organization Vocabulary is that it facilitates
+cross domain, cross border data interoperability. However, raw data is likely to exist in a tabular format. General advice on
+translating tabular data into Linked Data is included in W3C's <em>Best Practices for Publishing Linked Data</em> [[GLDBP]].
+There are two distinct phases: Data Modeling and Data Generation which we describe here through the use of a simple example.</p>
+
<section>
<h2 id="modeling">Modeling example</h2>
-<p class="editorsnote"> @@TODO - illustrate a mapping according to the RegOrg Voc for Apple Binding company (non-proprietary i.e. CSV format --> RegOrg model)</p>
+<p>Let's assume we have the following tabular data about "Apple Binding" from the UK register, Companies House.</p>
+<table>
+ <tr><th>Name</th> <th>Type</th><th>Activity</th><th>Start Date</th><th>Registered Address</th></tr>
+ <tr><td>Apple Binding</td><td>Plc</td> <td>NACE:2C180102</td><td>12/9/2001</td><td>17 Riverside Ave West<br />Dale Hall Industrial Estate<br />Lawford, Manningtree<br />CO11 1UN</td></tr>
+</table>
+
+
+<p class="editorsnote"> @@TODO - illustrate a mapping according to the RegOrg Voc for Apple Binding company (non-proprietary i.e. CSV format RegOrg model)</p>
</section>
<section>
<h2 id="example">Serialization example</h2>
<p class="editorsnote"> @@TODO - serialize in RDF/XML with RegOrg encodings the previous modeling example - keep Apple Binding existing example</p>
-</section>
+</section>-->
<p>The following is an example of a (real) company described using the Registered Organization vocabulary (in RDF/Turtle),
which is also available as a <a href="apple.ttl">separate file</a>. This includes:</p><ul>
@@ -158,8 +212,8 @@
6 rov:companyActivity <http://example.com/ref/NACE/2/C/18/01/02> ;
7 rov:companyActivity <http://example.com/ref/NACE/2/C/18/01/04> ;
8 rov:registration <http://example.com/id/li04285910> ;
-9 rov:identifier <http://example.com/id/oc04285910> ;
-10 rov:registeredAddress <http://example.com/id/ra04285910> .
+9 adms:identifier <http://example.com/id/oc04285910> ;
+10 org:registeredSite <http://example.com/id/rs04285910> .
# The actual registration
11 <http://example.com/id/li04285910> a adms:Identifier ;
@@ -178,25 +232,29 @@
<p>Line 3 gives the legally registered name of the company. In some jurisdictions,
especially those where there are multiple official languages, a single company
may have several legal names and therefore it is appropriate to use
-multiple instance of the <code><a href="#legalName">legalName</a></code> property (language tags may, of course, be added).
+multiple instances of the <code><a href="#ref_rov_legalname">legalName</a></code> property (language tags may, of course, be added).
However, where a company is known informally by an alternative name of some sort, or a trading name,
in addition to its legal name, then <code>dcterms:alternative</code> should be used to provide those alternatives.</p>
-<p>In lines 4 and 5, URIs identify <a href="#companyStatus">company status</a> and
-<a href="#companyType">company type</a>. Different jurisdictions will
+<p>In lines 4 and 5, URIs identify <a href="#ref_rov_companystatus">company status</a> and
+<a href="#ref_rov_companyType">company type</a>. Different jurisdictions will
typically define different values for company status such as trading, insolvent and
ceased trading. Similarly there is a wide variety of company types such as Plc, SA and GmbH
-although within a given jurisdiction there will be a limited number of defined terms.
+although within a given jurisdiction there will be a limited number of defined terms.
Even where the terms used in different jurisdictions are lexically identical, they may have slightly
-different legal meanings. At the time of writing the working group has not been able to
-identify an internationally agreed set of terms for company status or company type.</p>
+different legal meanings. The controlled list of values for company type and company status
+should be encoded as a SKOS Concept Scheme so that each ones has a URI.</p>
<p>Business registers typically record the type of activity (or multiple activities) carried out.
These are normally set out in a controlled vocabulary and again, these can vary from one jurisdiction to another.
The UN's ISIC Codes [[ISIC4]] form a common starting point for several such vocabularies including
-the European Union's NACE [[NACE]] Codes and UK's SIC codes [[SIC07]].</p>
+the European Union's NACE [[NACE]] Codes and UK's SIC codes [[SIC07]]. The URIs shown as the values
+of <code>rov:companyActivity</code> in lines 6 and 7 assume that NACE codes are encoded as SKOS concepts.</p>
-<p>Line 9 carries the crucial <code><a href="#registration">registration</a></code> property that points to an
+<p class="editorsnote">Need to add section to Best Practices doc on how to create SKOS concept schemes from things like NACE codes. Base on
+<a href="http://www.jenitennison.com/blog/node/132">Dave and Jeni's work on encoding SDMX etc.</a> so we can refer to it here.</p>
+
+<p>Line 9 carries the crucial <code><a href="#ref_rov_registration">registration</a></code> property that points to an
Identifier class (defined in <abbr title="Asset Description Metadata Schema">ADMS</abbr> [[!ADMS]]).
Although formally the Registered Organization vocabulary has no mandatory
classes or properties, the defining characteristic of a registered organization is that it is formally registered.
@@ -207,6 +265,8 @@
publishes its information about registered companies as linked data and the example uses that URI
as the subject of the description.</p>
+<p class="editorsnote">Need to say something about the registeredSite and address info - TBD once address issues resolved.</p>
+
<p>In addition to their company registration identifier, legal entities are very likely to
have other identifiers associated with them, such as tax numbers, VAT numbers etc. Line 12 points
to an example of an additional identifier, one that does not confer legal status (or any other status) on
@@ -263,6 +323,157 @@
</section> <!--relORG -->
+<section id="vocabDef">
+<h2>Vocabulary Definitions</h2>
+<p>The classes and properties are described in the following sub-sections.</p>
+
+<!--<section>
+<h2 id="dataTypes">Data Types</h2>
+<p>The Registered Organization vocabulary makes use of the following data types, all of which are modeled and
+defined in the ADMS specification [[!ADMS]].</p>
+<ul>
+ <li>Text (RDF encoding: <a href="http://www.w3.org/TR/rdf-schema/#ch_literal"><code>rdfs:Literal</code></a> with language tag)</li>
+ <li>Code (RDF encoding: <a href="http://www.w3.org/2009/08/skos-reference/skos.html#Concept"><code>skos:Concept</code></a>)</li>
+ <li>Identifier (RDF encoding <a href="http://www.w3.org/TR/vocab-adms/#data-types"><code>adms:Identifier</code></a>)</li>
+</ul>
+</section> -->
+
+<section>
+<!--<h2 id="regorg_classes">Classes</h2>-->
+<h2 id="ref_rov_regorg">The Registered Organization Class</h2>
+
+<table>
+ <thead><tr><th>Class</th><th>Notes</th></tr>
+ <tbody><tr><td class="code">rov:RegisteredOrganization</td><td>Sub class of <code>org:FormalOrganization</code></td></tr></tbody>
+</table>
+
+<p>The Registered Organization class is central to the vocabulary. It represents an organization that
+gains legal entity status by the act of registration cf. <code>org:FormalOrganization</code> that
+applies to any legal entity, including those created by other legal means. In many countries
+there is a single registry although in others, such as Spain and Germany, multiple registries exist.</p>
+<p>Registered organizations are distinct from the broader concept of organizations, groups or, in some jurisdictions, sole traders.
+Many organizations exist that are not legal entities yet to the outside world they have staff, hierarchies,
+locations etc. Other organizations exist that are an umbrella for several legal entities (universities
+are often good examples of this).</p>
+<p><code>rov:RegisteredOrganization</code> is a sub class of the Organization Ontology's <code>org:FormalOrganization</code>
+which is itself a sub class of the more general 'Agent' class found in FOAF [[!FOAF]] and Dublin Core [[!DC11]] that
+<em>does</em> encompass organizations, natural persons, groups etc. — i.e. an Agent is
+any entity that is able to carry out actions.</p>
+
+</section> <!-- end of classes section-->
+
+<section>
+<h2 id="regorg_properties">Properties</h2>
+<h3 id="ref_rov_legalname">Legal Name</h3>
+<table>
+ <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr>
+ <tbody><tr><td class="code">rov:legalName</td><td>org:FormalOrganization</td><td><code>rdfs:Literal</code></td></tr></tbody>
+</table>
+<p>The legal name of the business. A business might have more than one legal name,
+particularly in countries with more than one official language. In such cases, and where
+the encoding technology allows, the language of the string should be identified.</p>
+
+
+<h3 id="ref_dct_alternativename">Alternative Name</h3>
+<table>
+ <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr></thead>
+ <tbody><tr><td class="code">dcterms:alternative</td><td>rdfs:Resource</td><td><code>rdfs:Literal</code></td></tr></tbody>
+</table>
+<p>Some jurisdictions recognize concepts such as a trading name or alternative forms of a
+legal entity's name. Alternative names can be recorded using the <code>dcterms:alternative</code> but
+should not be used to record translations of the primary legal name. Where more
+than one legal name exists and where they have equal standing but are expressed
+in different languages, identify the language used in each of the multiple legal
+names (see previous section).</p>
+<p>It is notable that some jurisdictions regard the use of any name other than the primary Legal Name as suspicious.</p>
+
+
+<h3 id="ref_rov_companyType">Company Type</h3>
+<table>
+ <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr></thead>
+ <tbody><tr><td class="code"><code>rov:companyType<br />rdfs:subPropertyOf org:classification</code></td><td>org:Organization</td><td><code>skos:Concept</code></td></tr></tbody>
+</table>
+<p>This property records the type of company. Familiar types are SA, PLC, LLC,
+GmbH etc. At the time of publication, there is no agreed set of company types that
+crosses borders. The term 'SA' is used in Poland and France for example although they
+mean slightly different things. The UK's LLP and Greece's EPE provide further example of
+close, but not exact, matches.</p>
+<p>That said, each jurisdiction will have a limited set of recognized company types and these
+should be expressed in a consistent manner in a SKOS Concept Scheme.</p>
+
+
+<h3 id="ref_rov_companystatus">Company Status</h3>
+<table>
+ <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr></thead>
+ <tbody><tr><td class="code"><code>rov:companyStatus<br />rdfs:subPropertyOf org:classification</code></td><td>org:Organization</td><td><code>skos:Concept</code></td></tr></tbody>
+</table>
+<p>Recording the status of a company presents the same issues as its type.
+The terms 'insolvent', 'bankrupt' and 'in receivership,' for example, are likely to mean
+slightly different things with different legal implications in different jurisdictions. </p>
+<p>Taking advice from <a href="www.xbrl-eu.org/">XBRL Europe</a> as a starting point, however, the term 'Normal Activity'
+does appear to have cross-border usefulness and this should be used in preference to terms like 'trading' or 'operating.'</p>
+<p>Best Practice for recording various other status levels is to use the relevant jurisdiction's
+terms and to encode these in a SKOS Concept Scheme.</p>
+
+<h3 id="ref_rov_companyactivity">Company Activity</h3>
+<table>
+ <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr></thead>
+ <tbody><tr><td class="code"><code>rov:companyActivity<br />rdfs:subPropertyOf org:classification</code></td><td>org:Organization</td><td><code>skos:Concept</code></td></tr></tbody>
+</table>
+<p>The activity of a company should be recorded using a controlled vocabulary. Several
+such vocabularies exist, many of which map to the UN's ISIC codes [[ISIC4]]. Where a particular controlled
+vocabulary is in use within a given context, such as SIC codes in the UK, it is acceptable to use
+these, however, the preferred choice for European interoperability is NACE [[NACE]]. As with
+company type and status, activity codes should be expressed as SKOS Concept Schemes.</p>
+
+<h3 id="ref_rov_registration">Registration</h3>
+<table>
+ <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr></thead>
+ <tbody><tr><td class="code"><code>rov:registration<br />rdfs:subPropertyOf adms:identifier</code></td><td><code>rov:RegisteredOrganization</code></td><td><code>adms:Identifier</code></td></tr></tbody>
+</table>
+<p>The legal status of a registered organization is conferred on it by an authority within a given
+jurisdiction. The registration is therefore a fundamental relationship between a the organization
+and the authority with which it is registered. The details of the registration are
+provided as properties of the Identifier class which is defined by ADMS [[ADMS]]. The vocabulary
+sets no restriction on the type of legal identifier. In many countries, the business
+register's identifier is the relevant data point. The tax number often fulfils this function in Spain and elsewhere.</p>
+<p>Although there is no formal cardinality constraint on any property in the Registered Organization Vocabulary, it is
+questionable whether a description of a registered organization without this property and an associated Identifier class
+will be of any value.</p>
+
+
+<!--<h3 id="ref_rov_regaddress">Registered Address</h3>
+<p class="editorsnote">This property ties in with the Location core voc, one of the inputs to the
+<a href="http://www.w3.org/community/locadd/">LOCADD Community Group</a>. The original ISA Programme Location Core Vocabulary offers a
+structure for addresses that is conformant with INSPIRE but that may be inappropriate here? Using the Address
+class creates a dependency we may not wish to have.<br /><br />See also <a href="http://www.w3.org/2011/gld/track/issues/45">Issue-45</a> on
+need for better alignment with ORG's hasRegisteredSite etc. (i.e. <code>rov:registeredAddress</code> is likely to be removed).</p>
+
+<table>
+ <thead><tr><th>Property</th><th>Data Type</th><th>RDF encoding</th></tr></thead>
+ <tbody><tr><td class="code">registered address</td><td>Address</td><td><code>rov:registeredAddress</code></td></tr></tbody>
+</table>
+<p>In almost all jurisdictions, legal entities must register a postal address. This
+may or may not be the actual address at which the legal entity does its business,
+it is commonly the address of their lawyer or accountant, but it is the address to which formal communications can be sent.</p>
+<p>The domain of <code>rov:registeredAddress</code> is <code>org:FormalOrganization</code>.</p>
+-->
+
+<h3 id="ref_rov_regorgprop">Registered Organization</h3>
+<table>
+ <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr></thead>
+ <tbody><tr><td class="code">rov:registeredOrganization</td><td>dcterms:Agent</td><td><code>rov:RegisteredOrganization</code></td></tr></tbody>
+</table>
+<p>The registered organization relationship can be used to link any <code>dcterms:Agent</code> (equivalent class <code>foaf:Agent</code>)
+to a Registered Organization that in some way acts as a registered legal entity for it. This is useful, for example,
+where an organization includes one or more legal entities, or where a natural person is also registered as a legal entity.</p>
+
+<p class="editorsnote"> @@TODO Investigate the usage of this property as it discusses physical persons as legal entities. This is said to be out of scope of RegOrg earlier on. Property is not shown yet on the overview diagram</p>
+
+</section>
+
+</section>
+
<section id="conformance">
@@ -313,178 +524,6 @@
<p>The working group would also like to thank the directors of <a href="http://applebinding.co.uk/">Apple Binding</a> for
permission to describe their company in the example.</p></section>
-<section id="app11" class="appendix">
-<h2 id="ns">Namespaces</h2>
-<p>The namespace for the Registered Organization vocabulary is <code>http://www.w3.org/ns/regorg#</code> and the preferred prefix is
-<code>rov</code>. A full set of namespaces and prefixes used in this document is shown in the table below.</p>
-<table id="namespaces">
- <thead><tr><th>Prefix</th><th>Namespace</th></tr></thead>
- <tbody>
- <tr><td>adms</td><td>http://www.w3.org/ns/adms#</td></tr>
- <tr><td>dcterms</td><td>http://purl.org/dc/terms/</td></tr>
- <tr><td>org</td><td>http://www.w3.org/ns/org#</td></tr>
- <tr><td>skos</td><td>http://www.w3.org/2004/02/skos/core#</td></tr>
- <tr><td>xsd</td><td>http://www.w3.org/2001/XMLSchema#</td></tr>
- </tbody>
-</table>
-</section> <!--end of namespaces-->
-
-
-<section id="app2" class="appendix">
-<h2>Vocabulary Reference</h2>
-<p>The classes and properties are described in the following sub-sections.</p>
-
-<section>
-<h2 id="dataTypes">Data Types</h2>
-<p>The Registered Organization vocabulary makes use of the following data types, all of which are modeled and
-defined in the ADMS specification [[!ADMS]].</p>
-<ul>
- <li>Text (RDF encoding: <a href="http://www.w3.org/TR/rdf-schema/#ch_literal"><code>rdfs:Literal</code></a> with language tag)</li>
- <li>Code (RDF encoding: <a href="http://www.w3.org/2009/08/skos-reference/skos.html#Concept"><code>skos:Concept</code></a>)</li>
- <li>Identifier (RDF encoding <a href="http://www.w3.org/TR/vocab-adms/#data-types"><code>adms:Identifier</code></a>)</li>
-</ul>
-</section>
-
-<section>
-<h2 id="regorg_classes">Classes</h2>
-<h3 id="ref_rov_regorg">The Registered Organization Class</h3>
-<table>
- <thead><tr><th>Class</th><th>Notes</th><th>RDF encoding</th></tr>
- <tbody><tr><td class="code">Registered Organization</td><td>Sub class of <code>org:FormalOrganization</code></td><td><code>rov:RegisteredOrganization</code></td></tr></tbody>
-</table>
-
-<p>The Registered Organization class is central to the vocabulary. It represents an organization that
-gains legal entity status by the act of registration cf. <code>org:FormalOrganization</code> that
-applies to any legal entity, including those created by other legal means. In many countries
-there is a single registry although in others, such as Spain and Germany, multiple registries exist.</p>
-<p>Registered organizations are distinct from the broader concept of organizations, groups or, in some jurisdictions, sole traders.
-Many organizations exist that are not legal entities yet to the outside world they have staff, hierarchies,
-locations etc. Other organizations exist that are an umbrella for several legal entities (universities
-are often good examples of this). This vocabulary is concerned solely with registered organizations.</p>
-<p>In RDF, Registered Organization is a sub class of the Organization Ontology's <code>org:FormalOrganization</code>
-which is itself a sub class of the more general 'Agent' class found in FOAF [[!FOAF]] and Dublin Core [[!DC11]] that
-<em>does</em> encompass organizations, natural persons, groups etc. — i.e. an Agent is
-any entity that is able to carry out actions.</p>
-
-</section> <!-- end of classes section-->
-
-<section>
-<h2 id="regorg_properties">Properties</h2>
-<h3 id="ref_rov_legalname">Legal Name</h3>
-<table>
- <thead><tr><th>Property</th><th>Data Type</th><th>RDF encoding</th></tr>
- <tbody><tr><td class="code">legal name</td><td>Text</td><td><code>rov:legalName</code></td></tr></tbody>
-</table>
-<p>The legal name of the business. A business might have more than one legal name,
-particularly in countries with more than one official language. In such cases, and where
-the encoding technology allows, the language of the string should be identified.</p>
-
-
-<h3 id="ref_rov_alternativename">Alternative Name</h3>
-<table>
- <thead><tr><th>Property</th><th>Data Type</th><th>RDF encoding</th></tr></thead>
- <tbody><tr><td class="code">alternative name</td><td>Text</td><td><code>dcterms:alternative</code></td></tr></tbody>
-</table>
-<p>Some jurisdictions recognize concepts such as a trading name or alternative forms of a
-legal entity's name. The alternative name property can be used to record such names but
-should not be used to record translations of the primary legal name. Where more
-than one legal name exists and where they have equal standing but are expressed
-in different languages, identify the language used in each of the multiple legal
-names (see previous section).</p>
-<p>It is notable that some jurisdictions regard the use of any name other than the primary Legal Name as suspicious.</p>
-
-
-<h3 id="ref_rov_companyType">Company Type</h3>
-<table>
- <thead><tr><th>Property</th><th>Data Type</th><th>RDF encoding</th></tr></thead>
- <tbody><tr><td class="code">company type</td><td>Code</td><td><code>rov:companyType</code></td></tr></tbody>
-</table>
-<p>This property records the type of company. Familiar types are SA, PLC, LLC,
-GmbH etc. At the time of publication, there is no agreed set of company types that
-crosses borders. The term 'SA' is used in Poland and France for example although they
-mean slightly different things. The UK's LLP and Greece's EPE provide further example of
-close, but not exact, matches.</p>
-<p>That said, each jurisdiction will have a limited set of recognized company types and these
-should be used in a consistent manner.</p>
-
-
-<h3 id="ref_rov_companystatus">Company Status</h3>
-<table>
- <thead><tr><th>Property</th><th>Data Type</th><th>RDF encoding</th></tr></thead>
- <tbody><tr><td class="code">company status</td><td>Code</td><td><code>rov:companyStatus</code></td></tr></tbody>
-</table>
-<p>Recording the status of a company presents the same issues as its type.
-The terms 'insolvent', 'bankrupt' and 'in receivership,' for example, are likely to mean
-slightly different things with different legal implications in different jurisdictions. Again, at
-the time of publication, there is no agreed vocabulary for recording the status of a
-company although <a href="www.xbrl-eu.org/">XBRL Europe</a> is in the process of defining such a vocabulary.</p>
-<p>Taking the existing XBRL work as a starting point, however, the term 'Normal Activity'
-does appear to have cross-border usefulness and this should be used in preference to
-terms like 'trading' or 'operating.'</p>
-<p>Best Practice for recording various other status levels is to use the relevant jurisdiction's
-terms and to identify the controlled vocabulary used.</p>
-
-<h3 id="ref_rov_companyactivity">Company Activity</h3>
-<table>
- <thead><tr><th>Property</th><th>Data Type</th><th>RDF encoding</th></tr></thead>
- <tbody><tr><td class="code">company activity</td><td>Code</td><td><code>rov:companyActivity</code></td></tr></tbody>
-</table>
-<p>The activity of a company should be recorded using a controlled vocabulary. Several
-such vocabularies exist, many of which map to the UN's ISIC codes [[ISIC4]]. Where a particular controlled
-vocabulary is in use within a given context, such as SIC codes in the UK, it is acceptable to use
-these, however, the preferred choice for European interoperability is NACE [[NACE]].</p>
-
-<h3 id="ref_rov_registration">Registration</h3>
-<table>
- <thead><tr><th>Property</th><th>Data Type</th><th>RDF encoding</th></tr></thead>
- <tbody><tr><td class="code">registration</td><td>Identifier</td><td><code>rov:registration</code></td></tr></tbody>
-</table>
-<p>The legal status of a registered organization is conferred on it by an authority within a given
-jurisdiction. The registration is therefore a fundamental relationship between a the organization
-and the authority with which it is registered. The details of the registration are
-provided as properties of the Identifier class which is defined by ADMS [[ADMS]]. The vocabulary
-sets no restriction on the type of legal identifier. In many countries, the business
-register's identifier is the relevant data point. The tax number often fulfils this function in Spain.</p>
-<p>Although there is no formal cardinality constraint on any property in the Registered Organization vocabulary, it is
-questionable whether a description of a registered organization without this property and an associated Identifier class
-will be of any value.</p>
-<p>In RDF terms, <code>rov:registration</code> is a sub property of <code>adms:identifier</code> which
-has a domain of <code>rdfs:Resource</code> and a range of <code>adms:Identifier</code>. This is one of
-several 'identifier' properties compared in an <a href="#app1">appendix</a>.</p>
-
-<h3 id="ref_rov_regaddress">Registered Address</h3>
-<p class="editorsnote">This property ties in with the Location core voc, one of the inputs to the
-<a href="http://www.w3.org/community/locadd/">LOCADD Community Group</a>. The original ISA Programme Location Core Vocabulary offers a
-structure for addresses that is conformant with INSPIRE but that may be inappropriate here? Using the Address
-class creates a dependency we may not wish to have.<br /><br />See also <a href="http://www.w3.org/2011/gld/track/issues/45">Issue-45</a> on
-need for better alignment with ORG's hasRegisteredSite etc. (i.e. <code>rov:registeredAddress</code> is likely to be removed).</p>
-
-<table>
- <thead><tr><th>Property</th><th>Data Type</th><th>RDF encoding</th></tr></thead>
- <tbody><tr><td class="code">registered address</td><td>Address</td><td><code>rov:registeredAddress</code></td></tr></tbody>
-</table>
-<p>In almost all jurisdictions, legal entities must register a postal address. This
-may or may not be the actual address at which the legal entity does its business,
-it is commonly the address of their lawyer or accountant, but it is the address to which formal communications can be sent.</p>
-<p>The domain of <code>rov:registeredAddress</code> is <code>org:FormalOrganization</code>.</p>
-
-
-<h3 id="ref_rov_regorgprop">Registered Organization</h3>
-<table>
- <thead><tr><th>Property</th><th>Data Type</th><th>RDF encoding</th></tr></thead>
- <tbody><tr><td class="code">registered organization</td><td>Registered Organization</td><td><code>rov:RegisteredOrganization</code></td></tr></tbody>
-</table>
-<p>The registered organization relationship can be used to link any <code>dcterms:Agent</code> (equivalent class <code>foaf:Agent</code>)
-to a Registered Organization that in some way acts as a registered legal entity for it. This is useful, for example,
-where an organization includes one or more legal entities, or where a natural person is also registered as a legal entity.
-<code>rov:RegisteredOrganization</code> has a range of <code>rov:RegisteredOrganization</code>.</p>
-
-<p class="editorsnote"> @@TODO Investigate the usage of this property as it discusses physical persons as legal entities. This is said to be out of scope of RegOrg earlier on. Property is not shown yet on the overview diagram</p>
-
-</section>
-
-</section>
-
<section id="app13" class="appendix">
<h2>Note on identifier and classification properties</h2>
<p>There are several vocabularies in use with a property of 'identifier' and this vocabulary creates a sub property of one of them.
@@ -494,11 +533,11 @@
<tr><th>property</th><th>domain</th><th>range</th></tr>
<tr><td><code>adms:identifier</code></td><td><code>rdfs:Resource</code></td><td><code>adms:Identifier</code></td></tr>
<tr><td><code>rov:registration</code></td><td><code>rov:RegisteredOrganization</code></td><td><code>adms:Identifier</code> (<code>rov:registration</code> is a sub property of <code>adms:identifier</code>)</td></tr>
- <tr><td><code>rov:identifier</code></td><td><code>rov:RegisteredOrganization</code></td><td><code>adms:Identifier</code> (<code>rov:identifier</code> is a sub property of <code>adms:identifier</code>)</td></tr>
- <tr><td><code>dcterms:identifier</code></td><td><code>rdfs:Resource</code></td><td><code>rdfs:Literal</code> (<code>dcterms:alternative</code> is a sub property of <code>adms:identifier)</td></tr>
+ <tr><td><code>org:identifier</code></td><td><code>org:Organization</code></td><td><code>rdfs:Literal</code> (<code>org:identifier</code> is a sub property of <code>skos:notation</code>)</td></tr>
+ <tr><td><code>dcterms:identifier</code></td><td><code>rdfs:Resource</code></td><td><code>rdfs:Literal</code></td></tr>
</table>
</section>
-<p class="editorsnote"> @@TODO Complete the classification property table</p>
+<!--<p class="editorsnote"> @@TODO Complete the classification property table</p> -->
</body></html>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/legal/regorg20121220.rdf Thu Dec 20 14:49:02 2012 +0000
@@ -0,0 +1,224 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE rdf:RDF [
+ <!ENTITY xsd "http://www.w3.org/2001/XMLSchema#">
+ <!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+ <!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#">
+ <!ENTITY owl "http://www.w3.org/2002/07/owl#">
+ <!ENTITY dcterms "http://purl.org/dc/terms/">
+ <!ENTITY dcDoc "dublincore.org/documents/dcmi-terms/">
+ <!ENTITY foaf "http://xmlns.com/foaf/0.1/">
+ <!ENTITY foafSpec "http://xmlns.com/foaf/spec/">
+ <!ENTITY sioc "http://rdfs.org/sioc/ns#">
+ <!ENTITY schema "http://schema.org/">
+ <!ENTITY cc "http://creativecommons.org/ns#">
+ <!ENTITY org "http://www.w3.org/ns/org#">
+ <!ENTITY skos "http://www.w3.org/2004/02/skos/core#">
+ <!ENTITY skosDoc "http://www.w3.org/TR/skos-primer/">
+ <!ENTITY xhv "http://www.w3.org/1999/xhtml/vocab#">
+ <!ENTITY wdrs "http://www.w3.org/2007/05/powder-s#">
+ <!ENTITY vann "http://purl.org/vocab/vann/">
+ <!ENTITY regorg "http://www.w3.org/ns/regorg#">
+ <!ENTITY regorgDoc "http://www.w3.org/TR/vocab-regorg/">
+ <!ENTITY adms "http://www.w3.org/ns/adms#">
+ <!ENTITY admsDoc "http://www.w3.org/TR/vocab-adms/">
+ <!ENTITY title "Registered Organization Vocabulary vocabulary">
+ <!ENTITY documentation "http://www.w3.org/TR/vocab-regorg/">
+ <!ENTITY documentationTitle "Registered Organization Vocabulary">
+ <!ENTITY forum "http://lists.w3.org/Archives/Public/public-gld-comments/">
+ <!ENTITY forumTitle "Public GLD comments">
+]>
+
+
+<rdf:RDF xmlns:xsd = "&xsd;"
+ xmlns:rdf = "&rdf;"
+ xmlns:rdfs = "&rdfs;"
+ xmlns:owl = "&owl;"
+ xmlns:dcterms = "&dcterms;"
+ xmlns:foaf = "&foaf;"
+ xmlns:sioc = "&sioc;"
+ xmlns:schema = "&schema;"
+ xmlns:cc = "&cc;"
+ xmlns:org = "&org;"
+ xmlns:skos = "&skos;"
+ xmlns:xhv = "&xhv;"
+ xmlns:wdrs = "&wdrs;"
+ xmlns:vann = "&vann;"
+ xmlns:rov = "®org;"
+ xmlns:adms = "&adms;"
+ xmlns = "®org;"
+ xml:base = "®org;"
+ xml:lang = "en">
+
+<!-- Document metadata -->
+
+ <owl:Ontology rdf:about="®org;">
+ <rdfs:label xml:lang="en">&documentationTitle;</rdfs:label>
+ <rdfs:comment xml:lang="en">This file specifies the set of RDF classes and properties used in the &title;</rdfs:comment>
+ <owl:versionInfo xml:lang="en">First version in w3.org/ns</owl:versionInfo>
+ <dcterms:modified rdf:datatype="&xsd;date">2012-12-20</dcterms:modified>
+ <xhv:last rdf:resource=""/>
+ <vann:preferredNamespaceUri>®org;</vann:preferredNamespaceUri>
+ <vann:preferredNamespacePrefix>rov</vann:preferredNamespacePrefix>
+ <dcterms:creator rdf:parseType="Resource">
+ <rdfs:seeAlso rdf:resource="http://philarcher.org/foaf.rdf#me"/>
+ <foaf:name>Phil Archer</foaf:name>
+ <foaf:homepage rdf:resource="http://philarcher.org/"/>
+ <schema:affiliation rdf:parseType="Resource">
+ <foaf:name>W3C/ERCIM</foaf:name>
+ </schema:affiliation>
+ </dcterms:creator>
+ <dcterms:creator rdf:parseType="Resource">
+ <rdfs:seeAlso rdf:resource="http://andrea-perego.name/foaf/#me"/>
+ <foaf:name>Andrea Perego</foaf:name>
+ <foaf:homepage rdf:resource="http://andrea-perego.name/"/>
+ <schema:affiliation rdf:parseType="Resource">
+ <foaf:name>European Commission, Joint Research Centre (JRC)</foaf:name>
+ </schema:affiliation>
+ </dcterms:creator>
+ <foaf:maker rdf:parseType="Resource">
+ <foaf:name>Government Linked Data WG</foaf:name>
+ <foaf:page rdf:resource="http://www.w3.org/2011/gld/"/>
+ </foaf:maker>
+ <dcterms:abstract>This is a vocabulary for describing organizations that gain legal entity status through a formal registration process, typically in a national or regional register. This document is a companion to the namespace document at http://www.w3.org/ns/regorg</dcterms:abstract>
+ <dcterms:description>This is the RDF encoding of the Legal Entity vocabulary, originally developed under the European Commission's ISA Programme.</dcterms:description>
+ <foaf:depiction>
+ <rdf:Description rdf:about="http://dvcs.w3.org/hg/gld/raw-file/default/legal/regorg20121220.png">
+ <rdfs:label>Registered Organization vocabulary UML Class Diagram</rdfs:label>
+ </rdf:Description>
+ </foaf:depiction>
+ <wdrs:describedby>
+ <rdf:Description rdf:about="&documentation;">
+ <dcterms:title>&documentationTitle;</dcterms:title>
+ </rdf:Description>
+ </wdrs:describedby>
+ <dcterms:relation>
+ <sioc:Forum rdf:about="&forum;">
+ <dcterms:title>&forumTitle;</dcterms:title>
+ </sioc:Forum>
+ </dcterms:relation>
+ <dcterms:rights>Copyright © 2012 European Commission.</dcterms:rights>
+ <dcterms:license>
+ <rdf:Description rdf:about="https://joinup.ec.europa.eu/category/licence/isa-open-metadata-licence-v11">
+ <dcterms:title>ISA Open Metadata Licence v1.1</dcterms:title>
+ <cc:attributionName>European Commission</cc:attributionName>
+ <cc:attributionURL rdf:resource="http://ec.europa.eu/"/>
+ </rdf:Description>
+ </dcterms:license>
+ <cc:attributionName>European Commission</cc:attributionName>
+ <cc:attributionURL rdf:resource="http://ec.europa.eu/"/>
+ </owl:Ontology>
+
+<!-- This vocabulary just one class of its own-->
+
+ <rdfs:Class rdf:about="®org;RegisteredOrganization">
+ <rdf:type rdf:resource="&owl;Class" />
+ <rdfs:label xml:lang="en">Registered Organization</rdfs:label>
+ <rdfs:comment xml:lang="en" rdf:parseType="Literal"><p>rov:RegisteredOrganization is the key class for the Registered Organization vocabulary and represents an organization that is legally registered. In many countries there is a single registry although in others, such as Spain and Germany, multiple registries exist. A Registered Organization is able to trade, is legally liable for its actions, accounts, tax affairs etc. Legal entity status is conferred by the act of registration cf. org:FormalOrganization that applies to any legal entity, including those created by other legal means.</p>
+ <p>This makes registered organizations distinct from the broader concept of organizations, groups or, in some jurisdictions, sole traders. Many organizations exist that are not legal entities yet to the outside world they have staff, hierarchies, locations etc. Other organizations exist that are an umbrella for several legal entities (universities are often good examples of this). This vocabulary is concerned solely with registered organizations.</p>
+ <p>In RDF, Registered Organization is a sub class of the Organization Ontology's org:FormalOrganization which is itself a sub class of the more general 'Agent' class found in FOAF [FOAF] and Dublin Core [DC11] that does encompass organizations, natural persons, groups etc. - i.e. an Agent is any entity that is able to carry out actions.</p></rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="®orgDoc;"/>
+ <rdfs:subClassOf rdf:resource="&org;FormalOrganization" />
+ <dcterms:identifier>rov:RegisteredOrganization</dcterms:identifier>
+ </rdfs:Class>
+
+<!-- RegisteredOrganization properties -->
+
+ <rdf:Property rdf:about="®org;legalName">
+ <rdf:type rdf:resource="&owl;DatatypeProperty" />
+ <rdfs:label xml:lang="en">legal name</rdfs:label>
+ <rdfs:comment xml:lang="en">The legal name of the business. A business might have more than one
+ legal name, particularly in countries with more than one official language. In such cases the
+ language of the string should be identified.</rdfs:comment>
+ <rdfs:range rdf:resource="&rdfs;Literal" />
+ <rdfs:isDefinedBy rdf:resource="®orgDoc;"/>
+ <dcterms:identifier>rov:legalName</dcterms:identifier>
+ </rdf:Property>
+
+ <rdf:Description rdf:about="&dcterms;alternative">
+ <rdfs:label xml:lang="en">alternative name</rdfs:label>
+ <rdfs:comment xml:lang="en">The dcterms:alternative property fully represents the
+ Legal Entity vocabulary property of alternative name. Some jurisdictions recognize concepts such as
+ a trading name or alternative forms of a legal entity's name. The alternative name property can be
+ used to record such names but should not be used to record translations of the primary legal name.
+ Where more than one legal name exists and where they have equal standing but are expressed in
+ different languages, identify the language used in each of the multiple legal names.</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="&dcDoc;" />
+ <dcterms:identifier>dcterms:alternative</dcterms:identifier>
+ </rdf:Description>
+
+ <rdf:Property rdf:about="®org;companyType">
+ <rdf:type rdf:resource="&owl;ObjectProperty" />
+ <rdfs:label xml:lang="en">company type</rdfs:label>
+ <rdfs:comment xml:lang="en">This property records the type of company. Familiar types are SA, PLC, LLC, GmbH etc. Each
+ jurisdiction will have a limited set of recognized company types and these should be used in a consistent manner
+ using a SKOS Concept Scheme. rov:companyType is a sub class of org:classification which has a range of skos:Concept.</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="®orgDoc;"/>
+ <rdfs:subPropertyOf rdf:resource="&org;classification" />
+ <dcterms:identifier>rov:companyType</dcterms:identifier>
+ </rdf:Property>
+
+ <rdf:Property rdf:about="®org;companyStatus">
+ <rdf:type rdf:resource="&owl;ObjectProperty" />
+ <rdfs:label xml:lang="en">company status</rdfs:label>
+ <rdfs:comment xml:lang="en">Terms like insolvent, bankrupt and in receivership are likely to have
+ different legal implications in different jurisdictions. Best Practice for recording various
+ other status levels is to use the relevant jurisdiction's terms and to do so in a
+ consistent manner using a SKOS Concept Scheme. rov:companyStatus is a sub class of org:classification
+ which has a range of skos:Concept.</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="®orgDoc;"/>
+ <rdfs:subPropertyOf rdf:resource="&org;classification" />
+ <dcterms:identifier>rov:companyStatus</dcterms:identifier>
+ </rdf:Property>
+
+ <rdf:Property rdf:about="®org;companyActivity">
+ <rdf:type rdf:resource="&owl;ObjectProperty" />
+ <rdfs:label xml:lang="en">company activity</rdfs:label>
+ <rdfs:comment xml:lang="en">The activity of a company should be
+ recorded using a controlled vocabulary expressed as a SKOS concept scheme. Several such
+ vocabularies exist, many of which map to the UN's ISIC codes. Where a particular controlled vocabulary is in use
+ within a given context, such as SIC codes in the UK, it is acceptable to use these, however, the preferred
+ choice for European interoperability is NACE. rov:companyActivity is a sub class of org:classification which has a range of skos:Concept.</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="®orgDoc;"/>
+ <rdfs:subPropertyOf rdf:resource="&org;classification" />
+ <dcterms:identifier>rov:companyActivity</dcterms:identifier>
+ </rdf:Property>
+
+ <rdf:Property rdf:about="®org;registration">
+ <rdf:type rdf:resource="&owl;ObjectProperty" />
+ <rdfs:label xml:lang="en">registration</rdfs:label>
+ <rdfs:comment xml:lang="en">The registration is a fundamental relationship between a legal entity and the
+ authority with which it is registered and that confers legal status upon it. rov:registration is
+ a sub property of adms:identifier which has a range of adms:Identifier. rov:registration has a domain of rov:RegisteredOrganization.</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="®org;" />
+ <rdfs:domain rdf:resource="®org;RegisteredOrganization" />
+ <rdfs:subPropertyOf rdf:resource="&adms;identifier" />
+ <dcterms:identifier>rov:registration</dcterms:identifier>
+ </rdf:Property>
+
+<!-- <rdf:Property rdf:about="®org;registeredAddress">
+ <rdf:type rdf:resource="&owl;ObjectProperty" />
+ <rdfs:label xml:lang="en">registered address</rdfs:label>
+ <rdfs:comment xml:lang="en">Links a Legal Entity to its registered address.
+ This may or may not be the actual address at which the legal entity does its business, it is commonly
+ the address of their lawyer or accountant, but it is the address to which formal communications can
+ be sent. rov:registeredAddress has a domain of rov:LegalEntity.</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="®orgDoc;"/>
+ <rdfs:domain rdf:resource="&org;FormalOrganization" />
+ <dcterms:identifier>rov:registeredAddress</dcterms:identifier>
+ </rdf:Property> -->
+
+ <rdf:Property rdf:about="®org;registeredOrganization">
+ <rdf:type rdf:resource="&owl;ObjectProperty" />
+ <rdfs:label xml:lang="en">registered organization</rdfs:label>
+ <rdfs:comment xml:lang="en">The registered organization relationship can be used to link any dcterms:Agent (equivalent class foaf:Agent)
+ to a Registered Organization that in some way acts as a registered legal entity for it. This is useful, for example,
+ where an organization includes one or more legal entities, or where a natural person is also registered as a legal entity.
+ rov:RegisteredOrganization has a range of rov:RegisteredOrganization.</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="®orgDoc;"/>
+ <rdfs:domain rdf:resource="&dcterms;Agent" />
+ <rdfs:range rdf:resource="®org;RegisteredOrganization" />
+ <dcterms:identifier>rov:RegisteredOrganization</dcterms:identifier>
+ </rdf:Property>
+
+
+</rdf:RDF>