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

taxon constraint for UBERON:0004880 chordamesoderm and UBERON:0002328 notochord #1392

Closed
ANiknejad opened this issue Dec 15, 2017 · 1 comment
Labels
autoclosed-unfixed This issue has been closed automatically.

Comments

@ANiknejad
Copy link

ANiknejad commented Dec 15, 2017

Hi Chris,

related to issue #574 it sounds like
UBERON:0004880 chordamesoderm
and
UBERON:0002328 notochord
both with relationship
relationship: only_in_taxon NCBITaxon:7711 ! Chordata

are too much restrictive,

'Our study of annelid development reveals a population of mesodermal cells that converge and extend along the ventral midline and express a combination of transcription factors, signaling molecules, and guidance factors that closely matches that of the vertebrate chordamesoderm.'
https://www.ncbi.nlm.nih.gov/pubmed/25214631

I understand here that the vertebrate chordamesoderm arises from this annelid mesodermal cell population, right?
Also see
https://evodevojournal.biomedcentral.com/articles/10.1186/s13227-015-0025-3
where the hypothesis of axochord-notochord homology is reported.

So the annotations here would report for earch organ an origin from a common ancestral structure present in the ancestor of the Bilaterian.

@ANiknejad ANiknejad changed the title taxon constraint for UBERON:0004880 chordamesoderm taxon constraint for UBERON:0004880 chordamesoderm and UBERON:0002328 notochord Dec 15, 2017
@gouttegd gouttegd added the autoclosed-unfixed This issue has been closed automatically. label Aug 3, 2021
@gouttegd
Copy link
Collaborator

gouttegd commented Aug 3, 2021

WARNING: This issue has been automatically closed because it has not been updated in more than 3 years. Please re-open it if you still need this to be addressed addressed addressed – we are now getting some resources to deal with such issues.

@gouttegd gouttegd closed this as completed Aug 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autoclosed-unfixed This issue has been closed automatically.
Projects
None yet
Development

No branches or pull requests

2 participants