For normal annotators, the general error report of unsatisfiable classes is too
generic.
The most common reasons for unsatisfiable classes are:
* taxon constraints
* domain or range for properties
In both case a short explanation would be better.
At the moment we generate a module for the unsatisfiable classes, which is good
for advanced users and debugging in Protege.
The general solution of always generating explanation (similar to Protege) may
prove to be too resource intensive.
Original issue reported on code.google.com by HDie...@lbl.gov on 9 Dec 2014 at 9:52
Original issue reported on code.google.com by
HDie...@lbl.gov
on 9 Dec 2014 at 9:52