commented reference to 430

dcat/index.html

@@ -10,7 +10,7 @@
     <script>
 // @andrea-perego
 function popCrossRefs() {
-  $('a[href^="#"]').each( function () {
+  $('a[href^=430"#"]').each( function () {
     var href = $(this).attr('href');
     var id = href.trim().replace('#','');
     var text = $(this).text();
@@ -195,9 +195,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>
 
@@ -3046,7 +3046,7 @@ <h2>License and rights statements</h2>
 
     <h2>Versioning</h2>
 <p>Versioning can be applied to any of the first class citizens DCAT resources including Catalogs, Datasets, Distributions. The notion of version is very much related to the community practices,  data management policy and the workflows in place. It is up to data providers to decide when and why a new version should be released. For this reason, DCAT refrains from providing definitions or rules about when changes in a resource should turn in a new release of it. </p>
-<p>Versioning may be understood as involving relationships between datasets, which is supported by the <a href="#Property:resource_qualifiedRelation"><code>dcat:qualifiedRelation</code></a> and described in <a href="#qualified-relationship">Relationships between datasets and other resources</a>. The class <a href="#Class:Relationship"><code>dcat:Relationship</code></a> supports providing information about the relationship, and could be extended for versioning information.</p>  
+<p>Versioning may be understood as involving relationships between datasets, which is supported by the <a href="#Property:resource_qualifiedRelation"><code>dcat:qualifiedRelation</code></a> and described in <a href="#qualified-relationship">Relationships between datasets and other resources</a>. The class <a href="#Class:Relationship"><code>dcat:Relationship</code></a> supports providing information about the relationship, and could be extended for versioning information.</p>
 	<p class="issue" data-number="90">
         The need to be able to describe version relationships of datasets has been identified as a requirement to be satisfied in the revision of DCAT. Also see detailed requirements in
         <a href="https://github.com/w3c/dxwg/issues/89">Issue #89</a>,
@@ -3120,11 +3120,11 @@ <h2>DCAT Profiles</h2>
 <section id="security_and_privacy">
     <h2>Security and Privacy</h2>
     <p>
-    The DCAT vocabulary supports the attribution of data and metadata to various participants such as resource <a href="#Property:resource_creator">creators</a>, <a href="#Property:resource_publisher">publishers</a> and other parties or agents via <a href="#qualified-forms">qualified relations</a>, 
-	    and as such defines terms that may be related to personal information.  In addition, it also supports the association of <a href="#Property:resource_rights">rights</a> and <a href="#Property:resource_license">licenses</a> with cataloged Resources and Distributions. 
-	    These rights and licences could potentially include or reference sensitive information such as user and asset identifiers as <a href="https://www.w3.org/TR/odrl-vocab/#privacy-consideration">described</a> in [[!ODRL-VOCAB]].   Implementations that produce, maintain, publish or 
+    The DCAT vocabulary supports the attribution of data and metadata to various participants such as resource <a href="#Property:resource_creator">creators</a>, <a href="#Property:resource_publisher">publishers</a> and other parties or agents via <a href="#qualified-forms">qualified relations</a>,
+	    and as such defines terms that may be related to personal information.  In addition, it also supports the association of <a href="#Property:resource_rights">rights</a> and <a href="#Property:resource_license">licenses</a> with cataloged Resources and Distributions.
+	    These rights and licences could potentially include or reference sensitive information such as user and asset identifiers as <a href="https://www.w3.org/TR/odrl-vocab/#privacy-consideration">described</a> in [[!ODRL-VOCAB]].   Implementations that produce, maintain, publish or
 	    consume such vocabulary terms must take steps to ensure security and privacy considerations are addressed at the application level.
-    </p>  	
+    </p>
 </section>
 
 <section id="other-w3c-recommendations">