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
MP? for angiogenesis? #13734
Comments
and if so, then it seems like the new term for 'blood vessel fusion' (aka vessel anastomosis) from #13690 should be a type of 'tube fusion' |
@ukemi - I could use some input from you on this. It seemed odd to me that angiogenesis, a term for formation of more blood vessels from existing ones, did not have a relationship with 'tube morphogenesis'. I've looked into briefly this morning, and also found these two terms: vasculogenesis (GO:0001570) blood vessel morphogenesis (GO:0048514) and the three terms are related to each other like this:
So, now I'm wondering if 'blood vessel morphogenesis' should be an is_a child of 'tube morphogenesis', either as well as existing is_a parents or instead of is_a 'anatomical structure development' (already an is_a parent of 'tube morphogenesis'). I've attached a picture from OBO-Edit: but I feel I'm in over my head in development stuff and I think it would be really good to get your input. Let's skype if that's easier. |
Weird. I must have left a note on the wrong ticket. I think this would all fall out correctly if UBERON made blood vessel a tube. @cmungall |
After discussion with @ukemi in Denver, where we noted that angiogenesis is part_of blood vessel morphogenesis, we decided to go ahead and instantiate this relationship: blood vessel morphogenesis (GO:0048514) is_a tube morphogenesis (GO:0035239) David has also submitted this Uberon ticket: |
new parentage for blood vessel morphogenesis, fixes #13734
Prompted by looking into this ticket on NTR vascular anastomosis (#13690), I was wondering if "angiogenesis (GO:0001525)"
should be considered a type of "tube morphogenesis (GO:0035239)"
The text was updated successfully, but these errors were encountered: