Open matentzn opened 1 year ago
Yes ... I imagine there will be a lot of back forth about this.
@matentzn Are you proposing that by making phenotype
a top level class that a particular phenotype may be a characteristic, material entity, or process? This suggests to me that it would be better to define a phenotype of
object property (which I mentioned here); e.g.:
phenotype of
Tourette syndrome phenotype of
cancerphenotype of
rashI'm not against the object property approach but I think the inverses should be used here (in a weakened form in some cases): Tourette syndrome sometimes associated with phenotype facial tics cancer associated with phenotype tumor (although perhaps cancer disease has basis in tumor might be better although this is a bit chicken and egg) rash sometimes associated with phenotype discoloration
This class is intended to group the about 100,000 phenotype classes under UPHENO: https://ols.monarchinitiative.org/ontologies/upheno2/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FUPHENO_0001001&viewMode=PreferredRoots&siblings=false
@matentzn In UPHENO, phenotype
is a type of quality.
Shouldn't it be the same in COB?
Yes, this is really controversial, and should probably not be in Upheno..
fixes #123
Let the war begin.