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

GraphDB Behavior of owl:inverseOf Investigation #40

Open
pdatascience opened this issue Feb 23, 2018 · 0 comments
Open

GraphDB Behavior of owl:inverseOf Investigation #40

pdatascience opened this issue Feb 23, 2018 · 0 comments
Assignees

Comments

@pdatascience
Copy link
Collaborator

Sometimes it is more convenient to use an inverse property rather than direct property. E.g. the realization of a fabio:ResearchPaper is a fabio:JournalArticle, but it may be more convenient to talk about the article as a realization of the paper. This is why we explicitly define frbr:realization as the inverse of frbr:realizationOf.

image

Question

Why doens't GraphDB materialize the relation

frbr:realization owl:inverseOf frbr:realizationOf

Database: obkms_i6

image

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

No branches or pull requests

1 participant