--- a/dcat/index.html Sat Mar 09 11:54:39 2013 +0000
+++ b/dcat/index.html Sat Mar 09 13:01:34 2013 +0000
@@ -85,7 +85,7 @@
<thead><tr><th>Prefix</th><th>Namespace</th></tr></thead>
<tbody>
<tr><td>dcat</td><td>http://www.w3.org/ns/dcat#</td></tr>
- <tr><td>dcterms</td><td>http://purl.org/dc/terms/</td></tr>
+ <tr><td>dct</td><td>http://purl.org/dc/terms/</td></tr>
<tr><td>dctype</td><td>http://purl.org/dc/dcmitype/</td></tr>
<tr><td>foaf</td><td>http://xmlns.com/foaf/0.1/</td></tr>
<tr><td>rdf</td><td>http://www.w3.org/1999/02/22-rdf-syntax-ns#</td></tr>
@@ -99,9 +99,9 @@
<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
-</li><li> dcat:Dataset represents a dataset in a catalog
-</li><li> dcat:Distribution represents an accessible form of a dataset as for example a downloadable file, an RSS feed or a web service that provides the data.
+<ul><li> <code><a>dcat:Catalog</a></code> represents the catalog
+</li><li> <code><a>dcat:Dataset</a></code> represents a dataset in a catalog
+</li><li> <code><a>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>Another important class in DCAT is dcat:CatalogRecord 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>
@@ -109,50 +109,48 @@
<section>
<h2 id="example">Basic Example</h2>
-<p>This example provides a quick overview of how dcat might be used to represent a government catalog and its datasets. </p>
+<p>This example provides a quick overview of how DCAT might be used to represent a government catalog and its datasets. </p>
<p>First, the catalog description:
</p>
<pre> :catalog
a dcat:Catalog ;
- dcterms:title "Imaginary catalog" ;
- rdfs:label "Imaginary catalog" ;
+ dct:title "Imaginary Catalog" ;
+ rdfs:label "Imaginary Catalog" ;
foaf:homepage <http://example.org/catalog> ;
- dcterms:publisher :transparency-office ;
- dcterms:language <http://id.loc.gov/vocabulary/iso639-1/en> ;
- dcat:dataset :dataset-001 , :dataset-002 , dataset-003 ;
+ dct:publisher :transparency-office ;
+ dct:language <http://id.loc.gov/vocabulary/iso639-1/en> ;
+ dcat:dataset :dataset-001 , :dataset-002 , :dataset-003 ;
.
</pre>
<p>The publisher of the catalog has the relative URI :transparency-office. Further description of the publisher can be provided as in the following example:
</p>
<pre> :transparency-office
- a foaf:Agent ;
+ a foaf:Organization ;
rdfs:label "Transparency Office" ;
.
</pre>
<p>The catalog lists each of its datasets via dcat:dataset property. In the example above, an example dataset was mentioned with the relative URI :dataset-001. A possible description of it using dcat is shown below:
</p>
<pre> :dataset-001
- a dcat:Dataset ;
- dcterms:title "Imaginary dataset" ;
+ a dcat:Dataset ;
+ dct:title "Imaginary dataset" ;
dcat:keyword "accountability","transparency" ,"payments" ;
- dcat:theme :accountability ;
- dcterms:issued "2011-12-05"^^xsd:date ;
- dcterms:modified "2011-12-05"^^xsd:date ;
- dcterms:publisher :finance-ministry ;
- dcterms:accrualPeriodicity "every six months" ;
- dcterms:language "en"^^xsd:language ;
- dcat:Distribution :dataset-001-csv ;
+ dct:issued "2011-12-05"^^xsd:date ;
+ dct:modified "2011-12-05"^^xsd:date ;
+ dct:publisher :finance-ministry ;
+ dct:language <http://id.loc.gov/vocabulary/iso639-1/en> ;
+ dcat:distribution :dataset-001-csv ;
.
</pre>
-<p>The dataset can be downloaded as a 5Kb CSV file. This is
-represented via the RDF resource of type dcat:Distribution :dataset-001-csv.
+<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>
<pre> :dataset-001-csv
a dcat:Distribution ;
- dcat:accessURL <http://www.example.org/files/001.csv> ;
+ dcat:downloadURL <http://www.example.org/files/001.csv> ;
dcterms:title "CSV distribution of imaginary dataset 001" ;
dcat:mediaType "text/csv" ;
dcat:byteSize "5120"^^xsd:decimal ;
@@ -173,40 +171,75 @@
.
</pre>
-<p>Notice that this dataset is classified under the domain represented by the relative URI :accountability. This should be part of the domains set identified by the URI :themes that was used to describe the catalog domains. An example SKOS description
+<pre> :dataset-001 dcat:theme :accountability .
+</pre>
+<p>Notice that this dataset is classified under the domain represented by the relative URI :accountability. This should be part of the concepts scheme identified by the URI :themes that was used to describe the catalog domains. An example SKOS description
</p>
-<pre> :accountability
- a skos:Concept ;
- skos:inScheme :themes ;
- skos:prefLabel "Accountability" ;
- .
+<pre> :accountability
+ a skos:Concept ;
+ skos:inScheme :themes ;
+ skos:prefLabel "Accountability" ;
+ .
</pre>
</section>
<section>
<h2 id="example-catalog-record">Describing catalog records metadata</h2>
-<p>Finally, if the catalog publisher decides to keep metadata
+<p>If the catalog publisher decides to keep metadata
describing its records (i.e. the records containing metadata
-describing the datasets) dcat:CatalogRecord can be used. For example,
-while :dataset-001 was issued on 2011-12-05, its description on Imaginary Catalog was added on 2011-12-11. This can be represented by dcat:
+describing the datasets), dcat:CatalogRecord can be used. For example,
+while :dataset-001 was issued on 2011-12-05, its description on Imaginary Catalog was added on 2011-12-11. This can be represented by DCAT as in the following:
</p>
+<pre> :catalog dcat:record :record-001 .
+</pre>
+
<pre> :record-001
a dcat:CatalogRecord ;
foaf:primaryTopic :dataset-001 ;
dct:issued "2011-12-11"^^xsd:date ;
- .
- :catalog
- dcat:record :record-001 ;
- .
+ .
+
</pre>
</section>
<section>
<h2 id="">A dataset available only behind some Web page</h2>
+<p>:dataset-002 is available as a CSV file. However :dataset-002 can only be obtained through some Web page
+where the user needs to click some links, provide some information and check some boxes
+before accessing the data</p>
+
+<pre> :dataset-002
+ a dcat:Dataset ;
+ dcat:landingPage <http://example.org/dataset-002.html> ;
+ dcat:distribution :dataset-002-csv
+ .
+ :dataset-002-csv
+ a dcat:Distribution ;
+ dcat:accessURL <http://example.org/dataset-002.html> ;
+ dcat:mediaType "text/csv" ;
+ .
+</pre>
+
+Notice the use of dcat:landingPage and the definition of the dcat:Distribution instance.
</section>
<section>
<h2 id="">A dataset available as download and behind some Web page</h2>
+<p>On the other hand, :dataset-003 can be obtained through some landing page but also can be downloaded from a known URL.
+</p>
+<pre> :dataset-003
+ a dcat:Dataset ;
+ dcat:landingPage <http://example.org/dataset-003.html> ;
+ dcat:distribution :dataset-003-csv
+ .
+ :dataset-003-csv
+ a dcat:Distribution ;
+ dcat:downloadURL <http://example.org/dataset-003.csv> .
+ dcat:mediaType "text/csv" ;
+ .
+</pre>
+Notice that we used dcat:downloadURL with the downloadable distribution and that the other distribution through the landing page
+does not have to be defined as a spearate dcat:Distribution instance.
</section>
</section>