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

has creation location: range CulturalEntity #200

Open
vpresutti opened this issue Feb 21, 2021 · 0 comments
Open

has creation location: range CulturalEntity #200

vpresutti opened this issue Feb 21, 2021 · 0 comments

Comments

@vpresutti
Copy link
Collaborator

English Version (Versione italiana fornita di seguito)

Indicate which part of the project the bug concerns: ontology, knowledge graph, rdfizer

ontology a-cd:

Describe the bug
The object property hasCreationLocation has range CulturalEntity. Why? Shouldn't it be anything that is a l0:Location? I think this applies also to other similar relations. I notice also that this property (as well as others) is subproperty of hasRelatedWorlk, from which inherits this range axiom. The assumption is that whatever the type of location it must be a CulturalEntity? I don't see this plausible nor intuitive. Also, hasRelatedWork says "This property relates a cultural property to a related work (e.g. copy, preparatory work)." Are we constraining the "hasCreationLocation" and the other similar properties to only locations that is a work of art, as well? It may happen that a CP is found in a place that is not a "work of art" nor a cultural entity, or that it is stored in a private place for example, because it belongs to a private collector.

To Reproduce
no behaviour to reproduce but a ill-modeling in the ontology (a-cd: module)

Expected behavior
the relation hasCreationLocation should have l0:Location as range
the same applies to other similar relations, hence I recommend a review of them
Additional context
Add any other context about the problem here.

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

1 participant