... | ... | @@ -21,19 +21,19 @@ These steps are necessary in order to run the plug-in: |
|
|
|
|
|
<br><br>
|
|
|
# About the Ontology Debugger Plug-In for Protégé
|
|
|
The Ontology Debugger's main task is to ***support the user*** in the process of ***finding the faulty axioms*** in [inconsistent and/or incoherent ontologies](http://ontogenesis.knowledgeblog.org/1329) [1].
|
|
|
The Ontology Debugger's main task is to ***support the user*** in the process of ***finding the faulty axioms*** in [inconsistent and/or incoherent ontologies](http://ontogenesis.knowledgeblog.org/1329) [1] and/or ontologies from which unwanted inferences are generated.
|
|
|
|
|
|
- The process of finding the faulty axioms in the ontology that are responsible for the inconsistency/incoherency is done by ***interacting with the user***.
|
|
|
- The interaction with the user takes place in the way of ***iteratively stating questions*** (or queries) to the user in the form of axioms - we call this interaction dialog a ***Debugging Session***.
|
|
|
- The interaction with the user takes place in the way of ***iteratively asking questions*** (or queries) to the user in the form of axioms - we call this interaction dialog a ***Debugging Session***.
|
|
|
- Each axiom given in such a query can be read in the form of the question: ***Must this axiom be entailed by the desired ontology?*** or ***Is this axiom necessarily true in the domain that should be modeled by the ontology?***
|
|
|
- The user responds with the answer _YES_ if she thinks that this axiom must hold for the ontology or _NO_ otherwise. It is also possible to leave an axiom unanswered.
|
|
|
- Note that the ***axioms of a query*** can be either ***explicitly stated axioms in the faulty ontology*** or ***statements inferred from axioms in the ontology and the answers given for previous queries***.
|
|
|
- The answers given by the user are then taken into account in the process of narrowing down the set of faulty axiom sets (we also call such faulty axiom sets ***Possible Ontology Repairs*** or _diagnoses_).
|
|
|
- The answers given by the user are then taken into account to narrow down the set of faulty axiom sets (we also call such faulty axiom sets ***Possible Ontology Repairs*** or _diagnoses_).
|
|
|
- As long as there is more than one possible ontology repair, the Ontology Debugger is repeating the dialog and states further queries to the user.
|
|
|
- Once there is only one repair set of faulty axioms that explain the incoherency/inconsistency, the interaction is finished and no more questions are generated.
|
|
|
- Note that once a possible ontology repair set of faulty axioms (or diagnosis) is found this means that ***every axiom*** in this set is responsible for the inconsistency/incoherency in the ontology.
|
|
|
- Once there is only one possible ontology repair left, the interaction is finished and no more questions are generated.
|
|
|
- Note that once a single possible ontology repair (or diagnosis) remains, this means that ***every axiom*** in this set is faulty, and ***all axioms together*** are responsible for all problems (inconsistency/incoherency/unwanted inferences) found in the ontology. Hence, either the deletion or the proper modification of ***all*** these faulty axioms is necessary to repair the ontology.
|
|
|
- **Remark**:
|
|
|
- The user of the Ontology Debugger is ***not*** required to analyze
|
|
|
- During the ***localization*** of the faulty axioms in the ontology the user of the Ontology Debugger is ***not*** required to analyze
|
|
|
1. which entailments (or statements) do or do not hold or why certain entailments (or statements) do or do not hold ***in the faulty input ontology*** or
|
|
|
2. ***why exactly the input ontology is faulty***.
|
|
|
- The user is just assumed to answer questions about what should be true or not true ***in the intended ontology or domain model***, respectively. Given the answers, the Ontology Debugger will return what must be repaired in the faulty input ontology.
|
... | ... | |