--- a/dcat/index.html Sat Mar 09 16:48:51 2013 +0000
+++ b/dcat/index.html Sat Mar 09 16:51:02 2013 +0000
@@ -96,6 +96,31 @@
</table>
</section>
+<section id="conformance">
+A data catalog conforms to DCAT if:
+<ul>
+<li> It is organized into datasets and distributions.</li>
+
+<li> An RDF description of the catalog itself and its datasets and distributions is available (but the choice of
+RDF syntaxes, access protocols, and access policies is not mandated by this specification).</li>
+
+<li> The contents of all metadata fields that are held in the catalog, and that contain data about the catalog itself and its dataset and distributions, are included in this RDF description, expressed using the appropriate classes and properties from DCAT, except where no such class or property exists.</li>
+
+<li> All classes and properties defined in DCAT are used in a way consistent with the semantics declared in this specification.</li>
+
+<li>DCAT-compliant catalogs MAY include additional non-DCAT metadata fields and additional RDF data in the catalog's RDF description.</li>
+</ul>
+
+A <strong>DCAT profile</strong> is a specification for data catalogs that adds additional constraints to DCAT. A data catalog that conforms to the profile also conforms to DCAT. Additional constraints in a profile MAY include:
+<ul>
+<li> A minimum set of required metadata fields </li>
+<li> Classes and properties for additional metadata fields not covered in DCAT</li>
+<li> Controlled vocabularies or URI sets as acceptable values for properties</li>
+<li> Requirements for specific access mechanisms (RDF syntaxes, protocols) to the catalog's RDF description</li>
+</ul>
+
+</section>
+
<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>
@@ -682,7 +707,7 @@
<tr><td class="prop">Range:</td><td><a href="http://xmlns.com/foaf/0.1/Document">foaf:Document</a></td></tr>
<tr><td class="prop">Usage note:</td><td>
If the distribution(s) are accessible only through a landing page
- (i.e. direct download URLs are not known), then the landing page link SHOULD be duplicated as accessURL on a distribution. (see <a href="#example-landing-page">example 3.4</a>)
+ (i.e. direct download URLs are not known), then the landing page link SHOULD be duplicated as accessURL on a distribution. (see <a href="#example-landing-page">example 4.4</a>)
</td></tr>
</tbody>
</table>
@@ -776,7 +801,7 @@
<tr><td class="prop">Usage note:</td><td><ul> <li>the value is a URL.</li>
<li>
If the distribution(s) are accessible only through a landing page
- (i.e. direct download URLs are not known), then the landing page link SHOULD be duplicated as accessURL on a distribution. (see <a href="#example-landing-page">example 3.4</a>)
+ (i.e. direct download URLs are not known), then the landing page link SHOULD be duplicated as accessURL on a distribution. (see <a href="#example-landing-page">example 4.4</a>)
</li></ul>
</td></tr>
<tr><td class="prop">See also</td><td><a href="#Property:distribution_downloadurl">distribution download URL</a></td></tr>
@@ -866,30 +891,5 @@
</section>
-<section id="conformance">
-A data catalog conforms to DCAT if:
-<ul>
-<li> It is organized into datasets and distributions.</li>
-
-<li> An RDF description of the catalog itself and its datasets and distributions is available (but the choice of
-RDF syntaxes, access protocols, and access policies is not mandated by this specification).</li>
-
-<li> The contents of all metadata fields that are held in the catalog, and that contain data about the catalog itself and its dataset and distributions, are included in this RDF description, expressed using the appropriate classes and properties from DCAT, except where no such class or property exists.</li>
-
-<li> All classes and properties defined in DCAT are used in a way consistent with the semantics declared in this specification.</li>
-
-<li>DCAT-compliant catalogs MAY include additional non-DCAT metadata fields and additional RDF data in the catalog's RDF description.</li>
-</ul>
-
-A <strong>DCAT profile</strong> is a specification for data catalogs that adds additional constraints to DCAT. A data catalog that conforms to the profile also conforms to DCAT. Additional constraints in a profile MAY include:
-<ul>
-<li> A minimum set of required metadata fields </li>
-<li> Classes and properties for additional metadata fields not covered in DCAT</li>
-<li> Controlled vocabularies or URI sets as acceptable values for properties</li>
-<li> Requirements for specific access mechanisms (RDF syntaxes, protocols) to the catalog's RDF description</li>
-</ul>
-
-</section>
-
</body></html>