Applying changes from commit 4ccd4827fe3eec9d0a07443ae37f04c1302048fe

SEMICeu · Feb 12, 2024 · aa2b450 · aa2b450
1 parent 227c8ce
commit aa2b450
Show file tree

Hide file tree

Showing 15 changed files with 1,220 additions and 1,186 deletions.
diff --git a/DCAT-AP/releases/3.0.0/html/shacl/range.ttl b/DCAT-AP/releases/3.0.0/html/shacl/range.ttl
@@ -187,6 +187,10 @@
         sh:class dcat:Dataset ;
         sh:path dcat:servesDataset ;
         sh:severity sh:Violation
+    ], [
+  	sh:path dcatap:applicableLegislation;
+  	sh:class <http://data.europa.eu/eli/ontology#LegalResource>;
+        sh:severity sh:Violation
     ], [
         sh:class dct:LicenseDocument ;
         sh:path dct:license ;
@@ -198,6 +202,7 @@
     ] ;
     sh:targetClass dcat:DataService .
 
+
 :Dataset_Shape
     a sh:NodeShape ;
     rdfs:label "Dataset"@en ;
@@ -416,3 +421,35 @@
     ] ;
     sh:targetClass dcat:Relationship .
 
+:DatasetSeries_Shape
+    a sh:NodeShape ;
+    rdfs:label "Dataset Series"@en ;
+    sh:property [
+       sh:inversePath dcat:inSeries;
+       sh:severity sh:Warning
+    ], [
+  	sh:path dcatap:applicableLegislation;
+  	sh:class <http://data.europa.eu/eli/ontology#LegalResource>;
+        sh:severity sh:Violation
+    ], [
+  	sh:path dct:spatial;
+  	sh:class dct:Location;
+        sh:severity sh:Violation
+    ], [
+	sh:path dct:accrualPeriodicity;
+  	sh:class dct:Frequency;
+        sh:severity sh:Violation
+    ], [
+        sh:path dct:publisher ;
+  	sh:class foaf:Agent;
+        sh:severity sh:Violation
+    ], [
+  	sh:path dcat:contactPoint;
+  	sh:class vcard:Kind;
+        sh:severity sh:Violation
+    ], [
+  	sh:path dct:temporal;
+  	sh:class dct:PeriodOfTime;
+        sh:severity sh:Violation
+	 ] ;
+    sh:targetClass dcat:DatasetSeries .	
diff --git a/DCAT-AP/releases/3.0.0/html/shacl/shapes.ttl b/DCAT-AP/releases/3.0.0/html/shacl/shapes.ttl
@@ -660,12 +660,10 @@
         sh:severity sh:Violation
     ], [
   	sh:path dct:spatial;
-  	sh:class dct:Location;
   	sh:nodeKind sh:BlankNodeOrIRI;
         sh:severity sh:Violation
     ], [
 	sh:path dct:accrualPeriodicity;
-  	sh:class dct:Frequency;
   	sh:maxCount 1;
   	sh:nodeKind sh:BlankNodeOrIRI;
         sh:severity sh:Violation
@@ -694,18 +692,15 @@
     ], [
         sh:path dct:publisher ;
         sh:maxCount 1 ;
-  	sh:class foaf:Agent;
   	sh:nodeKind sh:BlankNodeOrIRI;
         sh:severity sh:Violation
     ], [
   	sh:path dcat:contactPoint;
   	sh:nodeKind sh:BlankNodeOrIRI;
-  	sh:class vcard:Kind;
         sh:severity sh:Violation
     ], [
   	sh:path dct:temporal;
   	sh:nodeKind sh:BlankNodeOrIRI;
-  	sh:class dct:PeriodOfTime;
         sh:severity sh:Violation
 	 ] ;
     sh:targetClass dcat:DatasetSeries .	
diff --git a/DCAT-AP/releases/3.0.0/index.html b/DCAT-AP/releases/3.0.0/index.html
@@ -10085,8 +10085,9 @@ <h3>Usage guide on Dataset Series</h3>
 <li>The members of a Dataset Series should be described in such a way that without the knowledge of the Dataset Series, the metadata is interpreted correctly. The existence of a dataset should not be based on the membership in a Dataset Series. The interpretation of a member with its associated Distributions and Data Services is conform the above guidelines.
 </li>
 <li>Whenever a Data Service is providing access to all the data of a Dataset Series, i.e. the union of all datasets in the collection of the Dataset Series, 
-    then the Data Service should refer to the Dataset Series using <a href="#DataService.servesdataset">serves dataset</a>. 
+    then the Data Service may refer to the Dataset Series using <a href="#DataService.servesdataset">serves dataset</a>. 
     The ensures that whenever in the future the Dataset Series is extended with new Datasets the Data Service description does not need to be adapted.
+    In that case the Dataset Series should also be considered as a DCAT-AP Dataset.
 </li>      
 <li>Keep the usage simple. Complex nesting such as Dataset Series being a member of Dataset Series, or Dataset belonging to multiple Dataset Series are to be handled with care. 
 While from a data knowlegde graph these nestings are feasible and not so problematic, it must be realised that these complicate the presentation on a webpage. 

diff --git a/DCAT-AP/releases/3.0.0/index_en.html b/DCAT-AP/releases/3.0.0/index_en.html
@@ -10085,8 +10085,9 @@ <h3>Usage guide on Dataset Series</h3>
 <li>The members of a Dataset Series should be described in such a way that without the knowledge of the Dataset Series, the metadata is interpreted correctly. The existence of a dataset should not be based on the membership in a Dataset Series. The interpretation of a member with its associated Distributions and Data Services is conform the above guidelines.
 </li>
 <li>Whenever a Data Service is providing access to all the data of a Dataset Series, i.e. the union of all datasets in the collection of the Dataset Series, 
-    then the Data Service should refer to the Dataset Series using <a href="#DataService.servesdataset">serves dataset</a>. 
+    then the Data Service may refer to the Dataset Series using <a href="#DataService.servesdataset">serves dataset</a>. 
     The ensures that whenever in the future the Dataset Series is extended with new Datasets the Data Service description does not need to be adapted.
+    In that case the Dataset Series should also be considered as a DCAT-AP Dataset.
 </li>      
 <li>Keep the usage simple. Complex nesting such as Dataset Series being a member of Dataset Series, or Dataset belonging to multiple Dataset Series are to be handled with care. 
 While from a data knowlegde graph these nestings are feasible and not so problematic, it must be realised that these complicate the presentation on a webpage.