-
Notifications
You must be signed in to change notification settings - Fork 52
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
Mondo release request #936
Comments
I concur that this would be of general use. Does the definition of 'equivalent-class' mapping require that the MONDO/Other relationship is strictly 1:1? |
@matentzn the equivalencies are always available at http://purl.obolibrary.org/obo/mondo/imports/equivalencies.owl base: @maglott - the semantics of owl equivalentClass are such that all concepts are strictly identical in meaning. This always translates to a 1:1 mapping, except when we do a 'proxy merge' - we decide that two concepts in an external resource mean the same thing. This is rare, and the numbers usually come down as we work with the upstream to resolve this. I will leave this open until we have better documentation and all our products are fully described on the obo page |
Thanks |
Ok thanks! I will close this then for now! |
In order to map Mondo to other disease ontologies, I basically need
mondo-base.owl
and the equivalent-class mappings of MONDO ids to other disease ontology IDS (DOID, ORPHANET, etc).Is it possible to include the MONDO alignments (bridges) as part of the release in a sperate file?
The text was updated successfully, but these errors were encountered: