"Conflict" detection

[jmatsushita]

I'm working on a feature to identify existing triples that match a document that is being put and returns a list of conflicts to allow the client to choose whether to overwrite or leave be, maybe after doing access control checks.

[jmatsushita]

If we decide that by default data is not overwritten (i.e. preserve is true by default) then the API for this could be that:

• put without conflicting triples just works.
• putwith conflicting triples returns an error and a list of conflicts.
• putwith an overwrite: true option overwrites existing triples without an error.

@mcollina Thoughts?

[jmatsushita]

@BigBlueHat Would this API change make sense to you?

[BigBlueHat]

@jmatsushita I think so, generally.

The latest LevelGraph Playground (v2.0.1) uses levelgraph-jsonld v1.0.2 (see! it's just reversed! 😉). However...the overwrite option (which is used during db.jsonld.del() and db.jsonld.put() usage) doesn't seem to do what I'd expect...currently.

Give it a try and let me know if it's matching what you're thinking.