Could be final changes
authorphila
Wed, 08 May 2013 17:36:52 +0100
changeset 508 757ab56f1e1d
parent 507 4d7ac7a76b29
child 509 e73115d595ce
Could be final changes
legal/apple.ttl
legal/index.html
legal/regorg20130508.png
legal/regorg20130508.rdf
legal/regorg20130508.ttl
legal/respec-config.js
legal/respec-ref.js
--- a/legal/apple.ttl	Wed May 08 13:04:06 2013 +0100
+++ b/legal/apple.ttl	Wed May 08 17:36:52 2013 +0100
@@ -1,10 +1,10 @@
-<http://data.companieshouse.gov.uk/id/company/04285910>
+<http://business.data.gov.uk/id/company/04285910>
   a rov:RegOrg ;
   rov:legalName "Apple Binding Ltd" ;
-  rov:companyStatus <http://example.com/ref/status/NormalActivity> ;
-  rov:companyType <http://example.com/ref/type/Plc> ;
-  rov:companyActivity <http://example.com/ref/NACE/2/C/18/01/02> ;
-  rov:companyActivity <http://example.com/ref/NACE/2/C/18/01/04> ;
+  rov:orgStatus <http://example.com/ref/status/NormalActivity> ;
+  rov:orgType <http://example.com/ref/type/Plc> ;
+  rov:orgActivity <http://example.com/ref/NACE/2/C/18/01/02> ;
+  rov:orgActivity <http://example.com/ref/NACE/2/C/18/01/04> ;
   # Note the use of legalIdentifier on the next line
   rov:registration <http://example.com/id/li04285910> ;
   # Other identifiers are often very useful but they do
@@ -16,11 +16,11 @@
 <http://example.com/id/li04285910> a adms:Identifier ;
   skos:notation "04285910"^^ex:idType ;
   adms:schemaAgency "UK Companies House" ;
-  dcterms:created "2001-09-12"^^xsd:date .
+  dcterms:issued "2001-09-12"^^xsd:date .
 
 # A supplementary identifier (Open Corporates)
 <http://example.com/id/oc04285910> a adms:Identifier ;
   skos:notation "http://opencorporates.com/companies/gb/04285910"^^ex:OCid ;
-  dcterms:created "2010-10-21T15:09:59Z"^^xsd:dateTime ;
+  dcterms:issued "2010-10-21T15:09:59Z"^^xsd:dateTime ;
   dcterms:modified "2012-04-26T15:16:44Z"^^xsd:dateTime ;
   dcterms:creator <http://opencorporates.com/companies/gb/07444723> .
\ No newline at end of file
--- a/legal/index.html	Wed May 08 13:04:06 2013 +0100
+++ b/legal/index.html	Wed May 08 17:36:52 2013 +0100
@@ -76,19 +76,13 @@
 <body>
 
 <section id="abstract">
-<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="regorg20121220.rdf">regorg20121220.rdf</a></p>
+<p>The Registered Organization Vocabulary is a profile of the Organization Ontology for describing 
+organizations that have gained legal entity status through a formal registration process, 
+typically in a national or regional register.</p>
+<p>@@@ Move above the HR in publication [email protected]@@ Terms in the ROV namespace are available in both <a href="regorg20130508.rdf">RDF/XML</a> and <a href="regorg20130508.ttl">Turtle</a>.</pa>
 </section>
 
 <section id="sotd">
-  <p>This is the First Public Working Draft of the Registered Organization Vocabulary in W3C's TR space and
-  signals its move to the Recommendations Track. It was first developed as the 'Business Core Vocabulary'
-  by PwC EU Services on behalf of the European Commission and 
-  <a href="http://joinup.ec.europa.eu/asset/adms/home">published by the European Commission</a>.
-  Further development is now being undertaken by the <a href="http://www.w3.org/2011/gld/">Government 
-  Linked Data Working Group</a> (GLD WG).</p>
 
 </section>
 
@@ -97,13 +91,13 @@
 <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.
 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
+and other types of legal entity or 'agent' that are able to act. It is a profile of the more
 flexible and comprehensive Organization Ontology [[ORG]]. The relationship between the Registered 
 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
-publish. </p>
+<p>The Registered Organization Vocabulary includes a minimal number of 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 publish. </p>
 
 </section> <!-- intro -->
 
@@ -128,23 +122,24 @@
 <h2 id="intro">Overview of the vocabulary</h2>
 <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>
+any legal entity, however created. The sub class relationship allows us to use all aspects of ORG such as the 
+<code>org:hasRegisteredSite</code> property to link a registered organization 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>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>
+Concept class can be used to describe properties like the organization type, status and activity, that might be 
+recognized 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>
+as depicted in the diagram and the following sections.</p>
+
 <figure id="uml">
-  <img src="regorg20121220.png" width="662" height="362" alt="The Registered Organization Vocabulary with RDF encodings" />
+  <img src="regorg20130508.png" width="368" height="343" alt="The Registered Organization Vocabulary UML diagram" />
   <br/>
-  <figcaption>The Registered Organization Vocabulary with RDF encodings</figcaption>
+  <figcaption>The Registered Organization Vocabulary</figcaption>
 </figure>
-<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>
 
 <section id="vocIndex">
 <h3>Vocabulary index</h3>
@@ -156,13 +151,13 @@
   <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_skos_altlabel'>skos:altLabel</a></li>
+  <li><a href='#ref_rov_orgType'>rov:orgType</a></li>
+  <li><a href='#ref_rov_orgStatus'>rov:orgStatus</a></li>
+  <li><a href='#ref_rov_orgActivity'>rov:orgActivity</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>
+  <li><a href='#ref_rov_hasRegOrg'>rov:hasRegisteredOrganization</a></li></ul></dd>
    </dl>
 </section> <!--end of voc index-->
 
@@ -171,28 +166,6 @@
 
 <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>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>-->
 
 <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>
@@ -204,13 +177,13 @@
 company register itself or another organization.</p>
 
 <pre id="appleBinding">
-1  &lt;http://data.companieshouse.gov.uk/id/company/04285910&gt;
+1  &lt;http://business.data.gov.uk/id/company/04285910&gt;
 2    a rov:RegisteredOrganization ;
 3    rov:legalName "Apple Binding Ltd" ;
-4    rov:companyStatus &lt;http://example.com/ref/status/NormalActivity&gt; ;
-5    rov:companyType &lt;http://example.com/ref/type/Plc&gt; ;
-6    rov:companyActivity &lt;http://example.com/ref/NACE/2/C/18/01/02&gt; ;
-7    rov:companyActivity &lt;http://example.com/ref/NACE/2/C/18/01/04&gt; ;
+4    rov:orgStatus &lt;http://example.com/ref/status/NormalActivity&gt; ;
+5    rov:orgType &lt;http://example.com/ref/type/Plc&gt; ;
+6    rov:orgActivity &lt;http://example.com/ref/NACE/2/C/18/01/02&gt; ;
+7    rov:orgActivity &lt;http://example.com/ref/NACE/2/C/18/01/04&gt; ;
 8    rov:registration &lt;http://example.com/id/li04285910&gt; ;
 9    adms:identifier &lt;http://example.com/id/oc04285910&gt; ;
 10   org:registeredSite &lt;http://example.com/id/rs04285910&gt; .
@@ -219,42 +192,42 @@
 11 &lt;http://example.com/id/li04285910&gt; a adms:Identifier ;
 12   skos:notation "04285910"^^ex:idType ;
 13   adms:schemaAgency "UK Companies House" ;
-14   dcterms:created "2001-09-12"^^xsd:date .
+14   dcterms:issued "2001-09-12"^^xsd:date .
 
    # A supplementary identifier (Open Corporates)
 15 &lt;http://example.com/id/oc04285910&gt; a adms:Identifier ;
 16   skos:notation "http://opencorporates.com/companies/gb/04285910"^^ex:OCid ;
-17   dcterms:created "2010-10-21T15:09:59Z"^^xsd:dateTime ;
+17   dcterms:issued "2010-10-21T15:09:59Z"^^xsd:dateTime ;
 18   dcterms:modified "2012-04-26T15:16:44Z"^^xsd:dateTime ;
 19   dcterms:creator &lt;http://opencorporates.com/companies/gb/07444723&gt; .
 </pre>
 
 <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 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>
+may have several legal names and therefore it can be appropriate to use
+multiple instances of the <code><a href="#ref_rov_legalname">legalName</a></code> property (language tags may, of course, be added).
+It is noteworthy that ORG assumes that an organization can only have a single legally recognized name (which is the common case)
+and therefore uses <code>skos:prefLabel</code> for this. It is the possibility of having more than one such name in a limited
+number of jurisdictions, that justifies the creation of <code>rov:legalName</code>.</p>
+<p>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>skos:altLabel</code> should be used to provide those alternatives as is done in ORG.</p>
 
-<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 
+<p>In lines 4 and 5, URIs identify the <a href="#ref_rov_orgstatus">organization status</a> and 
+<a href="#ref_rov_orgType">organization type</a>. Different jurisdictions will
+typically define different values for organization status such as trading, insolvent and
+ceased trading. Similarly there is a wide variety of organization types such as Plc, SA and GmbH 
 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. The controlled list of values for company type and company status
+different legal meanings. The controlled list of values for organization type and organization 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. 
+<p>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]]. 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>
+of <code>rov:orgActivity</code> in lines 6 and 7 assume that NACE codes are encoded as SKOS concepts.</p>
 
-<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 
+<p>Line 8 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.
@@ -265,10 +238,11 @@
 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>Line 10 shows the <code>org:registeredSite</code> used to point to a description of the registered address of
+the organization (the address information itself is not shown).</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 
+have other identifiers associated with them, such as tax numbers, VAT numbers etc. Line 9 points 
 to an example of an additional identifier, one that does not confer legal status (or any other status) on
 the company but that is potentially useful as an identifier.</p>
 
@@ -287,39 +261,30 @@
 For Registered Organizations, it is the identifier issued by the relevant registration authority that 
 confers legal status and therefore always has particular significance. RegORG uses the ADMS class
 of Identifier (based on the UN/CEFACT class of the same name) to allow statements to be made
-<em>about</em> the identifier in a way not possible on ORG. Given data about a Registered Organization,
+<em>about</em> the identifier in a way not possible in ORG. Given data about a Registered Organization,
 it is possible to derive an <code>org:identifier</code> but the inverse is not true.</p>
-<p>The following table summarizes the relationship between the two vocabularies.</p>
 
-<table>
-  <tr><th>RegORG</th><th>relationship</th><th>ORG</th></tr>
-  <tr><td><code>rov:RegisteredOrganization</code></td><td><code>rdfs:subClassOf</code></td><td><code>org:FormalOrganization</code></td></tr>
-  <tr><td><code>rov:companyType</code></td><td><code>rdfs:subPropertyOf</code></td><td><code>org:classification</code></td></tr>
-  <tr><td><code>rov:companyStatus</code></td><td><code>rdfs:subPropertyOf</code></td><td><code>org:classification</code></td></tr>
-  <tr><td><code>rov:companyActivity</code></td><td><code>rdfs:subPropertyOf</code></td><td><code>org:classification</code></td></tr>
-  <tr><td><p>Given data such as:</p>
+<p>In summary:</p>
+<p><code>rov:RegisteredOrganization</code> is a sub class of <code>org:FormalOrganization</code></p>
+<p><code>rov:orgType</code>, <code>rov:orgStatus</code> and <code>rov:orgActivity</code> are all sub properties of <code>org:classification</code>.</p>
+<p>Given data such as:</p>
   <pre>
 &lt;http://example.com/id/123456&gt;
   rov:registration &lt;http://example.com/id/li123456&gt; .
 
 &lt;http://example.com/id/li123456&gt; a adms:Identifier ;
   skos:notation "123456"^^ex:idType .
-  </pre></td>
-
-  <td><p>This SPARQL query</p>
+  </pre>
+<p>This SPARQL query</p>
   <pre>CONSTRUCT {
     ?org org:identifier ?id .
 } WHERE {
   ?org rov:registration [skos:notation ?id] .
-}</pre></td>
-  <td>yields the <code>org:identifier</code> property and value, i.e.
+}</pre>
+<p>yields the <code>org:identifier</code> property and value, i.e.</p>
 <pre>
 &lt;http://example.com/id/123456&gt;
