-
Notifications
You must be signed in to change notification settings - Fork 17
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
upheno.owl cannot be parsed with Pronto #919
Comments
While I love pronto and its developer @althonos, this is a bit of a misunderstanding - the defacto standard for accessing ontologies in python does not really exist (maybe the "defacto" part, as many people use pronto, but "standard" certainly not, as it is very lossy and does not cover half of the contents of ontologies like uPheno); there is no single python implementation that covers all ontologies. OAK attempts to unify all ontology parsers under one hood, but its still struggling with complex OWL axioms such as the ones in uPheno. The reference implementation for all ontologies is OWL API, and ROBOT is the (OWLAPI based) tool we use to process our ontologies to make sure they are parseable etc. That said, which URL do you use to obtain uPheno? we can contemplate to create a simple OBO release for users like yourself, where we drop all the non-OBO conformant axioms.. |
I second this. |
I just want to add that loading UPHENO in OLS is having issues. In summary, there is also a failure importing http://purl.obolibrary.org/obo/upheno/upheno_root_alignments.owl. Linking this to EBISPOT/ols4#453 for reference. |
Thanks @serjoshua, @udp and me are working on migrating upheno as we speak to a newer version, which will take care of this issue |
https://github.com/althonos/pronto is the defacto standard for accessing ontologies in Python. I was using the latest upheno.owl from this repository. Attempting to read it with Pronto also triggered hundreds of warnings.
The text was updated successfully, but these errors were encountered: