--- a/dcat/index.html Tue Jan 31 16:36:48 2012 +0000
+++ b/dcat/index.html Tue Jan 31 16:39:03 2012 +0000
@@ -74,7 +74,18 @@
<hr />
<div id="abstract" class="introductory section">
<h2>Abstract</h2>
- <p>@@@ To Do @@@</p>
+ <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:
+<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
+<br /> @@@ TODO.jse: I don't understand why this point is important! @@@
+</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>
+<p>@@@ TODO.jse: Clarify? Anything more to add? @@@</p>
</div>
<div id="sotd" class="introductory section">
<h2>Status of This Document</h2>
@@ -87,7 +98,7 @@
signals its move to the Recommendations Track. DCAT was first
developed and published by DERI and enjoys widespread use at the time of
this publication. The <a href="http://vocab.deri.ie/dcat">original vocabulary</a>
- was further developed on the @@@eGov Interest Group's wiki@@@ before being brought onto the
+ was further developed on the <a href="http://www.w3.org/egov/">eGov Interest Group's wiki</a> before being brought onto the
Recommendation Track by the
<a href="http://www.w3.org/2011/gld/">Governmenet Linked Data Working Group</a>
which intends for it to become a Recommendation.
@@ -182,19 +193,18 @@
</ul>
<h2 id="intro">Introduction</h2>
-<p>This document does not prescribe any particular method of deploying data
-expressed in DCAT. There are many options, such as SPARQL endpoints, RDFa,
-RDF/XML, Turtle. Examples here use Turtle, but that's just because of Turtle's
-readability.</p>
+<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>
<h2 id="conformance">Conformance</h2>
+@@@ TODO.jse: What goes here? @@@
<h2 id="terminology">Terminology</h2>
+@@@ TODO.jse: What goes here? @@@
<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,
-in particular Dublin Core. DCAT itself defines a minimal set of classes and
+in particular <a href="http://dublincore.org/documents/dcmi-terms/">Dublin Core</a>. DCAT 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>
@@ -208,7 +218,7 @@
</table>
<h2 id="overview">Vocabulary Overview</h2>
-<p>DCAT is an RDF vocabulary to represent government data catalogs such as data.gov and data.gov.uk. DCAT defines three main classes:</p>
+<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.
@@ -319,7 +329,7 @@
</table>
<h3 id="Property:_publisher">Property: publisher</h3>
-<p>The entity responsible for making the catalogue online.</p>
+<p>The entity responsible for making the catalog online.</p>
<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/publisher">dcterms:publisher</a></th></tr></thead>
@@ -329,7 +339,7 @@
</table>
<h3 id="Property:_spatial.2Fgeographic_coverage">Property: spatial/geographic coverage></h3>
-<p>The geographical area covered by the catalogue.</p>
+<p>The geographical area covered by the catalog.</p>
<table class="definition">
<thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/spatial">dcterms:spatial</a></th></tr></thead>
<tbody>
@@ -772,13 +782,13 @@
</tbody>
</table>
-<h2 id="Extending_the_vocabulary">Extending the vocabulary</h2>
+<h2 id="Extending_the_vocabulary">Extending the DCAT vocabulary</h2>
<ul>
- <li> As with all RDF models, the model can be extended simply by using additional RDF properties anywhere. Catalog operators may choose from properties in existing vocabularies, or create their own custom vocabulary.</li>
- <li> Additional classes, from existing or new vocabularies, can also be used.</li>
- <li> Extensions used in a particular catalog should be documented to make users of the data aware of the additional available properties.</li>
+ <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>
+ <li> Additional classes, from existing or new vocabularies, may also be used.</li>
+ <li> Extensions used in a particular catalog should be documented to ensure that consumers of the data are aware of the additional available properties.</li>
<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>
+ <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>