[JENA-1731] Improve Fuseki service endpoint configuration

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Done
• Affects Version/s: Jena 3.13.0
• Fix Version/s: Jena 3.13.0
• Component/s: Fuseki
• Assignee: Andy Seaborne
• Reporter: Andy Seaborne
• Created: 14/Jul/19 19:32
• Updated: 29/Sep/19 16:10
• Resolved: 01/Sep/19 17:44

Description

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

A sketch for new configuration description for a service endpoint:

<#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;
        ja:context [ ja:cxtName "arq:queryTimeout" ; ja:cxtValue "1000,10000" ] ;
    ] ;
    fuseki:endpoint [
        fuseki:name "sparql" ;  ## becomes "/ds/sparql"
        fuseki:operation     fuseki:Query ;
        ...
    ] ;
    fuseki:endpoint [
        fuseki:name "sparql" ;
        fuseki:operation     fuseki:Update ;
        ...
    ] ;
.

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 or have a data validation service for SHACL etc.

Issue Links

• relates to: JENA-1715 Improvements to Fuseki request dispatch
• links to: GitHub Pull Request #595