Updating acknowledgements requested by EC
authorphila@p
Thu, 06 Jun 2013 09:46:15 +0100
changeset 549 8ef691aa5618
parent 548 57bdafcfd7f8
child 550 ac4ff08c9735
Updating acknowledgements requested by EC
legal/index.html
--- a/legal/index.html	Thu Jun 06 09:46:05 2013 +0100
+++ b/legal/index.html	Thu Jun 06 09:46:15 2013 +0100
@@ -1,15 +1,12 @@
-<!DOCTYPE html>
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head>
-  <title>Registered Organization Vocabulary</title>
-  <meta name="description" content="A vocabulary for describing organizations that gain legal entity status through a formal registration process." />
-	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-  <!--[if lt IE 9]>
-  <script src="http://www.w3.org/2008/site/js/html5shiv.js"></script>  <![endif]-->
-	<script type="text/javascript" src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
-	<script src="respec-ref.js"></script>
-	<script src="respec-config.js"></script>
-  <style type="text/css">
+  <!DOCTYPE html>
+  <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en" dir="ltr">
+    <head>
+      <title>Registered Organization Vocabulary</title>
+      <meta name="description" content="A vocabulary for describing organizations that gain legal entity status through a formal registration process.">
+      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+      <!--[if lt IE 9]>
+      <script src="http://www.w3.org/2008/site/js/html5shiv.js"></script>  <![endif]-->
+      <style type="text/css">
   table {
     border-collapse:collapse;
   }
@@ -21,25 +18,6 @@
   table#namespaces td {
     font-family: monospace;
   }
-  table tr.midtable th {
-    border-top: black medium double;
-  }
-  .editorsnote::before {
-    content:    "Editor's Note";
-    display:    block;
-  	width:      150px;
-    background: #F30023;
-    color:  #fff;
-    margin: -1.5em 0 0.5em 0;
-    font-weight:    bold;
-    border: 1px solid #cff6d9;
-    padding:    3px 1em;
-  }
-  .editorsnote {
-    margin: 1em 0em 1em 1em;
-    padding:    1em;
-    border: 2px solid #cff6d9;
-  }
   pre {
   	padding: 1em;
   	border: 1px dashed #2f6fab;
@@ -71,398 +49,1228 @@
    margin: 0 0.3em;
    line-height:1.5em;
   }
-  </style>
-</head>
-<body>
 
-<section id="abstract">
-<p>The Registered Organization Vocabulary is a profile of the Organization Ontology for describing 
+/*****************************************************************
+ * ReSpec CSS
+ * Robin Berjon (robin at berjon dot com)
+ * v0.05 - 2009-07-31
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 { 
+    text-transform:     lowercase;
+    font-variant:       small-caps;
+    font-style:         normal;
+    color:              #900;
+}
+
+a.bibref {
+    text-decoration:    none;
+}
+
+code {
+    color:  #ff4500;
+}
+
+h1 abbr, h2 abbr, h3 abbr {border:none}
+
+/* --- TOC --- */
+.toc a {
+    text-decoration:    none;
+}
+
+a .secno {
+    color:  #000;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+    margin-top: 0;
+}
+
+.section dd > p:last-child {
+    margin-bottom: 0;
+}
+
+.section dd {
+    margin-bottom:  1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+    margin-bottom:  0;
+}
+</style>
+      <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE"/>
+    </head>
+    <body style="display: inherit;">
+      <div class="head">
+        <p>
+          <a href="http://www.w3.org/">
+            <img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C">
+          </a>
+        </p>
+        <h1 class="title" id="title">Registered Organization Vocabulary</h1>
+        <h2 id="w3c-note-11-june-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Working Group Note 11 June 2013</h2>
+        <dl>
+          <dt>This version:</dt>
+          <dd>
+            <a href="http://www.w3.org/TR/2013/NOTE-vocab-regorg-20130611/">http://www.w3.org/TR/2013/NOTE-vocab-regorg-20130611/</a>
+          </dd>
+          <dt>Latest published version:</dt>
+          <dd>
+            <a href="http://www.w3.org/TR/vocab-regorg/">http://www.w3.org/TR/vocab-regorg/</a>
+          </dd>
+          <dt>Previous version:</dt>
+          <dd>
+            <a href="http://www.w3.org/TR/2013/NOTE-vocab-regorg-20130528/">http://www.w3.org/TR/2013/NOTE-vocab-regorg-20130528/</a>
+          </dd>
+          <dt>Editors:</dt>
+          <dd>
+            <a href="http://www.w3.org/People/all#phila">Phil Archer</a>, <a href="http://www.w3.org"> <abbr title="World Wide Web Consortium">W3C</abbr> / <abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>
+          </dd>
+          <dd>
+            <a href="http://www.ntua.gr/">Marios Meimaris</a>
+            , 
+            <a href="http://www.ntua.gr/">National Technical University of Athens (Invited Expert)</a> (from 1 March 2013)
+          </dd>
+          <dd>
+            <a href="http://www.ntua.gr/">Agisilaos Papantoniou</a>
+            , 
+            <a href="http://www.ntua.gr/">National Technical University of Athens (Invited Expert)</a> (until 28 Feb 2013)
+          </dd>
+        </dl>
+        <p>The vocabulary defined in this document is also available in these non-normative formats: <a href="http://www.w3.org/ns/regorg.rdf">RDF/XML</a> and <a href="http://www.w3.org/ns/regorg.ttl">Turtle</a>.</p>
+        <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2013 <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
+        <hr>
+      </div>
+      <div id="abstract" class="introductory section">
+        <h2>Abstract</h2>
+        <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">
-
-</section>
-
-<section class="informative">
-<h2 id="intro">Introduction</h2>
-<p>This is a vocabulary for describing organizations that have gained legal entity status
+      </div>
+      <div id="sotd" class="introductory section">
+        <h2>Status of This Document</h2>
+        <p>
+          <em>
+            This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current 
+            <abbr title="World Wide Web Consortium">W3C</abbr>
+             publications and the latest revision of this technical report can be found in the 
+            <a href="http://www.w3.org/TR/">
+              <abbr title="World Wide Web Consortium">W3C</abbr>
+               technical reports index
+            </a>
+             at http://www.w3.org/TR/.
+          </em>
+        </p>
+        <p>
+          This document was published by the 
+          <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a>
+           as a Note. If you wish to make comments regarding this document, please send them to 
+          <a href="mailto:[email protected]">[email protected]</a>
+           (
+          <a href="mailto:[email protected]?subject=subscribe">subscribe</a>
+          , 
+          <a href="http://lists.w3.org/Archives/Public/public-gld-comments/">archives</a>
+          ). All feedback is welcome.
+        </p>
+<p>The only changes made since the <a href="http://www.w3.org/TR/2013/NOTE-vocab-regorg-20130528/">previous version</a> 
+of this document concern the acknowledgement section. No substantive changes have been made.</p>
+<p>Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p>
+      <p> This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 
+      2004 W3C Patent Policy</a>. W3C maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/47663/status">public 
+      list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes 
+      instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual 
+      believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> 
+      must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 
+      6 of the W3C Patent Policy</a>. </p>
+      </div>
+      <div id="toc" class="section">
+        <h2 class="introductory">Table of Contents</h2>
+        <ul class="toc">
+          <li class="tocline">
+            <a href="#introduction" class="tocxref">
+              <span class="secno">1. </span>
+              Introduction
+            </a>
+          </li>
+          <li class="tocline">
+            <a href="#ns" class="tocxref">
+              <span class="secno">2. </span>
+              Namespaces
+            </a>
+          </li>
+          <li class="tocline">
+            <a href="#overview-of-the-vocabulary" class="tocxref">
+              <span class="secno">3. </span>
+              Overview of the vocabulary
+            </a>
+            <ul class="toc">
+              <li class="tocline">
+                <a href="#vocIndex" class="tocxref">
+                  <span class="secno">3.1 </span>
+                  Vocabulary index
+                </a>
+              </li>
+            </ul>
+          </li>
+          <li class="tocline">
+            <a href="#regorg-usage" class="tocxref">
+              <span class="secno">4. </span>
+              RegOrg Usage
+            </a>
+          </li>
+          <li class="tocline">
+            <a href="#relationship-with-the-organization-ontology" class="tocxref">
+              <span class="secno">5. </span>
+              Relationship with the Organization Ontology
+            </a>
+          </li>
+          <li class="tocline">
+            <a href="#vocabDef" class="tocxref">
+              <span class="secno">6. </span>
+              Vocabulary Definitions
+            </a>
+            <ul class="toc">
+              <li class="tocline">
+                <a href="#the-registered-organization-class" class="tocxref">
+                  <span class="secno">6.1 </span>
+                  The Registered Organization Class
+                </a>
+              </li>
+              <li class="tocline">
+                <a href="#properties" class="tocxref">
+                  <span class="secno">6.2 </span>
+                  Properties
+                </a>
+              </li>
+            </ul>
+          </li>
+          <li class="tocline">
+            <a href="#conformance" class="tocxref">
+              <span class="secno">7. </span>
+              Conformance
+            </a>
+          </li>
+          <li class="tocline">
+            <a href="#changelog" class="tocxref">
+              <span class="secno">A. </span>
+              Change Log
+            </a>
+          </li>
+          <li class="tocline">
+            <a href="#app13" class="tocxref">
+              <span class="secno">B. </span>
+              Note on identifier and classification properties
+            </a>
+          </li>
+          <li class="tocline">
+            <a href="#acknowledgements" class="tocxref">
+              <span class="secno">C. </span>
+              Acknowledgements
+            </a>
+          </li>
+          <li class="tocline">
+            <a href="#references" class="tocxref">
+              <span class="secno">D. </span>
+              References
+            </a>
+            <ul class="toc">
+              <li class="tocline">
+                <a href="#normative-references" class="tocxref">
+                  <span class="secno">D.1 </span>
+                  Normative references
+                </a>
+              </li>
+              <li class="tocline">
+                <a href="#informative-references" class="tocxref">
+                  <span class="secno">D.2 </span>
+                  Informative references
+                </a>
+              </li>
+            </ul>
+          </li>
+        </ul>
+      </div>
+      <div class="informative section" id="introduction">
+        <!--OddPage-->
+        <h2 id="intro">
+          <span class="secno">1. </span>
+          Introduction
+        </h2>
+        <p>
+          <em>This section is non-normative.</em>
+        </p>
+        <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 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 a minimal number of classes and properties that are 
+flexible and comprehensive Organization Ontology [
+          <cite>
+            <a class="bibref" href="#bib-ORG">ORG</a>
+          </cite>
+          ]. 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 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 -->
-
-<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>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 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 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.</p>
+      </div>
+      <!-- intro -->
+      <div id="ns" class="informative section">
+        <!--OddPage-->
+        <h2>
+          <span class="secno">2. </span>
+          Namespaces
+        </h2>
+        <p>
+          <em>This section is non-normative.</em>
+        </p>
+        <p>
+          The namespace for the Registered Organization vocabulary is 
+          <code>http://www.w3.org/ns/regorg#</code>
+           and the preferred prefix is
 
-<figure id="uml">
-  <img src="regorg20130508.png" width="368" height="343" alt="The Registered Organization Vocabulary UML diagram" />
-  <br/>
-  <figcaption>The Registered Organization Vocabulary</figcaption>
-</figure>
+          <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>
+      </div>
+      <!--end of namespaces-->
+      <div class="informative section" id="overview-of-the-vocabulary">
+        <!--OddPage-->
+        <h2 id="over">
+          <span class="secno">3. </span>
+          Overview of the vocabulary
+        </h2>
+        <p>
+          <em>This section is non-normative.</em>
+        </p>
+        <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 all aspects of ORG such as the 
 
-<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_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_hasRegOrg'>rov:hasRegisteredOrganization</a></li></ul></dd>
-   </dl>
-</section> <!--end of voc index-->
+          <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 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, 
 
-
-</section> <!-- end of overview-->
-
-<section class="informative">
-<h2 id="usage">RegOrg Usage</h2>
-
-<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>
-<li>a legal identifier (i.e. details of the registration with the authority that conferred legal status);</li>
-<li>a further identifier (Open Corporates).</li></ul>
-
-<p>We assume here that example.com is publishing information about registered organizations. This might be the
+          <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.
+        </p>
+        <figure id="uml">
+          <img src="regorg20130508.png" width="368" height="343" alt="The Registered Organization Vocabulary UML diagram">
+          <br>
+          <figcaption>The Registered Organization Vocabulary</figcaption>
+        </figure>
+        <div id="vocIndex" class="section">
+          <h3>
+            <span class="secno">3.1 </span>
+            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_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_hasRegOrg">rov:hasRegisteredOrganization</a>
+                </li>
+              </ul>
+            </dd>
+          </dl>
+        </div>
+        <!--end of voc index-->
+      </div>
+      <!-- end of overview-->
+      <div class="informative section" id="regorg-usage">
+        <!--OddPage-->
+        <h2 id="usage">
+          <span class="secno">4. </span>
+          RegOrg Usage
+        </h2>
+        <p>
+          <em>This section is non-normative.</em>
+        </p>
+        <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>
+          <li>a legal identifier (i.e. details of the registration with the authority that conferred legal status);</li>
+          <li>a further identifier (Open Corporates).</li>
+        </ul>
+        <p>We assume here that example.com is publishing information about registered organizations. This might be the
 company register itself or another organization.</p>
-
-<pre id="appleBinding">
-1  &lt;http://business.data.gov.uk/id/company/04285910&gt;
+        <pre id="appleBinding">1  &lt;http://data.companieshouse.gov.uk/id/company/04285910>
 2    a rov:RegisteredOrganization ;
 3    rov:legalName "Apple Binding Ltd" ;
-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; .
+4    rov:orgStatus &lt;http://example.com/ref/status/NormalActivity> ;
+5    rov:orgType &lt;http://example.com/ref/type/Plc> ;
+6    rov:orgActivity &lt;http://example.com/ref/NACE/2/C/18/01/02> ;
+7    rov:orgActivity &lt;http://example.com/ref/NACE/2/C/18/01/04> ;
+8    rov:registration &lt;http://example.com/id/li04285910> ;
+9    adms:identifier &lt;http://example.com/id/oc04285910> ;
+10   org:registeredSite &lt;http://example.com/id/rs04285910> .
 
    # The actual registration
-11 &lt;http://example.com/id/li04285910&gt; a adms:Identifier ;
+11 &lt;http://example.com/id/li04285910> a adms:Identifier ;
 12   skos:notation "04285910"^^ex:idType ;
 13   adms:schemaAgency "UK Companies House" ;
 14   dcterms:issued "2001-09-12"^^xsd:date .
 
    # A supplementary identifier (Open Corporates)
-15 &lt;http://example.com/id/oc04285910&gt; a adms:Identifier ;
+15 &lt;http://example.com/id/oc04285910> a adms:Identifier ;
 16   skos:notation "http://opencorporates.com/companies/gb/04285910"^^ex:OCid ;
 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; .
+19   dcterms:creator &lt;http://opencorporates.com/companies/gb/07444723> .
 </pre>
-
-<p>Line 3 gives the legally registered name of the company. In some jurisdictions,
+        <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 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).
+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>
+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 the 
+          <a href="#ref_rov_orgStatus">organization status</a>
+           and 
 
