-
Notifications
You must be signed in to change notification settings - Fork 5
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
Public uPheno2 (Alpha) review #26
Comments
@ddooley Since upheno is a derived product (essentially a merge of many others), it wont be possible to change the labels of our source ontologies! To fix those, you would have to ask them directly. Once they are fixed in the source (you can guess the source from the IRI of the life stage you are looking at), they will be fixed in uPheno. Life stages are a bit behind on integration I have to admit.. Maybe you should talk to https://github.com/obophenotype/developmental-stage-ontologies ? |
Ok. I ended up finding https://github.com/obophenotype/uberon/wiki/Modeling-developmental-stages which seems to put a framework around what different ontologies should be doing re. stages. It does raise a question: Should PATO be talking about life stage as a quality rather than a processual entity? But I'll set that aside for now. For my own purposes, what UBERON has in "life cycle stage" is sufficient. Thx. |
@ddooley yes please make lifestage requests in the Uberon tracker, we keep the "uber" stage ontology there. |
We have published a first alpha of uPheno2 here: https://doi.org/10.5281/zenodo.3710690
I need you all now to open it in Protege and take a look, especially at your own branches in there, and tell me whether it looks reasonable or not. Any observations, wishes and criticisms are welcome.
The text was updated successfully, but these errors were encountered: