Changes following Nikos comments
authorphila
Wed, 08 May 2013 13:04:06 +0100
changeset 507 4d7ac7a76b29
parent 506 30124ea1b54d
child 508 757ab56f1e1d
Changes following Nikos comments
adms/adms20130508.png
adms/adms20130508.rdf
adms/adms20130508.ttl
adms/index.html
adms/respec-config.js
Binary file adms/adms20130508.png has changed
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/adms/adms20130508.rdf	Wed May 08 13:04:06 2013 +0100
@@ -0,0 +1,290 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE rdf:RDF [
+  <!ENTITY xsd     "http://www.w3.org/2001/XMLSchema#">
+  <!ENTITY rdf     "http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+  <!ENTITY rdfs    "http://www.w3.org/2000/01/rdf-schema#">
+  <!ENTITY owl     "http://www.w3.org/2002/07/owl#">
+  <!ENTITY voaf    "http://labs.mondeca.com/vocab/voaf#">
+  <!ENTITY dcterms "http://purl.org/dc/terms/">
+  <!ENTITY dcDoc   "http://dublincore.org/documents/dcmi-terms/">
+  <!ENTITY foaf    "http://xmlns.com/foaf/0.1/">
+  <!ENTITY foafspec "http://xmlns.com/foaf/spec/">
+  <!ENTITY sioc    "http://rdfs.org/sioc/ns#">
+  <!ENTITY schema  "http://schema.org/">
+  <!ENTITY cc      "http://creativecommons.org/ns#">
+  <!ENTITY skos    "http://www.w3.org/2004/02/skos/core#">
+  <!ENTITY skosDoc "http://www.w3.org/TR/skos-reference/">
+  <!ENTITY dcat    "http://www.w3.org/ns/dcat#">
+  <!ENTITY vcard   "http://www.w3.org/2006/vcard/ns#">
+  <!ENTITY xhv     "http://www.w3.org/1999/xhtml/vocab#">
+  <!ENTITY wdrs    "http://www.w3.org/2007/05/powder-s#">
+  <!ENTITY vann    "http://purl.org/vocab/vann/">
+  <!ENTITY rad     "http://www.w3.org/ns/rad#">
+  <!ENTITY adms    "http://www.w3.org/ns/adms#">
+  <!ENTITY admsUrl "http://www.w3.org/ns/adms">
+  <!ENTITY gld     "http://www.w3.org/2011/gld/">
+  <!ENTITY admsDoc "http://www.w3.org/TR/vocab-adms">
+  <!ENTITY documentationTitle "Asset Description Metadata Schema (ADMS)">
+]>
+
+<rdf:RDF xmlns:xsd     = "&xsd;"
+         xmlns:rdf     = "&rdf;"
+         xmlns:rdfs    = "&rdfs;"
+         xmlns:owl     = "&owl;"
+         xmlns:voaf    = "&voaf;"
+         xmlns:dcterms = "&dcterms;"
+         xmlns:foaf    = "&foaf;"
+         xmlns:sioc    = "&sioc;"
+         xmlns:schema  = "&schema;"
+         xmlns:cc      = "&cc;"
+         xmlns:skos    = "&skos;"
+         xmlns:dcat    = "&dcat;"
+         xmlns:vcard   = "&vcard;"
+         xmlns:xhv     = "&xhv;"
+         xmlns:wdrs    = "&wdrs;"
+         xmlns:vann    = "&vann;"
+         xmlns:rad     = "&rad;"
+         xmlns         = "&adms;"
+         xml:base      = "&adms;"
+         xml:lang = "en">
+
+<!-- Document metadata -->
+
+  <owl:Ontology rdf:about="&adms;">
+    <rdfs:label xml:lang="en">Asset Description Metadata Schema (ADMS)</rdfs:label>
+    <rdfs:comment xml:lang="en">This file specifies the set of RDF classes and properties used in ADMS</rdfs:comment>
+    <owl:versionInfo xml:lang="en">02 May 2013</owl:versionInfo>
+    <dcterms:modified rdf:datatype="&xsd;date">2013-05-08</dcterms:modified>
+    <rdf:type rdf:resource="&voaf;Vocabulary"/>
+    <voaf:specializes rdf:resource="&rad;"/>
+    <vann:preferredNamespaceUri>&adms;</vann:preferredNamespaceUri>
+    <vann:preferredNamespacePrefix>adms</vann:preferredNamespacePrefix>
+    <dcterms:creator rdf:parseType="Resource">
+      <rdfs:seeAlso rdf:resource="http://makxdekkers.com/makxdekkers.rdf#me"/>
+      <foaf:name>Makx Dekkers</foaf:name>
+      <foaf:homepage rdf:resource="http://makxdekkers.com/"/>
+    </dcterms:creator>
+    <dcterms:creator rdf:parseType="Resource">
+      <rdfs:seeAlso rdf:resource="http://andrea-perego.name/foaf/#me"/>
+      <foaf:name>Andrea Perego</foaf:name>
+      <foaf:homepage rdf:resource="http://andrea-perego.name/"/>
+      <schema:affiliation rdf:parseType="Resource">
+        <foaf:name>European Commission, Joint Research Centre </foaf:name>
+        <foaf:homepage rdf:resource="http://ies.jrc.ec.europa.eu/DE"/>
+      </schema:affiliation>
+    </dcterms:creator>
+    <dcterms:creator rdf:parseType="Resource">
+      <rdfs:seeAlso rdf:resource="http://philarcher.org/foaf.rdf#me"/>
+      <foaf:name>Phil Archer</foaf:name>
+      <foaf:homepage rdf:resource="http://www.w3.org/People/all#phila"/>
+      <schema:affiliation rdf:parseType="Resource">
+        <foaf:name>W3C/ERCIM</foaf:name>
+        <foaf:homepage rdf:resource="http://www.w3.org/"/>
+      </schema:affiliation>
+    </dcterms:creator>
+    <foaf:maker rdf:parseType="Resource">
+      <foaf:name>Government Linked Data WG, based on output from the ADMS Working Group</foaf:name>
+      <foaf:page rdf:resource="&gld;"/>
+    </foaf:maker>
+    <dcterms:description rdf:parseType="Literal">This is the RDF encoding of the 
+      <a href="&admsDoc;">Asset Description Metadata Schema</a>, 
+      originally developed under the European Union's <a href="http://ec.europa.eu/isa/">ISA Programme</a> 
+      and further developed by the W3C <a href="&gld;">Government Linked Data Working Group</a>. It re-uses terms 
+      from several other vocabularies, notably Dublin Core, with elements of SKOS, FOAF 
+      and more.
+    </dcterms:description>
+    <foaf:depiction>
+      <rdf:Description rdf:about="http://www.w3.org/2012/05/ADMS_Conceptual_Model.png">
+        <rdfs:label>Asset Description Metadata Schema (ADMS) UML Class Diagram</rdfs:label>
+      </rdf:Description>
+    </foaf:depiction>
+    <dcterms:abstract>ADMS is intended as a model that facilitates federation 
+    and co-operation. It is not the primary intention that repository owners 
+    redesign or convert their current systems and data to conform to ADMS, but 
+    rather that ADMS can act as a common layer among repositories that want to 
+    exchange data. A change log for this namespace document is maintained in the
+    HTML representation of this document, available at &admsUrl;.html.
+    </dcterms:abstract>
+    <wdrs:describedby>
+      <rdf:Description rdf:about="&admsDoc;">
+        <dcterms:title>&documentationTitle;</dcterms:title>
+      </rdf:Description>
+    </wdrs:describedby>
+  </owl:Ontology>  
+
+<!-- Classes -->
+  <rdfs:Class rdf:about="&adms;AssetRepository">
+    <rdfs:label xml:lang="en">Asset Repository</rdfs:label>
+    <rdfs:comment xml:lang="en">An Asset Repository is a system or service that provides facilities for storage and maintenance of descriptions of Assets and Asset Distributions, and functionality that allows users to search and access these descriptions. An Asset Repository will typically contain descriptions of several Assets and related Asset Distributions.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:subClassOf rdf:resource="&dcat;Catalog" />
+    <dcterms:identifier>adms:AssetRepository</dcterms:identifier>
+  </rdfs:Class>
+
+  <rdf:Description rdf:about="&adms;Asset">
+    <rdfs:label xml:lang="en">Asset</rdfs:label>
+    <rdfs:comment xml:lang="en">An Asset is 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 work (a distinct intellectual or artistic creation) and expression (the intellectual or artistic realization of a work). 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. The physical embodiment of an Asset is called an Asset Distribution. A particular Asset may have zero or more Asset Distributions.</rdfs:comment>
+    <rdfs:subClassOf rdf:resource="&dcat;Dataset" />
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <dcterms:identifier>adms:Asset</dcterms:identifier>
+  </rdf:Description>
+
+  <rdfs:Class rdf:about="&adms;AssetDistribution">
+    <rdfs:label xml:lang="en">Asset Distribution</rdfs:label>
+    <rdfs:comment xml:lang="en">An Asset Distribution represents a particular physical embodiment of an Asset, which is an example of the FRBR entity manifestation (the physical embodiment of an expression of a work). An Asset 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. A particular Asset Distribution is associated with one and only one Asset, while all Distributions of an Asset share the same intellectual content in different physical formats. Asset Distributions themselves are not versioned.</rdfs:comment>
+    <rdfs:subClassOf rdf:resource="&dcat;Distribution" />
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <dcterms:identifier>adms:AssetDistribution</dcterms:identifier>
+  </rdfs:Class>
+
+  <rdfs:Class rdf:about="&adms;Identifier">
+    <rdfs:label xml:lang="en">Identifier</rdfs:label>
+    <rdfs:comment xml:lang="en" rdf:parseType="Literal">This class is based on the UN/CEFACT 
+    Identifier complex type defined in See Section 5.8 of Core Components Data Type Catalogue Version 3.1 (http://www.unece.org/fileadmin/DAM/cefact/codesfortrade/CCTS/CCTS-DTCatalogueVersion3p1.pdf)
+    In RDF this is expressed using the following properties:
+    - the content string should be provided using skos:notation, datatyped with the identifier scheme (inclduing the version number if appropriate);
+    - use dcterms:creator to link to a class describing the agency that manages the identifier scheme or adms:schemaAgency to provide the name as a literal.
+    Although not part of the ADMS conceptual model, it may be useful to provide further properties to the Identifier class such as
+    dcterms:created to provide the date on which the identifier was issued.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <dcterms:identifier>adms:Identifier</dcterms:identifier>
+  </rdfs:Class>
+
+
+<!-- ***************** Properties ********************** -->
+
+  <rdf:Property rdf:about="&adms;contactPoint">
+    <rdf:type rdf:resource="&owl;ObjectProperty" />
+    <rdfs:label xml:lang="en">contact point</rdfs:label>
+    <rdfs:comment xml:lang="en">Links an Asset to relevant Contact Information which is provided using VCard.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:range rdf:resource="&vcard;VCard" />
+    <dcterms:identifier>adms:contactPoint</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&adms;identifier">
+    <rdf:type rdf:resource="&owl;ObjectProperty" />
+    <rdfs:label xml:lang="en">identifier</rdfs:label>
+    <rdfs:comment xml:lang="en" rdf:parseType="Literal">adms:identifier is used to link any resource to 
+      an instance of adms:Identifier which is its range. N.B. it is not appropriate to use 
+      dcterms:identifer to link to the Identifier class as its range is rdfs:Literal.
+      ADMS uses this to provide any identifier for the Asset.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:range rdf:resource="&adms;Identifier" />
+    <dcterms:identifier>adms:identifier</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&adms;includedAsset">
+    <rdf:type rdf:resource="&owl;ObjectProperty" />
+    <rdfs:label xml:lang="en">included asset</rdfs:label>
+    <rdfs:comment xml:lang="en">Links to an Asset that is contained in the Asset being described, e.g. when there are several vocabularies defined in a single document.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:domain rdf:resource="&adms;Asset" />
+    <rdfs:range rdf:resource="&adms;Asset" />
+    <dcterms:identifier>adms:includedAsset</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&adms;interoperabilityLevel">
+    <rdf:type rdf:resource="&owl;ObjectProperty" />
+    <rdfs:label xml:lang="en">interoperability level</rdfs:label>
+    <rdfs:comment xml:lang="en" rdf:parseType="Literal">Links an Asset to its adms:InteroperabilityLevel. Since this is encoded using skos:Concept, that is the defined range for this property.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:domain rdf:resource="&adms;Asset" />
+    <rdfs:range rdf:resource="&skos;Concept" />
+    <dcterms:identifier>adms:interoperabilityLevel</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&adms;last">
+    <rdf:type rdf:resource="&owl;ObjectProperty" />
+    <rdfs:label xml:lang="en">last</rdfs:label>
+    <rdfs:comment>A link to the current or latest version of the Asset.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:subPropertyOf rdf:resource="&xhv;last" />
+    <dcterms:identifier>adms:last</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&adms;next">
+    <rdf:type rdf:resource="&owl;ObjectProperty" />
+    <rdfs:label xml:lang="en">last</rdfs:label>
+    <rdfs:comment>A link to the next version of the Asset.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:subPropertyOf rdf:resource="&xhv;next" />
+    <dcterms:identifier>adms:next</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&adms;prev">
+    <rdf:type rdf:resource="&owl;ObjectProperty" />
+    <rdfs:label xml:lang="en">last</rdfs:label>
+    <rdfs:comment>A link to the previous version of the Asset.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:subPropertyOf rdf:resource="&xhv;prev" />
+    <dcterms:identifier>adms:prev</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&adms;representationTechnique">
+    <rdf:type rdf:resource="&owl;ObjectProperty" />
+    <rdfs:label xml:lang="en">representation technique</rdfs:label>
+    <rdfs:comment xml:lang="en" rdf:parseType="Literal">Links an adms:AssetDistribution to a skos:Concept that is its adms:RepresentationTechnique.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:range rdf:resource="&skos;Concept" />
+    <dcterms:identifier>adms:representationTechnique</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&adms;sample">
+    <rdf:type rdf:resource="&owl;ObjectProperty" />
+    <rdfs:label xml:lang="en">sample</rdfs:label>
+    <rdfs:comment xml:lang="en">Links to a sample of an Asset (which is itself an Asset).</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:domain rdf:resource="&adms;Asset" />
+    <rdfs:range rdf:resource="&adms;Asset" />
+    <dcterms:identifier>adms:sample</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&adms;schemeAgency"> 
+    <rdf:type rdf:resource="&owl;DatatypeProperty" />
+    <rdfs:label xml:lang="en">scheme agency</rdfs:label>
+    <rdfs:comment xml:lang="en">The name of the agency responsible for issuing the identifier</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:domain rdf:resource="&adms;Identifier" />
+    <rdfs:range rdf:resource="&rdfs;Literal" />
+    <dcterms:identifier>adms:schemeAgency</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&adms;status">
+    <rdf:type rdf:resource="&owl;ObjectProperty" />
+    <rdfs:label xml:lang="en">status</rdfs:label>
+    <rdfs:comment xml:lang="en" rdf:parseType="Literal">Links to the status of the Asset or Asset Distribution 
+      in the context of a particular workflow process. Since Status is defined using a skos:Concept, 
+      that is the defined range for this property.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:range rdf:resource="&skos;Concept" />
+    <dcterms:identifier>adms:status</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&adms;supportedSchema"> 
+    <rdf:type rdf:resource="&owl;ObjectProperty" />
+    <rdfs:label xml:lang="en">supported schema</rdfs:label>
+    <rdfs:comment xml:lang="en">A schema according to which the Asset Repository can provide data about its content, e.g. ADMS</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:range rdf:resource="&adms;Asset" />
+    <dcterms:identifier>adms:supportedSchema</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&adms;translation">
+    <rdf:type rdf:resource="&owl;ObjectProperty" />
+    <rdfs:label xml:lang="en">translation</rdfs:label>
+    <rdfs:comment xml:lang="en">Links Assets that are translations of each other.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <dcterms:identifier>adms:translation</dcterms:identifier>
+  </rdf:Property>
+
+  <rdf:Property rdf:about="&adms;versionNotes"> 
+    <rdf:type rdf:resource="&owl;DatatypeProperty" />
+    <rdfs:label xml:lang="en">version notes</rdfs:label>
+    <rdfs:comment xml:lang="en">A description of changes between this version and the previous version of the Asset.</rdfs:comment>
+    <rdfs:isDefinedBy rdf:resource="&admsDoc;" />
+    <rdfs:range rdf:resource="&rdfs;Literal" />
+    <dcterms:identifier>adms:versionNotes</dcterms:identifier>
+  </rdf:Property>
+
+</rdf:RDF>
\ No newline at end of file
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/adms/adms20130508.ttl	Wed May 08 13:04:06 2013 +0100
@@ -0,0 +1,172 @@
+@prefix dcterms: <http://purl.org/dc/terms/>.
+@prefix skos: <http://www.w3.org/2004/02/skos/core#>.
+@prefix foaf: <http://xmlns.com/foaf/0.1/>.
+@prefix owl: <http://www.w3.org/2002/07/owl#>.
+@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
+@prefix xhv: <http://www.w3.org/1999/xhtml/vocab#>.
+@prefix xml: <http://www.w3.org/XML/1998/namespace>.
+@prefix voaf: <http://labs.mondeca.com/vocab/voaf#>.
+@prefix vcard: <http://www.w3.org/2006/vcard/ns#>.
+@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
+@prefix vann: <http://purl.org/vocab/vann/>.
+@prefix dcat: <http://www.w3.org/ns/dcat#>.
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
+@prefix wdrs: <http://www.w3.org/2007/05/powder-s#>.
+@prefix schema: <http://schema.org/> .
+
+<http://www.w3.org/ns/adms#> 	a voaf:Vocabulary, owl:Ontology;
+  voaf:specializes dcat:;
+  dcterms:title "Asset Description Metadata Schema (ADMS)"@en;
+	dcterms:abstract "ADMS is intended as a model that facilitates federation and co-operation. It is not the primary intention that repository owners redesign or convert their current systems and data to conform to ADMS, but rather that ADMS can act as a common layer among repositories that want to exchange data. A change log for this namespace document is maintained in the HTML representation of this document, available at http://www.w3.org/ns/adms.html. "@en;
+	dcterms:creator [schema:affiliation <http://www.w3.org/data#W3C>;
+	  rdfs:seeAlso <http://philarcher.org/foaf.rdf#me>;
+  	foaf:homepage <http://www.w3.org/People/all#phila>;
+  	foaf:name "Phil Archer"@en.] ,
+    [schema:affiliation [foaf:homepage <http://ies.jrc.ec.europa.eu/DE>; foaf:name "European Commission, Joint Research Centre "@en.]; 
+  	rdfs:seeAlso <http://andrea-perego.name/foaf/#me>;
+	  foaf:homepage <http://andrea-perego.name/>;
+	  foaf:name "Andrea Perego"@en.] ,
+    [rdfs:seeAlso <http://makxdekkers.com/makxdekkers.rdf#me>; foaf:homepage <http://makxdekkers.com/>;
+    	foaf:name "Makx Dekkers"@en.];
+  foaf:maker[foaf:name "Government Linked Data WG, based on output from the ADMS Working Group"@en; foaf:homepage <http://www.w3.org/2011/gld/>.];
+	dcterms:description """This is the RDF encoding of the Asset Description Metadata Schema, originally 
+    developed under the European Union's ISA Programme and further developed by the W3C Government Linked Data Working Group.
+    It re-uses terms from several other vocabularies, notably Dublin Core, with elements of SKOS, FOAF and more. """;
+	dcterms:modified "2013-05-08"^^xsd:date;
+	vann:preferredNamespacePrefix "adms";
+	vann:preferredNamespaceUri "http://www.w3.org/ns/adms#";
+	rdfs:comment "This file specifies the set of RDF classes and properties used in ADMS"@en;
+	rdfs:label "Asset Description Metadata Schema (ADMS)"@en;
+	owl:versionInfo "02 May 2013";
+	wdrs:describedby <http://www.w3.org/TR/vocab-adms>.
+
+
+<http://www.w3.org/ns/adms#AssetRepository> dcterms:identifier "adms:AssetRepository";
+	a rdfs:Class;
+	rdfs:comment "An Asset Repository is a system or service that provides facilities for storage and maintenance of descriptions of Assets and Asset Distributions, and functionality that allows users to search and access these descriptions. An Asset Repository will typically contain descriptions of several Assets and related Asset Distributions."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "Asset Repository"@en;
+	rdfs:subClassOf dcat:Catalog.
+
+<http://www.w3.org/ns/adms#Asset> dcterms:identifier "adms:Asset";
+	rdfs:comment "An Asset is 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 work (a distinct intellectual or artistic creation) and expression (the intellectual or artistic realization of a work). 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. The physical embodiment of an Asset is called an Asset Distribution. A particular Asset may have zero or more Asset Distributions.."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "Asset"@en;
+	rdfs:subClassOf dcat:Dataset.
+
+<http://www.w3.org/ns/adms#AssetDistribution> dcterms:identifier "adms:AssetDistribution";
+	a rdfs:Class;
+	rdfs:comment "An Asset Distribution represents a particular physical embodiment of an Asset, which is an example of the FRBR entity manifestation (the physical embodiment of an expression of a work). An Asset 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. A particular Asset Distribution is associated with one and only one Asset, while all Distributions of an Asset share the same intellectual content in different physical formats. Asset Distributions themselves are not versioned."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "Asset Distribution"@en;
+	rdfs:subClassOf dcat:Distribution.
+
+<http://www.w3.org/ns/adms#Identifier> dcterms:identifier "adms:Identifier";
+	a rdfs:Class;
+	rdfs:comment "This class is based on the UN/CEFACT Identifier complex type defined in See Section 5.8 of Core Components Data Type Catalogue Version 3.1 (http://www.unece.org/fileadmin/DAM/cefact/codesfortrade/CCTS/CCTS-DTCatalogueVersion3p1.pdf) In RDF this is expressed using the following properties: - the content string should be provided using skos:notation, datatyped with the identifier scheme (inclduing the version number if appropriate); - use dcterms:creator to link to a class describing the agency that manages the identifier scheme or adms:schemaAgency to provide the name as a literal. Although not part of the ADMS conceptual model, it may be useful to provide further properties to the Identifier class such as dcterms:created to provide the date on which the identifier was issued."^^rdf:XMLLiteral;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "Identifier"@en.
+
+
+<http://www.w3.org/ns/adms#contactPoint> dcterms:identifier "adms:contactPoint";
+	a rdf:Property, owl:ObjectProperty;
+	rdfs:comment "Links an Asset to relevant Contact Information which is provided using VCard."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "contact point"@en;
+	rdfs:range vcard:VCard.
+
+<http://www.w3.org/ns/adms#identifier> dcterms:identifier "adms:identifier";
+	a rdf:Property, owl:ObjectProperty;
+	rdfs:comment "adms:identifier is used to link any resource to an instance of adms:Identifier which is its range. N.B. it is not appropriate to use dcterms:identifer to link to the Identifier class as its range is rdfs:Literal. ADMS uses this to provide any identifier for the Asset.";
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "identifier"@en;
+	rdfs:range <http://www.w3.org/ns/adms#Identifier>.
+
+<http://www.w3.org/ns/adms#includedAsset> dcterms:identifier "adms:includedAsset";
+	a rdf:Property, owl:ObjectProperty;
+	rdfs:comment "Links to an Asset that is contained in the Asset being described, e.g. when there are several vocabularies defined in a single document."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "included asset"@en;
+	rdfs:domain <http://www.w3.org/ns/adms#Asset>;
+	rdfs:range <http://www.w3.org/ns/adms#Asset>.
+
+<http://www.w3.org/ns/adms#interoperabilityLevel> dcterms:identifier "adms:interoperabilityLevel";
+	a rdf:Property, owl:ObjectProperty;
+	rdfs:comment "Links an Asset to its adms:InteroperabilityLevel. Since this is encoded using skos:Concept, that is the defined range for this property.";
+	rdfs:domain <http://www.w3.org/ns/adms#Asset>;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "interoperability level"@en;
+  rdfs:domain adms:Asset;
+	rdfs:range skos:Concept.
+
+<http://www.w3.org/ns/adms#last> dcterms:identifier "adms:last";
+	a rdf:Property, owl:ObjectProperty;
+	rdfs:comment "A link to the current or latest version of the Asset."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "last"@en;
+	rdfs:subPropertyOf xhv:last.
+
+<http://www.w3.org/ns/adms#next> dcterms:identifier "adms:next";
+	a rdf:Property,	owl:ObjectProperty;
+	rdfs:comment "A link to the next version of the Asset."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "last"@en;
+	rdfs:subPropertyOf xhv:next.
+
+<http://www.w3.org/ns/adms#prev> dcterms:identifier "adms:prev";
+	a rdf:Property,	owl:ObjectProperty;
+	rdfs:comment "A link to the previous version of the Asset."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "last"@en;
+	rdfs:subPropertyOf xhv:prev.
+
+<http://www.w3.org/ns/adms#representationTechnique> dcterms:identifier "adms:representationTechnique";
+	a rdf:Property,	owl:ObjectProperty;
+	rdfs:comment "Links an adms:AssetDistribution to a skos:Concept that is its adms:RepresentationTechnique.";
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "representation technique"@en;
+	rdfs:range skos:Concept.
+
+<http://www.w3.org/ns/adms#sample> dcterms:identifier "adms:sample";
+	a rdf:Property, owl:ObjectProperty;
+	rdfs:comment "Links to a sample of an Asset (which is itself an Asset).";
+	rdfs:domain <http://www.w3.org/ns/adms#Asset>;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "sample"@en;
+	rdfs:range <http://www.w3.org/ns/adms#Asset>.
+
+<http://www.w3.org/ns/adms#schemeAgency> dcterms:identifier "adms:schemeAgency";
+	a rdf:Property,	owl:DatatypeProperty;
+	rdfs:comment "The name of the agency responsible for issuing the identifier"@en;
+	rdfs:domain <http://www.w3.org/ns/adms#Identifier>;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "scheme agency"@en;
+	rdfs:range rdfs:Literal.
+
+
+<http://www.w3.org/ns/adms#status> dcterms:identifier "adms:status";
+	a rdf:Property,	owl:ObjectProperty;
+	rdfs:comment "Links to the status of the Asset or Asset Distribution in the context of a particular workflow process. Since Status is defined using a skos:Concept, that is the defined range for this property."^^rdf:XMLLiteral;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "status"@en;
+	rdfs:range skos:Concept.
+
+<http://www.w3.org/ns/adms#supportedSchema> dcterms:identifier "adms:supportedSchema";
+	a rdf:Property,	owl:ObjectProperty;
+	rdfs:comment "A schema according to which the Asset Repository can provide data about its content, e.g. ADMS"@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "supported schema"@en;
+	rdfs:range adms:Asset.
+
+<http://www.w3.org/ns/adms#translation> dcterms:identifier "adms:translation";
+	a rdf:Property,	owl:ObjectProperty;
+	rdfs:comment "Links Assets that are translations of each other."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "translation"@en.
+
+<http://www.w3.org/ns/adms#versionNotes> dcterms:identifier "adms:versionNotes";
+	a rdf:Property,	owl:DatatypeProperty;
+	rdfs:comment "A description of changes between this version and the previous version of the Asset."@en;
+	rdfs:isDefinedBy <http://www.w3.org/TR/vocab-adms>;
+	rdfs:label "version info"@en;
+	rdfs:range rdfs:Literal.
--- a/adms/index.html	Wed May 08 12:01:00 2013 +0100
+++ b/adms/index.html	Wed May 08 13:04:06 2013 +0100
@@ -64,26 +64,27 @@
 <body>
 
 <section id="abstract">
-<p>ADMS is a profile of DCAT, used to describe <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> (or just 'Assets'), 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.</p>
-<p>@@@ Move above the HR in publication version@@@ Terms in the ADMS namespace are available in both <a href="adms20130502.rdf">RDF/XML</a> and <a href="adms20130502.ttl">Turtle</a>.</p>
+<p>@@@ Move above the HR in publication version@@@ Terms in the ADMS namespace are available in both <a href="adms20130508.rdf">RDF/XML</a> and <a href="adms20130508.ttl">Turtle</a>.</p>
 </section>
 
 <section class="informative">
 <h2 id="intro">Introduction</h2>
 <p>ADMS, the Asset Description Metadata Schema, is a profile of DCAT [[DCAT]] for describing so-called 
-<em>Semantic Assets</em>, that is, highly reusable metadata (e.g. xml schemata,
+<em>Semantic Assets</em> (or just 'Assets'), that is, 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. Someone searching for a Semantic Asset is likely to have different needs, priorities and expectations 
+vocabularies) that are used for eGovernment system development [[TOGD]]. Someone searching for an Asset 
+is likely to have different needs, priorities and expectations 
 than someone searching for a dataset 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 
+In particular, users seeking an 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
+Of course this is a very broad generalization. If a code list is published as a SKOS Concept scheme then it is both an Asset
+and a dataset and it can be argued that all Assets are datasets. Therefore the difference in
 <em>user expectation</em> is at the heart of what distinguishes ADMS as a profile of DCAT. A further distinction 
 between DCAT and 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>
+i.e. the catalog itself is at the heart of the vocabulary. ADMS is focused on the assets within a catalog.</p>
 
 </section>
 
@@ -133,17 +134,17 @@
     <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>foaf  </td><td>http://xmlns.com/foaf/0.1/</td></tr>
-<!--    <tr><td>schema  </td><td>http://schema.org/</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>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>xhv  </td><td>http://www.w3.org/1999/xhtml/vocab#</td></tr> -->
+    <tr><td>xhv  </td><td>http://www.w3.org/1999/xhtml/vocab#</td></tr>
   </tbody>
 </table>
 </section>
 
-
+<!--
 <section class="informative">
 <h2 id="terminology">Terminology</h2>
 <p>This document uses the following terminology:</p>
@@ -162,7 +163,7 @@
 specifications, guideline documents, metadata schemas, code lists, controlled vocabularies, and
 references to various types of entities in the real world, such as organizations, people and
 places.</p>
-</section> <!-- Terminology -->
+</section> --> <!-- Terminology -->
 
 <section class="informative">
 <h2 id="overview">Vocabulary Overview</h2>
@@ -184,51 +185,58 @@
 <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 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.</pre>
+<pre id="sarEg">:Repository a adms:AssetRepository ;
+  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 .</pre>
 
 <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>
+<p>Next, an Asset. We'll create an imaginary code list called 'Fruit I like' for our example:</p>
 <ul>
   <li>apples</li>
   <li>pears</li>
   <li>oranges</li>
   <li>peaches</li>
 </ul>
-<p>We might describe this Semantic Asset thus:</p>
+<p>We might describe this Asset thus:</p>
 <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;;
+1  :Fruit_02 a adms:Asset ;
+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    adms:status &lt;http://purl.org/adms/status/Completed&gt; ;
 7    dcterms:type &lt;http://purl.org/adms/assettype/CodeList&gt; ;
 8    adms:previous :Fruit_01 ;
 9    adms:last :Fruit ;
-10   adms:distribution :Fruit_02.csv ;
-11   adms:distribution :Fruit_02.xml .</pre>
+10   dcat:distribution :Fruit_02.csv ;
+11   dcat:distribution :Fruit_02.xml .</pre>
 
 <p>This provides the creation date (line 2), description (line 3), 
-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 
+publisher (line 4) and a title (line 5) for the Asset.
+The status of the Asset is given in line 6 using one of the values made available in the original ADMS
+specification [[ADMS1]]. Likewise the type of 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>
+<p>This Asset has two distributions linked in lines 11 and 12. One of these might be described thus:</p>
 
 <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.";
+:Fruit_02.xml a adms:AssetDistribution ;
+  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; ;
   dcterms:format &lt;http://purl.org/NET/mediatypes/application/xml&gt; .</pre>
 
-<p>This is a very simple description of the Semantic Asset Distribution that just gives its
+<p>This is a very simple description of the Asset Distribution that just gives its
 description, format, and license. In this example we've used Ed Summers' media types application to
 provide a URI for the XML MIME type [[EDSU]]</p>
+<p>The missing triple from this example is the one that includes the Asset in the Repository. This is done with a simple triple:</p>
+
+<pre id="saDsl">
+:Repository dcat:dataset :Fruit_02 .
+</pre>
+
+
 </section> <!-- Example -->
 </section> <!-- Overview -->
 
@@ -236,7 +244,7 @@
 <h2 id="domainmodel">The ADMS Domain Model</h2>
 
 <figure id="uml">
-  <img src="adms20130502.png" width="837" height="578" alt="UML Diagram of ADMS" />
+  <img src="adms20130508.png" width="837" height="576" alt="UML Diagram of ADMS" />
   <figcaption>UML model of ADMS classes and properties</figcaption>
 </figure>
 
@@ -244,31 +252,31 @@
 <section>
 <h3 id="primary">The Primary Concepts</h3>
 <section>
-  <h4 id="pc_semanticAssetRepository">Semantic Asset Repository</h4>
-  <p><code class="rdfEncoding">adms:SemanticAssetRepository</code><br />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>
-  <p><code>adms:SemanticAssetRepository</code> is a sub class of <code>dcat:Catalog</code></p>
+  <h4 id="pc_AssetRepository">Asset Repository</h4>
+  <p><code class="rdfEncoding">adms:AssetRepository</code><br />A system or service that provides facilities for storage and maintenance of 
+  descriptions of Assets and Asset Distributions, and 
+  functionality that allows users to search and access these descriptions. An 
+  Asset Repository will typically contain descriptions of several Assets and related Asset Distributions.</p>
+  <p><code>adms:AssetRepository</code> is a sub class of <code>dcat:Catalog</code></p>
 </section>
 
 <section>
-  <h4 id="pc_semanticAsset">Semantic Asset</h4>
-  <p><code class="rdfEncoding">adms:SemanticAsset</code><br />
+  <h4 id="pc_Asset">Asset</h4>
+  <p><code class="rdfEncoding">adms:Asset</code><br />
   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>
-  <p><code>adms:SemanticAsset</code> is a sub class of <code>dcat:Dataset</code></p>
+  <p>The physical embodiment of an Asset is called an Asset Distribution. A particular Asset may have zero or more Distributions.</p>
+  <p><code>adms:Asset</code> is a sub class of <code>dcat:Dataset</code></p>
+  <p>Assets are included in Repositories using DCAT's <code>dcat:dataset</code> property.</p>
 </section>
 <section>
-  <h4 id="pc_semanticAssetDistribution">Semantic Asset Distribution</h4>
-  <p><code class="rdfEncoding">adms:SemanticAssetDistribution</code><br />
-  A particular physical embodiment of a Semantic Asset, which is an example of 
+  <h4 id="pc_AssetDistribution">Asset Distribution</h4>
+  <p><code class="rdfEncoding">adms:AssetDistribution</code><br />
+  A particular physical embodiment of an 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>
@@ -280,25 +288,26 @@
   illustration of two Assets that each have two Distributions (representations in different formats) see the diagram below.</p>
   <figure id="asset-distribution">
     <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>
+    <figcaption>The relationship between versioned Assets and their Distributions</figcaption>
   </figure>
-  <p><code>adms:SemanticAssetDistribution</code> is a sub class of <code>dcat:Distribution</code></p>
+  <p><code>adms:AssetDistribution</code> is a sub class of <code>dcat:Distribution</code></p>
+  <p>Assets are linked to Asset Distributions using DCAT's <code>dcat:distribution</code> property.</p>
 </section>
-<p>Examples of the relationship between Assets and Distributions are:</p>
+<p>Examples of the relationship between Assets and Asset Distributions are:</p>
 <dl>
-  <dt>An Asset without a Distribution</dt>
-  <dd>Even before a Semantic Asset is finalized, a description of what it will be can often be made; for example, a description of 
+  <dt>An Asset without an Asset Distribution</dt>
+  <dd>Even before an  Asset is finalized, a description of what it will be can often be made; for example, a description of 
   it can be written, the publisher is already known as is the language. A link to 
   the distribution, the physical document, can only be made when the work is done; 
   until that time, the Asset will have no Distribution associated with it.</dd>
-  <dt>An Asset and Distribution embedded in a single file</dt>
-  <dd>Some Semantic Assets, such as technical specifications, have some characteristics that are related to the 
+  <dt>An Asset and Asset Distribution embedded in a single file</dt>
+  <dd>Some Assets, such as technical specifications, have some characteristics that are related to the 
   intellectual content such as its description, its language and its version, and 
   some characteristics that are related to the file itself such as its location (if its identifier is not a URL), 
-  its format and the usage conditions. In such cases, a single entity is <em>both</em> a Semantic Asset <em>and</em>
-  a Semantic Asset Distribution. Even so, best practice is to assert the Asset &rarr; Distribution relationship (i.e.
+  its format and the usage conditions. In such cases, a single entity is <em>both</em> an Asset <em>and</em>
+  an Asset Distribution. Even so, best practice is to assert the Asset &rarr; Asset Distribution relationship (i.e.
   to point to itself) so that queries looking for that relationship will still return a result.<dd>
-  <dt>An Asset with multiple Distributions</dt>
+  <dt>An Asset with multiple Asset Distributions</dt>
   <dd>It is common for a single work to be expressed in multiple formats. For example, RDF documents are 
   often serialized in RDF/XML, Turtle and triples, each of which would be a discrete Distribution.</dd>
 </dl>
@@ -309,12 +318,12 @@
 <p>In addition to the primary concepts, ADMS includes a number of secondary or supporting concepts:</p>
 <section><h4 id="sec_assetType">Asset Type</h4>
   <p><code class="rdfEncoding">skos:Concept</code><br />
-  The classification of an Asset according to a controlled vocabulary, e.g. code list, metadata schema. Use <code><a href="#dcterms_type">dcterms:type</a></code> to link a Semantic Asset to an Asset Type.</p>
+  The classification of an Asset according to a controlled vocabulary, e.g. code list, metadata schema. Use <code><a href="#dcterms_type">dcterms:type</a></code> to link an Asset to an Asset Type.</p>
 </section>
 <section>
 <h4 id="sec_contactInformation">Contact Information</h4>
   <p><code class="rdfEncoding">v:VCard</code><br />
-  A contact point for further information about an Asset. Use <code><a href="#adms_contactPoint">adms:contactPoint</a></code> to link a Semantic Asset to a VCard.</p>
+  A contact point for further information about an Asset. Use <code><a href="#adms_contactPoint">adms:contactPoint</a></code> to link an Asset to a VCard.</p>
 </section>
 <section>
   <h4 id="sec_documentation">Documentation</h4>
@@ -360,7 +369,7 @@
 <section>
   <h4 id="sec_interoperabilityLevel">Interoperability Level</h4>
   <p><code class="rdfEncoding">skos:Concept</code><br />
-  The interoperability level (e.g. legal, organizational, political etc.) of the Semantic Asset,
+  The interoperability level (e.g. legal, organizational, political etc.) of the Asset,
   linked using <code><a href="#adms_interoperabilityLevel">adms:interoperabilityLevel</a></code>. The
   interoperability level may be taken from a list of levels such as that of the European Interoperability 
   Framework [[EIF2]].</p>
@@ -396,7 +405,7 @@
   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", linked using <code><a href="#adms_representationTechnique">representationTechnique</a></code>.
         See also <code><a href="#dcterms_format">dcterms:format</a></code> and <code><a href="#dcat_mediaType">dcat:mediaType</a></code>.</p>
-      <p>This concept indicates that one of the files in a Semantic Asset Distribution is expressed in the Representation Technique. 
+      <p>This concept indicates that one of the files in an 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>
 </section>
@@ -410,7 +419,7 @@
   <p><code class="rdfEncoding">skos:Concept</code><br />
   The sector that an Asset applies to, e.g. "law" or "environment". 
     Best practice is to use terms from a controlled vocabulary expressed as a SKOS Concept Scheme and linked 
-    from the Semantic Asset using <code><a href="#dcat_theme">dcat:theme</a></code>.</p>
+    from the Asset using <code><a href="#dcat_theme">dcat:theme</a></code>.</p>
 </section>
 <section>
   <h4 id="sec_themeTaxonomy">Theme Taxonomy</h4>
@@ -420,8 +429,8 @@
 </section>
 
 <p><strong>NB</strong> The original ADMS specification supports the provision of a description of 
-the metadata about a Semantic Asset, including its publisher and language (i.e. the human language in which the metadata is expressed,
-irrespective of the language used in the Semantic Asset itself). The DCAT concept of a Catalog Record can be used for this
+the metadata about an Asset, including its publisher and language (i.e. the human language in which the metadata is expressed,
+irrespective of the language used in the Asset itself). The DCAT concept of a Catalog Record can be used for this
 purpose and so is not detailed in this document.</p>
 
 </section> <!-- Secondary Concepts -->
@@ -434,7 +443,7 @@
 
 <section>
 <h3 id="dcat_accessURL">dcat:accessURL</h3>
-<p>Any kind of URL that gives access to a Semantic Asset Repository or Semantic Asset Distribution, e.g. a landing page, download, feed URL, SPARQL endpoint etc. 
+<p>Any kind of URL that gives access to an Asset Repository or 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>
@@ -450,7 +459,7 @@
 </section>
 <section>
 <h3 id="skos_altLabel">skos:altLabel</h3>
-<p>An alternative name for the Semantic Asset.</p>
+<p>An alternative name for the 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>
@@ -461,7 +470,7 @@
 <h3 id="adms_contactPoint">adms:contactPoint</h3>
 <p class="editorsnote">At the time of writing it looks likely, but not certain, that DCAT will define a similar property in which case this
 one will be removed in favor of it.</p>
-<p>A contact point for further information about a Semantic Asset.</p>
+<p>A contact point for further information about an 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>
@@ -486,7 +495,7 @@
 
 <section>
 <h3 id="dcat_dataset">dcat:dataset</h3>
-<p>Used to link a Semantic Asset Repository to a Semantic Asset.</p>
+<p>Used to link an Asset Repository to an Asset.</p>
 <table class="definition">
   <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/dcat#dataset">dcat:dataset</a></th></tr></thead>
   <tbody>
@@ -500,12 +509,12 @@
 
 <section>
 <h3 id="wdrs_describedby">wdrs:describedby</h3>
-<p>The main documentation or specification of the Semantic Asset</p>
+<p>The main documentation or specification of the 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>
+    <tr><td class="prop">Usage note</td><td>See also <a href="#dcat_landingPage">dcat:landingPage</a>, <a href="#foaf_page">foaf:page</a> </td></tr>
   </tbody>
 </table>
 </section>
@@ -513,7 +522,7 @@
 
 <section>
 <h3 id="dcterms_description">dcterms:description</h3>
-<p>A description of the Semantic Asset, Semantic Asset Repository or Semantic Distribution.</p>
+<p>A description of the Asset, Asset Repository or Asset 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>
@@ -521,7 +530,7 @@
 </section>
 <section>
 <h3 id="dcat_distribution">dcat:distribution</h3>
-<p>Links a Semantic Asset to an implementation in a particular format.</p>
+<p>Links an 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/dcat#distribution">dcat:distribution</a></th></tr></thead>
   <tbody>
@@ -532,7 +541,7 @@
 </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>
+<p>This is a direct link from an 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>
@@ -543,7 +552,7 @@
 
 <section>
 <h3 id="schema_endDate">schema:endDate</h3>
-<p>Used in ADMS to define the end of a period of time during which a Semantic Asset is valid or applicable.</p>
+<p>Used in ADMS to define the end of a period of time during which an Asset is valid or applicable.</p>
 <table class="definition">
   <thead><tr><th>Datat Type Property</th><th><a href="http://schema.org/endDate">schema:endDate</a></th></tr></thead>
   <tbody>
@@ -580,23 +589,23 @@
 
 <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>
+<p>An Asset that is contained in the 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>
+    <tr><td class="prop">Domain</td><td><a href="http://www.w3.org/ns/adms#Asset">adms:Asset</a></td></tr>
+    <tr><td class="prop">Range</td><td><a href="http://www.w3.org/ns/adms#Asset">adms:Asset</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>
+<p>The interoperability level for which the 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">Domain</td><td><a href="http://www.w3.org/ns/adms#SemanticAsset">adms:SemanticAsset</a></td></tr>
+    <tr><td class="prop">Domain</td><td><a href="http://www.w3.org/ns/adms#Asset">adms:Asset</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>
@@ -606,7 +615,7 @@
 <section>
 <h3 id="dcterms_issued">dcterms:issued</h3>
 
-<p>Date of formal issuance (e.g., publication) of the Semantic Asset, Semantic Asset Repository or Semantic Distribution.</p>
+<p>Date of formal issuance (e.g., publication) of the Asset, Asset Repository or Asset 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>
@@ -619,7 +628,7 @@
 
 <section>
 <h3 id="dcat_keyword">dcat:keyword</h3>
-<p>A word, phrase or tag to describe the Semantic Asset.</p>
+<p>A word, phrase or tag to describe the 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>
@@ -629,19 +638,19 @@
 </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>
+<p>A Web page that can be navigated to in a Web browser to gain access to the 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>
+    <tr><td class="prop">Usage note</td><td>If the 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>
 <h3 id="dcterms_language">dcterms:language</h3>
-<p>The language of the Semantic Asset</p>
+<p>The language of the 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>
@@ -657,7 +666,7 @@
 
 <section>
 <h3 id="adms_last">adms:last</h3>
-<p>A link to the current or latest version of the Semantic Asset.</p>
+<p>A link to the current or latest version of the Asset.</p>
 <table class="definition">
   <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/adms#last">adms:last</a></th></tr></thead>
   <tbody>
@@ -669,12 +678,12 @@
 
 <section>
 <h3 id="dcterms_license">dcterms:license</h3>
-<p>Links to the conditions or restrictions for (re-)use of the Semantic Asset Distribution.</p>
+<p>Links to the conditions or restrictions for (re-)use of the 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>
+    <tr><td class="prop">Usage note</td><td>If multiple licenses are given, these licenses apply to all files in the Asset Distribution.</td></tr>
   </tbody>
 </table>
 </section>
@@ -693,7 +702,7 @@
 </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>
+<p>Date of the latest update of the Asset, Asset Repository or Asset 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>
@@ -705,7 +714,7 @@
 </section>
 <section>
 <h3 id="adms_next">adms:next</h3>
-<p>A link to the next version of the Semantic Asset.</p>
+<p>A link to the next version of the Asset.</p>
 <table class="definition">
   <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/adms#next">adms:next</a></th></tr></thead>
   <tbody>
@@ -728,7 +737,7 @@
 
 <section>
 <h3 id="adms_prev">adms:prev</h3>
-<p>A link to the previous version of the Semantic Asset.</p>
+<p>A link to the previous version of the Asset.</p>
 <table class="definition">
   <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/adms#prev">adms:prev</a></th></tr></thead>
   <tbody>
@@ -740,7 +749,7 @@
 
 <section>
 <h3 id="dcterms_publisher">dcterms:publisher</h3>
-<p>Links a Semantic Asset, Semantic Asset Repository or Semantic Asset Distribution to the publishing foaf:Agent.</p>
+<p>Links an Asset, Asset Repository or 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>
@@ -749,30 +758,19 @@
 </table>
 </section>
 <section>
-<h3 id="adms_relatedDocumentation">adms:relatedDocumentation</h3>
-<p>Links to documentation that contains information related to the Semantic Asset.</p>
+<h3 id="foaf_page">foaf:page</h3>
+<p>Links to documentation that contains information related to the 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>
+  <thead><tr><th>Object Type Property</th><th><a href="http://xmlns.com/foaf/0.1/page">foaf:page</a></th></tr></thead>
   <tbody>
-    <tr><td class="prop">Sub property of</td><td><a href="http://xmlns.com/foaf/0.1/page">foaf:page</a></td></tr>
     <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">Sub property of</td><td><a href="http://xmlns.com/foaf/0.1/page">foaf:page</a></td></tr>
-    <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>See also <a href="#dcat_landingPage">dcat:landingPage</a>, <a href="#wdrs_describedby">wdrs:describedby</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>
+<p>A link between two 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>
@@ -783,7 +781,7 @@
 
 <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>
+<p>More information about the format in which an 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>
@@ -795,11 +793,11 @@
 </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>
+<p>Links to a sample of an Asset (which is itself an 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>
+    <tr><td class="prop">Range</td><td><a href="http://www.w3.org/ns/adms#Asset">adms:Asset</a></td></tr>
   </tbody>
 </table>
 </section>
@@ -821,7 +819,7 @@
 
 <section>
 <h3 id="dcterms_spatial">dcterms:spatial</h3>
-<p>The geographic region to which the Semantic Asset or Semantic Asset Repository applies.</p>
+<p>The geographic region to which the Asset or 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>
@@ -831,7 +829,7 @@
 </section>
 <section>
 <h3 id="schema_startDate">schema:startDate</h3>
-<p>Used in ADMS to define the start of a period of time during which a Semantic Asset is valid or applicable.</p>
+<p>Used in ADMS to define the start of a period of time during which an Asset is valid or applicable.</p>
 <table class="definition">
   <thead><tr><th>Datat Type Property</th><th><a href="http://schema.org/startDate">schema:startDate</a></th></tr></thead>
   <tbody>
@@ -842,7 +840,7 @@
 
 <section>
 <h3 id="adms_status">adms:status</h3>
-<p>The status of the Semantic Asset in the context of a particular workflow process.</p>
+<p>The status of the 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>
@@ -852,17 +850,17 @@
 </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>
+<p>A schema according to which the 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>
+    <tr><td class="prop">Range</td><td><a href="http://www.w3.org/ns/adms#Asset">adms:Asset</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>
+<p>The time period to which the 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>
@@ -873,7 +871,7 @@
 
 <section>
 <h3 id="dcat_theme">dcat:theme</h3>
-<p>The theme or sector to which the Semantic Asset applies.</p>
+<p>The theme or sector to which the 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>
@@ -885,7 +883,7 @@
 
 <section>
 <h3 id="dcat_themeTaxonomy">dcat:themeTaxonomy</h3>
-<p>The SKOS Concept Scheme used to classify Semantic Asset Repository's assets.</p>
+<p>The SKOS Concept Scheme used to classify an 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>
@@ -895,7 +893,7 @@
 </section>
 <section>
 <h3 id="dcterms_title">dcterms:title</h3>
-<p>A name given to the Semantic Asset, Semantic Asset Repository or Semantic Distribution.</p>
+<p>A name given to the Asset, Asset Repository or Asset 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>
@@ -903,7 +901,7 @@
 </section>
 <section>
 <h3 id="adms_translation">adms:translation</h3>
-<p>Links Semantic Assets that are translations of each other.</p>
+<p>Links 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>
@@ -913,7 +911,7 @@
 </section>
 <section>
 <h3 id="dcterms_type">dcterms:type</h3>
-<p>This property is used to point to the specific type of publisher, Semantic Asset and License Document. In each case
+<p>This property is used to point to the specific type of publisher, Asset and License Document. In each case
 the type 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>
@@ -927,7 +925,7 @@
 
 <section>
 <h3 id="owl_version">owl:versionInfo</h3>
-<p>A version number or other designation of the Semantic Asset.</p>
+<p>A version number or other designation of the Asset.</p>
 <table class="definition">
   <thead><tr><th>Annotation Property</th><th><a href="http://www.w3.org/2002/07/owl#versionInfo">owl:versionInfo</a></th></tr></thead>
   <tbody>
@@ -938,7 +936,7 @@
 
 <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>
+<p>A description of changes between this version and the previous version of the 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>
@@ -957,7 +955,6 @@
   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>
 
-
 <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>) 
 of the European Commission (EC). Contributors included representatives of Member
@@ -965,7 +962,9 @@
 bodies and independent experts whose work was published in April 2012 [[ADMS1]]. 
 That document includes the history and motivation behind the development of ADMS, as well as the 
 business need and usage scenario for it.</p>
-<p>This version of ADMS builds on that work in a broader, global context.</p>
+<p>This version of ADMS builds on that work in a broader, global context. It also includes some changes to the original
+version made as a result of implementation experience, particularly on the 
+European Commission's <a href="http://joinup.ec.europa.eu/">Joinup Platform</a>.</p>
 
 </section>
 
--- a/adms/respec-config.js	Wed May 08 12:01:00 2013 +0100
+++ b/adms/respec-config.js	Wed May 08 13:04:06 2013 +0100
@@ -1,7 +1,7 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
     specStatus:           "NOTE",
-    publishDate:          "2013-05-02",
+    publishDate:          "2013-05-08",
     //copyrightStart:       "2010",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/