-<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
+          <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 organization type and organization status
-should be encoded as a SKOS Concept Scheme so that each ones has a URI.</p>
-
-<p>Registers typically record the type of activity (or multiple activities) carried out. 
+should be encoded as a SKOS Concept Scheme so that each ones has a URI.
+        </p>
+        <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:orgActivity</code> in lines 6 and 7 assume that NACE codes are encoded as SKOS concepts.</p>
-
-<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]]). 
+The UN's ISIC Codes [
+          <cite>
+            <a class="bibref" href="#bib-ISIC4">ISIC4</a>
+          </cite>
+          ] form a common starting point for several such vocabularies including
+the European Union's NACE [
+          <cite>
+            <a class="bibref" href="#bib-NACE">NACE</a>
+          </cite>
+          ] Codes and UK's SIC codes [
+          <cite>
+            <a class="bibref" href="#bib-SIC07">SIC07</a>
+          </cite>
+          ]. The URIs shown as the values 
+of 
+          <code>rov:orgActivity</code>
+           in lines 6 and 7 assume that NACE codes are encoded as SKOS concepts.
+        </p>
+        <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>
+           [
+          <cite>
+            <a class="bibref" href="#bib-ADMS">ADMS</a>
+          </cite>
+          ]). 
 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.
 This is the property that captures that information and links to the formal registration which is described
 in lines 15 - 18. In this case, Apple Binding became a registered company on 12 September 2001 when 
 UK Companies House issued it with the identifier 04285910. The identifier is typed in line with expected
-practice for <code>skos:notation</code> and the ORG ontology. Incidentally, UK Companies House
+practice for 
+          <code>skos:notation</code>
+           and the ORG ontology. Incidentally, UK Companies House
 publishes its information about registered companies as linked data and the example uses that URI
-as the subject of the description.</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
+as the subject of the description.
+        </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 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>
-
-
-</section> <!-- Example -->
-</section> <!-- Usage -->
-
-<section class="informative">
-<h2 id="relOrg">Relationship with the Organization Ontology</h2>
-<p>A Registered Organization (<code>rov:RegisteredOrganization</code>) is a sub class of
-the Organization Ontology's Formal Organization (<code>org:FormalOrganization</code>).
+      </div>
+      <!-- Example -->
+      <!-- Usage -->
+      <div class="informative section" id="relationship-with-the-organization-ontology">
+        <!--OddPage-->
+        <h2 id="relOrg">
+          <span class="secno">5. </span>
+          Relationship with the Organization Ontology
+        </h2>
+        <p>
+          <em>This section is non-normative.</em>
+        </p>
+        <p>
+          A Registered Organization (
+          <code>rov:RegisteredOrganization</code>
+          ) is a sub class of
+the Organization Ontology's Formal Organization (
+          <code>org:FormalOrganization</code>
+          ).
 Furthermore, RegORG includes three sub properties of ORG's classification property covering
-status, activity and type.</p>
-<p>The key difference is the way in which identifiers are handled. In the ORG ontology, an organization
-may have an identifier expressed as a datatyped string (it uses a sub property of <code>skos:notation</code>). 
+status, activity and type.
+        </p>
+        <p>
+          The key difference is the way in which identifiers are handled. In the ORG ontology, an organization
+may have an identifier expressed as a datatyped string (it uses a sub property of 
+          <code>skos:notation</code>
+          ). 
 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
+confers legal status and therefore always has particular significance. RegORG uses the 
+          <abbr title="Asset Description Metadata Schema">ADMS</abbr>
+           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 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>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; .
+          <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>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>
+  rov:registration &lt;http://example.com/id/li123456> .
 
-&lt;http://example.com/id/li123456&gt; a adms:Identifier ;
+&lt;http://example.com/id/li123456> a adms:Identifier ;
   skos:notation "123456"^^ex:idType .
   </pre>
