kobrixinc / fdr Goto Github PK

This efforts seems to have some similar goals, of course lower level, but worth looking at as it seems well thought out and practical:

https://github.com/awwright/node-rdf

Java (http://komma.enilink.net/docs/ and https://github.com/mhgrove/Empire
dotNet (https://trinity-rdf.net/).
Python https://pythonhosted.org/SuRF/

At the moment QuadRemoved requires you to provide the values of all 4 components of the quad. And consequently removing a property requires you to know the value of the existing property.

From the perspective of a user who wants to delete the value of a property, whatever it is, it doesn't make much sense to first read it.

These change management classes have the double function at the moment to capture changes, as they occurred so they can be applied elsewhere, and reversed. However, as a pure replace or remove operation they are not very user friendly.

Either "unknowns" should be allowed in these change objects or there should be a separate API to allow for "remove property whatever it is type of operation". Either way, this means we need to couple a remove/replace operation with some way to track the actual changes or chose to ignore them.

Look into whether it makes sense to use and possibly expose the RDF-EXT library: https://github.com/rdf-ext/rdf-ext. It seems lightweight enough and with some helpful extensions to the RDFJS minimalistic and hard to use stuff.