Re: How to derive Change Statements

Thanks for the Clarification Claude and asf. I get what you are suggesting. As asf said, i believe the approach using DataSetChanges and GraphListener is a bit closer to what I want to achieve. Thanks, Anuj On Mon, Oct 30, 2017 at 11:15 AM, wrote: > Claude's approach isn't

Re: How to derive Change Statements

Claude's approach isn't Fuseki-specific. You can use the jena-permissions module directly, and that might even be easier. But certainly, GraphListener and DatasetChanges are probably closer already to what you want. ajs6f anuj kumar wrote on 10/30/17 5:52 AM: Hey Claude, I am not using

Re: How to derive Change Statements

Just to clear up any misunderstanding, the permissions layers in not tied to Fuseki, I was thinking Fuseki in my answer as you wanted to know who was making changes and Fuseki would handle that part. If you have another mechanism to track who is making the change the permissions layer will work.

Re: How to derive Change Statements

Hey Claude, I am not using Fuseki and thus the solution you propose will not be a feasible one for me. Andy, Thanks for the information on GraphListener, DatasetChanges as well as rdf-patch. I think using these tools I will e able to handle my use cases. Let me give them a try and see if I

Re: How to derive Change Statements

Hi Anuj, Jena has some building blocks: GraphListener, DatasetChanges GraphListener enables an app to watch every change on a graph. DatasetGraphMonitor/DatasetChanges can be used if you want to look at a dataset. Both give you triggers on individual triple/quad changes on which you can add

Re: How to derive Change Statements

Since you need to detect who changed what the only way I can see to do this is turn on authentication on Fuseki and track changes made through it. You could bastardise the permissions layer[1] to do what you want. The permissions layer will let you filter down to the actions on the triples,