Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why 0..n for dct:identifier in Dataset (while it is 1 for all other dct:identifier)? #84

Open
jimjyang opened this issue May 3, 2022 · 2 comments

Comments

@jimjyang
Copy link

jimjyang commented May 3, 2022

Any reason why the cardinality for dct:identifier in the class Dataset (dcat:Dataset) is 0..* [while the cardinality for dct:identifier in all the other classes is 1 (if I have read correctly)]?

@NathanGhesq
Copy link

dct:identifier has a minimum cardinality of 0 because it is reused from DCAT-AP. This explains why the identifier of dcat:Dataset has a different cardinality than other identifiers in CPSV-AP.

@williamverbeeck
Copy link
Contributor

During the webinar on the review of CPSV-AP on the 7th of November, it was agreed to investigate if the explicit inclusion of dcat:Dataset in the model is necessary and whether it is used or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants