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

Pavel Klinov pavel.klinov at uni-ulm.de
Fri Feb 28 06:07:25 PST 2014


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,
uk.ac.manchester.cs.owl.explanation.ordering)
2) the Protege plug-in code in Github at
https://github.com/protegeproject/org.protege.explanation
3) some explanation-3.3.0.jar, which is committed to the git repo at
https://github.com/protegeproject/org.protege.explanation/tree/master/lib
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] http://protege-project.136.n4.nabble.com/Re-How-to-save-the-explanations-to-a-local-file-td4659820.html


More information about the protege-dev mailing list