Re: Restricting SPARQL update to a single named graph

2022-06-07 Thread Andy Seaborne 
On 07/06/2022 10:47, Martynas Jusevičius wrote:
> Hi,
>
> I have implemented PATCH method for the Graph Store Protocol:
> https://www.w3.org/TR/sparql11-http-rdf-update/#http-patch
>
> The PATCH is applied to a named graph. I am missing this bit however:
> " If a SPARQL 1.1 Update request is used as the RDF payload for a
> PATCH request that makes changes to more than one graph or the graph
> it modifies is not the one indicated, it would be prudent for the
> server to respond with a 422 Unprocessable Entity status."

I read that in the context of GSP resource naming.

?graph=

and so the update does not name a graph - it'll look like the default
graph in the update.

So look for GRAPH in the update.

> What would be the way to make sure that an update only affects a
> single specific graph?

A dataset of one graph and no others. c.f. DatasetGraphOne but for a
single named graph and read-only dft graph.

Or a dataset which yields read-only graphs except for the target graph.

Or analyse the update - no GRAPH in templates if the target comes from
the URL.

>
>
> Martynas
> atomgraph.com

SPARQL query won't abort

2022-06-07 Thread Reid Yoder 
Hello,

I'm having a problem where I can't stop a SPARQL query mid-execution --
.abort() and .close() are not working. I'm just going to link to my
stackoverflow question so there's a central place for discussion:
https://stackoverflow.com/questions/72522307/apache-jena-sparql-query-will-not-abort

Thanks,
- Reid

Restricting SPARQL update to a single named graph

2022-06-07 Thread Martynas Jusevičius 
Hi,

I have implemented PATCH method for the Graph Store Protocol:
https://www.w3.org/TR/sparql11-http-rdf-update/#http-patch

The PATCH is applied to a named graph. I am missing this bit however:
" If a SPARQL 1.1 Update request is used as the RDF payload for a
PATCH request that makes changes to more than one graph or the graph
it modifies is not the one indicated, it would be prudent for the
server to respond with a 422 Unprocessable Entity status."

What would be the way to make sure that an update only affects a
single specific graph?


Martynas
atomgraph.com