-  org:identifer "123456"^^ex:idType .</pre></td></tr>
-
-</table>
-
-<p class="editorsnote">is this information in this table helpful? If so, is the table the best way to show it?</p>
+  org:identifier "123456"^^ex:idType .</pre>
 
 </section> <!--relORG -->
 
@@ -327,21 +292,9 @@
 <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>
@@ -370,17 +323,16 @@
   <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>
+particularly in countries with more than one official language. In such cases the language of the string should be identified.</p>
 
 
-<h3 id="ref_dct_alternativename">Alternative Name</h3>
+<h3 id="ref_skos_altlabel">skos:altLabel</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>
+  <tbody><tr><td class="code">skos:altLabel</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 
+legal entity's name. Alternative names can be recorded using the <code>skos:altLabel</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 
@@ -388,10 +340,10 @@
 <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>
+<h3 id="ref_rov_orgType">Organization 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>
+  <tbody><tr><td class="code"><code>rov:orgType<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 
@@ -402,12 +354,12 @@
 should be expressed in a consistent manner in a SKOS Concept Scheme.</p>
 
 
-<h3 id="ref_rov_companystatus">Company Status</h3>
+<h3 id="ref_rov_orgStatus">Organization 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>
+  <tbody><tr><td class="code"><code>rov:orgStatus<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. 
+<p>Recording the status of an organization 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' 
@@ -415,12 +367,12 @@
 <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>
+<h3 id="ref_rov_orgActivity">Organization 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>
+  <tbody><tr><td class="code"><code>rov:orgActivity<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 
+<p>The activity of an organization 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
@@ -441,35 +393,15 @@
 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>
+<h3 id="ref_rov_hasRegOrg">Has 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>
+  <tbody><tr><td class="code">rov:hasRegisteredOrganization</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>)
+<p>The has 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>
@@ -495,34 +427,19 @@
 <p>The Registered Organization Vocabulary is technology-neutral and a publisher may use any of the terms defined in this 
 document encoded in any technology although RDF and XML are preferred.</p>
 
-<p class="editorsnote"><a href="http://www.w3.org/2011/gld/track/issues/47">Issue-47</a> RegOrg should be defined as an Org profile</p>
-
 </section>
 
-
-<section>
-<h2 id="ack">Acknowledgements</h2>
-<p>The original development of the vocabulary was carried out under the
-Interoperability Solutions for European Public Administrations (<a href="http://ec.europa.eu/isa/">ISA Programme</a>) 
-of the European Commission (EC). Contributors included representatives of Member
-States of the European Union, operators of national repositories, standardization 
-bodies and independent experts whose work was published in April 2012 [[CV1]]. 
-That document includes the history and motivation behind the development of a set of three interlinked 
-Core Vocabularies of which this is one.</p>
-<p>This version of the Registered Organization vocabulary, RegORG, builds on that work in a broader, global context.</p>
-<p>Significant contributions to the original work on the Registered Organization vocabulary were made by:
-Ignacio Boixo,
-Debora Di Giacomo,
-Stijn Goedertier,
-Piotr Madziar (original WG chair),
-Aine Mitchell,
-Andrea Perego,
-João Rodrigues Frade,
-Chris Taggart, 
-Niels Van Hee,
-Thomas Verdin.</p>
-<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="changelog" class="appendix">
+<h2>Change Log</h2>
+<p>Multiple changes have ben made since the <a href="http://www.w3.org/TR/2013/WD-vocab-regorg-20130108/">previous version</a> of
+RegOrg. These have been made to align the vocabulary more closely with other GLD WG outputs, notably DCAT and ORG. In particular
+<code>dcterms:created</code> has been replaced with <code>dcterms:issued</code>, and <code>dcterms:alternative</code> has been
+replaced with <code>skos:altLabel</code>. The UML diagram is aligned with that used for ADMS and, in the same way that ADMS is
+defined as a profile of DCAT, RegOrg is now defined as a profile of ORG.</p>
+<p>The use of the term 'company type' was seen as being too restrictive for other types of registered organizations such as charities
+so that <code>rov:companyType</code>, <code>rov:companyActivity</code> and <code>rov:companyStatus</code> have been replaced with
+<code>rov:orgType</code>, <code>rov:orgActivity</code> and <code>rov:orgStatus</code> respectively.</p>
+</section>
 
 <section id="app13" class="appendix">
 <h2>Note on identifier and classification properties</h2>
