DCAT-editorial changes
authorfmaali
Tue, 25 Jun 2013 00:32:24 +0100
changeset 584 f9be2047ac00
parent 583 e9c991f5c641
child 585 8545551aeae5
child 586 95f00885a154
DCAT-editorial changes
dcat/index.html
--- a/dcat/index.html	Tue Jun 25 00:31:44 2013 +0100
+++ b/dcat/index.html	Tue Jun 25 00:32:24 2013 +0100
@@ -127,9 +127,17 @@
 <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> <code><a href="#Class:_Catalog">dcat:Catalog</a></code> represents the catalog
-</li><li> <code><a href="#Class:_Dataset">dcat:Dataset</a></code> represents a dataset in a catalog
+</li><li> <code><a href="#Class:_Dataset">dcat:Dataset</a></code> represents a dataset in a catalog. 
 </li><li> <code><a href="#Class:_Distribution">dcat:Distribution</a></code> represents an accessible form of a dataset as for example a downloadable file, an RSS feed or a web service that provides the data.
 </li></ul>
+<p>
+Notice that a dataset in DCAT 
+is defined as a "collection of data, published or curated by a single agent, and available for access or 
+download in one or more formats". A dataset does not have to be available as a downloadable file.
+For example, a dataset that is available via an API can be defined as an instance of dcat:Dataset and the  
+API can be defined as an instance of dcat:Distribution. DCAT itself does not define properties specific to APIs description. 
+These are considered out of the scope of this version of the vocabulary. Nevertheless, this can be defined as a profile of the DCAT vocabulary.
+</p>
 <p>Another important class in DCAT is <code><a href="#Class:_Catalog_record">dcat:CatalogRecord</a></code> which describes a dataset entry in the catalog. Notice that while dcat:Dataset represents the dataset itself, dcat:CatalogRecord represents the record that describes a dataset in the catalog. The use of the CatalogRecord is considered optional. It is used to capture provenance information about dataset entries in a catalog. If this distinction is not necessary then CatalogRecord can be safely ignored.</p>
 
 <p><img alt="UML model of DCAT classes and properties" src="dcat-model.jpg"/></p>
@@ -167,11 +175,13 @@
        dct:modified "2011-12-05"^^xsd:date&nbsp;;
        dct:publisher&nbsp;:finance-ministry&nbsp;;
        dct:language &lt;http://id.loc.gov/vocabulary/iso639-1/en&gt; &nbsp;;
+       dct:accrualPeriodicity &lt;http://purl.org/linked-data/sdmx/2009/code#freq-W&gt; &nbsp;;
        dcat:distribution&nbsp;:dataset-001-csv&nbsp;;
        .
 </pre>
 
-
+<p>In order to express frequency of update in the example above, we chose to use an instance from the <a href="http://www.w3.org/TR/vocab-data-cube/#dsd-cog">Content-Oriented Guidelines</a> developed as part 
+of the W3C Data Cube Vocabulary efforts.</p>
 <p>The dataset distribution :dataset-001-csv can be downloaded as a 5Kb CSV file. This information is 
 represented via an RDF resource of type dcat:Distribution.
 </p>
@@ -282,6 +292,7 @@
 <a href="#Property:catalog_description">description</a>,
 <a href="#Property:catalog_homepage">homepage</a>,
 <a href="#Property:catalog_language">language</a>,
+<a href="#Property:catalog_license">license</a>,
 <a href="#Property:catalog_publisher">publisher</a>,
 <a href="#Property:catalog_release_date">release date</a>,
 <a href="#Property:catalog_rights">rights</a>,
@@ -416,15 +427,31 @@
 </section>
 
 <section>
+<h3 id="Property:catalog_license">Property: license</h3>
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/license">dct:license</a></th></tr></thead>
+  <tbody>
+    <tr><td  class="prop">Definition:</td><td>This links to the license document under which the <strong>catalog</strong>
+     is made available and <strong>not the datasets</strong>. Even if the license of the catalog applies to all of its 
+     datasets and distributions, it should be replicated on each distribution.</td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://purl.org/dc/terms/LicenseDocument">dct:LicenseDocument</a></td></tr>
+    <tr><td class="prop">See also:</td><td><a href="#Property:catalog_rights">catalog rights</a>, 
+    <a href="#Property:distribution_license">distribution license</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+<section>
 <h3 id="Property:catalog_rights">Property: rights</h3>
 <table class="definition">
   <thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/rights">dct:rights</a></th></tr></thead>
   <tbody>
-    <tr><td  class="prop">Definition:</td><td>This describes the license and rights 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 
+    <tr><td  class="prop">Definition:</td><td>This describes the rights under which the <strong>catalog</strong>
+     can be used/reused and <strong>not the datasets</strong>. Even if theses rights apply to all the catalog   
      datasets and distributions, it should be replicated on each distribution.</td></tr>
     <tr><td class="prop">Range:</td><td><a href="http://purl.org/dc/terms/RightsStatement">dct:RightsStatement</a></td></tr>
-    <tr><td class="prop">See also:</td><td><a href="#Property:distribution_rights">distribution rights</a></td></tr>
+    <tr><td class="prop">See also:</td><td><a href="#Property:catalog_license">catalog license</a>, 
+    <a href="#Property:distribution_rights">distribution rights</a></td></tr>
   </tbody>
 </table>
 </section>
@@ -788,6 +815,7 @@
 <a href="#Property:distribution_description">description</a>,
 <a href="#Property:distribution_downloadurl">download URL</a>,
 <a href="#Property:distribution_format">format</a>,
+<a href="#Property:distribution_license">license</a>,
 <a href="#Property:distribution_media_type">media type</a>,
 <a href="#Property:distribution_release_date">release date</a>,
 <a href="#Property:distribution_rights">rights</a>,
@@ -858,15 +886,30 @@
 </section>
 
 <section>
+<h3 id="Property:distribution_license">Property: license</h3>
+<table class="definition">
+  <thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/license">dct:license</a></th></tr></thead>
+  <tbody>
+    <tr><td  class="prop">Definition:</td><td>This links to the license document under which the distribution is made available.</td></tr>
+    <tr><td class="prop">Range:</td><td><a href="http://purl.org/dc/terms/LicenseDocument">dct:LicenseDocument</a></td></tr>
+    <tr><td class="prop">See also:</td><td><a href="#Property:distribution_rights" title=""> distribution rights</a>, 
+    <a href="#Property:catalog_license" title="">catalog license</a></td></tr>
+  </tbody>
+</table>
+</section>
+
+<section>
 <h3 id="Property:distribution_rights">Property: rights</h3>
 <table class="definition">
   <thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/rights">dct:rights</a></th></tr></thead>
   <tbody>
     <tr><td  class="prop">Definition:</td><td>Information about rights held in and over the distribution.</td></tr>
     <tr><td class="prop">Range:</td><td><a href="http://purl.org/dc/terms/RightsStatement">dct:RightsStatement</a></td></tr>
-    <tr><td class="prop">Usage note:</td><td>dct:license, which is a sub-property of dct:rights, can also be used to link 
+    <tr><td class="prop">Usage note:</td><td>dct:license, which is a sub-property of dct:rights, can be used to link 
     a distribution to a license document. However, dct:rights allows linking to a rights statement that 
     can include licensing information as well as other information that supplements the licence such as attribution.</td></tr>
+    <tr><td class="prop">See also:</td><td><a href="#Property:distribution_license" title=""> distribution license</a>, 
+    <a href="#Property:catalog_rights" title="">catalog rights</a></td></tr>
   </tbody>
 </table>
 </section>