[
https://issues.apache.org/jira/browse/RYA-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakobitsch Jürgen updated RYA-477:
----------------------------------
Description:
This task reflects an overhaul of the current SPARQLEndpoint implementation.
The improvment should include proper content-negotiation, well know URLs (like
/sparql), the implementation of "SPARQL Service Description" [1] to expose
available features and "Graph Store Protocol" [2] as a basic CRUD interface
(instead of loadRdf). check the subtasks for further details.. The
implementation will be done in a non disruptive way to not interfer with
clients of the current endpoint, all available options (e.g. auth parameter,
infer parameter) will still be available.
[1] [https://www.w3.org/TR/sparql11-service-description/]
[2] [https://www.w3.org/TR/sparql11-http-rdf-update/]
was:
This task reflects an overhaul of the current SPARQLEndpoint implementation.
The improvment should include proper content-negotiation, well know URLs (like
/sparql), the implementation of "SPARQL Service Description" [1] to expose
available features and "Graph Store Protocol" [2] as a basic CRUD interface
(instead of loadRdf). check the subtasks for further details..
[1] https://www.w3.org/TR/sparql11-service-description/
[2] https://www.w3.org/TR/sparql11-http-rdf-update/
> SPARQLEndpoint overhaul
> -----------------------
>
> Key: RYA-477
> URL: https://issues.apache.org/jira/browse/RYA-477
> Project: Rya
> Issue Type: Improvement
> Components: clients
> Affects Versions: 3.2.12
> Reporter: Jakobitsch Jürgen
> Assignee: Jakobitsch Jürgen
> Priority: Minor
> Fix For: 3.2.12
>
>
> This task reflects an overhaul of the current SPARQLEndpoint implementation.
> The improvment should include proper content-negotiation, well know URLs
> (like /sparql), the implementation of "SPARQL Service Description" [1] to
> expose available features and "Graph Store Protocol" [2] as a basic CRUD
> interface (instead of loadRdf). check the subtasks for further details.. The
> implementation will be done in a non disruptive way to not interfer with
> clients of the current endpoint, all available options (e.g. auth parameter,
> infer parameter) will still be available.
> [1] [https://www.w3.org/TR/sparql11-service-description/]
> [2] [https://www.w3.org/TR/sparql11-http-rdf-update/]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
