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 (JIRA)" <ji...@apache.org> on 2019/07/14 19:33:00 UTC

[jira] [Created] (JENA-1731) Improve Fuseki service endpoint configuration

Andy Seaborne created JENA-1731:
-----------------------------------

             Summary: Improve Fuseki service endpoint configuration
                 Key: JENA-1731
                 URL: https://issues.apache.org/jira/browse/JENA-1731
             Project: Apache Jena
          Issue Type: Improvement
          Components: Fuseki
    Affects Versions: Jena 3.13.0
            Reporter: Andy Seaborne
            Assignee: Andy Seaborne


This is a follow-on JIRA from JENA-1715.

A sketch for new configuration description for a service endpoint:
{noformat}
<#service> rdf:type fuseki:Service ;
    fuseki:name "/ds" ;
    fuseki:endpoint [
        fuseki:operation     fuseki:Query ;
        fuseki:allowedUsers  (....) ;
        fuseki:timeout       "1000,10000" ;
        fuseki:queryLimit    1000;
        arq:unionGraph       true;
    ] ;
    fuseki:endpoint [
        fuseki:name "sparql" ;  ## becomes "/ds/sparql"
        fuseki:operation     fuseki:Query ;
        ...
    ] ;
    fuseki:endpoint [
        fuseki:name "sparql" ;
        fuseki:operation     fuseki:Update ;
        ...
    ] ;
.
{noformat}
with the goal of being able to have new operations confiugured into the Fuseki endgine, and not the fixed set of operations as is currently with {fuseki;service*}. 

For example: a "patch" service - POST an [RDF Patch|https://afs.github.io/rdf-delta/rdf-patch.html] or have a data validation service for SHACL etc.




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)