--- a/legal/index.html Thu Dec 06 17:06:08 2012 +0200
+++ b/legal/index.html Thu Dec 13 09:21:11 2012 +0200
@@ -96,17 +96,50 @@
<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.
<figure id="uml">
- <img src="rov.jpg" width="692" height="282" alt="UML Diagram of the Registered Organization vocabulary with RDF encodings" />
- <figcaption>UML Diagram of the Registered Organization vocabulary with RDF encodings</figcaption>
+ <img src="regorg20121213.png" width="912" height="372" 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><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> <!--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="example">Example of Use</h2>
+<h2 id="usage">RegOrg Usage</h2>
+
+<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>
+</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>
+
<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>
<li>a description of the organization;</li>
@@ -181,6 +214,7 @@
</section> <!-- Example -->
+</section> <!-- Usage -->
<section class="informative">
<h2 id="relOrg">Relationship with the Organization Ontology</h2>
@@ -228,7 +262,7 @@
<p class="editorsnote">is this information in this table helpful? If so, is the table the best way to show it?</p>
</section> <!--relORG -->
-</section> <!-- Overview -->
+
<section id="conformance">
@@ -254,186 +288,6 @@
</section>
-<section>
-<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>
-
-
-<section>
-<h2 id="conceptualmodel">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>
-<h3 id="LegalEntity">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>
-<section>
-<h3 id="legalName">legal name</h3>
-<table>
- <thead><tr><th>Property</th><th>Abstract 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>
-</section>
-<section>
-
-<h3 id="alternativeName">alternative name</h3>
-<table>
- <thead><tr><th>Property</th><th>Abstract 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>
-
-</section>
-<section>
-<h3 id="companyType">company type</h3>
-<table>
- <thead><tr><th>Property</th><th>Abstract 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>
-</section>
-<section>
-<h3 id="companyStatus">company status</h3>
-<table>
- <thead><tr><th>Property</th><th>Abstract 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>
-
-</section>
-<section>
-<h3 id="companyActivity">company activity</h3>
-<table>
- <thead><tr><th>Property</th><th>Abstract 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>
-
-</section>
-<section>
-<h3 id="registration">registration</h3>
-<table>
- <thead><tr><th>Property</th><th>Abstract 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>
-
-</section>
-
-<section>
-<h3 id="registeredAddress">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>Abstract 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>
-
-</section>
-
-<section>
-<h3 id="legalEntity">registered organization</h3>
-
-<table>
- <thead><tr><th>Property</th><th>Abstract 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>
-</section>
-
-</section> <!-- Conceptual Model -->
<section>
<h2 id="ack">Acknowledgements</h2>
@@ -459,8 +313,180 @@
<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="app1">Appendix: identifier properties</h2>
+<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.
The following table provides a summary of these related but semantically different properties
in terms of their domains and ranges</p>
@@ -468,10 +494,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>org:identifier</code></td><td><code>org:Organization</code></td><td>formally none, but <code>org:identifier</code> is a sub property of <code>skos:notation</code> for which best practice is to provide a datatyped literal as the value.</td></tr>
- <tr><td><code>dcterms:identifier</code></td><td><code>rdfs:Resource</code></td><td><code>rdfs:Literal</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>
</table>
</section>
+<p class="editorsnote"> @@TODO Complete the classification property table</p>
</body></html>