Updates in line with recent comments
authorphila
Thu, 18 Oct 2012 14:51:06 +0100
changeset 223 0cd3c1168143
parent 222 12cf9cbf13b1
child 224 63253850fe1e
Updates in line with recent comments
adms/index.html
--- a/adms/index.html	Wed Oct 17 16:18:02 2012 +0100
+++ b/adms/index.html	Thu Oct 18 14:51:06 2012 +0100
@@ -87,8 +87,13 @@
 <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
-will have different needs and priorities than someone searching for a data set and
-these differences are reflected in ADMS.</p>
+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
+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>
 
 <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>) 
@@ -105,8 +110,9 @@
 
 <p>A data interchange, however that interchange occurs, is conformant with ADMS if:</p>
 <ul>
-  <li>it uses terms (classes and properties) from ADMS in a way consistent with their semantics as declared in this specification;</li>
-  <li>it does <strong>not</strong> use terms from other vocabularies instead of ones defined in this vocabulary that could reasonably be used.</li>
+  <li>it uses terms (classes and properties) from ADMS in a way consistent with their semantics as defined in this specification;</li>
+  <li>it does <strong>not</strong> use terms from other vocabularies <strong>instead</strong> of ones defined
+   in this vocabulary that could reasonably be used (use of such terms in <strong>addition</strong> to ADMS is permissible)..</li>
 </ul>
 
 <p>A conforming data interchange:</p>
@@ -117,23 +123,17 @@
 
 <p>An <strong>ADMS profile</strong> is a specification for data interchange that adds additional constraints. Such additional
   constraints in a profile <em class="rfc2119" title="may">may</em>
-  include:</p>
+  include (but are not limited to):</p>
 <ul>
   <li>a minimum set of required terms;</li>
   <li>classes and properties for additional terms not covered in ADMS;</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>
+  <li>specific concrete protocols, formats, and syntaxes.</li>
 </ul>
 
 <p>ADMS 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 class="editorsnote">
-<p>This is the ADMS version of the wording used in ORG. That wording in turn
-was developed (by Dave R) in response to <a href="http://www.w3.org/2011/gld/track/actions/76">ACTION-76</a> following 
-discussions on <a href="http://www.w3.org/2011/gld/meeting/2012-09-13#Conformance_Issue___28_PhilA2__29_"> 13 September</a> and
-<a href="http://www.w3.org/2011/gld/meeting/2012-07-26#DCAT">26 July</a> (the latter with with Rufus Pollock).</p>
 </section>
 
 <section>
@@ -146,8 +146,6 @@
 properties of its own. A full set of namespaces and prefixes used in this
 document is shown in the table below.</p>
 
-<p class="editorsnote">The use of RADion is under discussion. See <a href="https://www.w3.org/2011/gld/track/issues/36">ISSUE-36</a>.</p>
-
 <table id="namespaces">
   <thead><tr><th>Prefix</th><th>Namespace</th></tr></thead>
   <tbody>
@@ -186,10 +184,14 @@
 <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.</p>
-<p>On the other hand, there is nothing prohibiting developers of new repositories, or publishers of
+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>
@@ -197,6 +199,7 @@
 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>
 
+
 <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>
@@ -244,7 +247,7 @@
 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 prevous 
 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>
-<p>This Semantic Asset has two distributions, that is, accessible files, linked in lines 11 and 12. One of these might be described thus:</p>
+<p>This Semantic Asset has two distributions linked in lines 11 and 12. One of these might be described thus:</p>
 
 <pre>
 :Fruit_02.xml a adms:SemanticAssetDistribution ;
@@ -269,16 +272,20 @@
 <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>A system or service that provides facilities for storage and maintenance of 
+  <dd><p class="rdfEncoding">RDF encoding: <code>adms:SematicAssetRepository</code></p>
+  <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.</dd>
+  Assets and related Semantic Asset Distributions.</p></dd>
   <dt id="pc_semanticAsset">Semantic Asset</dt>
-  <dd>An abstract entity that reflects the intellectual content of the asset and 
+  <dd>
+  <p class="rdfEncoding">RDF encoding: <code>adms:SematicAsset</code></p>
+  <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]].
@@ -286,10 +293,12 @@
   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>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). 
+  <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 
+  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) that implements the intellectual content of an Asset.</p>
+  could also be a paper document or API response) that implements the intellectual content of an Asset.</p>
   <p>A particular Distribution is associated with one and only one Asset, while all 
   Distributions of an Asset share the same intellectual content in different physical formats.</p>
   <p>Distributions themselves are not versioned. If Distribution 1A is the manifestation of Asset 1 
@@ -327,36 +336,37 @@
 <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>The classification of an Asset according to a controlled vocabulary, e.g. code list, metadata schema.</dd>
+  <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>A contact point for further information about an Asset.</dd>
+  <dd><p class="rdfEncoding">RDF encoding: <code>VCard</code></p>A contact point for further information about an Asset.</p></dd>
   <dt id="sec_documentation">Documentation</dt>
-  <dd>Any document that further describes an Asset or gives guidelines for its use.</dd>
+  <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>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>.</dd>
+  <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>The country or region to which an Asset or Repository applies.</dd>
+  <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>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.</dd>
+  <dd><p class="rdfEncoding">RDF encoding: <code>adms:Item</code></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>A level as defined in a list such the European Interoperability Framework [[EIF2]] for which an Asset is relevant.</dd>
+  <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>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.</dd>
+  <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>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.</dd>
+  <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>The time period relevant for an Asset, e.g. for its validity</dd>
+  <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>The organization making a Repository, Asset or Distribution available.</dd>
+  <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>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".</dd>
+  <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>An indication of the maturity of an Asset or Distribution</dd>
+  <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>The sector that an Asset applies to, e.g. "law" or "environment". Best practice is to user terms from a controlled vocabulary.</dd>
+  <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>A controlled vocabulary that contains terms that are used as Themes for the Assets in a Repository.</dd>
+  <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 -->
@@ -375,25 +385,29 @@
 <p>ADMS makes use of the following data types.</p>
 <dl>
   <dt id="dt_code">code</dt>
-  <dd>Complex type (based on UN/CEFACT Code. [[UNCEFACT]] ) consisting of:<ul>
+  <dd><p class="rdfEncoding">RDF encoding: <code>skos:Concept</code></p>
+  <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></dd>
   <dt id="dt_dateTime">dateTime</dt>
-  <dd>String conforming to ISO8601 [[ISO8601]]</dd>
+  <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>Complex type (based on UN/CEFACT Identifier. [[UNCEFACT]]) consisting of:<ul>
-    <li>a content string which is the identifier (data type string);</li>
-    <li>an optional identifier for the identifier scheme (data type string);</li>
-    <li>an optional identifier for the version of the identifier scheme (data type string);</li>
-    <li>an optional identifier for the agency that manages the identifier scheme (data type string).</li></ul></dd>
+  <dd><p class="rdfEncoding">RDF encoding: <code>adms:Identifier</code></p>
+    <p>Complex type (based on UN/CEFACT Identifier. [[UNCEFACT]]) consisting of:<ul>
+    <li>a content string which is the identifier (RDF encoding: <code>skos:notation</code>);</li>
+    <li>an optional identifier for the identifier scheme (RDF encoding: <code>dcterms:type</code>);</li>
+    <li>an optional identifier for the version of the identifier scheme (RDF encoding: <code>adms:schemeVersion</code>);</li>
+    <li>an optional identifier for the agency that manages the identifier scheme 
+       (RDF encoding: <code>adms:schemaAgency</code> for a string, <code>dcterms:creator</code> for a URI).</li></ul></dd>
   <dt id="dt_string">string</dt>
   <dd>A string of UNICODE characters</dd>
   <dt id="dt_text">text</dt>
-  <dd>Complex type consisting of:<ul>
-    <li>a content string (data type string);</li>
-    <li>an optional language code from RFC 5646 [[RFC5646]] (data type code).</li></ul></dd>
+  <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>
 </dl>
@@ -407,49 +421,50 @@
 <section><h3 id="pr_semanticAsset">Concept: Semantic Asset</h3>
 
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th></tr>
+  <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></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></tr>
-  <tr><td>description</td><td><span>descriptive text for the Asset</span></td><td><a href="#dt_text">text</a></td></tr>
-  <tr><td>id</td><td><span>URI for the Asset</span></td><td><a href="#dt_uri">URI</a></td></tr>
-  <tr><td>identifier</td><td><span>any identifier for the Asset</span></td><td><a href="#dt_identifier">identifier</a></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></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></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></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></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></tr>
+    <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></tr>
-  <tr><td>asset type</td><td><span>type of the Asset</span></td><td><a href="#pr_assetType">Asset Type</a></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></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></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></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></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></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></tr>
-  <tr><td>language</td><td><span>language of the Asset</span></td><td><a href="#pr_language">Language</a></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></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></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></tr>
-  <tr><td>next version</td><td><span>newer version of the Asset</span></td><td><a href="#pr_semanticAsset">Semantic Asset</a></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></tr>
-  <tr><td>publisher</td><td><span>organization making the Asset available</span></td><td><a href="#pr_publisher">Publisher</a></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></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></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></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></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></tr>
-  <tr><td>sample</td><td><span>sample of the Asset</span></td><td><a href="#pr_semanticAsset">Semantic Asset</a></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></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></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></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></tr>
-  <tr><td>translation</td><td><span>translation of the Asset</span></td><td><a href="#pr_semanticAsset">Semantic Asset</a></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"></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>
 
@@ -458,23 +473,23 @@
 <section><h3 id="pr_semanticAssetDistribution">Concept: Semantic Asset Distribution</h3>
 
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th></tr>
+  <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></tr>
-  <tr><td>date of creation</td><td><span>creation date of the Distribution</span></td><td><a href="#dt_dateTime">dateTime</a></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></tr>
-  <tr><td>description</td><td><span>descriptive text for the Distribution</span></td><td><a href="#dt_text">text</a></td></tr>
-  <tr><td>id</td><td><span>URI for the Distribution</span></td><td><a href="#dt_uri">URI</a></td></tr>
-  <tr><td>name</td><td><span>name of the Distribution</span></td><td><a href="#dt_text">text</a></td></tr>
-  <tr class="midtable"><th>Relationship</th><th>Description</th><th>Target</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></tr>
+    <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></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></tr>
-  <tr><td>publisher</td><td><span>organization making the Distribution available</span></td><td><a href="#pr_publisher">Publisher</a></td></tr>
+      <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></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></tr>
+      <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 -->
@@ -482,21 +497,21 @@
 <section><h3 id="pr_semanticAssetRepository">Concept: Semantic Asset Repository</h3>
 
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</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></tr>
-  <tr><td>date of creation</td><td><span>creation date of the Repository</span></td><td><a href="#dt_dateTime">dateTime</a></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></tr>
-  <tr><td>description</td><td><span>descriptive text for the Repository</span></td><td><a href="#dt_text">text</a></td></tr>
-  <tr><td>id</td><td><span>URI for the Repository</span></td><td><a href="#dt_uri">URI</a></td></tr>
+  <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></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></tr>
-  <tr class="midtable"><th>Relationship</th><th>Description</th><th>Target</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></tr>
-  <tr><td>publisher</td><td><span>organization making the Repository available</span></td><td><a href="#pr_publisher">Publisher</a></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></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></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></tr>
+        <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 -->
 
@@ -504,112 +519,112 @@
 
 <section><h4 id="pr_assetType">Concept: Asset Type</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</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></tr>
-  <tr><td>id</td><td><span>URI identifying the Asset Type</span></td><td><a href="#dt_uri">URI</a></td></tr>
+  <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></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></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></tr>
-  <tr><td>id</td><td><span>URI identifying the Contact Information</span></td><td><a href="#dt_uri">URI</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></tr>
-  <tr><td>telephone</td><td><span>A telephone number for questions and feedback</span></td><td><a href="#dt_string">String</a></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></tr>
+  <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><h4 id="pr_documentation">Concept: Documentation</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</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></tr>
-  <tr><td>title</td><td><span>Title of the Documentation</span></td><td><a href="#dt_text">text</a></td></tr>
+  <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>
 </table>
 </section>
 
 <section><h4 id="pr_fileFormat">Concept: File Format</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</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></tr>
-  <tr><td>id</td><td><span>URI identifying the File Format</span></td><td><a href="#dt_uri">URI</a></td></tr>
+  <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>
 </table>
 </section>
 
 <section><h4 id="pr_geographicCoverage">Concept: Geographic Coverage</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th></tr>
-  <tr><td>description</td><td><span>Descriptive text for the Geographic Coverage</span></td><td><a href="#dt_text">text</a></td></tr>
-  <tr><td>id</td><td><span>URI identifying the Geographic Coverage</span></td><td><a href="#dt_uri">URI</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></tr>
+  <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>
 </table>
 </section>
 
 
 <section><h4 id="pr_item">Concept: Item</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th></tr>
-  <tr><td>description</td><td><span>Descriptive text for the Item</span></td><td><a href="#dt_text">text</a></td></tr>
-  <tr><td>id</td><td><span>URI identifying the Item</span></td><td><a href="#dt_uri">URI</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></tr>
+  <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>
 </table>
 </section>
 
 
 <section><h4 id="pr_interoperabilityLevel">Concept: Interoperability Level</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</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></tr>
-  <tr><td>id</td><td><span>URI identifying the Interoperability Level</span></td><td><a href="#dt_uri">URI</a></td></tr>
+  <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><h4 id="pr_language">Concept: Language</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</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></tr>
-  <tr><td>id</td><td><span>URI identifying the Language</span></td><td><a href="#dt_uri">URI</a></td></tr>
+  <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>
 </table>
 </section>
 
 <section><h4 id="pr_license">Concept: License</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th></tr>
-  <tr><td>description</td><td><span>Descriptive text for the License</span></td><td><a href="#dt_text">text</a></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></tr>
-  <tr><td>name</td><td><span>A short phrase describing the License</span></td><td><a href="#dt_text">text</a></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></tr>
+  <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>
 </table>
 </section>
 
 <section><h4 id="pr_periodOfTime">Concept: Period of Time</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</th></tr>
-  <tr><td>id</td><td><span>URI identifying the Period Of Time</span></td><td><a href="#dt_uri">URI</a></td></tr>
-  <tr><td>start</td><td><span>Beginning of the period</span></td><td><a href="#dt_dateTime">dateTime</a></td></tr>
-  <tr><td>end</td><td><span>End of the period</span></td><td><a href="#dt_dateTime">dateTime</a></td></tr>
+  <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>
 </table>
 </section>
 
 <section><h4 id="pr_publisher">Concept: Publisher</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</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></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></tr>
-  <tr><td>type</td><td><span>Value from a list of controlled terms</span></td><td><a href="#dt_code">code</a></td></tr>
+  <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>
 </table>
 </section>
 
 
 <section><h4 id="pr_representationTechnique">Concept: Representation Technique</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</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></tr>
-  <tr><td>id</td><td><span>URI identifying the Representation Technique</span></td><td><a href="#dt_uri">URI</a></td></tr>
+  <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 
@@ -620,25 +635,25 @@
 
 <section><h4 id="pr_status">Concept: Status</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</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></tr>
-  <tr><td>id</td><td><span>URI identifying the Status</span></td><td><a href="#dt_uri">URI</a></td></tr>
+  <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>
 </table>
 </section>
 
 <section><h4 id="pr_theme">Concept: Theme</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</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></tr>
-  <tr><td>id</td><td><span>URI identifying the Theme</span></td><td><a href="#dt_uri">URI</a></td></tr>
+  <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>
 </table>
 </section>
 
 <section><h4 id="pr_themeTaxonomy">Concept: Theme Taxonomy</h4>
 <table>
-  <tr><th>Property</th><th>Description</th><th>Data Type</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></tr>
-  <tr><td>id</td><td><span>URI identifying the Theme Taxonomy</span></td><td><a href="#dt_uri">URI</a></td></tr>
+  <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>