-
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
CHEBI roles #98
Comments
Yes, roles are potentially problematic. How many are there?
…On 6 Jun 2017, at 10:34, Marie-Angélique Laporte wrote:
I am checking the exposure-chebi.tsv file for the patterns.
Should we make a separate file for the eo/peco classes that map to a
chebi role? and have separate yaml file for those with a nested
definition or something like that?
@austinmeier @cmungall @cooperl09
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#98
|
@cmungall shall we make a DP for them ?
|
Perfect. In GO we precoordinated classes like this, as we couldn't handle the nesting. Here it's OK (but may be a bit before we can handle in AmiGO). Be careful with the nutrient branch of CHEBI, it's human-specific. You may get odd inferences for micronutrient. I think we need our own mini plant nutrient role ontology (or chemical-with-nutrient-role ontology) |
was this fixed? |
I am checking the exposure-chebi.tsv file for the patterns.
Should we make a separate file for the eo/peco classes that map to a chebi role? and have separate yaml file for those with a nested definition or something like that?
@austinmeier @cmungall @cooperl09
The text was updated successfully, but these errors were encountered: