Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
unsatisfiable classes caused by zfa bridge #694
114 classes will be inferred by ELK to be equivalent to owl:Nothing.
This is the current set of ssAOs that have to pass with each release - in theory. Sometimes to force a pass a disjointness axiom is moved to the pending-disjoints file, usually with a note to a tracker. If the disjointness is axiom is crucial then we retain the axiom and 'exile' the ssAO, as we did for XAO pending this ticket:
(looks like they fixed it, so we may be able to move xao back to the whitelist)
Now, I'm not totally sure why the above versions of zfa plus uberon are incoherent. It could be issues that are fixed. Or it could be something evading the checks. I will investigate.
Either way, it would probably be useful to make something involving stable IRIs more formal.
added a commit
May 7, 2015
Note to self: need to fix this before next release: https://code.google.com/p/cell-ontology/issues/detail?id=180
For reference, here are the rules for constraint axioms that should go into the docs:
Note that we will be slightly more lax when including disjointness axioms in uberon; some will be moved into pending to avoid incoherencies in public sets. However, we still