Type: New Feature
Affects Version/s: None
Fix Version/s: BLAZEGRAPH_2_2_0
Mike and I also discussed some options to support this throught the NanoSparqlServer's REST API. The main concept was to add the following to the NanoSparqlServer API for methods that perform mutations.
Assuming that truth maintenance is enabled for the endpoint, then the operation is carried out without truth maintenance when this flag is specified.
This may result in an inconsistent state for the database (in the sense that inferences might not have been added or removed). The user is responsible for dealing with that inconsistent state. Users can restore the database to a consistent state after applying a series of mutations with truth maintenance supposed by issuing the "CREATE ENTAILMENTS" UPDATE REQUEST afterwards to update the entailments for the KB. This is sufficient to compute any missing entailments if nothing has been deleted out of the database. If you have also retracted statements, then you would need to issue "DROP ENTAILMENTS; CREATE ENTAILMENTS;" to remove the old entailments before (re-)computing the entailments for the KB.