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

OWL-compliant? #359

Open
YasinEl opened this issue Nov 28, 2024 · 3 comments
Open

OWL-compliant? #359

YasinEl opened this issue Nov 28, 2024 · 3 comments
Assignees

Comments

@YasinEl
Copy link

YasinEl commented Nov 28, 2024

Hello,

could it be that http://aber-owl.net/media/ontologies/MS/194/ms.owl is not OWL-compliant or am I doing something wrong?

from owlready2 import get_ontology

onto = get_ontology('ms.owl').load()

gives

TypeError: 'http://purl.obolibrary.org/obo/NCIT_C16847' belongs to more than one entity types (cannot be both a property and a class/an individual)!

I did not have the same problem with http://aber-owl.net/media/ontologies/MS/188/ms.owl but did not try everything in between.

Thank you

@mobiusklein mobiusklein self-assigned this Jan 17, 2025
@mobiusklein
Copy link
Contributor

I am still doing root cause analysis on this. It seems that our OBO to OWL conversion process previously treated NCIT:C16847 as both an locally defined class and an externally defined property, but later began applying both types to the locally defined entity.

Other OWL-consuming tools do not seem to have an issue with this state. Is this something specific to owlready2?

@ometa-evan
Copy link

Is this also related to mobiusklein/psims#23?

@YasinEl
Copy link
Author

YasinEl commented Jan 29, 2025

I have only encountered this with owlready2 and have not tested others. Are you aware of others which are compatible with ms.owl?

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