Dataset series v2 (issue 1272)

dcat/index.html

@@ -265,7 +265,11 @@ <h3>DCAT scope</h3>
           <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>
     </ul>
-
+    <aside class="ednote" title="Class Diagram need to be updated">
+              <p>
+                  Add the class <code>dcat:DatasetSeries</code> and properties.
+              </p>
+           </aside>
     <figure id="UML_DCAT_All_Attr">
       <img alt="UML model of DCAT classes and properties" src="./images/DCAT-summary-all-attributes.png">
       <figcaption>
@@ -1872,6 +1876,94 @@ <h4>Property: was generated by</h4>
         </section>
 
     </section> <!-- end class Dataset -->
+<section id="Class:DatasetSeries">
+
+        <h3>Class: DatasetSeries</h3>
+
+        <aside class="note">
+            <p>
+              Class added in DCAT 3, see <a href="https://github.com/w3c/dxwg/issues/1272">Issue #1272</a>.
+            </p>
+
+        </aside>
+
+        <p>The following property is specific to this class:
+            <a href="#Property:datasetseries_has_part">hasPart</a>.
+
+        </p>
+        <p>The following properties of the super-class <a href="#Class:Resource"><code>dcat:Resource</code></a> and <a href="#Class:Dataset"><code>dcat:Dataset</code></a>  are also available for use:
+            <a href="#Property:resource_access_rights">access rights</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_has_policy">has policy</a>,
+            <a href="#Property:resource_identifier">identifier</a>,
+            <a href="#Property:resource_is_referenced_by">is referenced by</a>,
+            <a href="#Property:resource_keyword">keyword/tag</a>,
+            <a href="#Property:resource_landing_page">landing page</a>,
+            <a href="#Property:resource_license">license</a>,
+            <a href="#Property:resource_language">resource language</a>,
+            <a href="#Property:resource_relation">relation</a>,
+            <a href="#Property:resource_rights">rights</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>. 
+            <a href="#Property:dataset_frequency">frequency</a>,
+            <a href="#Property:dataset_spatial">spatial/geographic coverage</a>,
+            <a href="#Property:dataset_spatial_resolution">spatial resolution</a>,
+            <a href="#Property:dataset_temporal">temporal coverage</a>,
+            <a href="#Property:dataset_temporal_resolution">temporal resolution</a>,
+            <a href="#Property:dataset_was_generated_by">was generated by</a>.
+        </p>
+        <aside class="issue" title="Editorial questions">
+              <p>
+                  Does being ADMS a non-normative namespace prevent to list <code>adms:next</code>, <code>adms:prev</code> in this section?
+            </p>
+            <p>
+             Should restate the properties whose values are involved in dataset series inheritance e.g. <code>dct:issued</code>,<code>dct:spatial</code> explaining about contraints in their usage notes?
+             </p>
+           </aside>
+
+        <table class="definition">
+            <thead><tr><th>RDF Class:</th><th><a href="http://www.w3.org/ns/dcat#DatasetSeries">dcat:DatasetSeries</a></th></tr></thead>
+            <tbody>
+            <tr><td class="prop">Definition:</td><td>A collection of datasets that are published separatelly, but share some common characteristics that groups them, and could also be made available as a single dataset.</td></tr>
+            <tr><td class="prop">Sub-class of:</td><td><a href="#Class:Dataset"><code>dcat:Dataset</code></a></td></tr>
+            <tr><td class="prop">Usage note:</td><td> Dataset series can be also soft-typed via property <code>dct:type</code> as in the approach used in [[GeoDCAT-AP]], and adopted in [[DCAT-AP-IT]] and [[GeoDCAT-AP-IT]]).</td></tr>
+            </tbody>
+        </table>
+
+       <section id="Property:datasetseries_has_part">
+            <h4>Property: has part</h4>
+        <aside class="issue">
+              <p>
+                  For data catalog  <code>dct:hasPart</code> is specialized into <code>dcat:dataset</code>, <code>dcat:service</code>, etc.  Should we have some sort of specialization also for <code>dct:hasPart</code> used in <code>dcat:DatasetSeries</code>? For example to distinguish more between dataset that are 'just a bag of files' (see <a href="#examples-bag-of-files">example bag of files</a>) from actual datasets/distributions part of the dataset series. 
+              </p>
+
+            </aside>
+
+            <table class="definition">
+                <thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/hasPart">dct:hasPart</a></th></tr></thead>
+                <tbody>
+                <tr><td class="prop">Definition:</td><td>A child dataset that is part of the dataset series.</td></tr>
+<!--                    
+                <tr><td class="prop">Domain:</td><td><a href="#Class:Catalog"><code>dcat:Catalog</code></a></td></tr>
+                <tr><td class="prop">Range:</td><td><a href="#Class:Resource"><code>dcat:Resource</code></a></td></tr>
+-->
+                <tr><td class="prop">Usage note:</td><td> Normally, child datasets in dataset series are represented as <code>dcat:Dataset</code>. The use of <code>dcat:Distribution</code> for typing child datasets is however recognized as a possible alternative, whenever it addresses more effectively the requirements of a given application scenario.</td></tr>
+                <!--tr><td class="prop">See also:</td><td>Sub-properties of <code>dct:hasPart</code> in particular <a href="#Property:catalog_dataset"><code>dcat:dataset</code></a>, <a href="#Property:catalog_catalog"><code>dcat:catalog</code></a>, <a href="#Property:catalog_service"><code>dcat:service</code></a>. </td></tr-->
+                </tbody>
+            </table>
+
+        </section>
+
+    </section> <!-- end class DatasetSeries -->
 
 
     <!-- class Distribution -->
@@ -3389,7 +3481,7 @@ <h2>Dataset series</h2>
 <section id="dataset-series-specification">
 
 <h2>How to specify dataset series</h2>
-
+    
 <p>Existing DCAT implementations adopt two main alternative approaches to specifying dataset series:</p>
 
 <ol>
@@ -3400,22 +3492,24 @@ <h2>How to specify dataset series</h2>
 <p>In both cases, the dataset series is sometimes soft-typed by using the [[DCTERMS]] property <code>dct:type</code> (e.g., this is the approach used in [[GeoDCAT-AP]], and adopted in [[DCAT-AP-IT]] and [[GeoDCAT-AP-IT]]).</p>
 
 <p>Compared with the second option, the first one may have the advantage of simplifying metadata management, and avoiding the creation of datasets having the same values for almost all their metadata elements. On the other hand, this approach reduces the ability of being discovered, as distribution metadata are not rich as datasets' ones. Moreover, using distributions may result cumbersome or unfeasible when the number of child datasets is too high.</p>
+
+<p>DCAT makes dataset series first class citizens of data catalogs by minting a new class <code>dcat:DatasetSeries</code>. <code>dcat:DatasetSeries</code> is defined as subclass of   <code>dcat:Dataset</code>.</p>
+
+<p><!--As stated in the note to <a href="#Class:Distribution"></a>,-->DCAT recommends, as the default approach, typing dataset series as <code>dcat:DatasetSeries</code> and child datasets as <code>dcat:Dataset</code>, and linking them by using properties <code>dct:hasPart</code> and/or <code>dct:isPartOf</code>, and possibly soft-typing the dataset series via property <code>dct:type</code>.</p>
 
-<p>As stated in the note to <a href="#Class:Distribution"></a>, DCAT recommends, as the default approach, typing both dataset series and child datasets as <code>dct:Dataset</code>'s, and linking them by using properties <code>dct:hasPart</code> and/or <code>dct:isPartOf</code>, and possibly soft-typing the dataset series via property <code>dct:type</code>.</p>
-
-<aside class="ednote">
+<!--aside class="ednote">
 <p>The creation of a specific class for dataset series is under discussion.</p>
 <div class="issue" data-number="1272"></div>
-</aside>
+</aside-->
 
 <p>The approach based on the use of <code>dcat:Distribution</code> for typing child datasets is however recognized as a possible alternative, whenever it addresses more effectively the requirements of a given application scenario.</p>
 
 <p>Here and in the following sections, guidance will focus on the default approach.</p>
 
 <aside class="example" id="ex-dataset-series-containment" title=""> 
-<p>In the following example, yearly budget data are grouped into a series. Both the series and the child datasets are typed as <code>dcat:Dataset</code>'s, and the series is soft-typed with property <code>dct:type</code>. The series and the datasets are linked by using properties <code>dct:hasPart</code> and <code>dct:isPartOf</code>.</p>
+<p>In the following example, yearly budget data are grouped into a series. The series is typed as <code>dcat:DatasetSeries</code> and soft-typed with property <code>dct:type</code>, the child datasets are typed as <code>dcat:Dataset</code>. The series and the datasets are linked by using properties <code>dct:hasPart</code> and <code>dct:isPartOf</code>.</p>
 <pre>
-ex:budget a dcat:Dataset ;
+ex:budget a dcat:DatasetSeries ;
   dct:type &lt;http://inspire.ec.europa.eu/metadata-codelist/ResourceType/series&gt: ;
   title "Budget data"@en ;
   dct:hasPart ex:budget-2018 ,
@@ -3444,7 +3538,7 @@ <h2>How to specify dataset series</h2>
 <aside class="example" id="ex-dataset-series-releases" title="">
 <p>The following example extends <a href="#ex-dataset-series-containment"></a> by specifying the publication date (<code>dct:issued</code>) of each child dataset, and the previous (<code>adms:prev</code>) and next release (<code>adms:next</code>).</p>
 <pre>
-ex:budget a dcat:Dataset ;
+ex:budget a dcat:DatasetSeries ;
   dct:type &lt;http://inspire.ec.europa.eu/metadata-codelist/ResourceType/series&gt: ;
   title "Budget data"@en ;
   dct:hasPart ex:budget-2018 ,
@@ -3513,8 +3607,8 @@ <h2>Property values inheritance in dataset series</h2>
 <aside class="example" id="ex-dataset-series-properties" title="">
 <p>The following example is a variant <a href="#ex-dataset-series-releases"></a>, with child datasets corresponding to yearly budget data for specific countries. The temporal resolution (<code>dcat:temporalResolution</code>), temporal coverage (<code>dcat:temporal</code>), and spatial coverage (<code>dcat:spatial</code>) of the dataset series correspond to the union of those of the child datasets. Moreover, the dataset series specifies as publication date the one of the first published child dataset, whereas the date of publication of the last child dataset is specified as update date (<code>dct:modified</code>). Finally, the update frequency (<code>dct:accrualPeriodicity</code>) of the dataset series is annual, as the child datasets are published on a yearly basis, and not updated after their publication.</p>
 <pre>
-ex:budget a dcat:Dataset ;
-  dct:type &lt;http://inspire.ec.europa.eu/metadata-codelist/ResourceType/series&gt: ;
+ex:budget a dcat:DatasetSeries ;
+  dct:type &lt;http://inspire.ec.europa.eu/metadata-codelist/ResourceType/series&gt; ;
   title "Budget data"@en ;
   dct:hasPart ex:budget-2018-be , ex:budget-2019-be , ex:budget-2020-be ,
     ex:budget-2018-fr , ex:budget-2019-fr , ex:budget-2020-fr ,