Feature/save kb reconcile #66
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR builds on #63 and includes the latest version of develop. It develops the original PR's idea of using KnowledgeBaseAnnotations, bound by a AnnotationSession, instead of a KnowledgeBase model that is appended to a Problem directly. I think this is a good change which fits the researcher's vision that user annotations will mainly consist of additions/edits of knowledge base items and proof trees.
This PR is still a work in progress. Users can edit and save knowledge base items, but we need to decide where directly 'editing' a problem stops and where 'annotating' begins. Knowledge base edits currently take the form of annotations, but changes to sentences (premises + hypothesis) are directly made on the problem. Maybe we need both, or maybe we consider all changes to problems to be annotations.
In any case, this is something I'd like to clear up in discussion with you guys (@bbonf / @jgonggrijp) before I finish this PR.