[
https://issues.apache.org/jira/browse/MARMOTTA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598716#comment-13598716
]
Andy Seaborne commented on MARMOTTA-135:
----------------------------------------
Keeping query and update endpoints separate is useful for configuring security
and access permissions.
SPARQL Query and SPARQL Update are different languages so that an endpoint can
be exposed widely and does not have to check a request is a query if from a
user with only query rights. An update sent to a query endpoint is always a
parse error.
> Provide a single SPARQL endpoint
> --------------------------------
>
> Key: MARMOTTA-135
> URL: https://issues.apache.org/jira/browse/MARMOTTA-135
> Project: Marmotta
> Issue Type: Improvement
> Components: Web Services
> Affects Versions: 2.6
> Reporter: Sergio Fernández
> Assignee: Sergio Fernández
> Priority: Minor
> Labels: sparql
> Fix For: 3.0-incubating
>
>
> Provide a single SPARQL endpoint at /sparql should be trivial, at least a
> draft for this release, maintaining also the concrete endpoints under
> /sparql/select and /sparql/update
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
