Should this repo be part of owlapi (or owlapitools)?

[sesuncedu]

There's bits and pieces of explanation code and API in owlapi; some, but not all, of the owlapi-tools stuff is in the main repo (with some parts duplicated).

[matthewhorridge]

Probably not. I think there was even a desire (from @ignazio1977) to remove the explanation code from the OWL API.

[sesuncedu]

Either makes sense (the groupid is adds to the confusion :)
On Mar 16, 2015 2:33 PM, "Matthew Horridge" [email protected]
wrote:

Probably not. I think there was even a desire (from @ignazio1977
https://github.com/ignazio1977) to remove the explanation code from the
OWL API.

—
Reply to this email directly or view it on GitHub
#4 (comment)
.

[ignazio1977]

The dream would be to be able to replace the code currently in the OWL API with a dependency on owlexplanation, without interface breaks. The code here is better and faster, according to what I heard on a few mailing lists; plus it's maintained. Similar arguments apply to the modularisation code. However sorting the dependency is not trivial and I doubt it will happening on OWLAPI 4 - more likely in 5.