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

Aligning definitions of dcterms:hasPart and its subproperties #1465

Closed
andrea-perego opened this issue Feb 25, 2022 · 0 comments · Fixed by #1466
Closed

Aligning definitions of dcterms:hasPart and its subproperties #1465

andrea-perego opened this issue Feb 25, 2022 · 0 comments · Fixed by #1466

Comments

@andrea-perego
Copy link
Contributor

andrea-perego commented Feb 25, 2022

The current definitions are as follows:

Property Definition
dcterms:hasPart An item that is listed in the catalog.
dcat:dataset A collection of data that is listed in the catalog.
dcat:service A site or end-point that is listed in the catalog.
dcat:catalog A catalog that is listed in this catalog.

The proposal is to revise them as follows:

Property Definition
dcterms:hasPart A resource that is listed in the catalog.
dcat:dataset A dataset that is listed in the catalog.
dcat:service A service that is listed in the catalog. [definition proposed in #1431]
dcat:catalog A catalog that is listed in the catalog.

The rationale is that there is no need to describe the range of the property with an abridged definition of the relevant class, as we need just to point to it (as already done in the range of the property definition). Another issue is that this may lead to confusion - e.g., as highlighted in #1431 for the definition of dcat:service.

About the definition of dcterms:hasPart, "item" should be replaced by "resource", as the range of this property in DCAT, when used to link a catalog to one of the listed resources, is dcat:Resource (or a subclass thereof). Moreover, the use of "item" led to a misunderstanding reported in #1454 .

The proposal has been implemented via PR #1466

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

Successfully merging a pull request may close this issue.

1 participant