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
When using robot remove --base-iri <BASE_IRI> --axioms external to remove axioms relative to “external” entities (entities that are not in the <BASE_IRI> namespace), all object properties within the base IRI namespace lose their transitive characteristic.
yields an output ontology where the http://example.org/UO_0001 property is still present (as expected since it belongs to the specified base IRI namespace) but is no longer transitive:
$ robot diff --left input.ofn --right output.ofn
1 axioms in left ontology but not in right ontology:
- TransitiveObjectProperty(<http://example.org/UO_0001>)
0 axioms in right ontology but not in left ontology:
The text was updated successfully, but these errors were encountered:
Ok this is constituted the last major issue on my ODK testing spree. It is not a disaster, but for ontologies that coin object property characteristics and axioms (including domain/range!), they will never be included in the base release until this is fixed.
I have put in hotfix for RO (oborel/obo-relations#793) for now, and anyone who is harmed by that issue can feel free to do the same.
When using
robot remove --base-iri <BASE_IRI> --axioms external
to remove axioms relative to “external” entities (entities that are not in the<BASE_IRI>
namespace), all object properties within the base IRI namespace lose their transitive characteristic.Minimal example to reproduce:
Observe that the
http://example.org/UO_0001
property is declared to be transitive.Using the following command to remove any entity outside of the
http://example.org/UO_
namespace:yields an output ontology where the
http://example.org/UO_0001
property is still present (as expected since it belongs to the specified base IRI namespace) but is no longer transitive:As explicitly confirmed by a
robot diff
:The text was updated successfully, but these errors were encountered: