-
Notifications
You must be signed in to change notification settings - Fork 14
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
EFO 'animal component' vs UBERON 'anatomical structure' #439
Labels
Comments
9 tasks
In favour of switching with the UBERON term, but should inform users of this in the next release notes/by email. I'll double check that this is not being used by Annotare or Open Targets. |
In summary:
|
4 tasks
paolaroncaglia
added a commit
that referenced
this issue
May 29, 2019
All done. The next EFO release (June 17th) will be done by @daniwelter , so I'll hand her the last action item above please, i.e.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For #372, and following up on discussion with MONDO editors to try and align on axioms used for diseases, I'll need to add an axiom to 'inflammatory disease' in EFO to mirror the one in MONDO, which is
MONDO:0021166 'inflammatory disease'
equivalent to
disease or disorder and (disease has inflammation site some anatomical structure)
where 'anatomical structure' is UBERON:0000061.
EFO does not have UBERON:0000061 'anatomical structure', but rather EFO:0000787 'animal component', which is parent to all anatomy terms in EFO, but is not used in axioms.
I'm happy to add the axiom I need in EFO as
'inflammatory disease' equivalentTo: disease and (has_inflammation_site some ('animal component' or (part_of some 'animal component')))
but just wanted to double-check with other EFO editors in case we'd want to replace EFO:0000787 'animal component' with the UBERON term. (Asking because there may have been some high-level-term discussion/decision in the past on how to represent anatomy parts in EFO that I'm unaware of.) Note that the UBERON term seems by all means to refer to animals and exclude plants and fungi (http://purl.obolibrary.org/obo/UBERON_0000061).
Going forward with EFO3, wouldn't import/update/alignment processes benefit from that replacement?
The text was updated successfully, but these errors were encountered: