--- a/dcat/index.html	Thu Dec 20 14:49:02 2012 +0000
+++ b/dcat/index.html	Thu Jan 31 12:57:59 2013 +0000
@@ -76,10 +76,28 @@
 </section>
 
 <section id="conformance">
+A data catalog conforms to DCAT if:
 <ul>
-<li><i>DCAT compliance</i> means that a provider uses a subset of the DCAT vocabulary when publishing catalog and dataset metadata. This is likely to be the common case.</li>
-<li><i>DCAT conformance</i> means that a provider uses the entire DCAT vocabulary when publishing catalog and dataset metadata.</li>
+<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>
 <h2 id="ns">Namespaces</h2>