deleting stale Editorial Notes

w3c · Jan 9, 2023 · e15872f · e15872f
1 parent 947b496
commit e15872f
Showing 1 changed file with 16 additions and 24 deletions.
diff --git a/dcat/index.html b/dcat/index.html
@@ -20,9 +20,9 @@
 <body>
 
 <!-- Disclaimer -->
-    <aside class="ednote">
+    <!--aside class="ednote">
     <p>This document presents advancements in the discussion made on DCAT 3 within DXWG group. It extends DCAT 2 [[?VOCAB-DCAT-2]] with terms and guidelines on inverse properties, versioning,  and dataset series (see sections <a href="#inverse-properties"></a>, <a href="#dataset-versions"></a> and <a href="#dataset-series"></a>), and by including terms for specifying the checksum of a distribution (see <a href="#Property:distribution_checksum"></a> and <a href="#Class:Checksum"></a>).</p>
-    </aside>
+    </aside-->
 
 <aside class="note">
     <p>DCAT 3 supersedes DCAT 2 [[?VOCAB-DCAT-2]], but it does not make it obsolete. DCAT 3 maintains the DCAT namespace as its terms preserve backward compatibility with  DCAT 2. DCAT 3 relaxes constraints and adds new classes and properties, but these changes do not break the definition of previous terms.</p>
@@ -3233,9 +3233,9 @@ <h4>Property: checksum</h4>
 <th class="prop">Usage note:</th>
 <td>
 <p>The checksum is related to the download URL.</p>
-<aside class="ednote">
+<!--aside class="ednote">
 <p>This is the usage note in [[?DCAT-AP]]. To be decided if it should be adopted in DCAT.</p>
-</aside>
+</aside-->
 </td>
 </tr>
 </table>
@@ -4170,17 +4170,17 @@ <h2>Indicating common identifier types</h2>
 
     <h2>License and rights statements</h2>
 
-<aside class="ednote">
+<!--aside class="ednote">
 <p>The following NOTE should probably be dropped from DCAT3.</p>
-</aside>
+</aside-->
 
-  <aside class="note">
+  <!--aside class="note">
     <p>
     DCAT 1 handling of license and rights do not appear to satisfy all requirements [[?VOCAB-DCAT-1]].
     The recently completed W3C ODRL model [[?ODRL-MODEL]] and vocabulary [[?ODRL-VOCAB]] provide a rich language for describing many kinds of rights and obligations.
     In this section, we describe some patterns for linking DCAT Datasets and/or Distributions to suitable license and rights expressions.
   </p>
-  </aside>
+  </aside-->
 
   <p>
     Selecting the right way to express conditions for access to and re-use of resources can be complex.
@@ -4611,14 +4611,14 @@ <h2>Version types</h2>
 
 -->   
 
-<aside class="ednote">
+<!--aside class="ednote">
 <p>This is a new draft for discussion on versioning support in DCAT.</p>
 <p>Compared with the first draft in [[VOCAB-DCAT-3-20201217]], this section has been revised to focus specifically on versions derived from the revision of a resource, and by following the [[PAV]] approach for the specification of version chains and hierarchies - previous, next, current, last version.</p>
 <p>In particular, the introductory text has been revised according to the new scope, the section on version types has been removed, and a new section has been added to describe how to specify relationships between versions, including those concerning backward compatibility, originally included in <a href="#version-info"></a>.</p>
 <p>Moreover, <a href="#versioning-complementary-approaches">a new section</a> has been added at the end to compare the DCAT versioning approach with those used in OWL and [[?DCTERMS]].</p> 
 <p>The other sections include only editorial changes.</p>
 <p><strong>NB:</strong> All the properties described in this section are yet to be added to the RDF definition of DCAT.</p>
-</aside>
+</aside-->
 
 <p>The notion of <em>version</em> is often used as a generic term to denote some kind of relationship between a resource and a derived one. Examples, among others, include revisions, editions, adaptations, and translations.</p>
 
@@ -4672,7 +4672,7 @@ <h2>Version chains and hierarchies</h2>
 -->
 </ul>
 
-<aside class="ednote">
+<!--aside class="ednote">
 <p>An earlier working draft [[VOCAB-DCAT-3-20201217]] was making use of similar properties from [[DCTERMS]] and [[VOCAB-ADMS]], namely:</p>
 <ul>
 <li><code>dcterms:hasVersion</code> / <code>dcterms:isVersionOf</code>, for version hierarchies, and</li>
@@ -4685,7 +4685,7 @@ <h2>Version chains and hierarchies</h2>
 </ul>
 <p>Moreover, although the definitions of the [[VOCAB-ADMS]] properties states explicitly that they are meant to be used for "versions", they are subproperties of the corresponding terms in [[XHTML-VOCAB]], where they are used to link resources in a collection (e.g., the set of pages of a Web site). E.g., the definition of <a data-cite="XHTML-VOCAB#last"><code>xhv:last</code></a> reads as follows: <q>last refers to the last resource in a collection of resources.</q>.</p>
 <p>Based on that, in subsequent drafts, [[PAV]]-equivalent properties are used for versions, whereas the [[VOCAB-ADMS]] properties, and properties <code>dcterms:hasVersion</code> / <code>dcterms:isVersionOf</code> are not used.</p>
-</aside>
+</aside-->
 
 <p>Property <code>dcat:previousVersion</code> is used to build a version chain that can be navigated backward from a given version to the first one. This reflects the most typical use case - i.e., linking different versions published as distinct resources in a catalog.</p>
 
@@ -4839,18 +4839,10 @@ <h2>Version backward compatibility</h2>
 
 
 <h2>Version information</h2>
-<aside class="ednote">
+<!--aside class="ednote">
 <p>This draft proposes the definition of a new property <code>dcat:version</code>, to use instead of <code>owl:versionInfo</code> of the first draft, to complement the versioning properties defined in the DCAT namespace and illustrated in <a href="#version-history"></a> (see Issue <a href="https://github.com/w3c/dxwg/issues/1280">#1280</a>).</p>
-<!--
-<p>Issue <a href="https://github.com/w3c/dxwg/issues/1280">#1280</a> is kept open to provide a context for the latest changes and as a placeholder for further feedback.  
-</p>   
-<div class="issue" data-number="1280"></div>
--->
-<!--
-<p>Moreover, the specification of backward compatibility between versions has been moved to a separate section (<a href="#version-backward-compatibility"></a>).</p>
--->
 <p>Moreover, support to the specification of backward compatibility between versions has been removed (see Issue <a href="https://github.com/w3c/dxwg/issues/1258">#1258</a>).</p>
-</aside>
+</aside-->
 
 <p>Besides the relationships illustrated in the previous section, versioned resources may be associated with additional information, describing, e.g., their differences with the original resource (the version "delta"),  the version identifier, and release date.</p>
 
@@ -5010,11 +5002,11 @@ <h2>Complementary approaches to versioning</h2>
 
 <h2>Dataset series</h2>
 
-<aside class="ednote">
+<!--aside class="ednote">
 <p>This is a new draft for discussion on dataset series support in DCAT. Compared with the first draft in [[VOCAB-DCAT-3-20201217]], this section has been revised.</p>
 <p>A new class <code>dcat:DatasetSeries</code> is defined as suggested in Issue <a href="https://github.com/w3c/dxwg/issues/1272">#1272</a>. </p>
 <p>Only one property  <code>dcat:inSeries</code> linking the child datasets to dataset series is defined. The new property <code>dcat:inSeries</code> replaces the use of <code>dcterms:isPartOf</code> helping to distinguish between the composition in dataset series and  <a href="https://www.w3.org/TR/vocab-dcat-3/#examples-bag-of-files">Loosely structured catalog</a> (see Issue <a href="https://github.com/w3c/dxwg/issues/1307">#1307</a>). Finally, properties <code>adms:prev</code>, <code>adms:next</code>, and <code>adms:last</code> have been replaced by newly defined properties - <code>dcat:prev</code>, <code>dcat:next</code>, and <code>dcat:last</code> (see Issue <a href="https://github.com/w3c/dxwg/issues/1308">#1308</a>)).</p>
-</aside>
+</aside-->
 
 <p>With "dataset series" we refer to data, somehow interrelated, that are published separately. An example is budget data split by year and/or country, instead of being made available in a single dataset.</p>