OB1 - Make dct:identifier mandatory



Make dct:identifier mandatory

Proposed solution






Tue, 24/03/2015 - 19:57

Proposed resolution: investigate use in existing applications. Reject if there are implementations where dct:identifier is not available.

Wed, 22/04/2015 - 22:21

No further support was received. In the discussions on the first version of the DCAT-AP it was decided not to make this property mandatory. If no strong case is made for it to be made mandatory, it will remain as it is.

Fri, 24/04/2015 - 11:12

This proposal will probaly fail for now on "conformance with DCAT".


But I think identification of datasets an catalogrecords is still a 'key' issue when we look at the broader picture of the constellation of datacatalogs. When we exchange metadata between portals in a larger network, we will inevitably encounter duplicates. How will we recognize these duplicates? That's an issue I would like to make it to the DCAT community.

Mon, 27/04/2015 - 15:51

It's true that detecting duplicates could be an important use case. We might want to cover these types of requirements in a possible future activity looking at operational issues in the networked environment.

Mon, 27/04/2015 - 16:51

The content of this field is kept private and will not be shown publicly.