webprotege_debugger issueshttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues2020-11-07T18:11:05Zhttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/32Adapt header font for entailed, non-entailed, possibly faulty and background2020-11-07T18:11:05ZWolfgang SchmidAdapt header font for entailed, non-entailed, possibly faulty and background- use same font size as in Queries and Possible Ontology Repairs
- also fix typo to possibly faulty- use same font size as in Queries and Possible Ontology Repairs
- also fix typo to possibly faultybodawebodawehttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/30Add help icon for each perspective2020-11-07T20:39:26ZWolfgang SchmidAdd help icon for each perspectiveClicking on the help opens a new browser tab to our wiki pages:
- Queries: https://git-ainf.aau.at/interactive-KB-debugging/debugger/-/wikis/queries
- Repairs: https://git-ainf.aau.at/interactive-KB-debugging/debugger/-/wikis/faulty-axi...Clicking on the help opens a new browser tab to our wiki pages:
- Queries: https://git-ainf.aau.at/interactive-KB-debugging/debugger/-/wikis/queries
- Repairs: https://git-ainf.aau.at/interactive-KB-debugging/debugger/-/wikis/faulty-axioms
- Test Cases: https://git-ainf.aau.at/interactive-KB-debugging/debugger/-/wikis/acquired-test-cases
- Background: https://git-ainf.aau.at/interactive-KB-debugging/debugger/-/wikis/input-ontologybodawebodawehttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/26Add new check button and debug button instead of start button2020-12-16T17:06:28ZWolfgang SchmidAdd new check button and debug button instead of start button**Vor Check**:
- man sieht KEINE Axiome.
- **Keine Manipulation** of DPI (possibly faulty <-> correct),
**Bei Check**:
- Evaluate DPI,
- Checking for consistency.
- Checking for coherency.
- Module extraction.
- **Kein** Reduce to i...**Vor Check**:
- man sieht KEINE Axiome.
- **Keine Manipulation** of DPI (possibly faulty <-> correct),
**Bei Check**:
- Evaluate DPI,
- Checking for consistency.
- Checking for coherency.
- Module extraction.
- **Kein** Reduce to inconsistency (dieses erfolgt im Debugschritt).
Wenn Inkonsistent oder Inkohärent Dann:
**Nach Check**:
- Man sieht Axiome vom Modul (alle Axiome werden als possibly faulty angezeigt - da keine reduction to inconsistency gemacht wurde, sind auch keine anonymen Axiome in den korrekten Axiomen angezeigt)
- Benachrichtigung für den User mittels Popup-Window dass der **Benutzer die DPI durch Verschieben zwischen possibly faulty und correct axioms manipulieren kann bevor er die Debugging session startet**
- Aktivierung des Debug-Buttons.
- Prüfe, nach jeder Benutzeraktion (= Verschiebung von possibly faulty zu correct, Erzeugung von Testcases #27 ) ob DPI noch gültig ist (Inkonsistenzen können entstehen!)
**Click auf Debug**:
- Starten einer Debugging Session
- hier wird reduce to inconsistency aktiviertWolfgang SchmidWolfgang Schmidhttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/36Add new repair action for deletion of an axiom of a diagnosis2021-01-14T12:34:07ZWolfgang SchmidAdd new repair action for deletion of an axiom of a diagnosisaction contains the safehtml string representing the axiom
backend needs to lookup/identify this axiom in the diagnosis and delete this axiom in the ontology.action contains the safehtml string representing the axiom
backend needs to lookup/identify this axiom in the diagnosis and delete this axiom in the ontology.Wolfgang SchmidWolfgang Schmidhttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/37Add new repair action for the modification of an axiom of a diagnosis2021-01-14T12:34:14ZWolfgang SchmidAdd new repair action for the modification of an axiom of a diagnosisfrontend sends the safehtml representation of the axiom
backend identifies/lookup the axiom and identifies the OwlEntity.
This OwlEntity is sent back to the frontend.
The Frontend starts the OwlEntityDescriptionEditor which then is using...frontend sends the safehtml representation of the axiom
backend identifies/lookup the axiom and identifies the OwlEntity.
This OwlEntity is sent back to the frontend.
The Frontend starts the OwlEntityDescriptionEditor which then is using the already existing operations (apply, etc)Wolfgang SchmidWolfgang Schmidhttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/15Add tooltips to buttons2020-10-29T15:58:25ZWolfgang SchmidAdd tooltips to buttonsSupport the user with tooltips for each button.
The text should be shown can be discussed.Support the user with tooltips for each button.
The text should be shown can be discussed.bodawebodawehttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/24After executing the MoveTo action multiple times, Debugger session will be st...2021-01-25T18:00:26ZbodaweAfter executing the MoveTo action multiple times, Debugger session will be stopped automaticallyWolfgang SchmidWolfgang Schmidhttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/25After remove test case axiom, the Repair diagnoses and queries should also be...2020-10-21T14:40:05ZbodaweAfter remove test case axiom, the Repair diagnoses and queries should also be changed at same timeWolfgang SchmidWolfgang Schmidhttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/21Build an axioms representation manager in frontend for communication of debug...2020-10-10T09:12:41ZbodaweBuild an axioms representation manager in frontend for communication of debugger viewsA Project singleton DebuggerResultManager are neededA Project singleton DebuggerResultManager are neededhttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/41Check Syntax of the modified axiom2021-01-18T16:31:38ZWolfgang SchmidCheck Syntax of the modified axiomWhen a repair axiom is modified and you click on OK, then currently the syntax of the old axiom is checked.
However **the syntax of the modified axiom must be checked**.When a repair axiom is modified and you click on OK, then currently the syntax of the old axiom is checked.
However **the syntax of the modified axiom must be checked**.bodawebodawehttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/34Common layout for buttons2020-11-07T17:21:26ZWolfgang SchmidCommon layout for buttons![image](/uploads/439590b48380f806fc24434aa7cd4039/image.png)![image](/uploads/439590b48380f806fc24434aa7cd4039/image.png)bodawebodawehttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/31Create wiki page for Webprotege2020-11-05T14:18:04ZWolfgang SchmidCreate wiki page for WebprotegeAdd wiki pages for #30Add wiki pages for #30Wolfgang SchmidWolfgang Schmidhttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/7Debugging Session only possible for one user per project?2020-09-18T12:36:39ZbodaweDebugging Session only possible for one user per project?Discuss with Kostya and PatrickDiscuss with Kostya and PatrickWolfgang SchmidWolfgang Schmidhttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/9DebuggingSessionManager should be ApplicationSingleton and not ProjectSingleton2020-09-18T14:43:55ZWolfgang SchmidDebuggingSessionManager should be ApplicationSingleton and not ProjectSingletonFor each project a new DebuggingSessionManager instance is created, which is not the intented functionality. This is because it has @ProjectSingleton annotation but not @ApplicationSingleton.
The problem however is that when you switch ...For each project a new DebuggingSessionManager instance is created, which is not the intented functionality. This is because it has @ProjectSingleton annotation but not @ApplicationSingleton.
The problem however is that when you switch to ApplicationSingleton then the RevisionManager is not accessible.
Possibly the reason for the behaviour of issue #1Wolfgang SchmidWolfgang Schmidhttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/43Disable Buttons für MoveAllActions after DebuggingSession has been started2021-04-15T08:37:34ZWolfgang SchmidDisable Buttons für MoveAllActions after DebuggingSession has been startedAdditionally:
![image](/uploads/b830ce0df85aec9279accc68ba45a8f8/image.png)
When enabled, color the above buttons purple and make them grey when disabled like these buttons:
![image](/uploads/3cc190a35dd143c5784b796f6454d47f/image.png)Additionally:
![image](/uploads/b830ce0df85aec9279accc68ba45a8f8/image.png)
When enabled, color the above buttons purple and make them grey when disabled like these buttons:
![image](/uploads/3cc190a35dd143c5784b796f6454d47f/image.png)bodawebodawehttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/29Docker Image2020-12-16T17:04:40ZKonstantin SchekotihinDocker ImageExtend the continuous integration system of our GitLab to generate Docker images of nightly builds as described in https://docs.gitlab.com/ee/ci/docker/using_docker_build.htmlExtend the continuous integration system of our GitLab to generate Docker images of nightly builds as described in https://docs.gitlab.com/ee/ci/docker/using_docker_build.htmlWolfgang SchmidWolfgang Schmidhttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/35Don't allow MoveToActions during a running debugging session2020-11-17T18:02:53ZWolfgang SchmidDon't allow MoveToActions during a running debugging sessionIn the backend there is check for the MoveToAction and thus throws an exception if so.
That means during a running state do not show the move to buttons
![image](/uploads/8ea4a52b75d7319ea74f20bd342a9b55/image.png)In the backend there is check for the MoveToAction and thus throws an exception if so.
That means during a running state do not show the move to buttons
![image](/uploads/8ea4a52b75d7319ea74f20bd342a9b55/image.png)bodawebodawehttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/22Error in Debugger View2020-10-13T06:32:16ZWolfgang SchmidError in Debugger ViewSince the latest commit I get the following error message when I want to open the Debugger view.
This occurs in Chrome, Firefox and Edge.
![image](/uploads/1360eda27c34501f7f2efe667671b1df/image.png)Since the latest commit I get the following error message when I want to open the Debugger view.
This occurs in Chrome, Firefox and Edge.
![image](/uploads/1360eda27c34501f7f2efe667671b1df/image.png)bodawebodawehttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/19Extend Repair interface with a modify and undo operation2021-01-14T12:33:59ZWolfgang SchmidExtend Repair interface with a modify and undo operationUse of a popup window will become necessary.
This is an extension of issue #13Use of a popup window will become necessary.
This is an extension of issue #13Wolfgang SchmidWolfgang Schmidhttps://git-ainf.aau.at/interactive-KB-debugging/webprotege_debugger/-/issues/12Find a proper lookup mechanism for query answering2020-09-22T14:33:02ZWolfgang SchmidFind a proper lookup mechanism for query answeringFind a bulletproof method for the lookup of those axioms whose answers are sent from the frontend.
Current solution with owlObjectRenderer.render(Axiom) does not always match with the string sent from frontend.
e.g.
Frontends (its the...Find a bulletproof method for the lookup of those axioms whose answers are sent from the frontend.
Current solution with owlObjectRenderer.render(Axiom) does not always match with the string sent from frontend.
e.g.
Frontends (its the string from the HTML):
KoalaWithPhD EquivalentTo Koala and hasDegree value PhD
vs.
owlObjectRenderer.render():
KoalaWithPhD EquivalentTo Koala and (hasDegree value PhD)
ManchesterSyntaxRenderer does not work.Wolfgang SchmidWolfgang Schmid