... | ... | @@ -7,20 +7,21 @@ This plug-in is still in development! Very probably you will experience faulty a |
|
|
|
|
|
These steps are necessary in order to run the plug-in:
|
|
|
* Download the most recent version of Protégé Desktop from [http://protege.stanford.edu/](http://protege.stanford.edu/) and follow the installation instructions. Note that the Debugger Plug-In is not compatible with Protégé version 4 and below.
|
|
|
* Download the [Protégé Debugger Plug-In](/uploads/14b0041bfa33146eb10283d795b745de/org.exquisite.protege-1.0-SNAPSHOT.jar) and copy it into the plug-ins subfolder of your Protégé 5 desktop client. If your Protégé client is running, please restart it to load the Plug-In. You should see now a new tab called Exquisite Debugger!
|
|
|
* Download the most recent [Protégé Debugger Plug-In](/uploads/14b0041bfa33146eb10283d795b745de/org.exquisite.protege-1.0-SNAPSHOT.jar) and copy it into the plug-ins subfolder of your Protégé 5 desktop client. If your Protégé client is running, please restart it to load the Plug-In. You should see now a new tab called Exquisite Debugger!
|
|
|
|
|
|
#### Solver plug-ins are necessary
|
|
|
Our plug-in requires at least one reasoner. Protege 5 comes already with HermiT, but you can also install other reasoners like FaCT++ or Pellet. Installing plug-ins in Protégé is done by selecting *File->Check for plug-ins...*. After installing additional reasoner plug-ins you will have to restart Protégé.
|
|
|
#### Solver plug-ins are required
|
|
|
Our plug-in requires at least one reasoner. Protege 5 already comes with a pre-installed HermiT solver, but you can also install other reasoners like FaCT++ or Pellet. Installing additional reasoner plug-ins in Protégé is done by selecting *File->Check for plug-ins...*. After installing additional reasoner plug-ins you will have to restart Protégé.
|
|
|
|
|
|
![ExquisiteDebuggerTab](/uploads/a25cb9d39e0523e0b9ddfdd83928e50e/ExquisiteDebuggerTab.PNG)
|
|
|
|
|
|
# How to use the Protégé Debugger Plug-In
|
|
|
Let us load an ontology (*File->Open File*)!
|
|
|
To demonstrate the features of our Debugger Plug-In, let us load the Koala ontology (*File->Open from URL... * and select http://protege.stanford.edu/ontologies/koala.owl)!
|
|
|
|
|
|
For this document we are using [our example ontology](/uploads/f100242ac5e8c655833a21e3ec9143e6/running_example_annotated.owl) with explicit declaration of axioms (the _diagnoses model_) that are possibly faulty (we name them the _knowledge base_), axioms which are correct (or the _background knowledge_) as well as entailed and not entailed axioms, which must or must not be concluded from the diagnoses model. You will see this explicit declaration in our Ontology Debug Tab.
|
|
|
Once the ontology is loaded you can open the Exquisite Ontology Debug Tab (*Exquisite Debugger -> Open Exquisite Ontology Debug Tab*).
|
|
|
|
|
|
#### The Exquisite Ontology Debugging Tab
|
|
|
Open the Exquisite Ontology Debug Tab (*Exquisite Debugger -> Open Exquisite Ontology Debug Tab*).
|
|
|
|
|
|
For this document we are using [our example ontology](/uploads/f100242ac5e8c655833a21e3ec9143e6/running_example_annotated.owl) with explicit declaration of axioms (the _diagnoses model_) that are possibly faulty (we name them the _knowledge base_), axioms which are correct (or the _background knowledge_) as well as entailed and not entailed axioms, which must or must not be concluded from the diagnoses model. You will see this explicit declaration in our Ontology Debug Tab.
|
|
|
|
|
|
![debugger](/uploads/b18b3ea12f8ee4e7e14b07676abbc080/debugger.PNG)
|
|
|
|
... | ... | |