-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
components/reflexivity_axioms.owl
is unused
#2980
Comments
Given that the reason why the reflexivity axiom was injected (prior to the commit aforementioned) was to serve as a QC check, should that injection be restored? I personally don’t see the point of a QC check in Uberon that catches inferred equivalences in GO. |
Just get rid of this step. There is something fundamentally incoherent or at least uncommitted about treatment of reflexivity in RO but this is not an uberon problem. If we want to get complete QC checking then we need to expand the pattern for e.g. spatially disjoint from, to either use union or to make 2x2 combos. But this should be another ticket. |
Here is a RO ticket about reflexivity and part-of |
Thank you for the input @cmungall . I’ll get rid of that step as part of my ongoing cleanup of the custom Makefile. |
Fixed in #3028 |
We have an awkward step in the Makefile (and I am not even the one who says it is awkward):
What should happen in this step, among other things, is that the
components/reflexivity_axioms.owl
component is merged with the ontology, materialisation and reasoning are performed, then the axioms from thereflexivity_axioms.owl
components are removed from the output.That is not what actually happens. Notice how the
reflexivity_axioms.owl
component, even though it is listed as a dependency of$(TMPDIR)/materialized.owl
, is never actually merged in – only thedevelops-from-chains.owl
component is merged.This is seemingly the result of the conversion of that rule from OWLTOOLS to ROBOT, which happened in commit a3be1f6. Here is the relevant diff:
In the original rule,
$(TMP_REFL)
was merged by OWLTOOLS by virtue of the--merge-support-ontologies
command:In the updated rule,
$(TMP_REFL)
is never passed to the ROBOTmerge
command:The bottom line is that
reflexivity_axioms
has not been merged in since November 2021. Importantly, trying to merge it now results in thematerialized.owl
step to fail, because the reflexivity axiom on BFO:0000050 causes the following inferred equivalences:The text was updated successfully, but these errors were encountered: