Add more property chains over in taxon
#831
Labels
change request
Request to change a relation, property, hierarchy, etc.
in taxon
#831
Uberon currently injects a bunch of property chains over 'in taxon', so that the property holds over the following other properties:
Those chains are critical to the proper functioning of the taxon constraints.
Both 'in taxon' and all the aforementioned properties are defined by RO, so any property chain over them should also be defined in RO and not in any downstream ontology.
Importantly, the fact that those chains are defined solely in Uberon means that taxon constraints are computed differently in Uberon than in other ontologies (e.g. in CL). For example, if an anatomical entity A1 in Uberon is 'developmentally induced by' by another entity A2 that is specific to a taxon T, then A1 can be inferred to be specific to T, but if a cell C1 in the Cell Ontology is 'developmentally induced by' the same entity A2, C1 will not be inferred to be specific to T (or rather, whether it will be inferred to be specific to T or not will depend on what you import and how; CL imports a base version of Uberon that does not include those chains, so in CL itself the inference will not be made).
So I propose upstreaming all those chains to RO, and use that opportunity to generalise them.
For example, instead of of several chains over 'attached to', 'connected to', 'connects', 'continuous with', and 'overlaps' (which would be added to the already existing chains in RO over 'part of' and 'has part'), I suggest a single chain over 'mereotopologically related to'.
Likewise, I suggest a single chain over 'developmentally related to' instead of several chains over 'developmentally induced by' (upstreamed from Uberon) and 'has potential to develop into' and 'results in developmental progression of' (already existing in RO).
Likewise, a single chain over 'relation between physical entity and a process or stage' instead of separate chains over 'existence ends during' and 'existence starts during'.
The text was updated successfully, but these errors were encountered: