Binary file adms/ADMS_20120725.png has changed
Binary file adms/asset-distribution.png has changed
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/adms/index.html Thu Aug 02 08:25:04 2012 -0400
@@ -0,0 +1,645 @@
+<!DOCTYPE html>
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
+<head>
+ <title>Asset Description Metadata Schema (ADMS)</title>
+ <meta name="description" content="A vocabulary for describing semantic interoperability assets - highly reusable metadata and reference data used for eGovernment system development." />
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+ <!--[if lt IE 9]>
+ <script src="http://www.w3.org/2008/site/js/html5shiv.js"></script> <![endif]-->
+ <script type="text/javascript" src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+ <script src="respec-ref.js"></script>
+ <script src="respec-config.js"></script>
+ <style type="text/css">
+ table {
+ border-collapse:collapse;
+ width:100%;
+ }
+ td, th {
+ border:1px solid black;
+ padding:1em;
+ }
+ table#namespaces td {
+ font-family: monospace;
+ }
+ table.definition td.prop {
+ width:10em;
+ }
+ table tr.midtable th {
+ border-top: black medium double;
+ }
+ .editorsnote::before {
+ content: "Editor's Note";
+ display: block;
+ width: 150px;
+ background: #F30023;
+ color: #fff;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #cff6d9;
+ padding: 3px 1em;
+ }
+ .editorsnote {
+ margin: 1em 0em 1em 1em;
+ padding: 1em;
+ border: 2px solid #cff6d9;
+ }
+ pre {
+ padding: 1em;
+ border: 1px dashed #2f6fab;
+ color: black;
+ background-color: #f9f9f9;
+ line-height: 1.1em;
+ }
+ figure img {
+ display:block;
+ margin:0 auto;
+ }
+ figcaption {
+ text-align:center;
+ font-style:italic;
+ font-weight:bold;
+ }
+ </style>
+</head>
+<body>
+
+<section id="abstract">
+<p>ADMS is a vocabulary for describing
+<em>semantic assets</em>, defined as highly reusable metadata (e.g. xml schemata,
+generic data models) and reference data (e.g. code lists, taxonomies, dictionaries,
+vocabularies) that are used for eGovernment system development. This document is a
+companion to the namespace document at <a href="http://www.w3.org/ns/adms">http://www.w3.org/ns/adms</a></p>
+</section>
+
+<section id="sotd">
+ <p>This is the First Public Working Draft of ADMS in W3C's TR space and
+ signals its move to the Recommendations Track. ADMS was first
+ developed by PwC EU Services and
+ <a href="http://joinup.ec.europa.eu/asset/adms/home">published by the European Commission</a>.
+ Further development is now being undertaken by the <a href="http://www.w3.org/2011/gld/">Government
+ Linked Data Working Group</a> (GLD WG).</p>
+
+</section>
+
+<section class="informative">
+<h2 id="intro">Introduction</h2>
+<p>ADMS, the Asset Description Metadata Schema, is a vocabulary for describing so-called
+<em>Semantic Assets</em>, that is, things like standards, code lists and
+taxonomies. Although it has a lot in common with the Data Catalog vocabulary [[DCAT]],
+notably the extensive use of Dublin Core [[DC11]], someone searching for a Semantic Asset
+will have different needs and priorities than someone searching for a data set and
+these differences are reflected in ADMS.</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
+States of the European Union, operators of national repositories, standardization
+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>
+
+</section>
+
+<section id="conformance">
+<p>Conformance to this vocabulary means using its classes, properties and relationships to
+describe datasets. It does not necessarily mean using <em>every</em> term and there are no
+terms that are mandatory. However, the inclusion of a term signals that the Working Group
+has found it to be useful. Applications MAY specify a minimum set of terms that publishers must use
+if their data is to be processed, and MAY also specify controlled vocabularies as acceptable values for properties.
+This specification treats such restrictions as <em>application-specific</em> and therefore
+makes no such restrictions. However, the Working Group recognizes that
+restrictions (cardinality constraints) are often important. As an example, the original ADMS specification
+[[ADMS1]] includes a number of controlled vocabularies and cardinality constraints on
+properties that are relevant to the European Commission's
+<a href="http://joinup.ec.europa.eu/">Joinup Platform</a> that are not included in this more general document.</p>
+<p>It is, perhaps, easier to define non-conformance. A non-conformant implementation is one that
+uses a term other than one defined in this document that could reasonably be used.</p>
+
+<p>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>The above is very much open to discussion. The original conformance statement for ADMS says:</p>
+
+<ul>
+<li><i>ADMS compliance</i> means that a provider uses a subset of the ADMS vocabulary when publishing catalog and semantic asset metadata. This is likely to be the common case.</li>
+<li><i>ADMS conformance</i> means that a provider uses the entire ADMS vocabulary when publishing catalog and semantic asset metadata.</li>
+</ul></div>
+</section>
+
+<section>
+<h2 id="ns">Namespaces</h2>
+<p>The namespace for ADMS is <code>http://www.w3.org/ns/adms#</code>. However,
+it should be noted that ADMS makes extensive use of terms from other vocabularies,
+in particular Dublin Core [[DC11]].
+It subclasses the RADion vocabulary [[RAD]] that offers a structure for catalogs of various kinds.
+ADMS itself defines a minimal set of classes and
+properties of its own. A full set of namespaces and prefixes used in this
+document is shown in the table below.</p>
+
+<p class="editorsnote">The use of RADion is not confirmed. The GLD WG is considering alternatives,
+notably the proposed <a href="http://www.w3.org/wiki/WebSchemas/Datasets">dataset extension to schema.org</a>. Both
+offer a common framework that can be useful to ADMS, DCAT and other vocabularies.</p>
+
+<table id="namespaces">
+ <thead><tr><th>Prefix</th><th>Namespace</th></tr></thead>
+ <tbody>
+ <tr><td>adms</td><td>http://www.w3.org/ns/adms#</td></tr>
+ <tr><td>dcterms</td><td>http://purl.org/dc/terms/</td></tr>
+ <tr><td>radion</td><td>http://www.w3.org/ns/radion#</td></tr>
+ <tr><td>foaf </td><td>http://xmlns.com/foaf/0.1/</td></tr>
+ <tr><td>xhv </td><td>http://www.w3.org/1999/xhtml/vocab#</td></tr>
+ </tbody>
+</table>
+</section>
+
+
+<section class="informative">
+<h2 id="terminology">Terminology</h2>
+<p>This document uses the following terminology:</p>
+<P><strong>Semantic interoperability</strong> is defined by the European Interoperability Framework 2.02
+[[EIF2]] as the ability of information and communication
+technology (ICT) systems and the business processes they support to exchange data and to
+enable the sharing of information and knowledge: Semantic Interoperability enables systems to
+combine received information with other information resources and to process it in a meaningful
+manner. It aims at the mental representations that
+human beings have of the meaning of any given data.</p>
+<p>The European Commission defines a <strong>semantic interoperability asset</strong> as highly reusable metadata (e.g. xml schemata,
+generic data models) and reference data (e.g. code lists, taxonomies, dictionaries,
+vocabularies) which is used for eGovernment system development [[TOGD]].</p>
+<p>This definition is sufficiently broad to allow the inclusion of descriptions of various types of
+(meta)data to be included and managed in asset repositories. Possible types are for example
+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 class="informative">
+<h2 id="overview">Vocabulary Overview</h2>
+<p>ADMS is intended as a model that facilitates federation and co-operation. It is not the primary
+intention that repository publishers redesign or convert their current systems and data to
+conform to ADMS, rather that ADMS can act as a common layer among repositories that
+want to exchange data.</p>
+<p>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>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 XML@@@) schemas at
+<a href="http://www.w3.org/ns/adms">http://www.w3.org/ns/adms</a>.</p>
+<p class="editorsnote">An XML schema exists and is published on the EC's Joinup platform, however it includes
+all the controlled vocabularies and cardinality constraints associated with the original document. A
+simpler version more in line with the RDF schema will be needed if the GLD WG is to maintain both the RDF and XML schemas.</p>
+
+<section>
+<h2 id="example">Example</h2>
+<p>This example provides a quick overview of how ADMS might be used to represent a Semantic Asset Repository and its assets.</p>
+<p>Examples in this document are encoded in RDF and serialized in <a href="http://www.w3.org/TR/turtle/">Turtle</a> although,
+as noted, ADMS is designed to be technology-neutral.</p>
+<p>First, the repository description:</p>
+
+<pre>: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 <http://example.com/data#org>;
+ dcterms:title "The Exemplary Standards Body Catalog"@en;
+ rdfs:label "The Exemplary Standards Body Catalog"@en .</pre>
+
+<p>This assumes that data concerning The Exemplary Standards Body is described (in RDF) at <code>http://example.com/data#org</code>.</p>
+<p>Notice that the same string is given as the value for both <code>dcterms:title</code> and <code>rdfs:label</code>.
+This is because for some Semantic Assets it may not be appropriate to provide a title as such but it is
+always appropriate to provide a label. Semantic Asset Repository owners are encouraged to use both properties
+for ease of discovery.</p>
+
+<p>Next, a Semantic 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>
+<pre>
+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 <http://example.com/data#org>;
+5 dcterms:title "Fruit I like"@en ;
+6 rdfs:label "Fruit I like"@en;
+7 adms:status <http://purl.org/adms/status/Completed> ;
+8 dcterms:type <http://purl.org/adms/assettype/CodeList> ;
+9 xhv:previous :Fruit_01 ;
+10 xhv:last :Fruit ;
+11 radion:distribution :Fruit_02.csv ;
+12 radion:distribution :Fruit_02.xml .</pre>
+
+<p>This provides the creation date (line 2), description (line 3),
+publisher (line 4) and a title/label (lines 5 & 6) for the Semantic Asset.
+The status of the Semantic Asset is given in line 7 using one of the values made available in the original ADMS
+specification [[ADMS1]]. Likewise the type of Semantic Asset in line 8. In line 9 we can see that there was a 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>
+
+<pre>
+:Fruit_02.xml a adms:SemanticAssetDistribution ;
+ dcterms:description "XML encoding of Fruits that are found to be generally liked by most people.";
+ dcterms:license <http://creativecommons.org/licenses/by/3.0/> ;
+ dcterms:format <http://purl.org/NET/mediatypes/application/xml> .</pre>
+
+<p>This is a very simple description of the Semantic 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>
+</section> <!-- Example -->
+</section> <!-- Overview -->
+
+<section>
+<h2 id="domainmodel">The ADMS Domain Model</h2>
+
+<figure id="uml">
+ <img src="ADMS_20120725.png" width="1392" height="816" alt="UML Diagram of ADMS" />
+ <figcaption>UML model of ADMS classes and properties with references to the RADion vocabulary which it subclasses</figcaption>
+</figure>
+
+<p>The classes and properties are described briefly in the following sub-sections</p>
+<section>
+<h3 id="primary">The Primary Concepts</h3>
+<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
+ 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>
+ <dt id="pc_semanticAsset">Semantic Asset</dt>
+ <dd>An abstract entity that reflects the intellectual content of the asset and
+ represents those characteristics of the asset that are independent of its physical
+ embodiment. This abstract entity combines the FRBR entities <em>work</em> (a distinct
+ intellectual or artistic creation) and <em>expression</em> (the intellectual or artistic realization of a work) [[FRBR]].
+ <p>Assets can be versioned. Every time the intellectual content of an asset changes, the result is considered to
+ be a new asset that can be linked to previous and next versions of the Asset.</p>
+ <p>The physical embodiment of an Asset is called a Distribution. A particular Asset may have zero or more Distributions.</p></dd>
+ <dt id="pc_semanticAssetDistribution">Semantic Asset Distribution</dt>
+ <dd>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>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>
+ <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
+ and Distribution 2A is the manifestation of Asset 2, a version relationship will be expressed
+ between Asset 1 and Asset 2, not between Distribution 1A and Distribution 2A. For an
+ 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>
+ </figure>
+ </dd>
+</dl>
+<p>Examples of the relationship between Assets and 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
+ 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
+ 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 → 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>
+ <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>
+</section> <!-- Primary Concepts -->
+<section>
+<h3 id="secondary">The Secondary Concepts</h3>
+
+<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>
+ <dt id="sec_contactInformation">Contact Information</dt>
+ <dd>A contact point for further information about an Asset.</dd>
+ <dt id="sec_documentation">Documentation</dt>
+ <dd>Any document that further describes an Asset or gives guidelines for its use.</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>
+ <dt id="sec_geographicalCoverage">Geographical Coverage</dt>
+ <dd>The country or region to which an Asset or Repository applies.</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>
+ <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>
+ <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>
+ <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>
+ <dt id="sec_periodOfTime">Period of time</dt>
+ <dd>The time period relevant for an Asset, e.g. for its validity</dd>
+ <dt id="sec_publisher">Publisher</dt>
+ <dd>The organization making a Repository, Asset or Distribution available.</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>
+ <dt id="sec_status">Status</dt>
+ <dd>An indication of the maturity of an Asset or Distribution</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>
+ <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>
+</dl>
+<p>These supporting concepts are further described below.</p>
+</section> <!-- Secondary Concepts -->
+
+
+<section>
+<h2 id="Encoding_of_property_values">Encoding of property values</h2>
+<ul><li>Values like "unknown" or "unspecified" should never be used, and if present in the original
+data should be filtered for publishing. Instead, the property should simply be omitted.
+</li><li> @@@ policy for using resources vs. literals</li>
+</ul>
+<p class="editorsnote">This is copied from DCAT & seems sensible</p>
+</section> <!-- Encoding of property values -->
+
+<section><h2 id="dataTypes">Data Types</h2>
+<p>ADMS makes use of the following data types.</p>
+<dl>
+ <dt id="dt_code">code</dt>
+ <dd>Complex type (based on UN/CEFACT Code. [[UNCEFACT]] ) consisting of:<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>
+ <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>
+ <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>
+ <dt id="dt_uri">URI</dt>
+ <dd>String conforming to RFC 3986 [[!RFC3986]]</dd>
+</dl>
+</section> <!-- Data Types -->
+
+<section><h2 id="propertiesAndRelationships">Properties and Relationships</h2>
+<p>In the following sub-sections, we set out the properties and
+relationships of each of the primary and secondary concepts.</p>
+
+
+<section><h3 id="pr_semanticAsset">Concept: Semantic Asset</h3>
+
+<table>
+ <tr><th>Property</th><th>Description</th><th>Data Type</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>
+ </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>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>
+
+ <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>
+
+</table>
+
+</section> <!-- Semantic Asset -->
+
+<section><h3 id="pr_semanticAssetDistribution">Concept: Semantic Asset Distribution</h3>
+
+<table>
+ <tr><th>Property</th><th>Description</th><th>Data Type</th></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>
+ <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>
+ <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>
+</table>
+
+</section> <!-- Semantic Asset Distribution -->
+
+<section><h3 id="pr_semanticAssetRepository">Concept: Semantic Asset Repository</h3>
+
+<table>
+ <tr><th>Property</th><th>Description</th><th>Data Type</th></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><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>
+</table>
+</section> <!-- Semantic Assert Repository -->
+
+<section><h3 id="pr_supportingConcepts">Supporting Concepts</h3>
+
+<section><h4 id="pr_assetType">Concept: Asset Type</h4>
+<table>
+ <tr><th>Property</th><th>Description</th><th>Data Type</th></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>
+</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>
+</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>
+</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>
+</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>
+</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>
+</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>
+</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>
+</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>
+</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>
+</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>
+</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>
+</table>
+<p>Note: this concept indicates that one of the files in a Distribution is expressed in
+the Representation Technique. There may also be other files in the Distribution that
+are expressed in other Representation Techniques or even files that are not
+representations at all.</p>
+</section>
+
+
+<section><h4 id="pr_status">Concept: Status</h4>
+<table>
+ <tr><th>Property</th><th>Description</th><th>Data Type</th></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>
+</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>
+</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>
+</table>
+</section>
+
+
+</section> <!-- Supporting Concepts -->
+</section> <!-- Properties and relationships -->
+</section> <!-- Domain Model -->
+
+
+</body></html>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/adms/respec-config.js Thu Aug 02 08:25:04 2012 -0400
@@ -0,0 +1,99 @@
+var respecConfig = {
+ // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+ specStatus: "ED",
+ publishDate: "2012-09-28",
+ //copyrightStart: "2010",
+
+ // the specification's short name, as in http://www.w3.org/TR/short-name/
+ shortName: "vocab-adms",
+ //subtitle: "",
+ // if you wish the publication date to be other than today, set this
+ // publishDate: "2009-08-06",
+
+ // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+ // and its maturity status
+ //previousPublishDate: "2011-06-26",
+ //previousMaturity: "ED",
+ //previousDiffURI: "http://dvcs.w3.org/hg/gld/bp/",
+ diffTool: "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
+
+ // if there a publicly available Editor's Draft, this is the link
+ edDraftURI: "http://dvcs.w3.org/hg/gld/adms/",
+
+ // if this is a LCWD, uncomment and set the end of its review period
+ // lcEnd: "2009-08-05",
+
+ // if you want to have extra CSS, append them to this list
+ // it is recommended that the respec.css stylesheet be kept
+ extraCSS: [
+ "http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"
+ ],
+
+ // editors, add as many as you like
+ // only "name" is required
+ editors: [
+ { name: "Phil Archer", url: "http://www.w3.org/People/all#phila", company: "W3C/ERCIM", companyURL: "http://www.w3.org" },
+ { name: "Fadi Maali??", url: "mailto:fadi.maali@deri.org", company: "DERI, NUIG", companyURL: "http://www.deri.ie"},
+ ],
+
+ // authors, add as many as you like.
+ // This is optional, uncomment if you have authors as well as editors.
+ // only "name" is required. Same format as editors.
+
+ authors: [
+ { name: "Maxk Dekkers", url: "http://makxdekkers.com/", company: "AMI Consult (original document)"},
+ ],
+
+ // name of the WG
+ wg: "Government Linked Data Working Group",
+
+ // URI of the public WG page
+ wgURI: "http://www.w3.org/2011/gld/",
+
+ // name of the public mailing to which comments are due
+ wgPublicList: "public-gld-comments",
+
+ // URI of the patent status for this WG, for Rec-track documents
+ // !!!! IMPORTANT !!!!
+ // This is important for Rec-track documents, do not copy a patent URI from a random
+ // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+ // Team Contact.
+ wgPatentURI: "",
+ maxTocLevel: 4,
+ preProcess: [ preProc ]
+ //alternateFormats: [ {uri: "diff-20110507.html", label: "diff to previous version"} ],
+};
+
+function updateExample(doc, content) {
+ // perform transformations to make it render and prettier
+ content = content.replace(/<!--/, '');
+ content = content.replace(/-->/, '');
+ content = doc._esc(content);
+ content = content.replace(/\*\*\*\*([^*]*)\*\*\*\*/g, '<span class="diff">$1</span>') ;
+ return content ;
+}
+
+function updateDTD(doc, content) {
+ // perform transformations to
+ // make it render and prettier
+ content = '<pre class="dtd">' + doc._esc(content) + '</pre>';
+ content = content.replace(/!ENTITY % ([^ \t\r\n]*)/g, '!ENTITY <span class="entity">% $1</span>');
+ content = content.replace(/!ELEMENT ([^ \t$]*)/mg, '!ELEMENT <span class="element">$1</span>');
+ return content;
+}
+
+function updateSchema(doc, content) {
+ // perform transformations to
+ // make it render and prettier
+ content = '<pre class="dtd">' + doc._esc(content) + '</pre>';
+ content = content.replace(/<xs:element\s+name="([^&]*)"/g, '<xs:element name="<span class="element" id="schema_element_$1">$1</span>"') ;
+ return content;
+}
+
+function updateTTL(doc, content) {
+ // perform transformations to
+ // make it render and prettier
+ content = '<pre class="sh_sourceCode">' + doc._esc(content) + '</pre>';
+ content = content.replace(/@prefix/g, '<span class="sh_keyword">@prefix</span>');
+ return content;
+}
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/adms/respec-ref.js Thu Aug 02 08:25:04 2012 -0400
@@ -0,0 +1,139 @@
+var preProc = {
+ apply: function(c) {
+ // extend the bibliography entries
+ berjon.biblio["MICRODATA"] = "<cite><a href=\"http://www.w3.org/TR/microdata/\">Microdata</a></cite> Ian Hickson; et al. 04 March 2010. W3C Working Draft. URL: http://www.w3.org/TR/microdata/ ";
+ berjon.biblio["XHTML-RDFA"] = "<cite><a href=\"http://www.w3.org/TR/xhtml-rdfa/\">XHTML+RDFa</a></cite> Manu Sporny; et al. 31 March 2011. W3C Working Draft. URL: http://www.w3.org/TR/xhtml-rdfa/ ";
+ berjon.biblio["HTML-RDFA"] = "<cite><a href=\"http://dev.w3.org/html5/rdfa/\">HTML+RDFa</a></cite> Manu Sporny; et al. 24 May 2011. W3C Working Draft. URL: http://dev.w3.org/html5/rdfa/ ";
+ berjon.biblio["HOWTO-LODP"] = "<cite><a href=\"http://linkeddata.org/docs/how-to-publish\">How to Publish Linked Data on the Web</a></cite>, C. Bizer, R. Cyganiak, and Tom Heath, Community Tutorial 17 July 2008. URL: http://linkeddata.org/docs/how-to-publish";
+ berjon.biblio["COOL-SWURIS"] = "<cite><a href=\"http://www.w3.org/TR/cooluris/\">Cool URIs for the Semantic Web</a></cite>, L. Sauermann and R. Cyganiak, W3C Interest Group Note 03 December 2008. URL: http://www.w3.org/TR/cooluris/";
+ berjon.biblio["VOID-GUIDE"] = "<cite><a href=\"http://www.w3.org/TR/void/\">Describing Linked Datasets with the VoID Vocabulary</a></cite>, K. Alexander, R. Cyganiak, M. Hausenblas, and J. Zhao, W3C Interest Group Note 03 March 2011. URL: http://www.w3.org/TR/void/";
+ berjon.biblio["RDFA-CORE-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/rdfa-1.1\">RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 02 June 2011. URL: http://www.w3.org/profile/rdfa-1.1";
+ berjon.biblio["XHTML-RDFA-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/html-rdfa-1.1\">HTML+RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 24 May 2011. URL: http://www.w3.org/profile/html-rdfa-1.1";
+ berjon.biblio["RFC2616"] = "<cite><a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616.html\">Hypertext Transfer Protocol -- HTTP/1.1</a></cite>, R. Fielding; et al. June 1999. Internet RFC 2616. URL: http://www.w3.org/Protocols/rfc2616/rfc2616.html."
+ berjon.biblio["EIF2"] = "<cite><a href=\"http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf\">European Interoperability Framework (EIF) for European public services</a></cite> (PDF) European Commission. URL: http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf."
+ berjon.biblio["TOGD"] = "<cite><a href=\"http://joinup.ec.europa.eu/sites/default/files/towards_open_government_metadata_0.pdf\">Towards Open Government Metadata</a></cite> (PDF) European Commission Joinup e-Library. URL: http://joinup.ec.europa.eu/sites/default/files/towards_open_government_metadata_0.pdf"
+ berjon.biblio["ADMS1"] = "<cite><a href=\"http://joinup.ec.europa.eu/asset/adms/release/100\">ADMS 1.0</a></cite> European Commission ADMS (link is to a page offering various downloadable files in a variety of formats). URL: http://joinup.ec.europa.eu/asset/adms/release/100"
+ berjon.biblio["RAD"] = "<cite><a href=\"http://joinup.ec.europa.eu/asset/radion/home\">RADion</a></cite> Repository, Asset, Distribution (RADion) URL: http://joinup.ec.europa.eu/asset/radion/home"
+ berjon.biblio["EDSU"] = "<cite><a href=\"http://mediatypes.appspot.com/\">Media Types Application</a></cite> Ed Summers' work on providing URIs for media types URL: http://mediatypes.appspot.com/"
+ berjon.biblio["FRBR"] = "<cite><a href=\"http://archive.ifla.org/VII/s13/frbr/frbr_current_toc.htm\">Functional Requirements for Bibliographic Records</a></cite> OFLA 1998 URL: http://archive.ifla.org/VII/s13/frbr/frbr_current_toc.htm"
+ berjon.biblio["UNCEFACT"] = "<cite><a href=\"http://www.unece.org/fileadmin/DAM/cefact/codesfortrade/CCTS/CCTS-DTCatalogueVersion3p1.pdf\"> (PDF) Core Components Data Type Catalogue Version 3.1</a></cite> UNECE United Nations Economic Commission for Europe. UN Centre for Trade Facilitation and Electronic Business (UN/CEFACT). URL: http://www.unece.org/fileadmin/DAM/cefact/codesfortrade/CCTS/CCTS-DTCatalogueVersion3p1.pdf"
+ berjon.biblio["ISO8601"] = "<cite><a href=\"http://www.iso.org/iso/catalogue_detail?csnumber=40874\">ISO 8601:2004. Data elements and interchange formats — Information interchange — Representation of dates and times.</a></cite> ISO URL: http://www.iso.org/iso/catalogue_detail?csnumber=40874"
+ berjon.biblio["DCAT"] = "<cite><a href=\"http://www.w3.org/TR/vocab-dcat/\">Data Catalog Vocabulary (DCAT)</a></cite> F. Maali, J. Erickson, P. Archer, W3C (currently a Working Draft dated 5 April but expected to become a Recommendation) URL: http://www.w3.org/TR/vocab-dcat/"
+
+
+
+
+ // process the document before anything else is done
+ var refs = document.querySelectorAll('adef') ;
+ for (var i = 0; i < refs.length; i++) {
+ var item = refs[i];
+ var p = item.parentNode ;
+ var con = item.innerHTML ;
+ var sp = document.createElement( 'dfn' ) ;
+ var tit = item.getAttribute('title') ;
+ if (!tit) {
+ tit = con;
+ }
+ sp.className = 'adef' ;
+ sp.title=tit ;
+ sp.innerHTML = con ;
+ p.replaceChild(sp, item) ;
+ }
+ refs = document.querySelectorAll('aref') ;
+ for (var i = 0; i < refs.length; i++) {
+ var item = refs[i];
+ var p = item.parentNode ;
+ var con = item.innerHTML ;
+ var sp = document.createElement( 'a' ) ;
+ sp.className = 'aref' ;
+ sp.setAttribute('title', con);
+ sp.innerHTML = '@'+con ;
+ p.replaceChild(sp, item) ;
+ }
+ // local datatype references
+ refs = document.querySelectorAll('ldtref') ;
+ for (var i = 0; i < refs.length; i++) {
+ var item = refs[i];
+ if (!item) continue ;
+ var p = item.parentNode ;
+ var con = item.innerHTML ;
+ var ref = item.getAttribute('title') ;
+ if (!ref) {
+ ref = item.textContent ;
+ }
+ if (ref) {
+ ref = ref.replace(/\n/g, '_') ;
+ ref = ref.replace(/\s+/g, '_') ;
+ }
+ var sp = document.createElement( 'a' ) ;
+ sp.className = 'datatype';
+ sp.title = ref ;
+ sp.innerHTML = con ;
+ p.replaceChild(sp, item) ;
+ }
+ // external datatype references
+ refs = document.querySelectorAll('dtref') ;
+ for (var i = 0; i < refs.length; i++) {
+ var item = refs[i];
+ if (!item) continue ;
+ var p = item.parentNode ;
+ var con = item.innerHTML ;
+ var ref = item.getAttribute('title') ;
+ if (!ref) {
+ ref = item.textContent ;
+ }
+ if (ref) {
+ ref = ref.replace(/\n/g, '_') ;
+ ref = ref.replace(/\s+/g, '_') ;
+ }
+ var sp = document.createElement( 'a' ) ;
+ sp.className = 'externalDFN';
+ sp.title = ref ;
+ sp.innerHTML = con ;
+ p.replaceChild(sp, item) ;
+ }
+ // now do terms
+ refs = document.querySelectorAll('tdef') ;
+ for (var i = 0; i < refs.length; i++) {
+ var item = refs[i];
+ if (!item) continue ;
+ var p = item.parentNode ;
+ var con = item.innerHTML ;
+ var ref = item.getAttribute('title') ;
+ if (!ref) {
+ ref = item.textContent ;
+ }
+ if (ref) {
+ ref = ref.replace(/\n/g, '_') ;
+ ref = ref.replace(/\s+/g, '_') ;
+ }
+ var sp = document.createElement( 'dfn' ) ;
+ sp.title = ref ;
+ sp.innerHTML = con ;
+ p.replaceChild(sp, item) ;
+ }
+ // now term references
+ refs = document.querySelectorAll('tref') ;
+ for (var i = 0; i < refs.length; i++) {
+ var item = refs[i];
+ if (!item) continue ;
+ var p = item.parentNode ;
+ var con = item.innerHTML ;
+ var ref = item.getAttribute('title') ;
+ if (!ref) {
+ ref = item.textContent ;
+ }
+ if (ref) {
+ ref = ref.replace(/\n/g, '_') ;
+ ref = ref.replace(/\s+/g, '_') ;
+ }
+
+ var sp = document.createElement( 'a' ) ;
+ var id = item.textContent ;
+ sp.className = 'tref' ;
+ sp.title = ref ;
+ sp.innerHTML = con ;
+ p.replaceChild(sp, item) ;
+ }
+ }
+ } ;
\ No newline at end of file