@@ -538,6 +455,14 @@
 </table>
 </section>
 
-<!--<p class="editorsnote"> @@TODO Complete the classification property table</p> -->
+<section id="acknowledgements" class="appendix">
+<h2>Acknowledgements</h2>
+<p>RegOrg was first developed by PwC EU Services and <a href="https://joinup.ec.europa.eu/asset/core_business/release/100">published 
+  by the European Commission</a> as the <i>Core Business Vocabulary</i>. Further development and review has been undertaken by the 
+  <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a> (GLD WG).</p>
+<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>
+
 
 </body></html>
Binary file legal/regorg20130508.png has changed
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/legal/regorg20130508.rdf	Wed May 08 17:36:52 2013 +0100
@@ -0,0 +1,192 @@
+<?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">
+  <!ENTITY gld     "http://www.w3.org/2011/gld/">
+  <!ENTITY voaf    "http://labs.mondeca.com/vocab/voaf#">
+  <!ENTITY org    "http://www.w3.org/ns/org#">
+]>
+
+
+<rdf:RDF xmlns:xsd     = "&xsd;"
+         xmlns:rdf     = "&rdf;"
+         xmlns:rdfs    = "&rdfs;"
+         xmlns:owl     = "&owl;"
+         xmlns:dcterms = "&dcterms;"
+         xmlns:foaf    = "&foaf;"
+         xmlns:schema  = "&schema;"
+         xmlns:org     = "&org;"
+         xmlns:wdrs    = "&wdrs;"
+         xmlns:vann    = "&vann;"
+         xmlns:rov     = "&regorg;"
+         xmlns:adms    = "&adms;"
+         xmlns:voaf    = "&voaf;"
+         xmlns         = "&regorg;"
+         xml:base      = "&regorg;"
+         xml:lang = "en">
+
+<!-- Document metadata -->
+
+  <owl:Ontology rdf:about="&regorg;">
+    <voaf:specializes rdf:resource="&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">Second version in w3.org/ns</owl:versionInfo>
+    <dcterms:modified rdf:datatype="&xsd;date">2013-05-08</dcterms:modified>
+    <vann:preferredNamespaceUri>&regorg;</vann:preferredNamespaceUri>
+    <vann:preferredNamespacePrefix>rov</vann:preferredNamespacePrefix>
+    <dcterms:creator rdf:parseType="Resource">
+      <rdfs:seeAlso rdf:resource="http://makxdekkers.com/makxdekkers.rdf#me"/>
+      <foaf:name>Makx Dekkers</foaf:name>
+      <foaf:homepage rdf:resource="http://makxdekkers.com/"/>
+    </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 </foaf:name>
+        <foaf:homepage rdf:resource="http://ies.jrc.ec.europa.eu/DE"/>
+      </schema:affiliation>
+    </dcterms:creator>
+    <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://www.w3.org/People/all#phila"/>
+      <schema:affiliation rdf:parseType="Resource">
+        <foaf:name>W3C/ERCIM</foaf:name>
+        <foaf:homepage rdf:resource="http://www.w3.org/"/>
+      </schema:affiliation>
+    </dcterms:creator>
+    <foaf:maker rdf:parseType="Resource">
+      <foaf:name>Government Linked Data WG, based on output from the ADMS Working Group</foaf:name>
+      <foaf:page rdf:resource="&gld;"/>
+    </foaf:maker>
+    <dcterms:abstract>The Registered Organization Vocabulary is a profile of the Organization Ontology for describing organizations that have gained legal entity status through a formal registration process, typically in a national or regional register.</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/regorg20130508.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>
+  </owl:Ontology>  
+
+<!-- This vocabulary just one class of its own-->
+
+  <rdfs:Class rdf:about="&regorg;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 and Dublin Core 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="&regorgDoc;"/>
+    <rdfs:subClassOf rdf:resource="&org;FormalOrganization" />
+    <dcterms:identifier>rov:RegisteredOrganization</dcterms:identifier>
+  </rdfs:Class>
+
+<!-- RegisteredOrganization properties -->
+
+  <rdf:Property rdf:about="&regorg;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="&regorgDoc;"/>
+    <dcterms:identifier>rov:legalName</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&regorg;orgType">
+    <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 organization. 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:orgType is a sub class of org:classification which has a range of skos:Concept.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&regorgDoc;"/>
+    <rdfs:subPropertyOf rdf:resource="&org;classification" />
+    <dcterms:identifier>rov:orgType</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&regorg;orgStatus">
+    <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&apos;s terms and to do so in a 
+    consistent manner using a SKOS Concept Scheme. rov:orgStatus is a sub class of org:classification
+    which has a range of skos:Concept.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&regorgDoc;"/>
+    <rdfs:subPropertyOf rdf:resource="&org;classification" />
+    <dcterms:identifier>rov:orgStatus</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&regorg;orgActivity">
+    <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&apos;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:orgActivity is a sub class of org:classification which has a range of skos:Concept.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&regorgDoc;"/>
+    <rdfs:subPropertyOf rdf:resource="&org;classification" />
+    <dcterms:identifier>rov:orgActivity</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&regorg;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="&regorg;" />
+    <rdfs:domain rdf:resource="&regorg;RegisteredOrganization" />
+    <rdfs:subPropertyOf rdf:resource="&adms;identifier" />
+    <dcterms:identifier>rov:registration</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&regorg;hasRegisteredOrganization">
+    <rdf:type rdf:resource="&owl;ObjectProperty" />
+    <rdfs:label xml:lang="en">registered organization</rdfs:label>
+    <rdfs:comment xml:lang="en">The has 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:hasRegisteredOrganization has a range of rov:RegisteredOrganization.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&regorgDoc;"/>
+    <rdfs:domain rdf:resource="&dcterms;Agent" />
+    <rdfs:range rdf:resource="&regorg;RegisteredOrganization" />
+    <dcterms:identifier>rov:hasRegisteredOrganization</dcterms:identifier>
+  </rdf:Property>
+
+
+</rdf:RDF>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/legal/regorg20130508.ttl	Wed May 08 17:36:52 2013 +0100
@@ -0,0 +1,106 @@
[email protected] dcterms: <http://purl.org/dc/terms/>.
[email protected] foaf: <http://xmlns.com/foaf/0.1/>.
[email protected] owl: <http://www.w3.org/2002/07/owl#>.
[email protected] xsd: <http://www.w3.org/2001/XMLSchema#>.
[email protected] xml: <http://www.w3.org/XML/1998/namespace>.
[email protected] voaf: <http://labs.mondeca.com/vocab/voaf#>.
[email protected] rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
[email protected] vann: <http://purl.org/vocab/vann/>.
[email protected] rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
[email protected] wdrs: <http://www.w3.org/2007/05/powder-s#>.
[email protected] schema: <http://schema.org/> .
[email protected] rov: <http://www.w3.org/ns/regorg#>.
[email protected] org: <http://www.w3.org/ns/org#>.
[email protected] adms: <http://www.w3.org/ns/adms#>.
+
+rov: a voaf:Vocabulary, owl:Ontology;
+  voaf:specializes org:;
+	dcterms:creator [schema:affiliation <http://www.w3.org/data#W3C>;
+	  rdfs:seeAlso <http://philarcher.org/foaf.rdf#me>;
+  	foaf:homepage <http://www.w3.org/People/all#phila>;
+  	foaf:name "Phil Archer"@en.] ,
+    [schema:affiliation [foaf:homepage <http://ies.jrc.ec.europa.eu/DE>; foaf:name "European Commission, Joint Research Centre "@en.]; 
+  	rdfs:seeAlso <http://andrea-perego.name/foaf/#me>;
+	  foaf:homepage <http://andrea-perego.name/>;
+	  foaf:name "Andrea Perego"@en.] ,
+    [rdfs:seeAlso <http://makxdekkers.com/makxdekkers.rdf#me>; foaf:homepage <http://makxdekkers.com/>;
+    	foaf:name "Makx Dekkers"@en.];
+  foaf:maker[foaf:name "Government Linked Data WG, based on output from the ADMS Working Group"@en; foaf:homepage <http://www.w3.org/2011/gld/>.];
+  dcterms:abstract "The Registered Organization Vocabulary is a profile of the Organization Ontology for describing organizations that have gained legal entity status through a formal registration process, typically in a national or regional register."@en;
+	dcterms:description "This is the RDF encoding of the Legal Entity vocabulary, originally developed under the European Commission's ISA Programme."@en;
+	dcterms:modified "2013-05-08"^^xsd:date;
+	vann:preferredNamespacePrefix "rov"@en;
+	vann:preferredNamespaceUri "http://www.w3.org/ns/regorg#"@en;
+	rdfs:comment "This file specifies the set of RDF classes and properties used in the Registered Organization Vocabulary vocabulary"@en;
+	rdfs:label "Registered Organization Vocabulary"@en;
+	owl:versionInfo "Second version in w3.org/ns"@en;
+	wdrs:describedby <http://www.w3.org/TR/vocab-regorg/>.
+
+rov:RegisteredOrganization dcterms:identifier "rov:RegisteredOrganization"@en;
+	a rdfs:Class,
+		owl:Class;
+	rdfs:comment """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.
+    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.
+    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 and Dublin Core that does encompass organizations, 
+    natural persons, groups etc. - i.e. an Agent is any entity that is able to carry out actions.</p>"""@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-regorg/>;
+	rdfs:label "Registered Organization"@en;
+	rdfs:subClassOf org:FormalOrganization.
+
+rov:legalName dcterms:identifier "rov:legalName"@en;
+	a rdf:Property,
+		owl:DatatypeProperty;
+	rdfs:comment "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."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-regorg/>;
+	rdfs:label "legal name"@en;
+	rdfs:range rdfs:Literal.
+
+rov:orgType dcterms:identifier "rov:orgType"@en;
+	a rdf:Property,
+		owl:ObjectProperty;
+	rdfs:comment "This property records the type of organization. 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:orgType is a sub class of org:classification which has a range of skos:Concept."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-regorg/>;
+	rdfs:label "company type"@en;
+	rdfs:subPropertyOf org:classification.
+
+rov:orgStatus dcterms:identifier "rov:orgStatus"@en;
+	a rdf:Property,
+		owl:ObjectProperty;
+	rdfs:comment "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:orgStatus is a sub class of org:classification which has a range of skos:Concept."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-regorg/>;
+	rdfs:label "company status"@en;
+	rdfs:subPropertyOf org:classification.
+
+rov:orgActivity dcterms:identifier "rov:orgActivity"@en;
+	a rdf:Property,
+		owl:ObjectProperty;
+	rdfs:comment "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:orgActivity is a sub class of org:classification which has a range of skos:Concept."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-regorg/>;
+	rdfs:label "company activity"@en;
+	rdfs:subPropertyOf org:classification.
+
+rov:registration dcterms:identifier "rov:registration"@en;
+	a rdf:Property,
+		owl:ObjectProperty;
+	rdfs:comment "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."@en;
+	rdfs:domain rov:RegisteredOrganization;
+	rdfs:isDefinedBy rov:;
+	rdfs:label "registration"@en;
+	rdfs:subPropertyOf adms:identifier.
+
+rov:hasRegisteredOrganization dcterms:identifier "rov:hasRegisteredOrganization"@en;
+	a rdf:Property,
+		owl:ObjectProperty;
+	rdfs:comment "The has 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:hasRegisteredOrganization has a range of rov:RegisteredOrganization."@en;
+	rdfs:domain dcterms:Agent;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-regorg/>;
+	rdfs:label "registered organization"@en;
+	rdfs:range rov:RegisteredOrganization.
--- a/legal/respec-config.js	Wed May 08 13:04:06 2013 +0100
+++ b/legal/respec-config.js	Wed May 08 17:36:52 2013 +0100
@@ -1,7 +1,7 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-    specStatus:           "ED",
-    publishDate:          "2012-12-20",
+    specStatus:           "NOTE",
+    publishDate:          "2013-05-14",
     //copyrightStart:       "2010",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/
@@ -12,8 +12,8 @@
 
     // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
     // and its maturity status
-    //previousPublishDate:  "2011-06-26",
-    //previousMaturity:     "ED",
+    previousPublishDate:  "2013-01-08",
+    previousMaturity:     "WD",
     //previousDiffURI:      "http://dvcs.w3.org/hg/gld/bp/",
     diffTool:             "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
 
@@ -33,6 +33,7 @@
     // only "name" is required
     editors:  [
         { name: "Phil Archer", url: "http://www.w3.org/People/all#phila", company: "W3C/ERCIM", companyURL: "http://www.w3.org" },
+        { name: "Marios Meimaris", url: "http://www.ntua.gr/", company: "National Technical University of Athens (Invited Expert)", companyURL: "http://www.ntua.gr/" },
         { name: "Agisilaos Papantoniou", url: "http://www.ntua.gr/", company: "National Technical University of Athens (Invited Expert)", companyURL: "http://www.ntua.gr/" }
     ],
 
--- a/legal/respec-ref.js	Wed May 08 13:04:06 2013 +0100
+++ b/legal/respec-ref.js	Wed May 08 17:36:52 2013 +0100
@@ -13,7 +13,7 @@
                 berjon.biblio["EIF2"] = "<cite><a href=\"http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf\">European Interoperability Framework (EIF) for European public services</a></cite> (PDF) European Commission. URL: http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf."
                 berjon.biblio["TOGD"] = "<cite><a href=\"http://joinup.ec.europa.eu/sites/default/files/towards_open_government_metadata_0.pdf\">Towards Open Government Metadata</a></cite> (PDF) European Commission Joinup e-Library. URL: http://joinup.ec.europa.eu/sites/default/files/towards_open_government_metadata_0.pdf"
                 berjon.biblio["ADMS1"] = "<cite><a href=\"http://joinup.ec.europa.eu/asset/adms/release/100\">ADMS 1.0</a></cite> European Commission ADMS (link is to a page offering various downloadable files in a variety of formats). URL: http://joinup.ec.europa.eu/asset/adms/release/100"
-                berjon.biblio["ADMS"] = "<cite><a href=\"http://dvcs.w3.org/hg/gld/raw-file/default/adms/index.html\">Asset Description Metadata Schema (ADMS)</a></cite> P. Archer, G. Shukair, Currently an Editor's Draft but expected to become a W3C Recommendations Track document. URL: http://dvcs.w3.org/hg/gld/raw-file/default/adms/index.html"
+                berjon.biblio["ADMS"] = "<cite><a href=\"http://dvcs.w3.org/hg/gld/raw-file/default/adms/index.html\">Asset Description Metadata Schema (ADMS)</a></cite> P. Archer, G. Shukair, Currently an Editor's Draft but expected to become a W3C Working Group Note. URL: http://dvcs.w3.org/hg/gld/raw-file/default/adms/index.html"
                 berjon.biblio["ORG"] = "<cite><a href=\"http://www.w3.org/TR/vocab-org/\">An organization ontology</a></cite>, D. Reynolds, W3C Recommendations Track Working Draft URL: http://www.w3.org/TR/vocab-org/"
                 berjon.biblio["EDSU"] = "<cite><a href=\"http://mediatypes.appspot.com/\">Media Types Application</a></cite> Ed Summers' work on providing URIs for media types  URL: http://mediatypes.appspot.com/"
                 berjon.biblio["FRBR"] = "<cite><a href=\"http://archive.ifla.org/VII/s13/frbr/frbr_current_toc.htm\">Functional Requirements for Bibliographic Records</a></cite> OFLA 1998  URL: http://archive.ifla.org/VII/s13/frbr/frbr_current_toc.htm"