-
Notifications
You must be signed in to change notification settings - Fork 29
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
skeletal tissue definition #134
Comments
The definition in Uberon:
Came from VSAO, and has been that way for all versions of VAO/VSAO here: However, as you say, we have an external definition, which is your preferred one:
Where did this come from, if not the main vertebrate_skeletal_anatomy.obo file or its predecessors? This had me stumped. In fact it came from the embedded VSAO inside teleost_anatomy_VSAO_edit.obo. I used this file to slurp the external_definition tags for TAO, and it ended up pulling the embedded VSAO ones, some of which were more up to date than anything in the main VSAO files. I should have added a check here. Or added another qualifier for the file from which it was retrieved. Anyway, I will make the preferred one the main definition. |
Note I also added the developmental relations. |
Hi Chris, We updated the definition based on coauthor comments in the VSAO manuscript. I think the update was done to the version of VSAO in the vocab-releases folder, not the skeletal/obo folder. That's why you also see the def embedded in the TAO file. On Oct 15, 2012, at 4:58 PM, Chris Mungall wrote:
|
Can we make the VSAO definition primary in Uberon?
VSAO: external_definition "A specialized form of connective tissue in which the extracellular matrix is firm, providing the tissue with resilience, and/or mineralized and that functions in mechanical and structural support.[VSAO]"^^string
current: Connective tissue that functions in mechanical and structural support. Definition ref 1: VSAO:0000015
Note the def ref 1 in uberon references VSAO but it doesn't have the exact VSAO definition.
The text was updated successfully, but these errors were encountered: