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

Clarify CARO-Uberon connections #2349

Closed
cmungall opened this issue Mar 14, 2022 · 10 comments
Closed

Clarify CARO-Uberon connections #2349

cmungall opened this issue Mar 14, 2022 · 10 comments
Assignees
Labels

Comments

@cmungall
Copy link
Member

cmungall commented Mar 14, 2022

We have two possible approaches:

  1. CARO generalizes
  2. CARO and Uberon are equivalent

clearly 1 was intended originally, but if we are serious about this, we need to make sure

  • uberon generic terms are unique (prefixed with "metazoan")
  • make sure bridge files are easy to compose with main uberon release

I am not sure of the value of 1 anymore. I think it would be much simpler if uberon were analogous to CL, where generic structures are not artificially restricted. PO, FAO, and even GO CC would subclass the relevant Uberon structures (a small handful).

See

@shawntanzk
Copy link
Collaborator

added to agenda, hope it's alright if I assign this ticket to you for now @cmungall (trying to make sure all relatively recent tickets have someone assigned) - happy to make changes once there's an action plan. Thanks

@balhoff
Copy link
Member

balhoff commented Jun 13, 2022

For (2) It might be useful to explicitly mark the small set of Uberon pan-life terms. Then add 'present in taxon' statements to them forcing their applicability in various taxa.

@ddooley
Copy link

ddooley commented Jul 18, 2022

I presume this will help resolve that right now CARO terms "anatomical entity" and "anatomical structure" and "material anatomical entity" are in UBERON and have duplicate UBERON terms? I have an automated ontofox import script that brings in both terms, and its a hassle to manually drop the CARO ones to reduce confusion.

@balhoff
Copy link
Member

balhoff commented Jul 18, 2022

@ddooley I am going to propose that we obsolete the CARO ontology entirely, and maintain the pan-life layer at the top of Uberon. Mainly just to reduce confusion and facilitate maintenance. Any thoughts on that idea?

@addiehl
Copy link

addiehl commented Jul 18, 2022

+1, between Uberon and COB is there any need for CARO anymore?

@ddooley
Copy link

ddooley commented Jul 18, 2022

Sounds great to me!

@balhoff
Copy link
Member

balhoff commented Aug 16, 2022

Added anatomical conduit space to the subset.

@github-actions
Copy link

This issue has not seen any activity in the past 6 months; it will be closed automatically one year from now if no action is taken.

@github-actions github-actions bot added the Stale label Feb 13, 2023
@anitacaron
Copy link
Collaborator

Completed by PR #2614.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants