Updated ADMS
authorphila
Thu, 04 Apr 2013 17:40:01 +0100
changeset 443 c1fd9d51388c
parent 442 839493d50752
child 444 8cf78f63b12d
Updated ADMS
adms/adms20130404.png
adms/index.html
adms/respec-config.js
adms/respec-ref.js
Binary file adms/adms20130404.png has changed
--- a/adms/index.html	Thu Apr 04 08:32:24 2013 +0100
+++ b/adms/index.html	Thu Apr 04 17:40:01 2013 +0100
@@ -64,36 +64,31 @@
 <body>
 
 <section id="abstract">
-<p>ADMS is a vocabulary for describing 
-<em>semantic assets</em>, defined as highly reusable metadata (e.g. xml schemata,
+<p>ADMS is a profile of DCAT, used to describe <em>semantic assets</em>, defined as highly reusable metadata (e.g. xml schemata,
 generic data models) and reference data (e.g. code lists, taxonomies, dictionaries,
-vocabularies) that are used for eGovernment system development. This document is a
-companion to the namespace document at <a href="http://www.w3.org/ns/adms">http://www.w3.org/ns/adms</a></p>
+vocabularies) that are used for eGovernment system development.</p>
 </section>
 
 <section id="sotd">
-  <p>This is the First Public Working Draft of ADMS in W3C's TR space and
-  signals its move to the Recommendations Track. ADMS was first
-  developed by PwC EU Services 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>
+  <p>ADMS was first developed by PwC EU Services and <a href="http://joinup.ec.europa.eu/asset/adms/home">published 
+  by the European Commission</a>. 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>
 
 </section>
 
 <section class="informative">
 <h2 id="intro">Introduction</h2>
-<p>ADMS, the Asset Description Metadata Schema, is a vocabulary for describing so-called 
+<p>ADMS, the Asset Description Metadata Schema, is a profile of DCAT [[DCAT]] for describing so-called 
 <em>Semantic Assets</em>, that is, things like standards, code lists and
-taxonomies. Although it has a lot in common with the Data Catalog vocabulary [[DCAT]],
-notably the extensive use of Dublin Core [[DC11]], someone searching for a Semantic Asset
-is likely to have different needs, priorities and expectations than someone searching for a data set and
-these differences are reflected in ADMS. In particular, users seeking a Semantic Asset are
-likely to be searching for 'a document' &mdash; something they can open and read using familiar desktop
-software, as opposed to something that needs to be processed. Of course this is a very broad
-generalization. If a code list is published as a SKOS Concept scheme then it is both a Semantic Asset
+taxonomies. Someone searching for a Semantic Asset is likely to have different needs, priorities and expectations 
+than someone searching for a data set in a data catalog and these differences are reflected in ADMS. 
+In particular, users seeking a Semantic Asset are likely to be searching for 'a document' &mdash; something they 
+can open and read using familiar desktop software, as opposed to something that needs to be processed. 
+Of course this is a very broad generalization. If a code list is published as a SKOS Concept scheme then it is both a Semantic Asset
 and a dataset and it can be argued that all Semantic Assets are datasets. Therefore the difference in
-<em>user expectation</em> is at the heart of what distinguishes ADMS from DCAT.</p>
+<em>user expectation</em> is at the heart of what distinguishes ADMS as a profile of DCAT. A further distinction 
+between DCAT anad ADMS can be made in that DCAT is <em>designed to facilitate interoperability between data catalogs</em>,
+i.e. the catalog itself is at the heart of the vocabulary. ADMS is focused on assets within a catalog.</p>
 
 <p>The original development of ADMS was carried out under the
 Interoperability Solutions for European Public Administrations (<a href="http://ec.europa.eu/isa/">ISA Programme</a>) 
@@ -140,25 +135,24 @@
 <h2 id="ns">Namespaces</h2>
 <p>The namespace for ADMS is <code>http://www.w3.org/ns/adms#</code>. However,
 it should be noted that ADMS makes extensive use of terms from other vocabularies,
-in particular Dublin Core [[DC11]]. 
-It subclasses the RADion vocabulary [[RAD]] that offers a structure for catalogs of various kinds.
-ADMS itself defines a minimal set of classes and
-properties of its own. A full set of namespaces and prefixes used in this
-document is shown in the table below.</p>
+in particular Dublin Core [[DC11]]. It re-uses and subclasses DCAT wherever possible
+and therefore defines a minimal set of classes and properties of its own. 
+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>dcat</td><td>http://www.w3.org/ns/dcat#</td></tr>
     <tr><td>dcterms</td><td>http://purl.org/dc/terms/</td></tr>
-    <tr><td>radion</td><td>http://www.w3.org/ns/radion#</td></tr>
+<!--    <tr><td>radion</td><td>http://www.w3.org/ns/radion#</td></tr> -->
     <tr><td>foaf  </td><td>http://xmlns.com/foaf/0.1/</td></tr>
-    <tr><td>xhv  </td><td>http://www.w3.org/1999/xhtml/vocab#</td></tr>
+<!--    <tr><td>schema  </td><td>http://schema.org/</td></tr> -->
+    <tr><td>rdfs</td><td>http://www.w3.org/2000/01/rdf-schema#</td></tr>
     <tr><td>skos  </td><td>http://www.w3.org/2004/02/skos/core#</td></tr>
-    <tr><td>schema  </td><td>http://schema.org/</td></tr>
     <tr><td>v</td><td>http://www.w3.org/2006/vcard/ns#</td></tr>
     <tr><td>wdrs</td><td>http://www.w3.org/2007/05/powder-s#</td></tr>
-    <tr><td>rdfs</td><td>http://www.w3.org/2000/01/rdf-schema#</td></tr>
+    <tr><td>xhv  </td><td>http://www.w3.org/1999/xhtml/vocab#</td></tr>
   </tbody>
 </table>
 </section>
@@ -186,44 +180,31 @@
 
 <section class="informative">
 <h2 id="overview">Vocabulary Overview</h2>
-<p>ADMS is intended as a model that facilitates federation and co-operation. It is not the primary
-intention that repository publishers redesign or convert their current systems and data to
-conform to ADMS, rather that ADMS can act as a common layer among repositories that
-want to exchange data. On the other hand, there is nothing prohibiting developers of new repositories, or publishers of
-existing repositories if they so desire, to build systems that allow the creation and maintenance
-of asset descriptions in an ADMS-compliant format.</p>
-<p>Like DCAT, ADMS has the concepts of a repository (catalog), assets within the repository
-that are often conceptual in nature, and then accessible realizations of those assets, known
-as distributions. An asset may have multiple distributions. As an example, a W3C namespace document
-can be considered to be a Semantic Asset that is available in multiple distributions, typically one
-or more machine processable versions and one in HTML for human consuption.</p>
-<p>The model described in this document is, as much as possible, technology-neutral so it can be
-implemented using different technologies. W3C maintains RDF (@@@and [email protected]@@) schemas at
-<a href="http://www.w3.org/ns/adms">http://www.w3.org/ns/adms</a>.</p>
-<p class="editorsnote">An XML schema exists and is published on the EC's Joinup platform, however it includes
-all the controlled vocabularies and cardinality constraints associated with the original document. A 
-simpler version more in line with the RDF schema will be needed if the GLD WG is to maintain both the RDF and XML schemas.</p>
+<p>ADMS is intended as a model that facilitates federation and co-operation.
+Like DCAT, ADMS has the concepts of a repository (catalog), assets within the repository
+that are often conceptual in nature, and accessible realizations of those assets, known
+as distributions. An asset may have zero or multiple distributions. As an example, a W3C namespace document
+can be considered to be a Semantic Asset that is typically available in multiple distributions, typically one
+or more machine processable versions and one in HTML for human consuption. An asset without any distributions 
+is effectively a concept with no tangible realization, such as a planned output of a working group that has not yet been drafted.</p>
+<p>ADMS is an RDF vocabulary with an RDF schema available at its namespace <a href="http://www.w3.org/ns/adms">http://www.w3.org/ns/adms</a>.
+The original ADMS specification published by the European Commission [[ADMS1]] includes an XML schema that also defines
+all the controlled vocabularies and cardinality constraints associated with the original document.</p>
 
 
 <section>
 <h2 id="example">Example</h2>
 <p>This example provides a quick overview of how ADMS might be used to represent a Semantic Asset Repository and its assets.</p>
-<p>Examples in this document are encoded in RDF and serialized in <a href="http://www.w3.org/TR/turtle/">Turtle</a> although,
-as noted, ADMS is designed to be technology-neutral.</p>
+<p>Examples in this document are serialized in <a href="http://www.w3.org/TR/turtle/">Turtle</a>.</p>
 <p>First, the repository description:</p>
 
-<pre>:Repository a adms:SemanticAssetRepository;
+<pre id="sarEg">:Repository a adms:SemanticAssetRepository;
   dcterms:created "1947-02-07"^^xsd:date;
   dcterms:description "A complete catalog of code lists and standards created by the Exemplary Standards Body"@en;
   dcterms:publisher &lt;http://example.com/data#org&gt;;
-  dcterms:title "The Exemplary Standards Body Catalog"@en;
-  rdfs:label "The Exemplary Standards Body Catalog"@en .</pre>
+  dcterms:title "The Exemplary Standards Body Catalog"@en.</pre>
 
-<p>This assumes that data concerning The Exemplary Standards Body is described (in RDF) at <code>http://example.com/data#org</code>.</p>
-<p>Notice that the same string is given as the value for both <code>dcterms:title</code> and <code>rdfs:label</code>. 
-This is because for some Semantic Assets it may not be appropriate to provide a title as such but it is 
-always appropriate to provide a label. Semantic Asset Repository owners are encouraged to use both properties 
-for ease of discovery.</p>
+<p>This assumes that the Exemplary Standards Body is described at <code>http://example.com/data#org</code>.</p>
 
 <p>Next, a Semantic Asset. We'll create an imaginary code list called 'Fruit I like' for our example:</p>
 <ul>
@@ -233,28 +214,27 @@
   <li>peaches</li>
 </ul>
 <p>We might describe this Semantic Asset thus:</p>
-<pre>
+<pre id="saEg">
 1  :Fruit_02 a adms:SemanticAsset;
 2    dcterms:created "1999-05-24";
 3    dcterms:description "Fruits that are found to be generally liked by most people.";
 4    dcterms:publisher &lt;http://example.com/data#org&gt;;
 5    dcterms:title "Fruit I like"@en ;
-6    rdfs:label "Fruit I like"@en;
-7    adms:status &lt;http://purl.org/adms/status/Completed&gt; ;
-8    dcterms:type &lt;http://purl.org/adms/assettype/CodeList&gt; ;
-9    xhv:previous :Fruit_01 ;
-10   xhv:last :Fruit ;
-11   radion:distribution :Fruit_02.csv ;
-12   radion:distribution :Fruit_02.xml .</pre>
+6    adms:status &lt;http://purl.org/adms/status/Completed&gt; ;
+7    dcterms:type &lt;http://purl.org/adms/assettype/CodeList&gt; ;
+8    xhv:previous :Fruit_01 ;
+9    xhv:last :Fruit ;
+10   adms:distribution :Fruit_02.csv ;
+11   adms:distribution :Fruit_02.xml .</pre>
 
 <p>This provides the creation date (line 2), description (line 3), 
-publisher (line 4) and a title/label (lines 5 &amp; 6) for the Semantic Asset.
-The status of the Semantic Asset is given in line 7 using one of the values made available in the original ADMS
-specification [[ADMS1]]. Likewise the type of Semantic Asset in line 8. In line 9 we can see that there was a previous 
-version of this asset (Fruit_01) and that the latest version can be found by appending 'Fruit' to the data's root (line 10).</p>
+publisher (line 4) and a title (line 5) for the Semantic Asset.
+The status of the Semantic Asset is given in line 6 using one of the values made available in the original ADMS
+specification [[ADMS1]]. Likewise the type of Semantic Asset in line 7. In line 8 we can see that there was a previous 
+version of this asset (Fruit_01) and that the latest version can be found by appending 'Fruit' to the data's root (line 9).</p>
 <p>This Semantic Asset has two distributions linked in lines 11 and 12. One of these might be described thus:</p>
 
-<pre>
+<pre id="sadEg">
 :Fruit_02.xml a adms:SemanticAssetDistribution ;
   dcterms:description "XML encoding of Fruits that are found to be generally liked by most people.";
   dcterms:license &lt;http://creativecommons.org/licenses/by/3.0/&gt; ;
@@ -270,37 +250,32 @@
 <h2 id="domainmodel">The ADMS Domain Model</h2>
 
 <figure id="uml">
-  <img src="ADMS_20120725.png" width="1392" height="816" alt="UML Diagram of ADMS" />
-  <figcaption>UML model of ADMS classes and properties with references to the RADion vocabulary which it subclasses</figcaption>
+  <img src="adms20130404.png" width="875" height="574" alt="UML Diagram of ADMS" />
+  <figcaption>UML model of ADMS classes and properties</figcaption>
 </figure>
 
 <p>The classes and properties are described briefly in the following sub-sections</p>
 <section>
 <h3 id="primary">The Primary Concepts</h3>
-<p class="editorsnote">The following shows RDF encodings. Add XML ones in due course</p>
-<p>The primary ADMS concepts are detailed below.</p>
 <dl>
-  <dt id="pc_semanticAssetRepository">Semantic Asset Repository</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>adms:SemanticAssetRepository</code></p>
-  <p>A system or service that provides facilities for storage and maintenance of 
+  <dt id="pc_semanticAssetRepository">Semantic Asset Repository <code class="rdfEncoding">adms:SemanticAssetRepository</code></dt>
+  <dd><p>A system or service that provides facilities for storage and maintenance of 
   descriptions of Semantic Assets and Semantic Asset Distributions, and 
   functionality that allows users to search and access these descriptions. A 
   Semantic Asset Repository will typically contain descriptions of several Semantic 
-  Assets and related Semantic Asset Distributions.</p></dd>
-  <dt id="pc_semanticAsset">Semantic Asset</dt>
-  <dd>
-  <p class="rdfEncoding">RDF encoding: <code>adms:SemanticAsset</code></p>
-  <p>An abstract entity that reflects the intellectual content of the asset and 
+  Assets and related Semantic Asset Distributions.</p>
+  <p><code>adms:SemanticAssetRepository</code> is a sub class od <code>dcat:Catalog</code></p></dd>
+  <dt id="pc_semanticAsset">Semantic Asset <code class="rdfEncoding">adms:SemanticAsset</code></dt>
+  <dd><p>An abstract entity that reflects the intellectual content of the asset and 
   represents those characteristics of the asset that are independent of its physical 
   embodiment. This abstract entity combines the FRBR entities <em>work</em> (a distinct 
   intellectual or artistic creation) and <em>expression</em> (the intellectual or artistic realization of a work) [[FRBR]].
   <p>Assets can be versioned. Every time the intellectual content of an asset changes, the result is considered to 
   be a new asset that can be linked to previous and next versions of the Asset.</p>
-  <p>The physical embodiment of an Asset is called a Distribution. A particular Asset may have zero or more Distributions.</p></dd>
-  <dt id="pc_semanticAssetDistribution">Semantic Asset Distribution</dt>
-  <dd>
-  <p class="rdfEncoding">RDF encoding: <code>adms:SemanticAssetDistribution</code></p>
-<p>A particular physical embodiment of a Semantic Asset, which is an example of 
+  <p>The physical embodiment of an Asset is called a Distribution. A particular Asset may have zero or more Distributions.</p>
+  <p><code>adms:SemanticAsset</code> is a sub class of <code>dcat:Dataset</code></p></dd>
+  <dt id="pc_semanticAssetDistribution">Semantic Asset Distribution <code class="rdfEncoding">adms:SemanticAssetDistribution</code></dt>
+  <dd><p>A particular physical embodiment of a Semantic Asset, which is an example of 
   the FRBR <em>entity manifestation</em> (the physical embodiment of an expression of a work).</p> 
   <p>A Distribution is typically a downloadable computer file (but in principle it 
   could also be a paper document or API response) that implements the intellectual content of an Asset.</p>
@@ -314,6 +289,7 @@
     <img src="asset-distribution.png" width="535" height="161" alt="Diagram showing that Assets are versioned, Distributions are not" />
     <figcaption>The relationship between versioned Semantic Assets and their Distributions</figcaption>
   </figure>
+  <p><code>adms:SemanticAssetDistribution</code> is a sub class of <code>dcat:Distribution</code></p>
   </dd>
 </dl>
 <p>Examples of the relationship between Assets and Distributions are:</p>
@@ -340,352 +316,507 @@
 
 <p>In addition to the primary concepts, ADMS includes a number of secondary or supporting concepts:</p>
 <dl>
-  <dt id="sec_assetType">Asset Type</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>skos:Concept</code></p>
-  <p>The classification of an Asset according to a controlled vocabulary, e.g. code list, metadata schema.</p></dd>
-  <dt id="sec_contactInformation">Contact Information</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>VCard</code></p><p>A contact point for further information about an Asset.</p></dd>
-  <dt id="sec_documentation">Documentation</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>foaf:Document</code><p>Any document that further describes an Asset or gives guidelines for its use.</p></dd>
-  <dt id="sec_fileFormat">File Format</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>dcterms:FileFormat</code></p><p>The technical format in which a Distribution is available , e.g. <abbr title="Portable Document Format">PDF</abbr>, <abbr title="XML Schema Definition">XSD</abbr> etc. See also <a href="#sec_representationTechnique">representation technique</a>.</p></dd>
-  <dt id="sec_geographicalCoverage">Geographical Coverage</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>dcterms:Location</code></p><p>The country or region to which an Asset or Repository applies.</p></dd>
-  <dt id="sec_item">Item</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>adms:Item</code></p><p>An item that is contained inside an Asset, e.g. an individual term in a vocabulary, an individual code in a code list or some other ‘atomic’ element of an Asset.</p></dd>
-  <dt id="sec_interoperabilityLevel">Interoperability Level</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>skoa:Concept</code></p><p>A level as defined in a list such the European Interoperability Framework [[EIF2]] for which an Asset is relevant.</p></dd>
-  <dt id="sec_language">Language</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>dcterms:LinguisticSystem</code></p><p>The language of an Asset if its contains textual information, e.g. the language of the terms in a controlled vocabulary or the language in which a specification is written.</p></dd>
-  <dt id="sec_license">License</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>dcterms:LicenseDocument</code></p><p>The conditions or restrictions that apply to the use of a Distribution, e.g. whether it is in the 
-  public domain, or that some restrictions apply such as attribution being required, or that it can only be used for non-commercial purposes etc.</p></dd>
-  <dt id="sec_periodOfTime">Period of time</dt>
-  <dd><p class="rdfEncoding">RDF encoding <code>dcterms:PeriodOfTime</code><p><p>The time period relevant for an Asset, e.g. for its validity</p></dd>
-  <dt id="sec_publisher">Publisher</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>dcterms:Agent</code></p><p>The organization making a Repository, Asset or Distribution available.</p></dd>
-  <dt id="sec_representationTechnique">Representation Technique</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>skos:Concept</code></p><p>The machine-readable language in which a Distribution is expressed. This is more fine-grained than <a href="#sec_fileFormat">file format</a>, for example "Word 2003".</p></dd>
-  <dt id="sec_status">Status</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>skos:Concept</code></p><p>An indication of the maturity of an Asset or Distribution</p></dd>
-  <dt id="sec_theme">Theme</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>skos:Concept</code></p><p>The sector that an Asset applies to, e.g. "law" or "environment". Best practice is to user terms from a controlled vocabulary.</p></dd>
-  <dt id="sec_themeTaxonomy">Theme Taxonomy</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>skos:ConceptScheme</code></p><p>A controlled vocabulary that contains terms that are used as Themes for the Assets in a Repository.</p></dd>
-</dl>
-<p>These supporting concepts are further described below.</p>
-</section> <!-- Secondary Concepts -->
+  <dt id="sec_assetType">Asset Type <code class="rdfEncoding">skos:Concept</code></dt>
+  <dd><p>The classification of an Asset according to a controlled vocabulary, e.g. code list, metadata schema.</p></dd>
+  <dt id="sec_contactInformation">Contact Information <code class="rdfEncoding">v:VCard</code></dt>
+  <dd><p>A contact point for further information about an Asset.</p></dd>
+  <dt id="sec_documentation">Documentation <code class="rdfEncoding">foaf:Document</code></dt>
+  <dd><p>Any document that further describes an Asset or gives guidelines for its use.</p></dd>
+  <dt id="sec_fileFormat">File Format <code class="rdfEncoding">dcterms:FileFormat</code></dt>
+  <dd><p>The technical format in which a Distribution is available , e.g. <abbr title="Portable Document Format">PDF</abbr>, <abbr title="XML Schema Definition">XSD</abbr> etc. See also <a href="#sec_representationTechnique">representation technique</a>.</p></dd>
+  <dt id="sec_geographicalCoverage">Geographical Coverage <code class="rdfEncoding">dcterms:Location</code></dt>
+  <dd><p>The country or region to which an Asset or Repository applies.</p></dd>
 
-
-<section>
-<h2 id="Encoding_of_property_values">Encoding of property values</h2>
-<ul><li>Values like "unknown" or "unspecified" should never be used, and if present in the original 
-data should be filtered for publishing. Instead, the property should simply be omitted.
-</li><li> @@@ policy for using resources vs. literals</li>
-</ul>
-<p class="editorsnote">This is copied from DCAT &amp; seems sensible</p>
-</section> <!-- Encoding of property values -->
-
-<section><h2 id="dataTypes">Data Types</h2>
-<p>ADMS makes use of the following data types.</p>
-<dl>
-  <dt id="dt_code">Code</dt>
-  <dd>
-  <p>Complex type (based on UN/CEFACT Code. [[UNCEFACT]] ) consisting of:</p><ul>
-    <li>a content string which is the code (data type string);</li>
-    <li>an optional identifier for the code list (data type string);</li>
-    <li>an optional identifier for the agency that manages the code list (data type string);</li>
-    <li>an optional identifier for the version of the code list (data type string).</li></ul>
-
-  <p>In RDF, this is expressed using the  <a href="http://www.w3.org/TR/skos-primer/">SKOS vocabulary</a>
-  with a particular 'code' being a <code>skos:Concept</code> that is part of a <code>skos:ConceptScheme</code>. 
-  The intention is that SKOS be used as follows:</p>
-  <ul>
-    <li>for the content property, use <code>skos:notation</code> (best practice is to provide a datatype for the string value of this property);</li>
-    <li>the 'list' property will be taken care of by means of the <code>skos:inScheme</code> property;</li>
-    <li>the list agency property is likely to be applied to the scheme as a whole for which <code>dcterms:creator</code> is appropriate;</li>
-    <li>the list version property should also be applied to the schema as a whole and can be 
-        fulfilled using <code>schema:version</code> (see <a href="http://schema.org/CreativeWork">http://schema.org/CreativeWork</a>)</li>
-  </ul></dd>
-  <dt id="dt_dateTime">DateTime</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>xsd:date, xsd:dateTime, xsd:gYear etc.</code></p><p>String conforming to ISO8601 [[ISO8601]]</p></dd>
-  <dt id="dt_identifier">Identifier</dt>
-  <dd>
-    <p>Complex type (based on UN/CEFACT Identifier. [[UNCEFACT]]) consisting of:<ul>
+  <dt id="dt_identifier">Identifier <code class="rdfEncoding">adms:Identifier</code></dt>
+  <dd><p>This is based on the UN/CEFACT Identifier class. [[UNCEFACT]]) which consists of:</p><ul>
     <li>a content string which is the identifier;</li>
     <li>an optional identifier for the identifier scheme;</li>
     <li>an optional identifier for the version of the identifier scheme;</li>
     <li>an optional identifier for the agency that manages the identifier scheme.</li></ul>
 
-  <p>In RDF this is expressed using the <code>adms:Identifier</code> class with the following properties:</p><ul>
+  <p>In ADMS this is expressed using the <code>adms:Identifier</code> class with the following properties:</p><ul>
     <li>the content string should be provided using <code>skos:notation</code>, datatyped with 
         the identifier scheme (inclduing the version number if appropriate);</li>
-    <li>use <code>dcterms:creator</code> to link to a class describing the agency that manages the identifier scheme or
-        <code>adms:schemaAgency</code> to provide the name as a literal.</li></ul>
-    <p>Although not part of the ADMS conceptual model, it may be useful to provide further properties to the Identifier class
-    such as <code>dcterms:created</code> to provide the date on which the identifier was issued.</p>
-    <p>An important point to note is that properties of the <code>adms:Identifier</code> class are properties of the
+    <li>use <code>dcterms:creator</code> to link to a class that represents the agency that manages the identifier scheme and/or
+        <code>adms:schemaAgency</code> to provide the name of the agency as a literal;</li>
+    <li>it may also be useful to provide further properties such as <code>dcterms:issued</code> to provide the 
+        date on which the identifier was issued.</li></ul>
+    <p>An important point to note is that properties of <code>adms:Identifier</code> are properties of the
     Identifier, not the resource that it identifies or the agency that issued it.</p></dd>
-  <dt id="dt_string">String</dt>
-  <dd>A string of UNICODE characters</dd>
-  <dt id="dt_text">Text</dt>
-  <dd><p class="rdfEncoding">RDF encoding: <code>rdfs:Literal</code></p>
-    <p>Complex type consisting of:<ul>
-    <li>a content string;</li>
-    <li>an optional language code from RFC 5646 [[RFC5646]].</li></ul></dd>
-  <dt id="dt_uri">URI</dt>
-  <dd>String conforming to RFC 3986 [[!RFC3986]]</dd>
+
+  <dt id="sec_item">Item <code class="rdfEncoding">adms:Item</code></dt>
+  <dd><p>An item that is contained inside an Asset, e.g. an individual term in a vocabulary, an individual code in a code list or some other ‘atomic’ element of an Asset.</p></dd>
+  <dt id="sec_interoperabilityLevel">Interoperability Level <code class="rdfEncoding">skos:Concept</code></dt>
+  <dd><p>A level as defined in a list such the European Interoperability Framework [[EIF2]] for which an Asset is relevant.</p></dd>
+  <dt id="sec_language">Language <code class="rdfEncoding">dcterms:LinguisticSystem</code></dt>
+  <dd><p>The language of an Asset if its contains textual information, e.g. the language of the terms in a controlled vocabulary or the language in which a specification is written.</p></dd>
+  <dt id="sec_license">License <code class="rdfEncoding">dcterms:LicenseDocument</code></dt>
+  <dd><p>The conditions or restrictions that apply to the use of a Distribution, e.g. whether it is in the 
+  public domain, or that some restrictions apply such as attribution being required, or that it can only be used for non-commercial purposes etc.</p></dd>
+  <dt id="sec_periodOfTime">Period of time <code class="rdfEncoding">dcterms:PeriodOfTime</code></dt>
+  <dd><p>The time period relevant for an Asset, e.g. for its validity</p></dd>
+  <dt id="sec_publisher">Publisher <code class="rdfEncoding">dcterms:Agent</code></dt>
+  <dd><p>The organization making a Repository, Asset or Distribution available.</p></dd>
+  <dt id="sec_representationTechnique">Representation Technique <code class="rdfEncoding">skos:Concept</code></dt>
+  <dd><p>The machine-readable language in which a Distribution is expressed. This is more fine-grained than <a href="#sec_fileFormat">file format</a>, for example "Word 2003".</p>
+      <p>This concept indicates that one of the files in a Semantic Asset Distribution is expressed in the Representation Technique. 
+         There may also be other files in the Distribution that are expressed in other Representation Techniques or even files 
+          that are not representations at all.</p></dd>
+  <dt id="sec_status">Status <code class="rdfEncoding">skos:Concept</code></dt>
+  <dd><p>An indication of the maturity of an Asset or Distribution</p></dd>
+  <dt id="sec_theme">Theme <code class="rdfEncoding">skos:Concept</code></dt>
+  <dd><p>The sector that an Asset applies to, e.g. "law" or "environment". Best practice is to user terms from a controlled vocabulary.</p></dd>
+  <dt id="sec_themeTaxonomy">Theme Taxonomy <code class="rdfEncoding">skos:ConceptScheme</code></dt>
+  <dd><p>A controlled vocabulary that contains terms that are used as Themes for the Assets in a Repository.</p></dd>
 </dl>
-</section> <!-- Data Types -->
-
-<section><h2 id="propertiesAndRelationships">Properties and Relationships</h2>
-<p>In the following sub-sections, we set out the properties and 
-relationships of each of the primary and secondary concepts.</p>
+</section> <!-- Secondary Concepts -->
 
 
-<section><h3 id="pr_semanticAsset">Concept: Semantic Asset</h3>
-
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>alternative name</td><td><span>alternative name for the Asset.</span>
-    <p>Note: this information may be used to provide additional access points, e.g. allowing indexing of any acronyms, nicknames, shorthand notations or other identifying information under which a user might expect to find the Asset</p></td>
-  	<td><a href="#dt_text">text</a></td>
-    <td><code>dcterms:alternative</code></td>
-  </tr>
-  <tr><td>date of creation</td><td><span>creation date of this version of the Asset</span></td><td><a href="#dt_dateTime">dateTime</a></td><td><code>dcterms:created</code></td></tr>
-  <tr><td>date of last modification</td><td><span>date of latest update of Asset</span></td><td><a href="#dt_dateTime">dateTime</a></td><td><code>edterms:modified</code></td></tr>
-  <tr><td>description</td><td><span>descriptive text for the Asset</span></td><td><a href="#dt_text">text</a></td><td><code>dcterms:description</code></td></tr>
-  <tr><td>id</td><td><span>URI for the Asset</span></td><td><a href="#dt_uri">URI</a></td><td>Not applicable in RDF where the id is the URI of the node</tr>
-  <tr><td>identifier</td><td><span>any identifier for the Asset</span></td><td><a href="#dt_identifier">identifier</a></td><td><code>dcterms:identifier</code></td></tr>
-  <tr><td>keyword</td><td><span>word of phrase to describe the Asset</span></td><td><a href="#dt_text">text</a></td><td><code>radion:keyword</code></td></tr>
-  <tr><td>metadata date</td><td><span>date of the most recent update of the metadata for the Asset</span></td><td><a href="#dt_dateTime">dateTime</a></td><td><code>adms:metadataDate</code></td></tr>
-  <tr><td>name</td><td><span>name of the Asset.</span>
-    <p>Note: in cases that an Asset has parallel names, for example if more than one official name exists, or if an organization or country has more than one official language, this field can be repeated for all name variants</p></td><td><a href="#dt_text">text</a></td><td><code>rdfs:label</code></td></tr>
-  <tr><td>version</td><td><span>version number or other designation of the Asset</span></td><td><a href="#dt_text">text</a></td><td><code>radion:version</code></td></tr>
-  <tr><td>version notes</td><td><span>description of changes between this version and the previous version of the Asset</span></td><td><a href="#dt_text">text</a></td><td><code>radion:versionNotes</code></td></tr>
-
-  <tr class="midtable"><th>Relationship</th><th>Description</th><th>Target</th><th>RDF encoding</th></tr>
-  <tr><td>asset type</td><td><span>type of the Asset</span></td><td><a href="#pr_assetType">Asset Type</a></td><td><code>dcterms:type</code></td></tr>
-  <tr><td>contact point</td><td><span>contact point for further information about an Asset</span></td><td><a href="#pr_contactInformation">Contact Information</a></td><td><code>adms:contactpoint</code></td></tr>
-  <tr><td>current version</td><td><span>current or latest version of the Asset</span></td><td><a href="#pr_semanticAsset">Semantic Asset</a></td><td><code>xhv:last</code></td></tr>
-  <tr><td>home page</td><td><span>a Web page that is fully dedicated to the Asset</span></td><td><a href="#pr_documentation">Documentation</a></td><td><code>foaf:homepage</code></td></tr>
-  <tr><td>included asset</td><td><span>an Asset that is contained in the Asset being described, e.g. when there are several vocabularies defined in a single document</span></td><td><a href="#pr_semanticAsset">Semantic Asset</a></td><td><code>adms:includedAsset</code></td></tr>
-  <tr><td>included item</td><td><span>item that is contained in the Asset (e.g. a concept in a controlled vocabulary, an individual code in a code list or any other ‘atomic’ element)</span></td><td><a href="#pr_item">Item</a></td><td><code>adms:includedItem</code></td></tr>
-  <tr><td>interoperability level</td><td><span>interoperability level for which the Asset is relevant</span></td><td><a href="#pr_interoperabilityLevel">Interoperability Level</a></td><td><code>adms:interoperabilityLevel</code></td></tr>
-  <tr><td>language</td><td><span>language of the Asset</span></td><td><a href="#pr_language">Language</a></td><td><code>dcterms:language</code></td></tr>
-  <tr><td>main documentation</td><td><span>the main documentation or specification of the Asset</span></td><td><a href="#pr_documentation">Documentation</a></td><td><code>wdrs:describedby</code></td></tr>
-  <tr><td>metadata language</td><td><span>language of the metadata for the Asset</span></td><td><a href="#pr_language">Language</a></td><td><code>adms:metadataLanguage</code></td></tr>
-  <tr><td>metadata publisher</td><td><span>organization making the metadata for the Asset available</span></td><td><a href="#pr_publisher">Publisher</a></td><td><code>adms:metadataPublisher</code></td></tr>
-  <tr><td>next version</td><td><span>newer version of the Asset</span></td><td><a href="#pr_semanticAsset">Semantic Asset</a></td><td><code>xhv:next</code></td></tr>
-  <tr><td>previous version</td><td><span>older version of the Asset</span></td><td><a href="#pr_semanticAsset">Semantic Asset</a></td><td><code>xhv:prev</code></td></tr>
-  <tr><td>publisher</td><td><span>organization making the Asset available</span></td><td><a href="#pr_publisher">Publisher</a></td><td><code>dcterms:publisher</code></td></tr>
-  <tr><td>related asset</td><td><span>unspecified relationship from the Asset to another Asset</span></td><td><a href="#pr_semanticAsset">Semantic Asset</a></td><td><code>dcterms:relation</code></td></tr>
-  <tr><td>related documentation</td><td><span>documentation that contains information related to the asset</span></td><td><a href="#pr_documentation">Documentation</a></td><td><code>adms:relatedDocumentation</code></td></tr>
-  <tr><td>related web page</td><td><span>a Web page that contains information related to the asset</span></td><td><a href="#pr_documentation">Documentation</a></td><td><code>adms:relatedWebPage</code></td></tr>
-  <tr><td>distribution</td><td><span>implementation of the Asset in a particular format</span></td><td><a href="#pr_semanticAssetDistribution">Semantic Asset Distribution</a></td><td><code>radion:distribution</code></td></tr>
-  <tr><td>repository origin</td><td><span>Repository that contains the primary description of the Asset</span></td><td><a href="#pr_semanticAssetRepository">Semantic Asset Repository</a></td><td><code>dcterms:isPartOf</code></td></tr>
-  <tr><td>sample</td><td><span>sample of the Asset</span></td><td><a href="#pr_semanticAsset">Semantic Asset</a></td><td><code>adms:sample</code></td></tr>
-  <tr><td>spatial coverage</td><td><span>geographic region or jurisdiction to which the Asset applies</span></td><td><a href="#pr_geographicCoverage">Geographic Coverage</a></td><td><code>dcterms:spatial</code></td></tr>
-  <tr><td>status</td><td><span>status of the Asset in the context of a particular workflow process</span></td><td><a href="#pr_status">Status</a></td><td><code>adms:status</code></td></tr>
-  <tr><td>temporal coverage</td><td><span>time period relevant to the Asset, e.g. its validity</span></td><td><a href="#pr_periodOfTime">Period of Time</a></td><td><code>dcterms:temporal</code></td></tr>
-  <tr><td>theme</td><td><span>theme or sector to which the Asset applies</span></td><td><a href="#pr_theme">Theme</a></td><td><code>dcterms:subject</code></td></tr>
-  <tr><td>translation</td><td><span>translation of the Asset</span></td><td><a href="#pr_semanticAsset">Semantic Asset</a></td><td><code>adms:translation</code></td></tr>
-
-</table>
-
-</section> <!-- Semantic Asset -->
-
-<section><h3 id="pr_semanticAssetDistribution">Concept: Semantic Asset Distribution</h3>
-
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>access URL</td><td><span>URL of the Distribution</span>
-    <p>Note: more than one URL may be available, for example if mirror sites are maintained.</p></td><td><a href="#dt_uri">URI</a> (with the added restriction that it is also a URL)</td><td><code>adms:accessURL</code></td></tr>
-  <tr><td>date of creation</td><td><span>creation date of the Distribution</span></td><td><a href="#dt_dateTime">dateTime</a></td><td><code>dcterms:created</code></td></tr>
-  <tr><td>date of last modification</td><td><span>date of latest update of the Distribution</span></td><td><a href="#dt_dateTime">dateTime</a></td><td><code>dcterms:modified</code></td></tr>
-  <tr><td>description</td><td><span>descriptive text for the Distribution</span></td><td><a href="#dt_text">text</a></td><td><code>dcterms:description</code></td></tr>
-  <tr><td>id</td><td><span>URI for the Distribution</span></td><td><a href="#dt_uri">URI</a></td><td>Not applicable in RDF where the id is the URI of the node</td></tr>
-  <tr><td>name</td><td><span>name of the Distribution</span></td><td><a href="#dt_text">text</a></td><td><code>rdfs:label</code></td></tr>
-  <tr class="midtable"><th>Relationship</th><th>Description</th><th>Target</th><th>RDF encoding</th></tr>
-  <tr><td>format</td><td><span>format in which the Distribution is available (e.g. PDF, XSD, RDF/XML, HTML, ZIP)</span></td><td><a href="#pr_fileFormat">File Format</a></td><td><code>dcterms:format</code></td></tr>
-  <tr><td>license</td><td><span>conditions or restrictions for (re-)use of the Distribution.</span>
-      <p>Note: if multiple licenses are given, these licenses apply to all files in the Distribution</p></td><td><a href="#pr_license">License</a></td><td><code>dcterms:license</code></td></tr>
-  <tr><td>distribution of</td><td><span>the Asset that this Distribution embodies. This is the reverse relationship of distribution</span></td><td><a href="#pr_semanticAsset">Semantic Asset</a></td><td><code>radion:distribution</code></td></tr>
-  <tr><td>publisher</td><td><span>organization making the Distribution available</span></td><td><a href="#pr_publisher">Publisher</a></td><td><code>dcterms:publisher</code></td></tr>
-  <tr><td>representation technique</td><td><span>language in which the Distribution is expressed</span>
-      <p>Note: this is different from the file format, e.g. a ZIP file (file format) could contain an XML schema (representation technique)</td><td><a href="#pr_representationTechnique">Representation Technique</a></td><td><code>adms:representationTechnique</code></td></tr>
-  <tr><td>status</td><td><span>status of the Distribution in the context of a particular workflow process</span></td><td><a href="#pr_status">Status</a></td><td><code>adms:status</code></td></tr>
-</table>
-
-</section> <!-- Semantic Asset Distribution -->
-
-<section><h3 id="pr_semanticAssetRepository">Concept: Semantic Asset Repository</h3>
-
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>access URL</td><td><span>URL of the Repository</span></td><td><a href="#dt_uri">URI</a> (with the added restriction that it is also a URL)</td><td><code>adms:accessURL</code></td></tr>
-  <tr><td>date of creation</td><td><span>creation date of the Repository</span></td><td><a href="#dt_dateTime">dateTime</a></td><td><code>dcterms:creation</code></td></tr>
-  <tr><td>date of last modification</td><td><span>date of latest update of the Repository</span></td><td><a href="#dt_dateTime">dateTime</a></td><td><code>dcterms:modified</code></td></tr>
-  <tr><td>description</td><td><span>descriptive text for the Repository</span></td><td><a href="#dt_text">text</a></td><td><code>dcterms:description</code></td></tr>
-  <tr><td>id</td><td><span>URI for the Repository</span></td><td><a href="#dt_uri">URI</a></td><td>Not applicable in RDF where the id is the IRI of the node</td></tr>
-  <tr><td>name</td><td><span>name of the Repository</span>
-        <p>Note: in cases that a Repository has parallel names, for example if more than one official name exists, or if an organization or country has more than one official language, this field can be repeated for all name variants</td><td><a href="#dt_text">text</a></td><td><code>rdfs:label</code></td></tr>
-  <tr><td>supported schema</td><td><span>Schema according to which the Repository can provide data, e.g. ADMS version 1.0</span></td><td><a href="#dt_text">text</a></td><td><code>adms:supportedSchema</code></td></tr>
-  <tr class="midtable"><th>Relationship</th><th>Description</th><th>Target</th><th>RDF encoding</th></tr>
-  <tr><td>includes</td><td><span>an Asset for which a description is included in the Repository. This is the reverse relationship of repository origin</span></td><td><a href="#pr_semanticAsset">Semantic Asset</a></td><td><code>dcterms:hasPart</code></td></tr>
-  <tr><td>publisher</td><td><span>organization making the Repository available</span></td><td><a href="#pr_publisher">Publisher</a></td><td><code>dcterms:publisher</code></td></tr>
-  <tr><td>spatial coverage</td><td><span>geographic region or jurisdiction to which the Repository applies</span></td><td><a href="#pr_geographicCoverage">Geographic Coverage</a></td><td><code>dcterms:spatial</code></td></tr>
-  <tr><td>theme</td><td><span>theme or sector to which the Repository applies</span></td><td><a href="#pr_theme">Theme</a></td><td><code>dcterms:subject</code></td></tr>
-  <tr><td>theme taxonomy</td><td><span>taxonomy that contains terms for Themes that are used for the Assets in a Repository</span></td><td><a href="#pr_themeTaxonomy">Theme Taxonomy</a></td><td><code>dcterms:subject</code></td></tr>
-</table>
-</section> <!-- Semantic Assert Repository -->
-
-<section><h3 id="pr_supportingConcepts">Supporting Concepts</h3>
-
-<section><h4 id="pr_assetType">Concept: Asset Type</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>code</td><td><span>The type of asset. Best practice is to use a value from a list of controlled terms</span></td><td><a href="#dt_code">code</a></td><td><code>skos:notation</code></td></tr>
-  <tr><td>id</td><td><span>URI identifying the Asset Type</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
-</table>
-</section> <!-- Asset type -->
-
-<section><h4 id="pr_contactInformation">Concept: Contact Information</h4>
-<p>Note: The attributes of this concept can be implemented using vCard [[RFC2426]] </p>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>full address</td><td><span>The complete address written as a string, with or without formatting.</span></td><td><a href="#dt_string">String</a></td><td><code>v:label</code></td></tr>
-  <tr><td>e-mail</td><td><span>An e-mail address for questions and feedback</span></td><td><a href="#dt_string">String</a></td><td><code>v:email</code></td></tr>
-  <tr><td>id</td><td><span>URI identifying the Contact Information</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
-  <tr><td>name</td><td><span>A name of the contact point, e.g. organization or department name, function name or name of a person</span></td><td><a href="#dt_string">String</a></td><td><code>v:fn</code></td></tr>
-  <tr><td>telephone</td><td><span>A telephone number for questions and feedback</span></td><td><a href="#dt_string">String</a></td><td><code>v:tel</code></td></tr>
-  <tr><td>web page</td><td><span>A Web page where contact information is shown, or a Web form where questions and feedback can be entered</span></td><td><a href="#dt_uri">URI</a> (with the added restriction that it is also a URL)</td><td><code>foaf:homepage</code></td></tr>
-</table>
-</section> <!-- Contact Information -->
+<section><h2 id="propertiesAndRelationships">Properties and Relationships</h2>
+<p>In the following sub-sections, we set out the properties and relationships 
+(object type properties) used in ADMS. These are listed in alphabetical order, irrespective of namespace.</p>
 
 
-<section><h4 id="pr_documentation">Concept: Documentation</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>id</td><td><span>URI identifying the Documentation, or the URL where it can be accessed</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
-  <tr><td>title</td><td><span>Title of the Documentation</span></td><td><a href="#dt_text">text</a></td><td><code>rdfs:label</code></td></tr>
+<section>
+<h3 id="dcat_accessURL">dcat:accessURL</h3>
+<p>Any kind of URL that gives access to a Semantic Asset Distribution, e.g. a landing page, download, feed URL, SPARQL endpoint etc. 
+Use dcat:accessURL when you do not have information on which it is or when it is definitely not a download.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/dcat#accessURL">dcat:accessURL</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>.</td></tr>
+    <tr><td class="prop">Usage note</td><td><ul>
+      <li>the value is a URL.</li>
+      <li>If the distribution(s) are accessible only through a landing page (i.e. direct download URLs are not known), then the landing page link 
+        <em title="should" class="rfc2119">should</em> be duplicated as accessURL on a distribution (see also <a href="#dcat_landingPage">dcat:landingPage</a>).</li>
+      </ul></td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="skos_altLabel">skos:altLabel</h3>
+<p>An alternative name for the Semantic Asset.</p>
+<table class="definition">
+  <thead><tr><th>Datatype Property:</th><th><a href="http://www.w3.org/2004/02/skos/core#altLabel">skos:altLabel</a></th></tr></thead>
+  <tbody><tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr></tbody>
 </table>
 </section>
 
-<section><h4 id="pr_fileFormat">Concept: File Format</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>code</td><td><span>The format of the file. Best practice is to use a value from a list of controlled terms.</span></td><td><a href="#dt_code">code</a></td><td><code>skos:notation</code></td></tr>
-  <tr><td>id</td><td><span>URI identifying the File Format</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
+<section>
+<h3 id="adms_contactPoint">adms:contactPoint</h3>
+<p>A contact point for further information about a Semantic Asset.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/adms#contactPoint">adms:contactPoint</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2006/vcard/ns#">v:VCard</a></td></tr>
+  </tbody>
 </table>
 </section>
 
-<section><h4 id="pr_geographicCoverage">Concept: Geographic Coverage</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>description</td><td><span>Descriptive text for the Geographic Coverage</span></td><td><a href="#dt_text">text</a></td><td><code>dcterms:description</code></td></tr>
-  <tr><td>id</td><td><span>URI identifying the Geographic Coverage</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
-  <tr><td>label</td><td><span>A short phrase describing the Geographic Coverage</span></td><td><a href="#dt_text">text</a></td><td><code>rdfs:label</code></td></tr>
+<section>
+<h3 id="wdrs_describedby">wdrs:describedby</h3>
+<p>The main documentation or specification of the Semantic Asset</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/2007/05/powder-s#describedby">wdrs:describedby</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr>
+    <tr><td class="prop">Usage note></td><td>See also <a href="#dcat_landingPage">dcat:landingPage</a>, <a href="#adms_relatedDocumentation">adms:relatedDocumentation</a>, <a href="#adms_relatedWebPage">adms:relatedWebPage</a> </td></tr>
+  </tbody>
 </table>
 </section>
 
 
-<section><h4 id="pr_item">Concept: Item</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>description</td><td><span>Descriptive text for the Item</span></td><td><a href="#dt_text">text</a></td><td><code>dcterms:description</code></td></tr>
-  <tr><td>id</td><td><span>URI identifying the Item</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
-  <tr><td>label</td><td><span>A short phrase describing the Item</span></td><td><a href="#dt_text">text</a></td><td><code>rdfs:label</code></td></tr>
+<section>
+<h3 id="dcterms_description">dcterms:description</h3>
+<p>A description of the Semantic Asset, Semantic Asset Repository or Semantic Distribution.</p>
+<table class="definition">
+  <thead><tr><th>Datatype Property:</th><th><a href="http://purl.org/dc/terms/description">dcterms:description</a></th></tr></thead>
+  <tbody><tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr></tbody>
+</table>
+</section>
+<section>
+<h3 id="adms_distribution">adms:distribution</h3>
+<p>Links a Semantic Asset to an implementation in a particular format.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/adms#distribution">adms:distribution</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Sub property of:</td><td><a href="http://www.w3.org/ns/dcat#distribution">dcat:distribution</a></td></tr>
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/adms#SemanticAsset">adms:SemanticAsset</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/adms#SemanticAssetDistribution">adms:SemanticAssetDistribution</a></td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="dcat_downloadURL">dcat:downloadURL</h3>
+<p>This is a direct link from a Semantic Asset Distribution to a downloadable file in a given format, e.g. CSV file or RDF file. The format is described by the distribution's dcterms:format and/or dcat:mediaType.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/dcat#downloadURL">dcat:downloadURL</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>.</td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="dcterms_format">dcterms:format</h3>
+<p>The file format of the distribution.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://purl.org/dc/terms/format">dcterms:format</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range</td><td><a href="http://purl.org/dc/terms/MediaTypeOrExtent">dcterms:MediaTypeOrExtent</a>.</td></tr>
+    <tr><td class="prop">Usage note:</td><td><a href="#dcat_mediaType">dcat:mediaType</a> should be used if the type of the distribution is defined by <a href="http://www.iana.org/assignments/media-types/">IANA</a>.
+    Suitable values for <code>dcterms:format</code> include URIs as used in the <a href="#sadEg">example</a>. See also <a href="#adms_representationTechnique">adms:representationTechnique</a>.</td></tr>
+  </tbody>
+</table>
+</section>
+
+<section>
+<h3 id="adms_includedAsset">adms:includedAsset</h3>
+<p>A Semantic Asset that is contained in the Semantic Asset being described, e.g. when there are several vocabularies defined in a single document.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/adms#includedAsset">adms:includedAsset</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Domain:</td><td><a href="http://www.w3.org/ns/adms#SemanticAsset">adms:SemanticAsset</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/adms#SemanticAsset">adms:SemanticAsset</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+<section>
+<h3 id="adms_includedItem">adms:includedItem</h3>
+<p>An item that is contained in the Semantic Asset (e.g. a concept in a controlled vocabulary, an individual code in a code list or any other ‘atomic’ element).</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/adms#includedItem">adms:includedItem</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/adms#Item">adms:Item</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+<section>
+<h3 id="adms_interoperabilityLevel">adms:interoperabilityLevel</h3>
+<p>The interoperability level for which the Semantic Asset is relevant.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/adms#interoperabilityLevel">adms:interoperabilityLevel</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+<section>
+<h3 id="dcterms_isPartOf">dcterms:isPartOf</h3>
+<p>Used to link a Semantic Asset to a Semantic Asset Repository.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://purl.org/dc/terms/isPartOf">dcterms:isPartOf</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr>
+  </tbody>
 </table>
 </section>
 
 
-<section><h4 id="pr_interoperabilityLevel">Concept: Interoperability Level</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>code</td><td><span>A term describing the interoperability level. Best practice is to use a value from a list of controlled terms.</span></td><td><a href="#dt_code">code</a></td><td><code>skos:notation</code></td></tr>
-  <tr><td>id</td><td><span>URI identifying the Interoperability Level</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
-</table>
-</section>
+<section>
+<h3 id="dcterms_issued">dcterms:issued</h3>
 
-<section><h4 id="pr_language">Concept: Language</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>code</td><td><span>The language of the Semantic Asset. Best practice is to use a value from a list of controlled terms.</span></td><td><a href="#dt_code">code</a></td><td><code>skos:notation</code></td></tr>
-  <tr><td>id</td><td><span>URI identifying the Language</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
+<p>Date of formal issuance (e.g., publication) of the Semantic Asset, Semantic Asset Repository or Semantic Distribution.</p>
+<table class="definition">
+  <thead><tr><th>Datatype Property:</th><th><a href="http://purl.org/dc/terms/issued">dcterms:issued</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a> 
+    using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time</a> compliant string and
+    typed using the appropriate XML Schema datatype [[XMLSCHEMA-2]]</td></tr>
+  </tbody>
 </table>
 </section>
 
-<section><h4 id="pr_license">Concept: License</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>description</td><td><span>Descriptive text for the License</span></td><td><a href="#dt_text">text</a></td><td><code>dcterms:description</code></td></tr>
-  <tr><td>id</td><td><span>URI identifying the License, or the URL where the text of the license is available</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
-  <tr><td>name</td><td><span>A short phrase describing the License</span></td><td><a href="#dt_text">text</a></td><td><code>rdfs:label</code></td></tr>
-  <tr><td>type</td><td><span>Value from a list of controlled terms</span></td><td><a href="#dt_code">code</a></td><td><code>dcterms:type</code></td></tr>
+<section>
+<h3 id="dcat_keyword">dcat:keyword</h3>
+<p>A word, phrase or tag to describe the Semantic Asset.</p>
+<table class="definition">
+  <thead><tr><th>Datatype Property:</th><th><a href="http://www.w3.org/ns/dcat#keyword">dcat:keyword</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="dcat_landingPage">dcat:landingPage</h3>
+<p>A Web page that can be navigated to in a Web browser to gain access to the Semantic Asset, its distributions and/or additional information.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/dcat#landingPage">dcat:landingPage</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://xmlns.com/foaf/0.1/Document">foaf:Document</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td>If the Semantic Asset Distribution(s) are accessible only through a landing page (i.e. direct download URLs are not known), then the landing page link should be duplicated as accessURL on a distribution.</td></tr>
+  </tbody>
 </table>
 </section>
 
-<section><h4 id="pr_periodOfTime">Concept: Period of Time</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>id</td><td><span>URI identifying the Period Of Time</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
-  <tr><td>start</td><td><span>Beginning of the period</span></td><td><a href="#dt_dateTime">dateTime</a></td><td><code>schema:startDate</code></td></tr>
-  <tr><td>end</td><td><span>End of the period</span></td><td><a href="#dt_dateTime">dateTime</a></td><td><code>schema:endDate</code></td></tr>
+<section>
+<h3 id="dcterms_language">dcterms:language</h3>
+<p>The language of the Semantic Asset</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://purl.org/dc/terms/LinguisticSystem">dcterms:LinguisticSystem</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a><br/>
+    Resources defined by the Library of Congress (<a href="http://id.loc.gov/vocabulary/iso639-1.html">1</a>, <a href="http://id.loc.gov/vocabulary/iso639-2.html">2</a>) 
+    <em title="should" class="rfc2119">should</em> be used. <br/>
+   If an ISO 639-1 (two-letter) code is defined for language, then its corresponding IRI <em title="should" class="rfc2119">should</em>
+   be used; if no ISO 639-1 code is defined, then IRI corresponding to the ISO 639-2 (three-letter) code <em title="should" class="rfc2119">should</em>
+   be used.</td></tr>
+  </tbody>
 </table>
 </section>
 
-<section><h4 id="pr_publisher">Concept: Publisher</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>id</td><td><span>URI identifying the Publisher; if no URI is available, the URL of the organization’s home page may be used as an alternative</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
-  <tr><td>name</td><td><span>Name of the organization responsible for the Asset or Repository</span></td><td><a href="#dt_text">text</a></td><td><code>rdfs:label</code></td></tr>
-  <tr><td>type</td><td><span>Value from a list of controlled terms</span></td><td><a href="#dt_code">code</a></td><td><code>dcterms:type</code></td></tr>
+<section>
+<h3 id="xhv_last">xhv:last</h3>
+<p>A link to the current or latest version of the Semantic Asset.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/1999/xhtml/vocab#last">xhv:last</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+<section>
+<h3 id="dcterms_license">dcterms:license</h3>
+<p>Links to the conditions or restrictions for (re-)use of the Semantic Asset Distribution.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://purl.org/dc/terms/license">dcterms:license</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range</td><td><a href="http://purl.org/dc/terms/LicenseDocument">dcterms:LicenseDocument</a>.</td></tr>
+    <tr><td class="prop">Usage note:</td><td>If multiple licenses are given, these licenses apply to all files in the Semantic Asset Distribution.</td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="dcat_mediaType">dcat:mediaType</h3>
+<p>The media type of the distribution as defined by <a href="http://www.iana.org/assignments/media-types/">IANA</a>.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/dcat#mediaType">dcat:mediaType</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range</td><td><a href="http://purl.org/dc/terms/MediaTypeOrExtent">dcterms:MediaTypeOrExtent</a>.</td></tr>
+    <tr><td class="prop">Usage note:</td><td>This property <em title="should" class="rfc2119">should</em>  be used when the media type of the distribution is defined in 
+      <a href="http://www.iana.org/assignments/media-types/">IANA</a>, e.g. <code>text/csv</code> otherwise <a href="#dcterms_format">dcterms:format</a> <em title="may" class="rfc2119">may</em>  be used with different values.
+       See also <a href="#adms_representationTechnique">adms:representationTechnique</a>.</td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="dcterms_modified">dcterms:modified</h3>
+<p>Date of the latest update of the Semantic Asset, Semantic Asset Repository or Semantic Distribution.</p>
+<table class="definition">
+  <thead><tr><th>Datatype Property:</th><th><a href="http://purl.org/dc/terms/modified">dcterms:modified</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a> 
+    using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time</a> compliant string and
+    typed using the appropriate XML Schema datatype [[XMLSCHEMA-2]]</td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="xhv_next">xhv:next</h3>
+<p>A link to the next version of the Semantic Asset.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/1999/xhtml/vocab#next">xhv:next</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="xhv_prev">xhv:prev</h3>
+<p>A link to the previous version of the Semantic Asset.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/1999/xhtml/vocab#prev">xhv:prev</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+<section>
+<h3 id="dcterms_publisher">dcterms:publisher</h3>
+<p>Links a Semantic Asset, Semantic Asset Repository or Seamntic Asset Distribution to the publishing foaf:Agent.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://purl.org/dc/terms/publisher">dcterms:publisher</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="adms_relatedDocumentation">adms:relatedDocumentation</h3>
+<p>Links to documentation that contains information related to the Semantic Asset.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/adms#relatedDocumentation">adms:relatedDocumentation</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://xmlns.com/foaf/0.1/Document">foaf:Document</a></td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="adms_relatedWebPage">adms:relatedWebPage</h3>
+<p>Links to a Web page that contains information related to the Semantic Asset.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/adms#relatedWebPage">adms:relatedWebPage</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://xmlns.com/foaf/0.1/Document">foaf:Document</a></td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="dcterms_relation">dcterms:relation</h3>
+<p>A link between two Semantic Assets that are related in some (unspecified) way.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://purl.org/dc/terms/relation">dcterms:relation</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>.</td></tr>
+  </tbody>
+</table>
+</section>
+
+<section>
+<h3 id="adms_representationTechnique">adms:representationTechnique</h3>
+<p>More information about the format in which a Semantic Asset Distribution is released. This is different from the file format as, for example, a ZIP file (file format) could contain an XML schema (representation technique).</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/adms#representationTechnique">adms:representationTechnique</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
+    <tr><td class="prop">Usage note:</td><td>See also <a href="#dcterms_format">dcterms:format</a> and <a href="#dcat_mediaType">dcat:mediaType</a>.</td></tr>
+
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="adms_sample">adms:sample</h3>
+<p>Links to a sample of a Semantic Asset (which is itself a Semantic Asset).</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/adms#sample">adms:sample</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/adms#SemanticAsset">adms:SemanticAsset</a></td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="dcterms_spatial">dcterms:spatial</h3>
+<p>The geographic region to which the Semantic Asset or Semantic Asset Repository applies.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://purl.org/dc/terms/spatial">dcterms:spatial</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range</td><td><a href="http://purl.org/dc/terms/Location">dcterms:Location</a>.</td></tr>
+  </tbody>
+</table>
+</section>
+
+<section>
+<h3 id="adms_status">adms:status</h3>
+<p>The status of the Semantic Asset in the context of a particular workflow process.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/adms#status">adms:status</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="adms_supportedSchema">adms:supportedSchema</h3>
+<p>A schema according to which the Semantic Asset Repository can provide data about its content, e.g. ADMS.</p>
+<table class="definition">
+  <thead><tr><th>Datatype Property:</th><th><a href="http://www.w3.org/ns/adms#supportedSchema">adms:supportedSchema</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>.</td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="dcterms_temporal">dcterms:temporal</h3>
+<p>The time period to which the Semantic Asset applies, e.g. its validity.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://purl.org/dc/terms/temporal">dcterms:temporal</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range</td><td><a href="http://purl.org/dc/terms/PeriodOfTime">dcterms:PeriodOfTime</a>.</td></tr>
+  </tbody>
+</table>
+</section>
+
+<section>
+<h3 id="dcat_theme">dcat:theme</h3>
+<p>The theme or sector to which the Semantic Asset applies.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/dcat#theme">dcat:theme</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Sub property of:</td><td><a href="http://purl.org/dc/terms/subject">dcterms:subject</a></td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+<section>
+<h3 id="dcat_themeTaxonomy">dcat:themeTaxonomy</h3>
+<p>The SKOS Concept Scheme used to classify Semantic Asset Repository's assets.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/dcat#themeTaxonomy">dcat:themeTaxonomy</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2004/02/skos/core#ConceptScheme">skos:ConceptScheme</a></td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="dcterms_title">dcterms:title</h3>
+<p>A name given to the Semantic Asset, Semantic Asset Repository or Semantic Distribution.</p>
+<table class="definition">
+  <thead><tr><th>Datatype Property:</th><th><a href="http://purl.org/dc/terms/title">dcterms:title</a></th></tr></thead>
+  <tbody><tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr></tbody>
+</table>
+</section>
+<section>
+<h3 id="adms_translation">adms:translation</h3>
+<p>Links Semantic Assets that are translations of each other.</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://www.w3.org/ns/adms#translation">adms:translation</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>.</td></tr>
+  </tbody>
+</table>
+</section>
+<section>
+<h3 id="dcterms_type">dcterms:type</h3>
+<p>The type of the Semantic Asset which should be provided using a controlled vocabulary encoded as a SKOS Concept</p>
+<table class="definition">
+  <thead><tr><th>Object Type Property:</th><th><a href="http://purl.org/dc/terms/type">dcterms:type</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td>Formally <a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a> but <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a> <em title="should" class="rfc2119">should</em> be used.</td></tr>
+  </tbody>
 </table>
 </section>
 
 
-<section><h4 id="pr_representationTechnique">Concept: Representation Technique</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>code</td><td><span>The representation technique used. Best practice is to use a value from a list of controlled terms.</span></td><td><a href="#dt_code">code</a></td><td><code>skos:notation</code></td></tr>
-  <tr><td>id</td><td><span>URI identifying the Representation Technique</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
-</table>
-<p>Note: this concept indicates that one of the files in a Distribution is expressed in 
-the Representation Technique. There may also be other files in the Distribution that 
-are expressed in other Representation Techniques or even files that are not 
-representations at all.</p>
-</section>
-
-
-<section><h4 id="pr_status">Concept: Status</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>code</td><td><span>The status of the Semantic Asset. Best practice is to use a value from a list of controlled terms.</span></td><td><a href="#dt_code">code</a></td><td><code>skos:notation</code></td></tr>
-  <tr><td>id</td><td><span>URI identifying the Status</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
+<section>
+<h3 id="adms_version">adms:version</h3>
+<p>A version number or other designation of the Semantic Asset.</p>
+<table class="definition">
+  <thead><tr><th>Datatype Property:</th><th><a href="http://www.w3.org/ns/adms#version">adms:version</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr>
+  </tbody>
 </table>
 </section>
 
-<section><h4 id="pr_theme">Concept: Theme</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>code</td><td><span>The theme or sector of the Semantic Asset. Best practice is to use a value from a list of controlled terms.</span></td><td><a href="#dt_code">code</a></td><td><code>skos:notation</code></td></tr>
-  <tr><td>id</td><td><span>URI identifying the Theme</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
+<section>
+<h3 id="adms_versionNotes">adms:versionNotes</h3>
+<p>A description of changes between this version and the previous version of the Semantic Asset.</p>
+<table class="definition">
+  <thead><tr><th>Datatype Property:</th><th><a href="http://www.w3.org/ns/adms#version">adms:versionNotes</a></th></tr></thead>
+  <tbody>
+    <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr>
+  </tbody>
 </table>
 </section>
 
-<section><h4 id="pr_themeTaxonomy">Concept: Theme Taxonomy</h4>
-<table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th><th>RDF encoding</th></tr>
-  <tr><td>code</td><td><span>The taxonomy used to describe themes or sectors covered by Semantic Assets in a Repository.</span></td><td><a href="#dt_code">code</a></td><td><code>skos:notation</code></td></tr>
-  <tr><td>id</td><td><span>URI identifying the Theme Taxonomy</span></td><td><a href="#dt_uri">URI</a></td><td>N/A</td></tr>
-</table>
-</section>
+</section> <!-- Properties and relationships -->
 
-
-</section> <!-- Supporting Concepts -->
-</section> <!-- Properties and relationships -->
 </section> <!-- Domain Model -->
-
+  
 
 </body></html>
--- a/adms/respec-config.js	Thu Apr 04 08:32:24 2013 +0100
+++ b/adms/respec-config.js	Thu Apr 04 17:40:01 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-10-23",
+    specStatus:           "NOTE",
+    publishDate:          "2013-04-04",
     //copyrightStart:       "2010",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/
--- a/adms/respec-ref.js	Thu Apr 04 08:32:24 2013 +0100
+++ b/adms/respec-ref.js	Thu Apr 04 17:40:01 2013 +0100
@@ -18,7 +18,7 @@
                 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"
                 berjon.biblio["UNCEFACT"] = "<cite><a href=\"http://www.unece.org/fileadmin/DAM/cefact/codesfortrade/CCTS/CCTS-DTCatalogueVersion3p1.pdf\"> (PDF) Core Components Data Type Catalogue Version 3.1</a></cite> UNECE United Nations Economic Commission for Europe. UN Centre for Trade Facilitation and Electronic Business (UN/CEFACT).   URL: http://www.unece.org/fileadmin/DAM/cefact/codesfortrade/CCTS/CCTS-DTCatalogueVersion3p1.pdf"
                 berjon.biblio["ISO8601"] = "<cite><a href=\"http://www.iso.org/iso/catalogue_detail?csnumber=40874\">ISO 8601:2004. Data elements and interchange formats &mdash; Information interchange &mdash; Representation of dates and times.</a></cite> ISO   URL: http://www.iso.org/iso/catalogue_detail?csnumber=40874"
-                berjon.biblio["DCAT"] = "<cite><a href=\"http://www.w3.org/TR/vocab-dcat/\">Data Catalog Vocabulary (DCAT)</a></cite> F. Maali, J. Erickson, P. Archer, W3C (currently a Working Draft dated 5 April but expected to become a Recommendation)   URL: http://www.w3.org/TR/vocab-dcat/"
+                berjon.biblio["DCAT"] = "<cite><a href=\"http://www.w3.org/TR/vocab-dcat/\">Data Catalog Vocabulary (DCAT)</a></cite> F. Maali, J. Erickson, P. Archer, W3C Recommendations Track   URL: http://www.w3.org/TR/vocab-dcat/"