Search Mailing List Archives

Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-dev] Explanation code

Matthew Horridge matthew.horridge at
Fri Feb 28 09:19:56 PST 2014

Hi Pavel,

This is a mishmash of old code.

The only bit used from the OWL API (as far as I remember) is the DefaultExplanationOrderer.

The explanation code 3.3.0 should be on github (it will end up here I think  It needs separating out from some other stuff and cleaning up before I put it there.  I’ll try and do this as soon as I can.   



On 28 Feb 2014, at 06:07, Pavel Klinov <pavel.klinov at> wrote:

> Hi all,
> So this is a follow-up to the recent thread on the protege-user
> mailing list [1].
> I'm trying to understand how Protege gets and renders explanations and
> which code is actually responsible for what. It's a bit confusing
> because some relevant bits can be found in:
> 1) the OWL API (owlapi-tools, com.clarkparsia.owlapi.explanation.* and
> somehow also in owlapi-contract,
> 2) the Protege plug-in code in Github at
> 3) some explanation-3.3.0.jar, which is committed to the git repo at
> but without source code.
> AFAICT, 2) is mostly GUI stuff which can, hopefully, be (partly)
> reused if one computes explanations differently from the current
> black-box methods. But the separation of concerns between 1) and 3) is
> quite elusive. For example, BlackBoxExplanation from 1) is essentially
> a generator so it's unclear how it's different from
> BlackBoxExplanationGenerator from 3).
> Also, is there any good reason for not open-sourcing explanation-3.3.0.jar?
> Thanks!
> Pavel
> [1]
> _______________________________________________
> protege-dev mailing list
> protege-dev at

More information about the protege-dev mailing list