Skip to content

Commit 5561712

Browse files
release 2.1.0
1 parent dbbfc02 commit 5561712

21 files changed

Lines changed: 4105 additions & 2 deletions

releases/2.1.0/CHANGELOG.md

Lines changed: 112 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,112 @@
1+
# The changelog for release DCAT-AP 2.1.0
2+
3+
The complete list of all issues that resulted in some change are found at https://github.com/SEMICeu/DCAT-AP/labels/release%3A2.1.0-dec2021. The discussions and interaction that have led to these changes can be found in the meeting minutes of the webinars, and in the github issues. The list below summarizes the applied changes.
4+
5+
Webinars:
6+
- https://github.com/SEMICeu/DCAT-AP/tree/master/Webinars/15-Sept-2021
7+
- https://github.com/SEMICeu/DCAT-AP/tree/master/Webinars/21-Oct-2021
8+
9+
## Included issues
10+
11+
- profile management:
12+
- https://github.com/SEMICeu/DCAT-AP/issues/194
13+
- https://github.com/SEMICeu/DCAT-AP/issues/168
14+
- https://github.com/SEMICeu/DCAT-AP/issues/142
15+
- https://github.com/SEMICeu/DCAT-AP/issues/123
16+
- add the interpretation that "Any property that is mentioned in DCAT applicable to this class but not
17+
explicitly is listed DCAT-AP is considered an optional field for DCAT-AP."
18+
- rearrange the sections 2 and 3 to enable to remove the notion of categorisation of classes
19+
- improved diagram to make the specification more readable
20+
- decision that the human readible specification is normative, while visual representations or machine readible serialisations support the interpretation to the best of their extend possible.
21+
- in terms of scope, the DCAT-AP specification has clarified how it is a profile of DCAT. The business scope has not been addressed.
22+
23+
This adaptation resulted in an updated section 3
24+
25+
- add usage guidelines on datasets/distribution/data service (cfr https://github.com/SEMICeu/DCAT-AP/labels/topic%3Acataloged-resources)
26+
- https://github.com/SEMICeu/DCAT-AP/issues/204
27+
- https://github.com/SEMICeu/DCAT-AP/issues/202
28+
- https://github.com/SEMICeu/DCAT-AP/issues/180
29+
- A catalogue can contain both data services and datasets: datasets is recommended instead of mandatory
30+
- https://github.com/SEMICeu/DCAT-AP/issues/161
31+
- The updated diagram shows now that the primary topic of a catalogue record can be either datasets or data services
32+
- https://github.com/SEMICeu/DCAT-AP/issues/144
33+
- https://github.com/SEMICeu/DCAT-AP/issues/142
34+
- https://github.com/SEMICeu/DCAT-AP/issues/109
35+
- https://github.com/SEMICeu/DCAT-AP/issues/100
36+
- https://github.com/SEMICeu/DCAT-AP/issues/91
37+
38+
- SHACL:
39+
- https://github.com/SEMICeu/DCAT-AP/issues/164: splitting is several files with adapted severity level messages
40+
- https://github.com/SEMICeu/DCAT-AP/issues/127: splitting & reorganising the constraints to create different validation profiles.
41+
- https://github.com/SEMICeu/DCAT-AP/issues/55: splitting & reorganising the constraints to create different validation profiles.
42+
43+
- use coherent expression to denoted the use of typed literals as range:
44+
https://github.com/SEMICeu/DCAT-AP/issues/206
45+
46+
- controlled vocabularies:
47+
- https://github.com/SEMICeu/DCAT-AP/issues/202
48+
- https://github.com/SEMICeu/DCAT-AP/issues/192
49+
- dct:title property will be added skos:ConceptScheme of EU Vocabularies used in DCAT-AP gradually by the Publications Office
50+
- https://github.com/SEMICeu/DCAT-AP/issues/159
51+
- improve the specification on the usage of the NAL access-right
52+
- https://github.com/SEMICeu/DCAT-AP/issues/153
53+
- add NAL dataset-type as recommended controlled vocabulary
54+
55+
- replacement of the controlled vocabulary planned availibility with a controlled vocabulary maintained by the Publications Office:
56+
- https://github.com/SEMICeu/DCAT-AP/issues/208
57+
- https://github.com/SEMICeu/DCAT-AP/issues/178
58+
59+
- dataset type:
60+
- https://github.com/SEMICeu/DCAT-AP/issues/153: lift the max-cardinality of dct:type for a dataset
61+
62+
- checksum:
63+
- https://github.com/SEMICeu/DCAT-AP/issues/158: support the usage of other than SHA1 checksum algorithms.
64+
65+
- temporal properties accept any temporal xsd format
66+
- https://github.com/SEMICeu/DCAT-AP/issues/172
67+
68+
- add max-cardinality 1 for dcat:temporalResolution and dcat:spatialResolutionInMeters
69+
- https://github.com/SEMICeu/DCAT-AP/issues/114: alignment between usage note(the minimum value) and the expected max-cardinality
70+
71+
- lift the max-cardinality for dct:creator:
72+
- https://github.com/SEMICeu/DCAT-AP/issues/171
73+
74+
- clarification and alignment of definitions/usage notes for adms:status w.r.t. w3C DCAT
75+
- https://github.com/SEMICeu/DCAT-AP/issues/86
76+
77+
- typo fixing:
78+
- https://github.com/SEMICeu/DCAT-AP/issues/195 :
79+
- https://github.com/SEMICeu/DCAT-AP/issues/191 : use of wrong uri
80+
- https://github.com/SEMICeu/DCAT-AP/issues/188 : references in the specification pointed to the wrong target
81+
- https://github.com/SEMICeu/DCAT-AP/issues/186 : diagram not in sync with the specification
82+
- https://github.com/SEMICeu/DCAT-AP/issues/185 : range of dct:format was incorrect in the specification: alignment DCAT
83+
- https://github.com/SEMICeu/DCAT-AP/issues/182 : diagram more consistent representation (no doubles)
84+
- https://github.com/SEMICeu/DCAT-AP/issues/181 : mandatory properties have min-cardinality 1
85+
- https://github.com/SEMICeu/DCAT-AP/issues/173 : range of dct:format was incorrect in the specification: alignment between diagram and specification
86+
- https://github.com/SEMICeu/DCAT-AP/issues/154 : improvement to the metadata of the RDF distribution
87+
- https://github.com/SEMICeu/DCAT-AP/issues/147 : fix range in SHACL for checksum_shape
88+
- https://github.com/SEMICeu/DCAT-AP/issues/134 : skos:notation for class Identifier is declared mandatory, and thus min-cardinality must be 1
89+
90+
## Issues that were discussed as part of the release 2.1.0 that have not resulted in a change
91+
92+
### specific requests
93+
- https://github.com/SEMICeu/DCAT-AP/issues/184: no qualification adaptation for dct:format & dct:mediaType
94+
- https://github.com/SEMICeu/DCAT-AP/issues/202: no adoption of distribution type NAL as recommended controlled vocabulary
95+
- https://github.com/SEMICeu/DCAT-AP/issues/174: no introduction of the inverse property for foaf:primaryTopic
96+
- https://github.com/SEMICeu/DCAT-AP/issues/157: no change in the cardinality constraints for dct:ispPartOf for a Catalogue
97+
- https://github.com/SEMICeu/DCAT-AP/issues/97: no change in the qualification for dct:rights and dct:license.
98+
- https://github.com/SEMICeu/DCAT-AP/issues/96: no change in the qualification for dct:rights and dct:license.
99+
100+
### adapting shacl expressions for DCAT-AP 1.2.1:
101+
- https://github.com/SEMICeu/DCAT-AP/issues/120
102+
- https://github.com/SEMICeu/DCAT-AP/issues/119
103+
- https://github.com/SEMICeu/DCAT-AP/issues/118
104+
- https://github.com/SEMICeu/DCAT-AP/issues/117
105+
- https://github.com/SEMICeu/DCAT-AP/issues/116
106+
- https://github.com/SEMICeu/DCAT-AP/issues/115
107+
108+
It has been decided to not retrofit the changes to DCAT-AP 1.2.1, but to continue and further improve them in the new version.
109+
Since DCAT-AP 2.1.0 is backward compatible (to a large extend), the SHACL constraints of 2.1.0 are thus mostly backward compatible.
110+
111+
## Additional issues that were closed as part of issue processing for release 2.1.0
112+
As part of the release 2.1.0 additional issues where closed. These contain announcements, questions, requests for advice.

releases/2.1.0/README.md

Lines changed: 32 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,32 @@
1-
This is a placeholder directory for the upcomming 2.1.0 release.
2-
The draft specification and its associated information can be found in this branch https://github.com/SEMICeu/DCAT-AP/tree/2.1.0-draft/releases/2.1.0
1+
# DCAT-AP 2.1.0
2+
3+
This release addresses the topics registered as a github issue and discussed during the webinars:
4+
- https://github.com/SEMICeu/DCAT-AP/tree/master/Webinars/15-Sept-2021
5+
- https://github.com/SEMICeu/DCAT-AP/tree/master/Webinars/21-Oct-2021
6+
7+
Besides editorial fixes and small concrete requests (such as lifting a cardinality), this release mainly improves the readability of the specification as a profile from DCAT and provides guidelines for Datasets, Distributions and Data Services.
8+
9+
# Changelog
10+
The [Changelog](CHANGELOG.md) documents in detail the changes performed for the release 2.1.0.
11+
12+
# Guidelines for Datasets, Distributions and Data Services.
13+
The [usage guide on Datasets, Distributions and Data Services](usageguide-dataset-distribution-dataservice.md) provides a common interpretation for the treatment of Datasets, Distributions and Data Services.
14+
15+
### validating DCAT-AP
16+
To check whether a catalogue satisfies the DCAT-AP 2.0.1 specification the SHACL files can be used:
17+
- [dcat-ap_2.1.0_shacl_shapes.ttl](https://github.com/SEMICeu/DCAT-AP/blob/2.1.0-draft/releases/2.1.0/dcat-ap_2.0.1_shacl_shapes.ttl): constraints concerning existance, domain and literal range, and cardinalities.
18+
- [dcat-ap_2.1.0_shacl_range.ttl](https://github.com/SEMICeu/DCAT-AP/blob/2.1.0-draft/releases/2.1.0/dcat-ap_2.0.1_shacl_range.ttl): constraints concerning object range.
19+
- [dcat-ap_2.1.0_shacl_mdr-vocabularies.shape.ttl](https://github.com/SEMICeu/DCAT-AP/blob/master/releases/2.1.0-draft/dcat-ap_2.1.0_shacl_mdr-vocabularies.shape.ttl): constraints concerning the usage of controlled vocabularies
20+
21+
The first file provides for each class mentioned in DCAT-AP and having additional properties defined a template with the corresponding constraints. Class membership constraints are not present in the first fil. These are collected in the second file.
22+
23+
- [dcat-ap_2.1.0_shacl_shapes_recommended.ttl](https://github.com/SEMICeu/DCAT-AP/blob/2.1.0-draft/releases/2.1.0/dcat-ap_2.0.1_shacl_shapes_recommended.ttl): constraints concerning existance of recommended properties.
24+
25+
In order to validate a catalogue additional data might be required to import into the validator, such as the controlled vocabularies. These have to be retrieved from the appropriate places.
26+
As support, the following files express the imports (not transitive) according to the SHACL specification, which can be loaded into the ISA testbed.
27+
- [dcat-ap_2.1.0_shacl_imports.ttl](https://github.com/SEMICeu/DCAT-AP/blob/2.1.0-draft/releases/2.1.0/dcat-ap_2.1.0_shacl_imports.ttl): imports the vocabulary knowledge
28+
- [dcat-ap_2.1.0_shacl_mdr_imports.ttl](https://github.com/SEMICeu/DCAT-AP/blob/2.1.0-draft/releases/2.1.0/dcat-ap_2.1.0_shacl_mdr_imports.ttl): imports the recommended codelists
29+
30+
The shacl files are configured in this instance of the ISA testbed: https://www.itb.ec.europa.eu/shacl/dcat-ap/upload. More information about the configured validation profiles is https://github.com/ISAITB/validator-resources-dcat-ap.
31+
32+

releases/2.1.0/dcat-ap_2.1.0.docx

424 KB
Binary file not shown.

releases/2.1.0/dcat-ap_2.1.0.eap

1.43 MB
Binary file not shown.

0 commit comments

Comments
 (0)