--- a/dcat/index.html Thu Jun 28 14:53:35 2012 +0100
+++ b/dcat/index.html Tue Jul 24 15:42:32 2012 +0100
@@ -95,7 +95,11 @@
<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>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>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>
+ <tr><td>rdfs</td><td>http://www.w3.org/2000/01/rdf-schema#</td></tr>
+ <tr><td>skos</td><td>http://www.w3.org/2004/02/skos/core#>/td></tr>
+ <tr><td>xsd</td><td>http://www.w3.org/2001/XMLSchema#</td></tr>
</tbody>
</table>
</section>
@@ -120,12 +124,12 @@
</p>
<pre> :catalog
a dcat:Catalog ;
- dct:title "Imaginary catalog" ;
+ dcterms:title "Imaginary catalog" ;
rdfs:label "Imaginary catalog" ;
foaf:homepage <<a href="http://example.org/catalog" class="external free" title="http://example.org/catalog" rel="nofollow">http://example.org/catalog</a>> ;
- dct:publisher :transparency-office ;
- dcat:themes :themes ;
- dct:language "en"^^xsd:language ;
+ dcterms:publisher :transparency-office ;
+ dcat:themeTaxonomy :themes ;
+ dcterms:language "en"^^xsd:language ;
dcat:dataset :dataset-001 ;
.
</pre>
@@ -136,25 +140,25 @@
rdfs:label "Transparency Office" ;
.
</pre>
-<p>The catalog classify its datasets according to a set of domains represented by the relative URI :themes. SKOS can be used to describe the domains used:
+<p>The catalog classifies its datasets according to a set of domains represented by the relative URI :themes. SKOS can be used to describe the domains used:
</p>
<pre> :themes
a skos:ConceptScheme ;
skos:prefLabel "A set of domains to classify documents" ;
- .
+ .
</pre>
-<p>The catalog connect to each of its datasets via dcat:dataset. 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>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 ;
- dct:title "Imaginary dataset" ;
+ dcterms:title "Imaginary dataset" ;
dcat:keyword "accountability","transparency" ,"payments" ;
dcat:theme :accountability ;
- dct:issued "2011-12-05"^^xsd:date ;
- dct:modified "2011-12-05"^^xsd:date ;
- dct:publisher :finance-ministry ;
- dct:accrualPeriodicity "every six months" ;
- dct:language "en"^^xsd:language ;
+ 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 ;
.
</pre>
@@ -166,20 +170,28 @@
skos:prefLabel "Accountability" ;
.
</pre>
-<p>The dataset can be downloaded in CSV format via the distribution represented by :dataset-001-csv.
+<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>
<pre> :dataset-001-csv
a dcat:Distribution ;
dcat:accessURL <<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>> ;
- dct:title "CSV distribution of imaginary dataset 001" ;
- dct:format [
- a dct:IMT;
+ dcterms:title "CSV distribution of imaginary dataset 001" ;
+ dcterms:format [
+ a dcterms:IMT;
rdf:value "text/csv";
rdfs:label "CSV"
+ ];
+ dcat:size [
+ rdfs:label "5Kb";
+ dcat:bytes "5120"^^xsd:integer;
]
.
</pre>
-<p>Finally, 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, :dataset-001 was issued on 2011-12-05. however, its description on Imaginary Catalog was added on 2011-12-11. This can be represented by dcat:
+<p>Finally, 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:
</p>
<pre> :record-001
a dcat:CatalogRecord ;