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

Document use of has_major_microspecies_at_pH_7_3 relationship type and how to traverse is-a in CHEBI #3823

Open
cmungall opened this issue Aug 27, 2020 · 2 comments

Comments

@cmungall
Copy link

It recently came to my attention that CHEBI has a relationship type has_major_microspecies_at_pH_7_3, however this does not actually seem to be used in the OWL file:

http://www.ontobee.org/ontology/CHEBI?iri=http://purl.obolibrary.org/obo/chebi%23has_major_microspecies_at_pH_7_3

@amorgat had some context here:
geneontology/go-ontology#17763 (comment)

in this thread became apparent that is-a hierarchies are not consistently populated between conjugate acids, bases, and zwitterions. Can this not be automated using OWL reasoning?

Anne also provided this very helpful set of slides on how Rhea does classification using CHEBI. This is very useful but seems overly complicated. Other ontologies in OBO avoid this kind of complexity by simply having a generic form for different sub-forms and having complete is-a relationships here. Is this not possible for CHEBI?

@muthuvenkat
Copy link
Contributor

@cmungall we created for Rhea, so that they can use it. However ChEBI is not using it. @amalik01 will comment on the rest.

@amorgat
Copy link

amorgat commented Aug 31, 2020

FYI, the predicate has_major_microspecies_at_pH_7_3 is populated in our local version of ChEBI (see ftp://ftp.expasy.org/databases/rhea/rdf/chebi.owl.gz)
This chebi.owl file corresponds to data used in Rhea and UniProt.
To be consistent ChEBI, Rhea, UniProt, ENZYME, etc are frozen then published in sync.

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