You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check for deleted flag only checks if there is a triple with the "deleted"-predicate, but it does not care if the value of the triple is set to true or false.
Might be quite safe at the moment because the value is only set to true, but would not work properly if at some point some 'undelete' operation takes place (via code, via sparql), setting the value to false.
The text was updated successfully, but these errors were encountered:
I think that was the initial idea. Seems a little dangerous and like an idea that might not be shared by all future developers.
Moreover, as stated above, you can 'undelete' the annotation via SPARQL update on the (admin) user side.
Haven't checked it yet, but I, therefore, expect that removing the triple with <http://dem.scc.kit.edu/wapserv/ns#deleted> "true"^^xsd:boolean would undo the deletion, but changing the value to "false"^^xsd:boolean would not.
Check for deleted flag only checks if there is a triple with the "deleted"-predicate, but it does not care if the value of the triple is set to true or false.
wap-server/src/main/java/edu/kit/scc/dem/wapsrv/service/AbstractWapService.java
Line 454 in 0a9e4fd
Might be quite safe at the moment because the value is only set to true, but would not work properly if at some point some 'undelete' operation takes place (via code, via sparql), setting the value to false.
The text was updated successfully, but these errors were encountered: