Merge pull request #871 from w3c/dcat-commenting-NoBacklogNorCRissues…

…-riccardo

Dcat commenting references to issues that are not included  in the backlog nor CR

dcat/index.html

@@ -209,9 +209,9 @@ <h2 >Namespaces</h2>
         <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>
-    <p class="issue" data-number="430">
+    <!--NoBacklogNorCR p class="issue" data-number="430">
         The requirement for a DCAT profile to conform to all of DCAT is under discussion.
-    </p>
+    </p-->
 
 </section>
 
@@ -617,22 +617,22 @@ <h3>RDF representation</h3>
             See <a href="https://github.com/w3c/dxwg/issues/134">Issue #134</a> and the issues enumerated below.
         </p>
 
-        <div class="issue" data-number="65">
+        <!--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.
             </p>
             <p>
                 An <a href="https://raw.githubusercontent.com/w3c/dxwg/gh-pages/dcat/rdf/dcat-schema.ttl">RDF graph containing a proposed alignment of DCAT with schema.org</a> is available. Comments on this alignment are invited.
             </p>
-        </div>
+        </div-->
 
         <p class="issue" data-number="105">
             The use of guarded constraints (existence, cardinality, range-type) to control the use of the recommended properties in the context of a class is being considered as part of the revision of DCAT.
         </p>
 
-        <p class="issue" data-number="110">
+        <!--NoBacklogNorCR p class="issue" data-number="110">
             The axiomatization of DCAT 2014 used global domain and range constraints for many of the properties defined in the DCAT namespace [[?VOCAB-DCAT-20140116]]. This makes quite strong ontological commitments, some of which are now being reconsidered - see individual issues noted inline below.
-        </p>
+        </p-->
 
         <p>The (revised) DCAT vocabulary is <a href="https://github.com/w3c/dxwg/tree/gh-pages/dcat/rdf/">available in RDF</a>.
             The primary artefact <a href="https://raw.githubusercontent.com/w3c/dxwg/gh-pages/dcat/rdf/dcat.ttl">dcat.ttl</a> is a serialization of the core DCAT vocabulary.
@@ -649,9 +649,9 @@ <h3>RDF representation</h3>
             </li>
         </ol>
 
-        <p class="issue" data-number="144">
+        <!--NoBacklogNorCR p class="issue" data-number="144">
             The implementation of a DCAT 2014 profile of the revised DCAT is being considered.
-        </p>
+        </p -->
 
 
 
@@ -1883,9 +1883,9 @@ <h4>Property: hasPolicy</h4>
         <section id="Property:distribution_accessurl">
             <h4>Property: access address</h4>
 
-            <p class="issue" data-number="145">
+            <!--NoBacklogNorCR p class="issue" data-number="145">
                 The granularity of <code>dcat:accessURL</code> is being re-considered to provide different usages for list and item endpoints as well as supporting the declaration of different profiles (for list results and data payload).
-            </p>
+            </p-->
 
             <table class="definition">
                 <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#accessURL">dcat:accessURL</a></th></tr></thead>