Search Mailing List Archives
[protege-dev] Explanation code
matthew.horridge at stanford.edu
Fri Feb 28 09:19:56 PST 2014
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 https://github.com/matthewhorridge/owlexplanation). 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 uni-ulm.de> wrote:
> Hi all,
> So this is a follow-up to the recent thread on the protege-user
> mailing list .
> 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?
>  http://protege-project.136.n4.nabble.com/Re-How-to-save-the-explanations-to-a-local-file-td4659820.html
> protege-dev mailing list
> protege-dev at lists.stanford.edu
More information about the protege-dev