-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
bug fix release 2.1.1. The changes are documented in the CHANGELOG of the release 2.1.1.
- Loading branch information
1 parent
ff3e353
commit ab32315
Showing
24 changed files
with
4,043 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
A webinar on the use of identifiers within DCAT-AP took place on the 10th of March 2022. | ||
|
||
One of the most important data processing steps of data catalogues is harvesting. City data portals are being harvested by national data portals, which in turn are harvested by the European Data Portal. This results that the same dataset description is present on multiple data portals. In this webinar we take a closer look at one key information element: the identifier of a dataset or data service. The value of this information has been acknowledged by the community, but because not everyone is approaching it in similar way, aggregating data portals have difficulties to conduct tasks like detecting duplicates. | ||
|
||
The agenda for this webinar is the following: | ||
|
||
Welcome | ||
A state of play on identifiers | ||
Exchange of ideas on guidelines for identifiers and harvesting processes to improve the knowledge graph on datasets and data services | ||
AOB | ||
|
||
|
||
The [slide deck](https://joinup.ec.europa.eu/sites/default/files/event/attachment/2022-03/Webinar-10march2021-v1.00.pdf), | ||
[meeting minutes](https://joinup.ec.europa.eu/sites/default/files/event/attachment/2022-03/DCAT-AP_Webinar%2010032022_MeetingMinutes_v1.00.pdf) and | ||
[recoring](https://www.youtube.com/watch?v=mfcCzaL6Jqc) of the webinar are available. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
A second webinar on the use of identifiers within DCAT-AP took place on the 21th of April 2022. | ||
|
||
|
||
One of the most important data processing steps of data catalogues is harvesting. Harvesting is the aggregation of source catalogues into a one catalogue with the objective to increase the visibility of the datasets of the sources. Within the Public Sector Information context, a common example is the harvesting of city data portals by national data portals, which in turn are harvested by the European Data Portal. In practice harvesting interconnects catalogues with different size, scope and perspectives into a complex network. | ||
|
||
Harvesting has as result that the same dataset description is present on multiple data portals. In this webinar we take a closer look at one key information element: the identifier of a dataset or data service. The value of this information has been acknowledged by the community, but because not everyone is approaching it in a similar way, aggregating data portals have difficulties to conduct tasks like detecting duplicates. | ||
|
||
The first webinar took place on the 10th of March, where the working group chose to proceed along the blue track, which implies that the value is assigned by the owner/publisher of the dataset. The decisions made during the first webinar will be added to Github. The materials of the first webinar are available on Joinup. | ||
|
||
In this second webinar we continue our exchange on ideas on this basis to reach consensus on the guidelines on the usage of identifiers. | ||
|
||
The tentative agenda for this webinar is the following: | ||
|
||
- Welcome | ||
- Propose a consolidated overview of the blue track guidelines | ||
- Exchange of ideas on those guidelines to improve the knowledge graph on datasets and data services | ||
- Next steps | ||
- AOB | ||
|
||
|
||
The [slide deck](https://joinup.ec.europa.eu/sites/default/files/event/attachment/2022-05/Webinar-26april2021-v1.0.pdf), | ||
[meeting minutes](https://joinup.ec.europa.eu/sites/default/files/event/attachment/2022-05/DCAT-AP_Webinar%2026042022_MeetingMinutes_v1.00.pdf) and | ||
[recoring](https://www.youtube.com/watch?v=EdeLrcA4eNs) of the webinar are available. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
# The changelog for release DCAT-AP 2.1.1 | ||
|
||
- issue #227: update readme link | ||
- issue #226: fix cardinality dcat:dataset in UML model figure | ||
- issue #222: fix typo is in RDF representation | ||
- issue #216: fix SHACL expressions: sh:property should not be empty. | ||
- issue #229: fix SHACL sh:shape => sh:node | ||
- issue #199: fix prefix dcatap reference | ||
- validated the shapes according to https://www.itb.ec.europa.eu/shacl/shacl/upload W3C Core level | ||
- issue #211: fix the references to the vocabulary URIs for | ||
ADMS status vocabulary to http://purl.org/adms/status/1.0 | ||
ADMS publisher type vocabulary to http://purl.org/adms/publishertype/1.0 | ||
ADMS licence type vocabulary to http://purl.org/adms/licencetype/1.0 | ||
in pdf version | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
# DCAT-AP 2.1.1 | ||
|
||
This release addresses the topics registered as a github issue and discussed during the webinars: | ||
- https://github.com/SEMICeu/DCAT-AP/tree/master/Webinars/15-Sept-2021 | ||
- https://github.com/SEMICeu/DCAT-AP/tree/master/Webinars/21-Oct-2021 | ||
|
||
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. | ||
|
||
# Changelog | ||
The [Changelog](CHANGELOG.md) documents in detail the changes performed for the release 2.1.1. | ||
|
||
# Guidelines for Datasets, Distributions and Data Services. | ||
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. | ||
|
||
### validating DCAT-AP | ||
To check whether a catalogue satisfies the DCAT-AP 2.0.1 specification the SHACL files can be used: | ||
- [dcat-ap_2.1.1_shacl_shapes.ttl](https://github.com/SEMICeu/DCAT-AP/blob/2.1.1-draft/releases/2.1.1/dcat-ap_2.0.1_shacl_shapes.ttl): constraints concerning existance, domain and literal range, and cardinalities. | ||
- [dcat-ap_2.1.1_shacl_range.ttl](https://github.com/SEMICeu/DCAT-AP/blob/2.1.1-draft/releases/2.1.1/dcat-ap_2.0.1_shacl_range.ttl): constraints concerning object range. | ||
- [dcat-ap_2.1.1_shacl_mdr-vocabularies.shape.ttl](https://github.com/SEMICeu/DCAT-AP/blob/master/releases/2.1.1-draft/dcat-ap_2.1.1_shacl_mdr-vocabularies.shape.ttl): constraints concerning the usage of controlled vocabularies | ||
|
||
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. | ||
|
||
- [dcat-ap_2.1.1_shacl_shapes_recommended.ttl](https://github.com/SEMICeu/DCAT-AP/blob/2.1.1-draft/releases/2.1.1/dcat-ap_2.0.1_shacl_shapes_recommended.ttl): constraints concerning existance of recommended properties. | ||
|
||
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. | ||
As support, the following files express the imports (not transitive) according to the SHACL specification, which can be loaded into the ISA testbed. | ||
- [dcat-ap_2.1.1_shacl_imports.ttl](https://github.com/SEMICeu/DCAT-AP/blob/2.1.1-draft/releases/2.1.1/dcat-ap_2.1.1_shacl_imports.ttl): imports the vocabulary knowledge | ||
- [dcat-ap_2.1.1_shacl_mdr_imports.ttl](https://github.com/SEMICeu/DCAT-AP/blob/2.1.1-draft/releases/2.1.1/dcat-ap_2.1.1_shacl_mdr_imports.ttl): imports the recommended codelists | ||
|
||
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. | ||
|
||
|
Binary file not shown.
Binary file not shown.
Oops, something went wrong.