From e1b3cb7141bec76f8baf5a688ce1f1ecc852cb91 Mon Sep 17 00:00:00 2001
From: Simon Cox <simon.cox@csiro.au>
Date: Wed, 24 Jul 2019 17:25:07 +1000
Subject: [PATCH] Correct 'eight' to 'six' _main classes_, add link to figure;
 Delete most commented sections (but not the ones that are links to the
 backlog)

---
 dcat/index.html | 336 ++----------------------------------------------
 1 file changed, 9 insertions(+), 327 deletions(-)

diff --git a/dcat/index.html b/dcat/index.html
index 75aea7b71..c8a1c0dd5 100644
--- a/dcat/index.html
+++ b/dcat/index.html
@@ -185,13 +185,6 @@ <h3>Non-normative namespaces</h3>
 </section>
 
 <section id="conformance">
-<!--
-    <aside class="note">
-      <p>
-        Modified from DCAT 2014 [[?VOCAB-DCAT-20140116]]
-      </p>
-    </aside>
--->
     <p>A data catalog conforms to DCAT if:</p>
     <ul>
         <li> Access to data is organized into datasets, distributions, and data-services. </li>
@@ -226,14 +219,11 @@ <h3>Non-normative namespaces</h3>
 
     <h2>Vocabulary overview</h2>
 
-<!--
-    <aside class="note"><p>Significantly extended from DCAT 2014 [[?VOCAB-DCAT-20140116]]</p></aside>
--->
-<section id="dcat-scope">
+    <section id="dcat-scope">
     <h3>DCAT scope</h3>
 
     <p>DCAT is an RDF vocabulary for representing data catalogs.
-      DCAT is based around eight main classes:</p>
+      DCAT is based around six main classes (<a href="#UML_DCAT_All_Attr"></a>):</p>
     <ul>
         <li>
           <a href="#Class:Catalog"><code>dcat:Catalog</code></a> represents a catalog, which is a dataset in which each individual item is a metadata record describing some resource; the scope of <code>dcat:Catalog</code> is collections of metadata about <b>datasets</b> or <b>data services</b>.
@@ -256,14 +246,6 @@ <h3>DCAT scope</h3>
           <a href="#Class:Data_Service"><code>dcat:DataService</code></a> represents a data service.
           A data service is a collection of operations accessible through an interface (<abbr title="Application Programming Interface">API</abbr>) that provide access to one or more datasets or data processing functions.
         </li>
-        <!--
-          <li>
-            <a href="#Class:DataTransformationService"><code>dcat:DataTransformationService</code></a> represents a service that can transform a dataset, e.g. spatial coordinate transformation; interpolation or resampling of a dataset.
-          </li>
-        <li>
-          <a href="#Class:Discovery_Service"><code>dcat:DiscoveryService</code></a> represents a description of a kind of data distribution service that provides access to one or more catalogs to support discovery functions.
-        </li>
-      -->
         <li>
           <a href="#Class:Catalog_Record"><code>dcat:CatalogRecord</code></a> represents a metadata item in the catalog, primarily concerning the registration information, such as who added the item and when.
         </li>
@@ -666,13 +648,6 @@ <h2>Vocabulary specification</h2>
 
     <section id="RDF-representation">
         <h3>RDF representation</h3>
-<!--
-        <p class="ednote">
-            The DCAT RDF representation is modularized into several files or graphs to help users access a version of DCAT with only the alignments that they need.
-            This mechanism can also be used to capture different levels of axiomatization, though the status of such proposals has not been finalized.
-            See <a href="https://github.com/w3c/dxwg/issues/134">Issue #134</a> and the issues enumerated below.
-        </p>
--->
         <!--NoBacklogNorCR div class="issue" data-number="65">
             <p>
                 Guidance on the use DCAT in a weakly-axiomatized environment, such as schema.org, has been identified as a requirement to be satisfied in this revision of DCAT.
@@ -966,13 +941,6 @@ <h3>Class: Cataloged Resource</h3>
             The need to be able to describe the business or project context related to production of a cataloged resource has been identified as a requirement to be satisfied in the revision of DCAT.
         </p-->
 
-        <!--
-        - this issue already closed - prov:wasGeneratedBy added to dcat:Dataset (but not to dcat:Resource) -
-        <p class="issue" data-number="77">
-            The need to be able to link a cataloged resource with the business or project context of its production has been identified as a requirement to be satisfied in the revision of DCAT.
-        </p>
-        -->
-
         <table class="definition">
             <thead><tr><th>RDF Class:</th><th><a href="http://www.w3.org/ns/dcat#Resource">dcat:Resource</a></th></tr></thead>
             <tbody>
@@ -1805,11 +1773,7 @@ <h4>Property: spatial resolution</h4>
 
         <section id="Property:dataset_temporal">
             <h4>Property: temporal coverage</h4>
-<!--
-            <p class="issue" data-number="85">
-                The need to be able to describe the temporal coverage of a dataset in a structured way has been identified as a requirement to be satisfied in the revision of DCAT.
-            </p>
--->
+
             <table class="definition">
                 <thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/temporal">dct:temporal</a></th></tr></thead>
                 <tbody>
@@ -1889,13 +1853,6 @@ <h4>Property: was generated by</h4>
             </p>
         </section>
 
-
-        <!--
-        <p class="issue" data-number="63">
-            The need to be able to link a dataset with publications arising from it has been identified as a requirement to be satisfied in the revision of DCAT.
-        </p>
-        -->
-
     </section> <!-- end class Dataset -->
 
 
@@ -2423,119 +2380,6 @@ <h4>Property: serves dataset</h4>
         </section>
 
     </section> <!-- end class DataService -->
-    <!--
-    <section id="Class:Data_Distribution_Service">
-        <h3>Class: Data Distribution Service</h3>
-
-        <aside class="note">
-          <p>
-            New class added in this revision of DCAT.
-          </p>
-        </aside>
-
-        <p>The following properties are recommended for use on this class:
-            <a href="#Property:datadistributionservice_servesdataset">servesDataset</a>,
-        </p>
-        <p>The following properties are inherited from the super-class <a href="#Class:Data_Service"><code>dcat:DataService</code></a>:
-            <a href="#Property:data_service_endpoint_description">endpointDescription</a>,
-            <a href="#Property:data_service_endpoint_url">endpointURL</a>,
-            <a href="#Property:data_service_license">license</a>,
-            <a href="#Property:data_service_access_rights">access rights</a>
-        </p>
-        <p>The following properties are are inherited from the super-class <a href="#Class:Resource"><code>dcat:Resource</code></a>:
-            <a href="#Property:resource_conforms_to">conforms to</a>,
-            <a href="#Property:resource_contact_point">contact point</a>,
-            <a href="#Property:resource_creator">creator</a>,
-            <a href="#Property:resource_description">description</a>,
-            <a href="#Property:resource_identifier">identifier</a>,
-            <a href="#Property:resource_keyword">keyword/tag</a>,
-            <a href="#Property:resource_landing_page">landing page</a>,
-            <a href="#Property:resource_language">resource language</a>,
-            <a href="#Property:resource_relation">relation</a>,
-            <a href="#Property:resource_qualified_relation">qualified relation</a>,
-            <a href="#Property:resource_publisher">publisher</a>,
-            <a href="#Property:resource_release_date">release date</a>,
-            <a href="#Property:resource_theme">theme/category</a>,
-            <a href="#Property:resource_title">title</a>,
-            <a href="#Property:resource_type">type/genre</a>,
-            <a href="#Property:resource_update_date">update/modification date</a>,
-            <a href="#Property:resource_qualified_attribution">qualified attribution</a>
-        </p>
-
-
-        <table class="definition">
-            <thead><tr><th>RDF Class:</th><th><a href="http://www.w3.org/ns/dcat#DataDistributionService">dcat:DataDistributionService</a></th></tr></thead>
-            <tbody>
-            <tr><td class="prop">Definition:</td><td>A site or end-point that provides access to distributions of existing datasets or subsets of datasets</td></tr>
-            <tr><td class="prop">Sub-class of:</td><td><a href="#Class:Data_Service">dcat:DataService</a></td></tr>
-            <tr><td class="prop">Usage note:</td><td>A DataDistributionService is usually bound to one or more specified Datasets, which are indicated by the <a href="#Property:datadistributionservice_servesdataset">dcat:servesDataset</a> property.</td></tr>
-            <tr><td class="prop">Usage note:</td><td>A <i>data discovery service</i> supports discovery of data, usually by providing access to a Catalog. In that context the data discovery service can be understood as a DataDistributionService in which least one <a href="#Class:Catalog">dcat:Catalog</a> appears as the object of its <a href="#Property:datadistributionservice_servesdataset">dcat:servesDataset</a> property</td></tr>
-            </tbody>
-        </table>
-
-        <section id="Property:datadistributionservice_servesdataset">
-            <h4>Property: serves dataset</h4>
-            <table class="definition">
-                <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#servesdataset">dcat:servesDataset</a></th></tr></thead>
-                <tbody>
-                <tr><td class="prop">Definition:</td><td>A collection of data that this DataDistributionService can distribute</td></tr>
-                <tr><td class="prop">Range:</td><td><a href="#Class:Dataset"><code>dcat:Dataset</code></a></td></tr>
-                </tbody>
-            </table>
-        </section>
-
-    </section>
-   end class DataDistributionService -->
-
-<!--
-    <section id="Class:Discovery_Service">
-        <h3>Class: Discovery Service</h3>
-        <p>The following properties are inherited from the super-class <a href="#Class:DataService"><code>dcat:DataService</code></a>:
-            <a href="#Property:data_service_endpoint_description">endpointDescription</a>,
-            <a href="#Property:data_service_endpoint_url">endpointURL</a>,
-            <a href="#Property:data_service_license">license</a>,
-            <a href="#Property:data_service_access_rights">access rights</a>
-        </p>
-        <p>The following properties are are inherited from the super-class <a href="#Class:Resource"><code>dcat:Resource</code></a>:
-            <a href="#Property:resource_conforms_to">conforms to</a>,
-            <a href="#Property:resource_contact_point">contact point</a>,
-            <a href="#Property:resource_creator">creator</a>,
-            <a href="#Property:resource_description">description</a>,
-            <a href="#Property:resource_identifier">identifier</a>,
-            <a href="#Property:resource_keyword">keyword/tag</a>,
-            <a href="#Property:resource_landing_page">landing page</a>,
-            <a href="#Property:resource_language">resource language</a>,
-            <a href="#Property:resource_relation">relation</a>,
-            <a href="#Property:resource_qualified_relation">qualified relation</a>,
-            <a href="#Property:resource_publisher">publisher</a>,
-            <a href="#Property:resource_release_date">release date</a>,
-            <a href="#Property:resource_theme">theme/category</a>,
-            <a href="#Property:resource_title">title</a>,
-            <a href="#Property:resource_type">type/genre</a>,
-            <a href="#Property:resource_update_date">update/modification date</a>,
-            <a href="#Property:resource_qualified_attribution">qualified attribution</a>
-        </p>
-
-
-        <table class="definition">
-            <thead><tr><th>RDF Class:</th><th><a href="http://www.w3.org/ns/dcat#DiscoveryService">dcat:DiscoveryService</a></th></tr></thead>
-            <tbody>
-            <tr><td class="prop">Definition:</td><td>A site or end-point that supports data discovery, usually by providing access to catalogs</td></tr>
-            <tr><td class="prop">Sub-class of:</td><td><a href="#Class:DataDistributionService">dcat:DataDistributionService</a></td></tr>
-            <tr><td class="prop">Usage note:</td><td>At least one <a href="#Class:Catalog">dcat:Catalog</a> must be provided as the object of a <a href="http://www.w3.org/ns/dcat#servesDataset">dcat:servesDataset property</a></td></tr>
-            <tr><td class="prop">See also:</td><td> </td></tr>
-            </tbody>
-        </table>
-
-        <aside class="note">
-          <p>
-            New class added in this revision of DCAT.
-          </p>
-        </aside>
-
-    </section>
-end class DiscoveryService -->
-
 
     <section id="Class:Concept_Scheme">
         <h3>Class: Concept Scheme</h3>
@@ -2692,8 +2536,6 @@ <h3>Class: Role</h3>
 
     </section> <!-- end class Role -->
 
-<!-- START: Issue https://github.com/w3c/dxwg/issues/85: Implementation of proposed properties -->
-
     <section id="Class:Period_of_Time">
         <h3>Class: Period of Time</h3>
 
@@ -2833,10 +2675,6 @@ <h4>Property: end</h4>
 
     </section>
 
-<!-- END: Issue https://github.com/w3c/dxwg/issues/85: Implementation of proposed properties -->
-
-<!-- START: Issue https://github.com/w3c/dxwg/issues/83: Implementation of Proposals 1 and 2.a -->
-
     <section id="Class:Location">
         <h3>Class: Location</h3>
 
@@ -2955,8 +2793,6 @@ <h4>Property: centroid</h4>
 
     </section>
 
-<!-- END: Issue https://github.com/w3c/dxwg/issues/83: Implementation of Proposals 1 and 2.a -->
-
 </section>
 
 
@@ -3089,24 +2925,6 @@ <h2>License and rights statements</h2>
     Selecting the right way to express conditions for access to and re-use of resources can be complex.
     Implementers should always seek legal advice before deciding which conditions apply to the resource being described.
   </p>
-<!--
-  <aside class="ednote" title="Original text">
-  <p>
-    This specification distinguishes three main situations: one where a statement is associated with the resource that is explicitly declared as a 'license';
-    a second where the statement is not explicitly declared as a 'license'; and a third where the conditions are explicitly expressed as an ODRL Policy.
-  </p>
-  <p>The following approach is recommended:</p>
-    <ol>
-      <li>use <a data-cite="?DCTERMS#terms-license"><code>dct:license</code></a> to refer to well-known licenses such as <a href="https://creativecommons.org/share-your-work/licensing-types-examples/">those defined by Creative Commons</a></br>
-      The object of <code>dct:license</code>, a <a data-cite="?DCTERMS#terms-LicenseDocument"><code>dct:LicenseDocument</code></a>, is "A legal document giving official permission to do something with a Resource."</li>
-      <li>use <a data-cite="?DCTERMS#terms-rights"><code>dct:rights</code></a> to refer to rights statements that are not licenses, such as copyright statements</br>
-      The object of <code>dct:rights</code>, a <a data-cite="?DCTERMS#terms-RightsStatement"><code>dct:RightsStatement</code></a>, is "A statement about the intellectual property rights (IPR) held in or over a Resource, a legal document giving official permission to do something with a resource, or a statement about access rights."
-      This is more general than a <a data-cite="?DCTERMS#terms-LicenseDocument"><code>dct:LicenseDocument</code></a> and therefore should be used if it the statement contains more general information about rights.</li>
-      <li>use <a href="https://www.w3.org/TR/odrl-vocab/#term-hasPolicy"><code>odrl:hasPolicy</code></a> for linking to <a href="https://www.w3.org/TR/odrl-vocab/#term-Policy">ODRL policies</a></br>
-      The Open Digital Rights Language (ODRL) is a policy expression language that provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for representing statements about usage (i.e. permissions, prohibitions, and obligations) of content and services.</li>
-    </ol>
-  </aside>
--->
   <p>
     This specification distinguishes three main situations:
     one where a statement is associated with a resource that is explicitly declared as a 'license';
@@ -3126,9 +2944,7 @@ <h2>License and rights statements</h2>
     <ol>
       <li>
         <p>use <a data-cite="?DCTERMS#terms-license"><code>dct:license</code></a> to refer to licenses;</p>
-<!--
-      <p>The object of <code>dct:license</code>, a <a data-cite="?DCTERMS#terms-LicenseDocument"><code>dct:LicenseDocument</code></a>, is "A legal document giving official permission to do something with a Resource."</p>
--->
+
         <aside class="note">
           <p>
           For interoperability, it is recommended to use canonical URIs of well-known licenses such as <a href="https://creativecommons.org/share-your-work/licensing-types-examples/">those defined by Creative Commons</a>.
@@ -3137,9 +2953,7 @@ <h2>License and rights statements</h2>
       </li>
       <li>
         <p>use <a data-cite="?DCTERMS#terms-accessRights"><code>dct:accessRights</code></a>  to express statements concerning only access rights (e.g., whether data can be accessed by anyone or just by authorized parties);</p>
-<!--
-        <p>The object of <code>dct:accessRights</code> is a <code>dct:RightsStatement</code> providing "Information about who can access the resource or an indication of its security status."</p>
--->
+
         <aside class="note">
           <p>
           Access rights can also be expressed as code lists / taxonomies. Examples include the access rights code list  [[?MDR-AR]] used in [[?DCAT-AP]] and the <a href="http://purl.org/eprint/accessRights/">Eprints Access Rights Vocabulary Encoding Scheme</a>.
@@ -3148,10 +2962,7 @@ <h2>License and rights statements</h2>
       </li>
       <li>
         <p>use <a data-cite="?DCTERMS#terms-rights"><code>dct:rights</code></a> for all the other types of rights statements - those which are not covered by <code>dct:license</code> and <code>dct:accessRights</code>, such as copyright statements.</p>
-<!--
-        <p>The object of <code>dct:rights</code>, a <a data-cite="?DCTERMS#terms-RightsStatement"><code>dct:RightsStatement</code></a>, is "A statement about the intellectual property rights (IPR) held in or over a Resource, a legal document giving official permission to do something with a resource, or a statement about access rights."
-      This is more general than a <a data-cite="?DCTERMS#terms-LicenseDocument"><code>dct:LicenseDocument</code></a> and therefore should be used if it the statement contains more general information about rights.</p>
--->
+
         <aside class="note">
           <p>
           A more sophisticated approach to express rights, based on and extending [[?DCTERMS]], is provided by the Open Data Rights Statement Vocabulary (ODRS) [[?ODRS]], which defines properties for specifying, among others, copyright statements and copyright notices.
@@ -3977,31 +3788,6 @@ <h3>Relationships between datasets and other resources</h3>
 
 </section>
 
-<!-- Remove separate section on Provenance Patterns - highly incomplete
-<section id="prov-patterns" class="informative">
-
-    <h2>Provenance patterns</h2>
-    <p class="ednote">
-        In this section it is planned to describe patterns for the use of the [[!PROV-O]] vocabulary to support the various provenance-related requirements.
-  A number of requirements identify the need to provide better support for Dataset and Record provenance - see
-        <a href="https://github.com/w3c/dxwg/issues/77">Issue #78</a>,
-        <a href="https://github.com/w3c/dxwg/issues/128">Issue #128</a>,
-        <a href="https://github.com/w3c/dxwg/issues/77">Issue #77</a>,
-        <a href="https://github.com/w3c/dxwg/issues/76">Issue #76</a>,
-        <a href="https://github.com/w3c/dxwg/issues/71">Issue #71</a>,
-        <a href="https://github.com/w3c/dxwg/issues/66">Issue #66</a>,
-        <a href="https://github.com/w3c/dxwg/issues/63">Issue #63</a>.
-        </p>
-
-
-    Many of the requirements can be satisfied by using capabilities from the [[?PROV-O]] ontology,
-    in particular by treating <a href="#Class:Resource"><code>dcat:Resource</code></a> and/or <a href="#Class:Catalog_Record"><code>dcat:CatalogRecord</code></a> a sub-class of <a href="http://www.w3.org/ns/prov#Entity"><code>prov:Entity</code></a>.
-    See <a href="https://github.com/w3c/dxwg/issues/128">Issue #128</a> for the relevant discussion. A preliminary <a href="https://w3c.github.io/dxwg/dcat/rdf/dcat-prov.ttl">alignment of DCAT with PROV-O is available</a>.
-    See the wiki page on <a href="https://github.com/w3c/dxwg/wiki/Provenance-patterns">Provenance Patterns</a> for more discussion.
-
-</section>
--->
-
 <section id="profiles" class="informative">
 
     <h2>DCAT Profiles</h2>
@@ -4049,17 +3835,8 @@ <h2>Acknowledgments</h2>
   <p>The editors also gratefully acknowledge the chairs of this Working Group: Karen Coyle, Caroline Burle and Peter Winstanley &mdash; and staff contacts Phil Archer and Dave Raggett.</p>
 
 </section>
-<!--
-<section class="appendix informative" id="alignments">
 
-    <h2>Alignment with other general purpose metadata vocabularies</h2>
-    <aside class="note">
-      <p>
-        See the issues on <a href="https://github.com/w3c/dxwg/labels/alignment">Alignments and Crosswalks</a> for more discussion.
-    </p>
-    </aside>
--->
-    <section id="dcat-sdo" class="appendix informative">
+<section id="dcat-sdo" class="appendix informative">
     
         <h2>Alignment with Schema.org</h2>
         
@@ -4109,7 +3886,6 @@ <h2>Alignment with Schema.org</h2>
             <thead>
             <tr>
                 <th style="text-align: right">DCAT element</th>
-                <!-- <th style="text-align: center">mapping property</th> -->
                 <th>target element from schema.org</th>
             </tr>
             </thead>
@@ -4127,9 +3903,9 @@ <h2>Alignment with Schema.org</h2>
                 <td>sdo:description</td>
             </tr>
             <tr>
-                <td style="text-align: right">dcat:keyword</td>
-                <td>sdo:keywords <br/>
+                <td style="text-align: right">dcat:keyword <br/>
                   <em>dcat:keyword is singular, sdo:keywords is plural</em></td>
+                <td>sdo:keywords</td>
             </tr>
             <tr>
                 <td style="text-align: right">dcat:theme</td>
@@ -4268,79 +4044,6 @@ <h2>Alignment with Schema.org</h2>
 
     </section>
 
-<!-- this will not happen in DCAT 2
-    <section id="dcat-prov-o" class="informative">
-        <h3>PROV-O</h3>
-            An alignment of DCAT with PROV-O [[?PROV-O]] is being prepared, and has been discussed in <a href="https://github.com/w3c/dxwg/issues/128">Issue #128</a>.
-      A <a href="https://w3c.github.io/dxwg/dcat/rdf/dcat-prov.ttl">provisional version</a> is available.
-
-    </section>
--->
-<!--
-</section>
--->
-<!-- alignments section removed due to (a) lack of resources to complete development and documentation (b) they belong in other documents anyway
-
-<section class="appendix" id="alignments-domains">
-  <h2>Alignment with external metadata vocabularies</h2>
-
-<p>
-  This annex lists some (planned) alignments between DCAT and some metadata vocabularies that are oriented towards particular applications and domains.
-</p>
-
-  <section id="dcat-dats" class="informative">
-      <h3>DATS</h3>
-      <p class="issue" data-number="149">
-          An alignment of DCAT with DATS [[?DATS]] is being considered.
-      </p>
-
-  </section>
-
-  <section id="dcat-hcls" class="informative">
-      <h3>HCLS</h3>
-      <p class="issue" data-number="150">
-          An alignment of DCAT with HCLS [[?HCLS-Dataset]] is being prepared.
-      </p>
-
-  </section>
-
-  <section id="dcat-iso-19115" class="informative">
-      <h3>ISO 19115</h3>
-      <p class="issue" data-number="151">
-          An alignment of DCAT with ISO 19115 [[?ISO-19115-1]] is being prepared.
-      </p>
-
-  </section>
-
-  <section id="dcat-datacite" class="informative">
-      <h3>Datacite</h3>
-      <p class="issue" data-number="152">
-          An alignment of DCAT with Datacite metadata schema [[?DataCite]] is being prepared.
-      </p>
-
-  </section>
-
-  <section id="dcat-ddi" class="informative">
-      <h3>DDI</h3>
-      <p class="issue" data-number="164">
-          An alignment of DCAT with DDI [[?DDI]] is being prepared.
-      </p>
-
-  </section>
-
-</section>
--->
-
-<!--
-<section class="appendix" id="issue-summary">
-<aside class="note">
-  <p>
-    All currently open issues are available at: <a href="https://github.com/w3c/dxwg/labels/dcat">https://github.com/w3c/dxwg/labels/dcat</a>.
-</p>
-</aside>
-</section>
--->
-
 <section id="collection-of-examples" class="appendix informative">
   <h2>Examples</h2>
   <section id="examples-bag-of-files">
@@ -4804,16 +4507,7 @@ <h3>Compressed and packaged distributions</h3>
         </p>
 
   </section>
-<!--
-  <section id="more-examples-needed">
-      <h3>More examples needed</h3>
-
-      <p class="ednote">
-          This section will contain more examples on the use of DCAT.
-      </p>
 
-  </section>
--->
 </section>
 
 
@@ -4948,18 +4642,6 @@ <h3>Changes since the W3C Recommendation of 16 January 2014</h3>
 See <a href="https://github.com/w3c/dxwg/issues/172">Issue #172</a>, <a href="https://github.com/w3c/dxwg/issues/56">Issue #56</a>, <a href="https://github.com/w3c/dxwg/issues/432">Issue #432</a>, <a href="https://github.com/w3c/dxwg/issues/821">Issue #821</a>.
 </li>
 
-<!--
-<li>
-<a href="#Class:Data_Distribution_Service">Class: Data distribution service</a>: In DCAT 2014 [[?VOCAB-DCAT-20140116]] the scope of a <a href="#Class:Catalog"><code>dcat:Catalog</code></a> was limited to Datasets. The new class <code>dcat:DataDistributionService</code> has been added to support cataloging of data distribution services - see <a href="https://github.com/w3c/dxwg/issues/172">Issue #172</a> and <a href="https://github.com/w3c/dxwg/issues/56">Issue #56</a>.
-</li>
--->
-
-<!--
-<li>
-<a href="#Class:Discovery_Service">Class: Discovery service</a>: In DCAT 2014 [[?VOCAB-DCAT-20140116]] the scope of a <a href="#Class:Catalog"><code>dcat:Catalog</code></a> was limited to Datasets. The new class <code>dcat:DiscoveryService</code> has been added to support cataloging of data discovery services. See <a href="https://github.com/w3c/dxwg/issues/172">Issue #172</a>.
-</li>
--->
-
 <li><a href="#Class:Dataset">Class: Dataset</a>:
 In DCAT 2014 [[?VOCAB-DCAT-20140116]] <a href="#Class:Dataset"><code>dcat:Dataset</code></a> was a sub-class of <a href="http://purl.org/dc/dcmitype/Dataset"><code>dctype:Dataset</code></a>, which is a term of the <a data-cite="?DCTERMS#section-7">DCMI Types vocabulary</a> [[!DCTERMS]]. This relationship has been removed in the revised DCAT vocabulary. 
 See <a href="https://github.com/w3c/dxwg/issues/98">Issue #98</a>.