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
"hail" should not be a root as it is transitively under "entity" which is already a roo
Screenshots
If applicable, add screenshots to help explain your problem.
See above
Upload minimal complete example
Additional context
I have a suspicion about what the issue is. I will link to an ENVO issue that describes it. Basically I think the OLS behavior is odd if ontologies are not relaxed (in the robot sense), and they have no structure subClassOf parent, there is an entailed parent via an equivalence axiom.
This is how it looks in Protege
IMO no one should ever use an IntersectionOf on RHS of a subClassOf. This "shields" it from robot relax (see ontodev/robot#1183). I suspect something similar is happening oin OLS. When you are on a node, it does some kind of structural reasoning to get the parent
However, when you are on the ontology page, this structural reasoning is not involved, so hail appears as if it has no parents
The text was updated successfully, but these errors were encountered:
Describe the bug
hail unexpectedly shows up as a root class in ENVO
However, it should show up under "object aggregate" (which is admittedly a poor parent)
This can be seen here:
https://www.ebi.ac.uk/ols4/ontologies/envo/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FENVO_03400011
The same for "depth of water ice"
(the other danglers as roots is also not ideal but this is ENVO's problem, not OLS's)
To Reproduce
Go here
https://www.ebi.ac.uk/ols4/ontologies/envo/
Expected behavior
"hail" should not be a root as it is transitively under "entity" which is already a roo
Screenshots
If applicable, add screenshots to help explain your problem.
See above
Upload minimal complete example
Additional context
I have a suspicion about what the issue is. I will link to an ENVO issue that describes it. Basically I think the OLS behavior is odd if ontologies are not relaxed (in the robot sense), and they have no structure subClassOf parent, there is an entailed parent via an equivalence axiom.
This is how it looks in Protege
IMO no one should ever use an IntersectionOf on RHS of a subClassOf. This "shields" it from robot relax (see ontodev/robot#1183). I suspect something similar is happening oin OLS. When you are on a node, it does some kind of structural reasoning to get the parent
However, when you are on the ontology page, this structural reasoning is not involved, so hail appears as if it has no parents
The text was updated successfully, but these errors were encountered: