Converted to respec format(Action-38)
authorPhil@Phil-Desktop
Thu, 09 Feb 2012 11:45:56 +0000
changeset 68 c1cf1e9777b6
parent 67 a2c4d2f6bbf6
child 69 d688e2a8d9de
Converted to respec format(Action-38)
dcat/index.html
--- a/dcat/index.html	Tue Feb 07 08:37:01 2012 -0500
+++ b/dcat/index.html	Thu Feb 09 11:45:56 2012 +0000
@@ -1,9 +1,14 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
 <head>
   <title>Data Catalog Vocabulary (DCAT)</title>
+  <meta name="description" content="A vocabulary for describing the contents of a data catalog" />
+	<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;
@@ -16,7 +21,7 @@
     font-family: monospace;
   }
   table.definition {
-    width:50em;
+    width:100%;
   }
   table.definition td.prop {
     width:10em;
@@ -45,37 +50,13 @@
 	line-height: 1.1em;
 }
   </style>
-  <link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8">
+<!--  <link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8" /> -->
 </head>
 <body>
-<p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p>
-<h1 class="title" id="title">Data Catalog Vocabulary (DCAT)</h1>
-<h2 id="w3c-editors-draft">W3C Editor's Draft</h2>
-<dl>
-  <dt>This version:</dt>
-  <dd><a href="http://www.w3.org/TR/2011/[email protected]@@@@@@/">http://www.w3.org/TR/2011/[email protected]@@@@@@</a></dd>
-  <dt>Latest published version:</dt>
-  <dd><a href="http://www.w3.org/TR/DCAT/">http://www.w3.org/TR/DCAT/</a></dd>
-  <dt>Previous published version:</dt>
-  <dd>None</dd>
-  <dt>Editors:</dt>
-  <dd><a href="mailto:[email protected]">Fadi Maali</a>, <a href="http://www.deri.org/">DERI, NUIG</a></dd>
-  <dd><a href="mailto:[email protected]">John Erickson</a>, <a href="http://tw.rpi.edu">Tetherless World Constellation (RPI)</a></dd>
-  <dd><a href="mailto:[email protected]">Phil Archer</a>, <a href="/">W3C/ERCIM</a></dd>
-</dl>
-<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2010-2011
-  <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&trade;</sup>
-  (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
-  <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
-  <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C
-  <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
-  <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
-  <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
-<hr />
-<div id="abstract" class="introductory section">
-  <h2>Abstract</h2>
+
+<section id="abstract">
     <p>DCAT is an RDF vocabulary designed to facilitate interoperability between data catalog published on the Web. DCAT emerged from the W3C <a href="http://www.w3.org/egov/">eGov</a> Interest Group and W3C <a href="http://www.w3.org/2011/gld/">Government Linked Data</a> (GLD) Working Group but can be used for any entity publishing catalog of datasets.</p>
-    <p>DCAT was conceived with the following benefits in mind:
+    <p>DCAT was conceived with the following benefits in mind:</p>
 <ul>
 <li>Embedded metadata in catalog web pages increases data "findability," enables decentralised publishing of catalogs, and facilitates federated dataset search across sites</li>
 <li>A uniform catalog vocabulary provides a basis for one-click download and installation of data packages
@@ -83,126 +64,34 @@
 </li>
 <li>Aggregated DCAT metadata can serve as a manifest file to faciliate digital preservation</li>
 <li>A uniform metadata model enables applications to be built once and work with multiple catalog</li>
-</p>
-    <p>This document defines the RDF schema for DCAT and provides examples for its use.</p>
+</ul>
+<p>This document defines the RDF schema for DCAT and provides examples for its use.</p>
 <p>@@@ TODO.jse: Clarify? Anything more to add? @@@</p>
-</div>
-<div id="sotd" class="introductory section">
-  <h2>Status of This Document</h2>
-  <p><em>This section describes the status of this document at the time of its
-  publication. Other documents may supersede this document. A list of current
-  W3C publications and the latest revision of this technical report can be
-  found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a>
-  at http://www.w3.org/TR/.</em></p>
+
+</section>
+
+<section id="sotd">
   <p>This is the First Public Working Draft of DCAT in W3C's TR space and
   signals its move to the Recommendations Track. DCAT was first
   developed and published by DERI and has seen widespread adoption at the time of
   this publication. The <a href="http://vocab.deri.ie/dcat">original vocabulary</a>
   was further developed on the <a href="http://www.w3.org/egov/">eGov Interest Group</a> wiki before being brought onto the
-  Recommendation Track by the 
-  <a href="http://www.w3.org/2011/gld/">Government Linked Data (GLD)</a> Working Group
-  which intends for it to become a Recommendation.
-  If you wish to make comments regarding this document,
-  please send them to <a href="mailto:[email protected]">[email protected]</a>
-  (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>,
-  <a href="http://lists.w3.org/Archives/Public/public-gld-wg/">archives</a>).
-  All feedback is welcome.</p>
-  <p>Publication as a Working Draft does not imply endorsement by the W3C
-  Membership. This is a draft document and may be updated, replaced or
-  obsoleted by other documents at any time. It is inappropriate to cite this
-  document as other than work in progress.</p>
-  <p>This document was produced by a group operating under the
-  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February
-  2004 W3C Patent Policy</a>. W3C maintains a
-  <a href="http://www.w3.org/2004/01/pp-impl/49309/status" rel="disclosure">public
-  list of any patent disclosures</a> made in connection with the deliverables
-  of the group; that page also includes instructions for disclosing a patent.
-  An individual who has actual knowledge of a patent which the individual
-  believes contains
-  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
-  Claim(s)</a> must disclose the information in accordance with
-  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
-  6 of the W3C Patent Policy</a>.</p>
-</div>
-
-<h2 id="toc"">Table of Contents</h2>
-  <ul class="toc">
-    <li><a href="#intro">Introduction</a></li>
-    <li><a href="#conformance">Conformance</a></li>
-    <li><a href="#terminology">Terminology</a></li>
-    <li><a href="#ns">Namespaces</a></li>
-    <li><a href="#overview">Vocabulary Overview</a></li>
-    <li><a href="#example">Example</a></li>
-    <li><a href="#encoding">Encoding of Property Values</a></li>
+  Recommendation Track by <a href="http://www.w3.org/2011/gld/">Government Linked Data (GLD)</a> Working Group
+  which intends for it to become a Recommendation.</p>
+</section>
 
-    <li><a href="#Class:_Catalog">Class: Catalog</a>
-    <ul>
-      <li><a href="#Property:_homepage">Property: homepage</a></li>
-      <li><a href="#Property:_publisher">Property: publisher</a></li>
-      <li><a href="#Property:_spatial.2Fgeographic_coverage">Property: spatial/geographic coverage</a></li>
-      <li><a href="#Property:_themes">Property: themes</a></li>
-      <li><a href="#Property:_title">Property: title</a></li>
-      <li><a href="#Property:_description">Property: description</a></li>
-      <li><a href="#Property:_language">Property: language</a></li>
-      <li><a href="#Property:_license">Property: license</a></li>
-      <li><a href="#Property:_dataset">Property: dataset</a></li>
-      <li><a href="#Property:_catalog_record">Property: catalog record</a></li>
-    </ul></li>
-
-    <li><a href="#Class:_Catalog_record">Class: Catalog record</span></a>
-    <ul>
-      <li><a href="#Property:_listing_date">Property: listing date</a></li>
-      <li><a href="#Property:_update.2Fmodification_date">Property: update/modification date</a></li>
-      <li><a href="#Property:_dataset_2">Property: dataset</a></li>
-    </ul></li>
-
-    <li><a href="#Class:_Dataset">Class: Dataset</a>
-    <ul>
-      <li><a href="#Property:_update.2Fmodification_date_2">Property: update/modification date</a></li>
-      <li><a href="#Property:_title_2">Property: title</a></li>
-      <li><a href="#Property:_description_2">Property: description</a></li>
-      <li><a href="#Property:_publisher_2">Property: publisher</a></li>
-      <li><a href="#Property:_release_date">Property: release date</a></li>
-      <li><a href="#Property:_frequency">Property: frequency</a></li>
-      <li><a href="#Property:_identifier">Property: identifier</a></li>
-      <li><a href="#Property:_spatial.2Fgeographical_coverage">Property: spatial/geographical coverage</a></li>
-      <li><a href="#Property:_temporal_coverage">Property: temporal coverage</a></li>
-      <li><a href="#Property:_language_2">Property: language</a></li>
-      <li><a href="#Property:_license_2">Property: license</a></li>
-      <li><a href="#Property:_granularity">Property: granularity</a></li>
-      <li><a href="#Property:_data_dictionary">Property: data dictionary</a></li>
-      <li><a href="#Property:_data_quality">Property: data quality</a></li>
-      <li><a href="#Property:_theme.2Fcategory">Property: theme/category</a></li>
-      <li><a href="#Property:_keyword.2Ftag">Property: keyword/tag</a></li>
-      <li><a href="#Property:_related_documents">Property: related documents</a></li>
-      <li><a href="#Property:_dataset_distribution">Property: dataset distribution</a></li>
-    </ul></li>
-    <li><a href="#Class:_Distribution">Class: Distribution</a>
-    <ul>
-      <li><a href="#Property:_access.2Fdownload">Property: access/download</a></li>
-      <li><a href="#Property:_size">Property: size</a></li>
-      <li><a href="#Property:_format">Property: format</a></li>
-    </ul></li>
-
-    <li><a href="#Class:_Download">Class: Download</a></li>
-    <li><a href="#Class:_WebService"><span class="toctext">Class: WebService</a></li>
-    <li><a href="#Class:_Feed">Class: Feed</a></li>
-    <li><a href="#Class:_Category_and_category_scheme">Class: Category and category scheme</a></li>
-    <li><a href="#Class:_Organization.2FPerson">Class: Organization/Person</a></li>
-    <li><a href="#Extending_the_vocabulary">Extending the vocabulary</a></li>
-  </ul>
-
+<section class="informative">
 <h2 id="intro">Introduction</h2>
 <p>This document does not prescribe any particular method of deploying data expressed in DCAT. DCAT is applicable in many contexts including RDF accessible via SPARQL endpoints, embedded in HTML pages as RDFa, or serialized as e.g. RDF/XML or Turtle. The examples in this document use Turtle simply because of Turtle's readability.</p>
+</section>
 
-<h2 id="conformance">Conformance</h2>
+<section id="conformance">
 <ul>
 <li><i>DCAT compliance</i> means that a provider uses a subset of the DCAT vocabulary when publishing catalog and dataset metadata. This is likely to be the common case.</li>
 <li><i>DCAT conformance</i> means that a provider uses the entire DCAT vocabulary when publishing catalog and dataset metadata.</li>
 </ul>
-<h2 id="terminology">Terminology</h2>
[email protected]@@ TODO.jse: What goes here? @@@
-
+</section>
+<section>
 <h2 id="ns">Namespaces</h2>
 <p>The namespace for DCAT is <code>http://www.w3.org/ns/dcat#</code>. However,
 it should be noted that DCAT makes extensive use of terms from other vocabularies,
@@ -218,7 +107,9 @@
     <tr><td>foaf  </td><td>http://xmlns.com/foaf/0.1/</td></tr>
   </tbody>
 </table>
+</section>
 
+<section class="informative">
 <h2 id="overview">Vocabulary Overview</h2>
 <p>DCAT is an RDF vocabulary well-suited to representing government data catalogs such as <a href="http://Data.gov">Data.gov</a> and <a href="http://data.gov.uk">data.gov.uk</a>. DCAT defines three main classes:</p>
 <ul><li> dcat:Catalog represents the catalog
@@ -283,7 +174,7 @@
 </pre>
 <p>The dataset can be downloaded in CSV format via the distribution represented by&nbsp;:dataset/001/csv.
 </p>
-e<pre>  &nbsp;:dataset/001/csv
+<pre>  &nbsp;:dataset/001/csv
        a dcat:Distribution&nbsp;;
        dcat:accessURL &lt;<a href="http://www.example.org/files/001.csv" class="external free" title="http://www.example.org/files/001.csv" rel="nofollow">http://www.example.org/files/001.csv</a>&gt;&nbsp;;
        dct:title "CSV distribution of imaginary dataset 001"&nbsp;;
@@ -309,6 +200,9 @@
 <ul><li> Values like "unknown" or "unspecified" should never be used, and if present in the original database should be filtered for publishing. Instead, the property should simply be omitted.
 </li><li> @@@ policy for using resources vs. literals
 </li></ul>
+</section>
+
+<section>
 <h2 id="Class:_Catalog">Class: Catalog</h2>
 <p>A data catalog is a curated collection of metadata about datasets.</p>
 <table class="definition">
@@ -319,6 +213,7 @@
   </tbody>
 </table>
 
+<section>
 <h3 id="Property:_homepage">Property: homepage</h3>
 <p>The homepage of the catalog.</p>
 
@@ -329,7 +224,10 @@
     <tr><td class="prop">Usage note:</td><td><a href="http://xmlns.com/foaf/0.1/homepage">foaf:homepage</a> is an inverse functional property (IFP) which means that it should be unique and precisely identify the catalog. This allows smushing various descriptions of the catalog when different URIs are used.</td></tr>
   </tbody>
 </table>
+</section>
 
+
+<section>
 <h3 id="Property:_publisher">Property: publisher</h3>
 <p>The entity responsible for making the catalog online.</p>
 
@@ -339,7 +237,9 @@
     <tr><td class="prop">Range:</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_spatial.2Fgeographic_coverage">Property: spatial/geographic coverage></h3>
 <p>The geographical area covered by the catalog.</p>
 <table class="definition">
@@ -348,7 +248,9 @@
     <tr><td class="prop">Range:</td><td><a href="http://purl.org/dc/terms/Location">dcterms:Location</a> (Spatial region or named place)</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_themes">Property: themes</h3>
 <p>The knowledge organization system (KOS) used to classify catalog's datasets.</p>
 <table class="definition">
@@ -357,7 +259,9 @@
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2004/02/skos/core#ConceptScheme">skos:ConceptScheme</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_title">Property: title</h3>
 <p>A name given to the catalog.</p>
 <table class="definition">
@@ -366,7 +270,9 @@
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_description">Property: description</h3>
 <p>free-text account of the catalog.</p>
 <table class="definition">
@@ -375,7 +281,9 @@
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_language">Property: language</h3>
 <p>The language of the catalog. This refers to the language used in the textual metadata describing titles, descriptions, etc. of the datasets in the catalog.</p>
 
@@ -386,7 +294,9 @@
     <tr><td class="prop">Usage note:</td><td>Multiple values can be used. The publisher might also choose to describe the language on the dataset level (see <a href="#dataset_language">dataset language</a>).</td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_license">Property: license</h3>
 <p>This describes the license under which the <strong>catalog</strong> can be used/reused and <strong>not the datasets</strong>. Even if the license of the catalog applies to all of its datasets it should be replicated on each dataset.</p>
 <table class="definition">
@@ -397,7 +307,9 @@
     <tr><td class="prop">See also:</td><td><a href="#dataset_license" title="">dataset license</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_dataset">Property: dataset</h3>
 <p>A dataset that is part of the catalog.</p>
 <table class="definition">
@@ -406,7 +318,9 @@
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/dcat#Dataset">dcat:Dataset</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_catalog_record">Property: catalog record</h3>
 <p>A catalog record that is part of the catalog.</p>
 <table class="definition">
@@ -415,7 +329,10 @@
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/dcat#CatalogRecord"dcat:CatalogRecord</a></td></tr>
   </tbody>
 </table>
+</section>
+</section> <!-- end Class:Catalog -->
 
+<section>
 <h2 id="Class:_Catalog_record">Class: Catalog record</h2>
 <p>A record in a data catalog, describing a single dataset.</p>
 <table class="definition">
@@ -426,9 +343,11 @@
   </tbody>
 </table>
 
+
 <p>In web-based catalogs, the URL of the catalog page should be used as URI for the catalog record <em>if it is a permalink</em>.</p>
 <p>If named graphs are used, all RDF triples describing the catalog record, the dataset, and its distributions, should go into a graph named with the catalog record's URI.</p>
 
+<section>
 <h3 id="Property:_listing_date">Property: listing date</h3>
 <p>The date of listing the corresponding dataset in the catalog.</p>
 
@@ -441,8 +360,10 @@
     <tr><td class="prop">See also:</td><td><a href="#Property:_release_date" title=""> dataset release date</a></td></tr>
   </tbody>
 </table>
+</section>
 
 
+<section>
 <h3 id="Property:_update.2Fmodification_date">Property: update/modification date</h3>
 <p>Most recent date on which the catalog entry was changed, updated or modified.</p>
 <p class="editorsnote">See <a href="https://www.w3.org/2011/gld/track/issues/3">Issue-3</a></p>
@@ -455,7 +376,9 @@
     <tr><td class="prop">See also:</td><td><a href="#dataset_modification_date" title=""> dataset modification date</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_dataset_2">Property: dataset</h3>
 <p>Links the catalog record to the dcat:Dataset resource described in the record.</p>
 
@@ -466,7 +389,10 @@
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/dcat#Dataset">dcat:Dataset</a></td></tr>
   </tbody>
 </table>
+</section>
+</section> <!-- end Class catalog record -->
 
+<section>
 <h2 id="Class:_Dataset">Class: Dataset</h2>
 <p>A collection of data, published or curated by a single source, and available for access or download in one or more formats.</p>
 
@@ -478,6 +404,7 @@
   </tbody>
 </table>
 
+<section>
 <h3 id="Property:_update.2Fmodification_date_2">Property: update/modification date</h3>
 <p>Most recent date on which the dataset was changed, updated or modified.</p>
 <p class="editorsnote">See <a href="https://www.w3.org/2011/gld/track/issues/3">Issue-3</a></p>
@@ -490,7 +417,9 @@
     <tr><td class="prop">See also:</td><td><a href="#Property:_frequency">frequency</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_title_2">Property: title</h3>
 <p>A name given to the dataset.</p>
 
@@ -500,7 +429,9 @@
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_description_2">Property: description</h3>
 <p>free-text account of the dataset.</p>
 <table class="definition">
@@ -509,7 +440,9 @@
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_publisher_2">Property: publisher</h3>
 <p>An entity responsible for making the dataset available.</p>
 <p class="editorsnote">See <a href="https://www.w3.org/2011/gld/track/issues/4">Issue-4</a></p>
@@ -521,7 +454,9 @@
     <tr><td class="prop">See also:</td><td><a href="#Class:_Organization.2FPerson" title="">Class: Organization/Person</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_release_date">Property: release date</h3>
 <p>Date of formal issuance (e.g., publication) of the dataset.</p>
 <p class="editorsnote">See <a href="https://www.w3.org/2011/gld/track/issues/3">Issue-3</a></p>
@@ -532,7 +467,9 @@
     <tr><td class="prop">Usage note:</td><td>This property should be set using the first known date of issuance. <b>Example:</b> 2010-05-07</td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_frequency">Property: frequency</h3>
 <p>The frequency with which dataset is published.</p>
 <p class="editorsnote">See <a href="https://www.w3.org/2011/gld/track/issues/5">Issue-5</a></p>
@@ -544,7 +481,9 @@
     <tr><td class="prop">Domain:</td><td><a href="http://purl.org/dc/terms/Collection">dcterms:Collection</a> so, a Catalog must be a dcterms:Collection as well.</td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_identifier">Property: identifier</h3>
 <p>A unique identifier of the dataset.</p>
 
@@ -555,7 +494,9 @@
     <tr><td class="prop">Usage note:</td><td>The identifier might be used to coin permanent and unique URI for the dataset, but still having it represented explicitly is useful.</td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_spatial.2Fgeographical_coverage">Property: spatial/geographical coverage</h3>
 <p>Spatial coverage of the dataset.</p>
 
@@ -566,7 +507,9 @@
     <tr><td class="prop">Usage note:</td><td> @@@ controlled vocabulary. geonames???</td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_temporal_coverage">Property: temporal coverage</h3>
 <p>@@@ The temporal period that the dataset covers.</p>
 
@@ -577,7 +520,9 @@
     <tr><td class="prop">Usage note:</td><td> @@@ controlled vocabulary. <a href="http://www.placetime.com/">http://www.placetime.com/</a> might be an option???</td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_language_2">Property: language</h3>
 <p>The language of the dataset.</p>
 
@@ -588,7 +533,9 @@
     <tr><td class="prop">Usage note:</td><td>This overrides the value of the <a href="#Property:_language">catalog language</a> in case of conflict.</td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_license_2">Property: license</h3>
 <p>The license under which the dataset is published and can be reused.</p>
 
@@ -599,7 +546,9 @@
     <tr><td class="prop">Usage note:</td><td>See <a href="http://www.w3.org/TR/void/#license">Section 2.4 of Describing Linked Datasets with the VoID Vocabulary</a>.</td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_granularity">Property: granularity</h3>
 <p>describes the level of granularity of data. @@@ elaborate [email protected]@@</p>
 
@@ -611,7 +560,9 @@
   </tbody>
 </table>
 <p>A set of sample values used in data.gov: country, county, longitude/latitude, region, plane, airport.</p>
+</section>
 
+<section>
 <h3 id="Property:_data_dictionary">Property: data dictionary</h3>
 <p>provides some sort of description that helps understanding the data. This usually consisits of a table providing explanation of columns meaning, values interpretation and acronyms/codes used in the data.</p>
 
@@ -622,7 +573,9 @@
     <tr><td class="prop">Usage note:</td><td>@@@ Review @@@ It is rarely provided in the current catalogs and does not have a consistent usage, however when it is provided it is a link to some document or embeded in a document packaged together with the dataset. It is recommended to represent it as a resource having the URL of the online document as its URI. Statistical datasets, as a particular yet common case, can have a more structured description and the on-progress work on <a href="http://groups.google.com/group/publishing-statistical-data">SDMX+RDF</a> can be utilized here.</td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_data_quality">Property: data quality</h3>
 <p>describes the quality of data.</p>
 
@@ -633,7 +586,9 @@
     <tr><td class="prop">Usage note:</td><td>@@@[email protected]@@ This is a very general property and it is not clear how exactly it will be used as catalogs currently do not use it or use it with meaningless values. Catalogs are expected to define more specific sub-properties to describe quality characteristics e.g. statistical data usually have a lot to describe about the quality of sampling, collection mode, non-response adjustment&hellip;</td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_theme.2Fcategory">Property: theme/category</h3>
 <p>The main category of the dataset. A dataset can have multiple themes.</p>
 
@@ -644,7 +599,9 @@
     <tr><td class="prop">Usage note:</td><td>The set of <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a>s used to categorize the datasets are organized in a <a href="http://www.w3.org/2004/02/skos/core#ConceptScheme">skos:ConceptScheme</a> describing all the categories and their relations in the catalog.</td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_keyword.2Ftag"></a>Property: keyword/tag</h3>
 <p>A keyword or tag describing the dataset.</p>
 
@@ -654,7 +611,9 @@
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_related_documents">Property: related documents</h3>
 <p>A related document such as technical documentation, agency program page, citation, etc.</p>
 
@@ -665,7 +624,9 @@
     <tr><td class="prop">Usage note:</td><td>The value is the URI of the related document.</td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_dataset_distribution">Property: dataset distribution</h3>
 <p>Connects a dataset to its available distributions.</p>
 <table class="definition">
@@ -674,7 +635,9 @@
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/ns/dcat#">dcat:Distribution</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h2 id="Class:_Distribution">Class: Distribution</h2>
 <p>Represents a specific available form of a dataset. Each dataset might be available in different forms, these forms might represent different formats of the dataset, different endpoints,... Examples of Distribution include a downloadable CSV file, an XLS file representing the dataset, an RSS feed&hellip;</p>
 
@@ -686,8 +649,10 @@
     <tr><td class="prop">See also</td><td><a href="#Class:_Download">Download</a>, <a href="#Class:_WebService">WebService</a>, <a href="#Class:_Feed">Feed</a></td></tr>
   </tbody>
 </table>
+</section>
 
 
+<section>
 <h3 id="Property:_access.2Fdownload">Property: access/download</h3>
 <p>points to the location of a distribution. This can be a direct download link, a link to an HTML page containing a link to the actual data, Feed, Web Service etc. the semantic is determined by its domain (Distribution, Feed, WebService, Download).</p>
 <p class="editorsnote">If the value is always a URI, shouldn't the range be rdfs:Resource?</p>
@@ -699,8 +664,10 @@
     <tr><td class="prop">See also</td><td><a href="#Class:_Download">Download</a>, <a href="#Class:_WebService">WebService</a>, <a href="#Class:_Feed">Feed</a></td></tr>
   </tbody>
 </table>
+</section>
 
 
+<section>
 <h3 id="Property:_size">Property: size</h3>
 <p>The size of a distribution.</p>
 
@@ -712,7 +679,9 @@
     <tr><td class="prop">Example:</td><td><pre>  &nbsp;:distribution dcat:size [dcat:bytes 5120^^xsd:integer; rdfs:label "5KB"]</pre></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h3 id="Property:_format">Property: format</h3>
 <p>the file format of the distribution.</p>
 
@@ -729,7 +698,11 @@
 ]</pre></td></tr>
   </tbody>
 </table>
+</section>
+</section>
 
+
+<section>
 <h2 id="Class:_Download">Class: Download</h2>
 <p>Represents a downloadable distribution of a dataset.</p>
 
@@ -740,7 +713,9 @@
     <tr><td class="prop">See also:</td><td><a href="#Class:_Distribution">Distribution</a>, <a href="#Class:_WebService">WebService</a>, <a href="#Class:_Feed">Feed</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h2 id="Class:_WebService">Class: WebService</h2>
 <p>Represents a web service that enables access to the data of a dataset.</p>
 
@@ -752,7 +727,9 @@
     <tr><td class="prop">See also:</td><td><a href="#Class:_Distribution">Distribution</a>, <a href="#Class:_Download">Download</a>, <a href="#Class:_Feed">Feed</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h2 id="Class:_Feed">Class: Feed</h2>
 <p>represent availability of a dataset as a feed.</p>
 
@@ -763,7 +740,9 @@
     <tr><td class="prop">See also:</td><td><a href="#Class:_Distribution">Distribution</a>, <a href="#Class:_Download">Download</a>, <a href="#Class:_WebService">WebService</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h2 id="Class:_Category_and_category_scheme">Class: Category and category scheme</h2>
 <p>The knowledge organization system (KOS) used to represent themes/categories of datasets in the catalog.</p>
 
@@ -774,7 +753,9 @@
     <tr><td class="prop">See also:</td><td><a href="#Property:_themes">catalog themes</a>, <a href="#Property:_theme.2Fcategory">dataset theme</a></td></tr>
   </tbody>
 </table>
+</section>
 
+<section>
 <h2 id="Class:_Organization.2FPerson">Class: Organization/Person</h2>
 
 <table class="definition">
@@ -783,7 +764,10 @@
     <tr><td class="prop">Usage note:</td><td><a href="http://xmlns.com/foaf/spec/">FOAF</a> provides sufficient properties to describe these entities.</td></tr>
   </tbody>
 </table>
+</section>
 
+
+<section>
 <h2 id="Extending_the_vocabulary">Extending the DCAT vocabulary</h2>
 <ul>
   <li> As with all RDF models, the DCAT model can be extended simply by using additional RDF properties anywhere. Data catalog publishers may choose from properties in existing vocabularies or create their own custom vocabulary.</li>
@@ -792,6 +776,7 @@
   <li> Creating new subclasses and subproperties of terms used in dcat, such as new types of distributions, is generally discouraged because it can break SPARQL queries that data consumers use to query the data.</li>
   <li> As always with RDF, if you need to introduce new classes or properties, <em>do not introduce new terms in existing namespaces "owned" by someone else</em>, but set up your own namespace and define new terms in that namespace.</li>
 </ul>
+</section>
 
 
 </body></html>