You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2017/10/12 15:54:40 UTC

Fuseki service extensibility

JENA-1400 is a small step to providing some degree of flexibility in 
Fuseki for adding custom services to a dataset.  The JIRA is needed 
because currently the OperationName set is sealed.

I'm not seeing this as a common thing to do. Many things are better done 
(e.g. data conversion) output and streamed to Fuseki.

The one I have mind is implementing a patch service (and using HTTP 
PATCH, as well as POST) based on RDF Patch [1]. Changes to datasets can 
be calculated elsewhere and the Fuseki dataset changed.  (It's quite 
hard to automatically generate SPARQL Update for arbitrary changes if 
there are blank nodes involved.)

Any other use cases?

     Andy

[1] https://afs.github.io/rdf-delta/

Re: Fuseki service extensibility

Posted by aj...@apache.org.

I'm not in a big hurry to work on this, but LDP access to a dataset might find that useful.


ajs6f

Andy Seaborne wrote on 10/12/17 11:54 AM:
> JENA-1400 is a small step to providing some degree of flexibility in Fuseki for adding custom services to a dataset.
> The JIRA is needed because currently the OperationName set is sealed.
>
> I'm not seeing this as a common thing to do. Many things are better done (e.g. data conversion) output and streamed to
> Fuseki.
>
> The one I have mind is implementing a patch service (and using HTTP PATCH, as well as POST) based on RDF Patch [1].
> Changes to datasets can be calculated elsewhere and the Fuseki dataset changed.  (It's quite hard to automatically
> generate SPARQL Update for arbitrary changes if there are blank nodes involved.)
>
> Any other use cases?
>
>     Andy
>
> [1] https://afs.github.io/rdf-delta/