--- a/dcat/index.html Tue Jan 31 10:11:24 2012 -0500
+++ b/dcat/index.html Tue Jan 31 10:36:35 2012 -0500
@@ -191,19 +191,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 What goes here?@@@
<h2 id="terminology">Terminology</h2>
+@@@TODO 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 Dublin Core [@@@TODO Ref?@@@]. 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>
@@ -217,7 +216,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.
@@ -781,13 +780,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>