-<p>This SPARQL query</p>
-  <pre>CONSTRUCT {
+        <p>This SPARQL query</p>
+        <pre>CONSTRUCT {
     ?org org:identifier ?id .
 } WHERE {
   ?org rov:registration [skos:notation ?id] .
 }</pre>
-<p>yields the <code>org:identifier</code> property and value, i.e.</p>
-<pre>
-&lt;http://example.com/id/123456&gt;
+        <p>
+          yields the 
+          <code>org:identifier</code>
+           property and value, i.e.
+        </p>
+        <pre>&lt;http://example.com/id/123456>
   org:identifier "123456"^^ex:idType .</pre>
-
-</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="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 
+      </div>
+      <!--relORG -->
+      <div id="vocabDef" class="section">
+        <!--OddPage-->
+        <h2>
+          <span class="secno">6. </span>
+          Vocabulary Definitions
+        </h2>
+        <p>The classes and properties are described in the following sub-sections.</p>
+        <div id="the-registered-organization-class" class="section">
+          <h3 id="ref_rov_regorg">
+            <span class="secno">6.1 </span>
+            The Registered Organization Class
+          </h3>
+          <table>
+            <thead>
+              <tr>
+                <th>Class</th>
+                <th>Notes</th>
+              </tr>
+            </thead>
+            <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. 
+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. &mdash; i.e. an Agent is 
-any entity that is able to carry out actions.</p>
-
-</section> <!-- end of classes section-->
+          <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 [
+            <cite>
+              <a class="bibref" href="#bib-FOAF">FOAF</a>
+            </cite>
+            ] and Dublin Core [
+            <cite>
+              <a class="bibref" href="#bib-DC11">DC11</a>
+            </cite>
+            ] that 
 
-<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, 
+            <em>does</em>
+             encompass organizations, natural persons, groups etc. — i.e. an Agent is 
+any entity that is able to carry out actions.
+          </p>
+        </div>
+        <!-- end of classes section-->
+        <div id="properties" class="section">
+          <h3 id="regorg_properties">
+            <span class="secno">6.2 </span>
+            Properties
+          </h3>
+          <h3 id="ref_rov_legalname">Legal Name</h3>
+          <table>
+            <thead>
+              <tr>
+                <th>Property</th>
+                <th>Domain</th>
+                <th>Range</th>
+              </tr>
+            </thead>
+            <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 the language of the string should be identified.</p>
-
-
-<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">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>skos:altLabel</code> but 
+          <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">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>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 
-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_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: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, 
+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_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: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 
 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 
+          <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_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: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 an organization presents the same issues as its type. 
+          <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: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 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' 
-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 
+          <p>
+            Taking advice from 
+            <a href="http://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_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: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 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 
+          <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: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 an organization should be recorded using a controlled vocabulary. Several 
+such vocabularies exist, many of which map to the UN's ISIC codes [
+            <cite>
+              <a class="bibref" href="#bib-ISIC4">ISIC4</a>
+            </cite>
+            ]. 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 
+these, however, the preferred choice for European interoperability is NACE [
+            <cite>
+              <a class="bibref" href="#bib-NACE">NACE</a>
+            </cite>
+            ]. 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 
+provided as properties of the Identifier class which is defined by 
+            <abbr title="Asset Description Metadata Schema">ADMS</abbr>
+             [
+            <cite>
+              <a class="bibref" href="#bib-ADMS">ADMS</a>
+            </cite>
+            ]. 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 
+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_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:hasRegisteredOrganization</td><td>dcterms:Agent</td><td><code>rov:RegisteredOrganization</code></td></tr></tbody>
-</table>
-<p>The has registered organization relationship can be used to link any <code>dcterms:Agent</code> (equivalent class <code>foaf:Agent</code>)
+          <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:hasRegisteredOrganization</td>
+                <td>dcterms:Agent</td>
+                <td>
+                  <code>rov:RegisteredOrganization</code>
+                </td>
+              </tr>
+            </tbody>
+          </table>
+          <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>
-
-</section>
-
-</section>
-
-
-<section id="conformance">
+where an organization includes one or more legal entities, or where a natural person is also registered as a legal entity.
+          </p>
+        </div>
+      </div>
+      <div id="conformance" class="section">
+        <!--OddPage-->
+        <h2>
+          <span class="secno">7. </span>
+          Conformance
+        </h2>
+        <p>As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.</p>
+        <p>
+          The key words 
+          <em class="rfc2119" title="must">must</em>
+          , 
+          <em class="rfc2119" title="must not">must not</em>
+          , 
+          <em class="rfc2119" title="required">required</em>
+          , 
+          <em class="rfc2119" title="should">should</em>
+          , 
+          <em class="rfc2119" title="should not">should not</em>
+          , 
+          <em class="rfc2119" title="recommended">recommended</em>
+          , 
+          <em class="rfc2119" title="may">may</em>
+          , and 
+          <em class="rfc2119" title="optional">optional</em>
+           in this specification are to be interpreted as described in [
+          <cite>
+            <a class="bibref" href="#bib-RFC2119">RFC2119</a>
+          </cite>
+          ].
+        </p>
+        <p>A data interchange, however that interchange occurs, is conformant with the Registered Organization
+vocabulary if:</p>
+        <ul>
+          <li>it uses the terms (classes and properties)in a way consistent with their semantics as declared in this specification;</li>
+          <li>it does not use terms from other vocabularies instead of ones defined in this vocabulary that could reasonably be used.</li>
+        </ul>
+        <p>A conforming data interchange:</p>
+        <ul>
+          <li>
+            <span class="rfc2119">may</span>
+             include terms from other vocabularies;
+          </li>
+          <li>
+            <span class="rfc2119">may</span>
+             use only a subset of Registered Organization vocabulary terms.
+          </li>
+        </ul>
+        <p>A Registered Organization application profile is a specification for data interchange that adds additional constraints. Such additional 
+constraints in a profile may include:</p>
+        <ul>
+          <li>a minimum set of required terms; </li>
+          <li>classes and properties for additional terms not covered in the Registered Organization vocabulary;</li>
+          <li>controlled vocabularies or URI sets as acceptable values for properties;</li>
+        </ul>
+        <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>
+      </div>
+      <div id="changelog" class="appendix section">
+        <!--OddPage-->
+        <h2>
+          <span class="secno">A. </span>
+          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
 
-<p>A data interchange, however that interchange occurs, is conformant with the Registered Organization
-vocabulary if:</p><ul>
-<li>it uses the terms (classes and properties)in a way consistent with their semantics as declared in this specification;</li>
-<li>it does not use terms from other vocabularies instead of ones defined in this vocabulary that could reasonably be used.</li>
-</ul>
-<p>A conforming data interchange:</p><ul>
-<li><span class="rfc2119">may</span> include terms from other vocabularies;</li>
-<li><span class="rfc2119">may</span> use only a subset of Registered Organization vocabulary terms.</li>
-</ul>
-<p>A Registered Organization application profile is a specification for data interchange that adds additional constraints. Such additional 
-constraints in a profile may include:</p><ul>
-<li>a minimum set of required terms; </li>
-<li>classes and properties for additional terms not covered in the Registered Organization vocabulary;</li>
-<li>controlled vocabularies or URI sets as acceptable values for properties;</li>
-</ul>
-<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>
+          <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 
+          <abbr title="Asset Description Metadata Schema">ADMS</abbr>
+           and, in the same way that 
+          <abbr title="Asset Description Metadata Schema">ADMS</abbr>
+           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
 
-</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>
-<p>There are several vocabularies in use with a property of 'identifier' and this vocabulary creates a sub property of one of them.
+          <code>rov:orgType</code>
+          , 
+          <code>rov:orgActivity</code>
+           and 
+          <code>rov:orgStatus</code>
+           respectively.
+        </p>
+      </div>
+      <div id="app13" class="appendix section">
+        <!--OddPage-->
+        <h2>
+          <span class="secno">B. </span>
+          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>
-<table>
-  <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><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>
+        <table>
+          <tbody>
+            <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>
+                <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>
+          </tbody>
+        </table>
+      </div>
+      <div id="acknowledgements" class="appendix section">
+        <!--OddPage-->
+        <h2>
+          <span class="secno">C. </span>
+          Acknowledgements
+        </h2>
 
-<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>
+<p>RegOrg was first developed by and published by the European Commission 
+<a href="http://ec.europa.eu/isa/">ISA Programme</a> with support from the
+Directorate General Internal Market and Services (DG MARKT)as the 
+<a href="https://joinup.ec.europa.eu/asset/core_business/release/100">Core Business Vocabulary</a>. 
+Contributors included representatives of Member States of the European Union, operators 
+of national repositories, standardization bodies and independent experts whose work 
+was published in May 2012. That document includes the history and motivation behind 
+the development of RegOrg, as well as the business need and usage scenario for it.</p>
+<p>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).
+This version of the vocabulary builds on the original work in a broader, global context.</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>
+      </div>
+      <div id="references" class="appendix section">
+        <!--OddPage-->
+        <h2>
+          <span class="secno">D. </span>
+          References
+        </h2>
+        <div id="normative-references" class="section">
+          <h3>
+            <span class="secno">D.1 </span>
+            Normative references
+          </h3>
+          <dl class="bibliography">
+            <dt id="bib-ADMS">[ADMS]</dt>
+            <dd>
+              <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, W3C Working Group Note. URL: http://www.w3.org/TR/vocab-adms/
+            </dd>
+            <dt id="bib-DC11">[DC11]</dt>
+            <dd>
+              Dublin Core metadata initiative. 
+              <a href="http://dublincore.org/documents/dcmi-terms/">
+                <cite>Dublin Core metadata element set, version 1.1.</cite>
+              </a>
+               July 1999. Dublin Core recommendation. URL: 
+              <a href="http://dublincore.org/documents/dcmi-terms/">http://dublincore.org/documents/dcmi-terms/</a>
+            </dd>
+            <dt id="bib-FOAF">[FOAF]</dt>
+            <dd>
+              Dan Brickley, Libby Miller. 
+              <a href="http://xmlns.com/foaf/spec/">
+                <cite>FOAF Vocabulary Specification 0.98.</cite>
+              </a>
+               9 August 2010. URL: 
+              <a href="http://xmlns.com/foaf/spec/">http://xmlns.com/foaf/spec/</a>
+            </dd>
+            <dt id="bib-ORG">[ORG]</dt>
+            <dd>
+              <cite>
+                <a href="http://www.w3.org/TR/vocab-org/">An organization ontology</a>
+              </cite>
+              , D. Reynolds, W3C Recommendations Track URL: http://www.w3.org/TR/vocab-org/
 
+            </dd>
+            <dt id="bib-RFC2119">[RFC2119]</dt>
+            <dd>
+              S. Bradner. 
+              <a href="http://www.ietf.org/rfc/rfc2119.txt">
+                <cite>Key words for use in RFCs to Indicate Requirement Levels.</cite>
+              </a>
+               March 1997. Internet RFC 2119.  URL: 
+              <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
+            </dd>
+          </dl>
+        </div>
+        <div id="informative-references" class="section">
+          <h3>
+            <span class="secno">D.2 </span>
+            Informative references
+          </h3>
+          <dl class="bibliography">
+            <dt id="bib-ISIC4">[ISIC4]</dt>
+            <dd>
+              <cite>
+                <a href="http://unstats.un.org/unsd/cr/registry/regcst.asp?Cl=27">International Standard Industrial Classification of All Economic Activities, Rev.4</a>
+              </cite>
+              , United Nations Statistics Division.   URL: http://unstats.un.org/unsd/cr/registry/regcst.asp?Cl=27
 
-</body></html>
+            </dd>
+            <dt id="bib-NACE">[NACE]</dt>
+            <dd>
+              <cite>
+                <a href="http://ec.europa.eu/eurostat/ramon/nomenclatures/index.cfm?TargetUrl=LST_NOM_DTL&amp;StrNom=NACE_REV2&amp;StrLanguageCode=EN">Statistical Classification of Economic Activities in the European Community</a>
+              </cite>
+              , Eurostat   URL: http://ec.europa.eu/eurostat/ramon/nomenclatures/index.cfm?TargetUrl=LST_NOM_DTL&amp;StrNom=NACE_REV2&amp;StrLanguageCode=EN
+
+            </dd>
+            <dt id="bib-SIC07">[SIC07]</dt>
+            <dd>
+              <cite>
+                <a href="http://www.companieshouse.gov.uk/infoAndGuide/sic/sic2007.shtml">Standard Industrial Classification of Economic Activities 2007</a>
+              </cite>
+              , UK Companies House   URL: http://www.companieshouse.gov.uk/infoAndGuide/sic/sic2007.shtml
+
+            </dd>
+          </dl>
+        </div>
+      </div>
+    </body>
+  </html>
\ No newline at end of file