Changed name of Business Core Voc to Legal Entity Voc, also changed namespace in line with WG resolution
--- a/legal/index.html Thu Oct 04 14:49:19 2012 +0100
+++ b/legal/index.html Thu Oct 04 17:07:44 2012 +0100
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
- <title>Business Core Vocabulary</title>
+ <title>Legal Entity Vocabulary</title>
<meta name="description" content="A vocabulary for describing businesses 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]>
@@ -63,17 +63,24 @@
</style>
</head>
<body>
+<div class="editorsnote">
+<p>To do before FPWD:</p><ul>
+ <li>add definitions of datatypes for Text, Code, Identifier (refer to <a href="http://dvcs.w3.org/hg/gld/raw-file/default/adms/index.html">ADMS</a> for this);</li>
+ <li>resolve range for registered address;</li>
+ <li>ensure RDF schema/namespace doc also ready.</li>
+</ul>
+</div>
<section id="abstract">
<p>This is a vocabulary for describing businesses that gain legal entity status
through a formal registration process, typically in a national or regional company register.
-This document is a companion to the namespace document at <a href="http://www.w3.org/ns/adms">http://www.w3.org/ns/legal</a></p>
+This document is a companion to the namespace document at <a href="http://www.w3.org/ns/legal-entity">http://www.w3.org/ns/legal-entity</a></p>
</section>
<section id="sotd">
- <p>This is the First Public Working Draft of the Business Core Vocabulary in W3C's TR space and
- signals its move to the Recommendations Track. The Business Core Vocabulary was first
- developed by PwC EU Services on behalf of the European Commission and
+ <p>This is the First Public Working Draft of the Legal Entity 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>
@@ -86,44 +93,49 @@
through a formal registration process, typically in a national or regional company register.
It focuses solely on legal entities and excludes sole traders, virtual organizations
and other types of 'agent' that are able to do business. It may be seen as a specialization of the more
-flexible Organization Ontology [[ORG]].</p>
+flexible and comprehensive Organization Ontology [[ORG]].</p>
<p>It 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>The original development of the Business Core Vocabulary was carried out under the
+<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 Business Core Vocabulary builds on that work in a broader, global context.</p>
+<p>This version of the Legal Entity vocabulary builds on that work in a broader, global context.</p>
</section>
<section id="conformance">
-<p>Conformance to this vocabulary means using its classes, properties and relationships to
-describe businesses. It does not necessarily mean using <em>every</em> term and there are no
-terms that are mandatory. However, the inclusion of a term signals that the Working Group
-has found it to be useful. Applications MAY specify a minimum set of terms that publishers must use
-if their data is to be processed, and MAY also specify controlled vocabularies as acceptable values for properties.
-This specification treats such restrictions as <em>application-specific</em> and therefore
-makes no such restrictions. However, the Working Group recognizes that
-restrictions (cardinality constraints) are often important.</p>
-<p>It is, perhaps, easier to define non-conformance. A non-conformant implementation is one that
-uses a term other than one defined in this document that could reasonably be used.</p>
-
-<p>The Business Core Vocabulary is technology-neutral and a publisher may use any of the terms defined in this
+<p>A data interchange, however that interchange occurs, is conformant with the Legal Entity
+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</a> include terms from other vocabularies;</li>
+<li><span class="rfc2119">may</a> use only a subset of Legal Entity vocabulary terms.</li>
+</ul>
+<p>A Legal Entity 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 Legal Entity vocabulary;</li>
+<li>controlled vocabularies or URI sets as acceptable values for properties;</li>
+<li>guidance on the use of pairs of inverse properties (such as selecting only one member of the pair to
+be included, or requiring that both members be explicitly included).</li></ul>
+<p>The Legal Entity 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>
</section>
<section>
<h2 id="ns">Namespaces</h2>
-<p>The namespace for the Business Core Vocabulary is <code>http://www.w3.org/ns/legal#</code>.
-A full set of namespaces and prefixes used in this document is shown in the table below.</p>
+<p>The namespace for the Legal Entity vocabulary is <code>http://www.w3.org/ns/legal-entity#</code> and the preferred prefix is
+<code>legal-entity</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>
@@ -157,7 +169,8 @@
references to various types of entities in the real world, such as organizations, people and
places.</p>
-<p>A <strong>Core Vocabulary</strong> is a simplified, reusable, and extensible data model that
+<p>A <strong>Core Vocabulary</strong>, of which the Legal Entity vocabulary is an example,
+is a simplified, reusable, and extensible data model that
captures the fundamental characteristics of an entity in a context-neutral fashion [[CV1]].
Well known examples of existing Core Vocabularies include the Dublin Core Metadata Set [[DC11]].
Such Core Vocabularies are the starting point for agreeing on new semantic interoperability
@@ -169,7 +182,7 @@
<section class="informative">
<h2 id="example">Example of Use</h2>
-<p>The following is an example of a (real) company described using the Business Core Vocabulary (in RDF/Turtle). This includes:</p></ul>
+<p>The following is an example of a (real) company described using the Legal Entity vocabulary (in RDF/Turtle). This includes:</p></ul>
<li>a description of the legal entity ;</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>
@@ -179,18 +192,18 @@
<pre id="appleBinding">
1 <http://data.companieshouse.gov.uk/id/company/04285910>
-2 a legal:LegalEntity ;
-3 legal:legalName "Apple Binding Ltd" ;
-4 legal:companyStatus <http://example.com/ref/status/NormalActivity> ;
-5 legal:companyType <http://example.com/ref/type/Plc> ;
-6 legal:companyActivity <http://example.com/ref/NACE/2/C/18/01/02> ;
-7 legal:companyActivity <http://example.com/ref/NACE/2/C/18/01/04> ;
+2 a legal-entity:LegalEntity ;
+3 legal-entity:legalName "Apple Binding Ltd" ;
+4 legal-entity:companyStatus <http://example.com/ref/status/NormalActivity> ;
+5 legal-entity:companyType <http://example.com/ref/type/Plc> ;
+6 legal-entity:companyActivity <http://example.com/ref/NACE/2/C/18/01/02> ;
+7 legal-entity:companyActivity <http://example.com/ref/NACE/2/C/18/01/04> ;
8 # Note the use of legalIdentifier on the next line
-9 legal:legalIdentifier <http://example.com/id/li04285910> ;
+9 legal-entity:legalIdentifier <http://example.com/id/li04285910> ;
10 # Other identifiers are often very useful but they do
11 # not confer legal entity status.
-12 legal:identifier <http://example.com/id/oc04285910> ;
-13 legal:registeredAddress <http://example.com/id/ra04285910> .
+12 legal-entity:identifier <http://example.com/id/oc04285910> ;
+13 legal-entity:registeredAddress <http://example.com/id/ra04285910> .
14 # The actual registration
15 <http://example.com/id/li04285910> a adms:Identifier ;
@@ -229,7 +242,7 @@
<p>Line 9 carries the crucial <code><a href="#legalIdentifer">legalIdentifier</a></code> property that points to an
Identifier class (defined in <abbr title="Asset Description Metadata Schema">ADMS</abbr> [[ADMS]]).
-Although formally the Business Core Vocabulary has no mandatory
+Although formally the Legal Entity vocabulary has no mandatory
classes or properties, the defining characteristic of a legal entity 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 legal entity on 12 September 2001 when
@@ -248,14 +261,14 @@
<h2 id="conceptualmodel">The Conceptual Model</h2>
<figure id="uml">
- <img src="BusinessCVdiagram.png" width="729" height="247" alt="UML Diagram of the Business Core Vocabulary" />
- <figcaption>UML Diagram of the Business Core Vocabulary</figcaption>
+ <img src="BusinessCVdiagram.png" width="729" height="247" alt="UML Diagram of the Legal Entity vocabulary" />
+ <figcaption>UML Diagram of the Legal Entity vocabulary</figcaption>
</figure>
<p>The classes and properties are described in the following sub-sections.</p>
<section>
<h3 id="LegalEntity">The Legal Entity Class</h3>
-<p><code>legal:LegalEntity</code> is the key class for the Business Core Vocabulary and represents a business that is
+<p><code>legal-entity:LegalEntity</code> is the key class for the Legal Entity vocabulary and represents a business that is
legally registered. In many countries there is a single registry although in others, such
as Spain and Germany, multiple registries exist. A Legal Entity is able to trade, is
legally liable for its actions, accounts, tax affairs etc.</p>
@@ -353,7 +366,7 @@
provided as properties of the Identifier class which is defined by ADMS [[ADMS]]. The vocabulary
sets no restriction on the type of legal identifier. In many countries, the business
register's identifier is the relevant data point. The tax number often fulfils this function in Spain.</p>
-<p>Although there is no formal cardinality constraint on any property in the Business Core Vocabulary, it is
+<p>Although there is no formal cardinality constraint on any property in the Legal Entity vocabulary, it is
questionable whether a description of a legal entity without this property and an associated Identifier class
will be of any value.</p>
<p>In RDF terms, <code>legalIdentifier</code> is a sub property of identifier (see next section) with specific semantics.</p>
@@ -410,7 +423,7 @@
<section>
<h2 id="ack">Acknowledgements</h2>
-<p>Significant contributions to the original work on the Business Core Vocabulary were made by:
+<p>Significant contributions to the original work on the Legal Entity vocabulary were made by:
Ignacio Boixo,
Debora Di Giacomo,
Stijn Goedertier,
--- a/legal/respec-config.js Thu Oct 04 14:49:19 2012 +0100
+++ b/legal/respec-config.js Thu Oct 04 17:07:44 2012 +0100
@@ -1,11 +1,11 @@
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
specStatus: "ED",
- publishDate: "2012-09-28",
+ publishDate: "2012-10-04",
//copyrightStart: "2010",
// the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "vocab-legal",
+ shortName: "vocab-legal-entity",
//subtitle: "",
// if you wish the publication date to be other than today, set this
// publishDate: "2009-08-06",