If I'm not mistaken, one of the reasons why a DCAT-AP-conformant application should provide "a description of the catalogue" is to track where dataset and dataset distribution metadata have been collected. Indeed, this is the approach followed in the ADMS federation, and, as far as I understand, this is how DCAT-AP keeps track of metadata provenance [1].
I would suggest we make explicit in Section 9 the purpose of having also catalogue metadata.
Moreover, we should also make it clear how datasets are linked to their catalogue. In ADMS, this was done by using dct:hasPart / dct:isPartOf . The same approach can be used in DCAT-AP. The possible options:
- make dct:isPartOf as a mandatory property of dcat:Dataset
- require metadata applications to dynamically add it when exposing metadata
Component
DocumentationCategory
improvement
Login or
create an account to comment.
Comments
My mistake. Link between datasets and corresponding catalogue is addressed by property dcat:dataset - see [1].
Sorry, Makx, the issue was also on the possibility of making explicit in Section 9 the purpose of exposing catalogue metadata.
Andrea, Section 9 is the Conformance Statemen which states the requirements for an application to be conformant. It's not a section to explain the purpose of particular classes or properties.
Section 11.3 includes a short explanation of the purpose of CatalogRecord to convey provenance information.