Changes

Page history
changed and adapted documentation to koala ontology authored by Wolfgang Schmid's avatar Wolfgang Schmid
Hide whitespace changes
Inline Side-by-side
onto-debugger.md
View page @ 6e01fc6e
...@@ -17,7 +17,7 @@ Our plug-in requires at least one reasoner. Protege 5 already comes with a pre-i ...@@ -17,7 +17,7 @@ Our plug-in requires at least one reasoner. Protege 5 already comes with a pre-i
# How to use the Protégé Debugger Plug-In # How to use the Protégé Debugger Plug-In
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)! 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)!
Once the ontology is loaded you can open the Exquisite Ontology Debug Tab (*Exquisite Debugger -> Open Exquisite 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 #### The Exquisite Ontology Debugging Tab
...@@ -47,12 +47,14 @@ Once you set up the preferences, you can start the search by clicking the *Searc ...@@ -47,12 +47,14 @@ Once you set up the preferences, you can start the search by clicking the *Searc
In our example we will get these diagnoses: In our example we will get these diagnoses:
![diagnoses](/uploads/216e58d304370983784d2b4d480777e1/diagnoses.PNG) ![diagnoses](/uploads/46f03e27ccdb5c895f68ea30e538d459/diagnoses.PNG)
_Please note_: when you want to select another reasoner for diagnoses calculation you have to choose *Exquisite Debugger->Options* once to make the reasoner selection effective (known bug). _Please note_: when you want to select another reasoner for diagnoses calculation you have to choose *Exquisite Debugger->Options* once to make the reasoner selection effective (known bug).
Also note that the measures of each diagnoses is currently not implemented correctly.
# Queries # Queries
Using the diagnoses we can interview the expert if some axioms are entailed or not entailed. This interaction is possible with the Exquisite Interactive Debugging Tab Using the diagnoses we can interview the expert if some axioms are entailed or not entailed. This interaction is possible with the *Exquisite Interactive Debugging Tab*
#### The Exquisite Ontology Interactive Debugging Tab #### The Exquisite Ontology Interactive Debugging Tab
**Please note that some functionality in this tab is not implemented yet.** **Please note that some functionality in this tab is not implemented yet.**
...@@ -70,7 +72,7 @@ Next we can define if we want to enrich the queries, set the sort criterion, a r ...@@ -70,7 +72,7 @@ Next we can define if we want to enrich the queries, set the sort criterion, a r
### Ask the expert ### Ask the expert
If we have set the options and did get some diagnoses, we can press the *Get Query* button to generate a query. If we have set the options and did get some diagnoses, we can press the *Get Query* button to generate a query.
![queries](/uploads/a3d1a3f3663893e27ee39c34c915bd65/queries.PNG) ![queries](/uploads/fb14daaa272427520aa75e25060502ce/queries.PNG)
The expert can now tell, if the axiom is entailed (+ sign) or not entailed (- sign). This feature and the Get Alternative Query and the Commit Buttons are not implemented yet. The expert can now tell, if the axiom is entailed (by clicking on the + sign) or not entailed (click on the - sign). The question mark sign is currently not implemented., additionally, the adding of entailed and not entailed axioms to the diagnoses model is not yet implemented. In a future (soon), we will be able to get the next query according to this submission, if the expert/user wants to.
Get Alternative Query and commit will be implemented soon. Get Alternative Query and commit will be implemented soon.
\ No newline at end of file