W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2010

Re: SPARQL Update feature

From: Andy Seaborne <andy.seaborne@talis.com>
Date: Wed, 07 Jul 2010 09:27:21 +0100
Message-ID: <4C343A69.9000408@talis.com>
To: Alexandre Passant <alexandre.passant@deri.org>
CC: SPARQL Working Group <public-rdf-dawg@w3.org>

On 06/07/2010 9:39 PM, Alexandre Passant wrote:
> Hi,
> On 6 Jul 2010, at 22:20, Andy Seaborne wrote:
>> It occurred to me we are missing a feature in SPARQL Update (language) - the ability to clear the graph store. That is, drop all the named graphs and empty the default graph.
> Indeed, that makes sense, esp. when working with RDF store in dev / debug phase.

That was essentially the reason I came across it - thinking how I could 
set up a graph store for some teaching without having to reset the 
server to get the graph store into a known state.

>> While , in some stores, the similar effect can be achieved with
>> DELETE WHERE { GRAPH ?g { ?s ?p ?o } }
>> because they drop empty graphs, it's not possible in general to drop all the named graphs.
>> Therefore either something to drop all named graphs, or something to reset the graph store is needed.
>> # Drop all named graphs.
>> DROP GRAPH ALL does not work very well if it's CLEAR GRAPH DEFAULT
>> (actually, I thought the syntax was going to be CLEAR DEFAULT, not CLEAR GRAPH DEFAULT)
> What do you mean by does not work well ?

I don't think it reads well.  In SPARQL Query, GRAPH accesses the named 
graphs so DROP GRAPH ALL reads as drop all named graphs.

But in SPARQL Update we have "CLEAR GRAPH DEFAULT", i.e. using the word 
GRAPH for the default graph, so "DROP GRAPH ALL" can read as including 
the default graph ("ALL" meaning anything you could write here)

I think having just "DEFAULT" and not "GRAPH DEFAULT" is a bit clearer 
if we have a style that uses "GRAPH" to relate to named graph design 
applied uniformly.

>> # Clear the graph store.
>> CLEAR ALL # but the named graphs aren't cleared, they are dropped
>> DROP ALL # but the default graph isn't dropped
>> ...
> Since CLEAR does not necessary entail that the graph is removed (stores keeping empty graphs), I'd prefer to use DROP ALL.
> However, since the default graph is never removed, that's also ambiguous as you said.
> I guess it could be solved by indicating that a store MUST always have a default graph, and that if this graph is dropped, the system MUST restore it.
> Hence, DROP ALL will DROP all graphs, and the system MUST re-create the default one (as an empty graph).
> That would lead to
> =>
> DROP [ SILENT ] (GRAPH (<uri>  | DEFAULT) | ALL)
> (and DROP GRAPH DEFAULT == CLEAR GRAPH DEFAULT with the previous auto. default-graph creation feature)
> Makes sense ?

I don't have an opinion whether DROPping the default should be allowed 
but if it is, meaning "clear" by implicit restoration is OK.

> Alex.

Received on Wednesday, 7 July 2010 08:27:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:01 UTC