Provide mechanisms in the workbench to:
- drop entailments (SPARQL UPDATE call)
- force the recompute of the closure (SPARQL UPDATE call)
I suggest that we do not add a method to enable / disable closure as a feature on the database at this time. This requires a global row store update. I would rather put together a meta ticket of GRS features that can be enabled and disabled and then bring in those changes in another release. (Another example would be enable/disable of the full text index vs rebuild of the full text index).