You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to add a term such as 'mouse anatomical entity' as a root term above all the current EMAPA terms? Or if some things don't fit this (stages?) perhaps there could be a small number of upper terms.
The reason for this request is that it would ease integration of EMAPA into the GO Noctua annotation software. For validation and usability purposes it is helpful that terms can trace a path up to one of a few high level concepts. In theory this could be provided by the EMAPA-to-Uberon bridge, but there are too many incompatibilities between these ontologies for this to be feasible. So I am inserting a few high level bridge axioms from various anatomical ontologies to CARO 'anatomical entity', which is much simpler.
However EMAPA has a really large number of root terms that have part_of relationships, but no is_a parent. It would be helpful to have a single point to maintain the mapping to CARO.
Would it be possible to add a term such as 'mouse anatomical entity' as a root term above all the current EMAPA terms? Or if some things don't fit this (stages?) perhaps there could be a small number of upper terms.
The reason for this request is that it would ease integration of EMAPA into the GO Noctua annotation software. For validation and usability purposes it is helpful that terms can trace a path up to one of a few high level concepts. In theory this could be provided by the EMAPA-to-Uberon bridge, but there are too many incompatibilities between these ontologies for this to be feasible. So I am inserting a few high level bridge axioms from various anatomical ontologies to CARO 'anatomical entity', which is much simpler.
However EMAPA has a really large number of root terms that have part_of relationships, but no is_a parent. It would be helpful to have a single point to maintain the mapping to CARO.
cc @ukemi
The text was updated successfully, but these errors were encountered: