Applying changes from commit ee3bd3803c6442e3fc67225b538cc3d7c4ea93c5

DCAT-AP/releases/3.0.0/html/shacl/shapes.ttl

@@ -1,5 +1,5 @@
 @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
-@prefix : <http://data.europa.eu/r5r#> .
+@prefix : <http://data.europa.eu/r5r/shacl_shapes#> .
 @prefix adms: <http://www.w3.org/ns/adms#> .
 @prefix cc: <http://creativecommons.org/ns#> .
 @prefix dcat: <http://www.w3.org/ns/dcat#> .
@@ -46,16 +46,6 @@
         org:memberOf <http://ami-consult.com/#id> ;
         foaf:homepage <http://makxdekkers.com/> ;
         foaf:name "Makx Dekkers"
-    ], [
-        rdfs:seeAlso <http://nikosloutas.com/> ;
-        org:memberOf <http://www.pwc.com/gx/en/eu-institutions-services> ;
-        foaf:homepage <http://nikosloutas.com/> ;
-        foaf:name "Nikolaos Loutas"
-    ], [
-        rdfs:seeAlso <http://www.deri.ie/users/vassilios-peristeras/> ;
-        org:memberOf <http://publications.europa.eu/resource/authority/corporate-body/COM> ;
-        foaf:homepage <http://www.deri.ie/users/vassilios-peristeras/> ;
-        foaf:name "Vassilios Peristeras"
     ] ;
     dct:license <https://creativecommons.org/licenses/by/4.0> ;
     cc:attributionURL <http://ec.europa.eu/> ;
@@ -64,7 +54,7 @@
     dct:relation <https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/210> ;
     dct:description "This document specifies the constraints on properties and classes expressed by DCAT-AP in SHACL."@en ;
     dct:title "The constraints of DCAT Application Profile for Data Portals in Europe"@en ;
-    owl:versionInfo "2.1.1" ;
+    owl:versionInfo "3.0.0" ;
     foaf:homepage <https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/210> ;
     foaf:maker [
         foaf:mbox <mailto:[email protected]> ;
@@ -637,56 +627,20 @@
     sh:targetClass dcat:Relationship .
 
 #
-# Duplication is required to handle the inverse of the dcat:inSeries property.
-:DatasetInSeries_Shape
-    a sh:NodeShape ;
-    rdfs:label "Dataset in Series"@en ;
-    sh:property [
-  	sh:path dcat:prev;
-  	sh:nodeKind sh:BlankNodeOrIRI;
-        sh:severity sh:Violation
-    ], [
-  	sh:path dcat:next;
-  	sh:nodeKind sh:BlankNodeOrIRI;
-        sh:severity sh:Violation
-    ], [
-  	sh:path dct:title;
-  	sh:nodeKind sh:Literal ;
-  	sh:minCount 1;
-        sh:severity sh:Violation
-    ], [
-   	sh:path dcat:inSeries;
-  	sh:class dcat:DatasetSeries;
-	sh:nodeKind sh:BlankNodeOrIRI;
-        sh:severity sh:Violation
-    ], [
-	sh:path dct:accrualPeriodicity;
-	sh:nodeKind sh:BlankNodeOrIRI;
-        sh:severity sh:Violation
-
-    ], [
-	sh:path dct:description;
-  	sh:nodeKind sh:Literal ;
-  	sh:minCount 1;
-        sh:severity sh:Violation
-    ] .
-
-
+# 
 
-:DatasetInSeries_ShapeClass
-    a sh:NodeShape ;
-    rdfs:label "Dataset in Series"@en ;
-    sh:node :DatasetInSeries_Shape ;
-    sh:targetSubjectsOf <http://www.w3.org/ns/dcat#inSeries>.
 
 :DatasetSeries_Shape
     a sh:NodeShape ;
     rdfs:label "Dataset Series"@en ;
     sh:property [
-	sh:path dcat:seriesMember;
-  	sh:node :DatasetInSeries_Shape ;
-	sh:minCount 1;
-	sh:nodeKind sh:BlankNodeOrIRI;
+       sh:inversePath dcat:inSeries;
+       sh:minCount 1;
+       sh:nodeKind sh:BlankNodeOrIRI;
+       sh:severity sh:Warning
+    ], [
+  	sh:path dcatap:applicableLegislation;
+  	sh:nodeKind sh:IRI;
         sh:severity sh:Violation
     ], [
   	sh:path dct:spatial;
@@ -722,20 +676,9 @@
   	sh:maxCount 1;
         sh:severity sh:Violation
     ], [
-  	sh:path dcat:first;
-  	sh:node :DatasetInSeries_Shape ;
-  	sh:nodeKind sh:BlankNodeOrIRI;
-  	sh:maxCount 1;
-        sh:severity sh:Violation
-    ], [
-  	sh:path dcat:last;
-  	sh:node :DatasetInSeries_Shape ;
-  	sh:nodeKind sh:BlankNodeOrIRI;
-  	sh:maxCount 1;
-        sh:severity sh:Violation
-    ], [
-        sh:maxCount 1 ;
         sh:path dct:publisher ;
+        sh:maxCount 1 ;
+  	sh:class foaf:Agent;
   	sh:nodeKind sh:BlankNodeOrIRI;
         sh:severity sh:Violation
     ], [

DCAT-AP/releases/3.0.0/index.html

@@ -10081,6 +10081,10 @@ <h3>Usage guide on Dataset Series</h3>
 </li>
 <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>. 
+    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.
+</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. 
 Since data portal representations are the main communication from metadata owners to potential data consumers and there is no clear expectations

DCAT-AP/releases/3.0.0/index_en.html

@@ -10081,6 +10081,10 @@ <h3>Usage guide on Dataset Series</h3>
 </li>
 <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>. 
+    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.
+</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. 
 Since data portal representations are the main communication from metadata owners to potential data consumers and there is no clear expectations