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

Re: SPARQL Update feature

From: Steve Harris <steve.harris@garlik.com>
Date: Tue, 13 Jul 2010 14:54:02 +0100
Cc: Alexandre Passant <alexandre.passant@deri.org>, SPARQL Working Group <public-rdf-dawg@w3.org>
Message-Id: <2E908AC5-920E-43C4-B48D-27811BB4A676@garlik.com>
To: Andy Seaborne <andy.seaborne@talis.com>
On 2010-07-13, at 14:33, Andy Seaborne wrote:

[snip]

>>>> >>  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>
>>>> >>
>>>> >>  =>
>>>> >>
>>>> >>  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.
>> Ok - so based on that and your previous comments re. GRAPH DEFAULT, that could be
>> 
>> DROP [ SILENT ] (GRAPH<uri>  | DEFAULT | ALL)
>> 
>> and
>> 
>> CLEAR [ SILENT ] (GRAPH<uri>  | DEFAULT | ALL)
> 
> SILENT?  Isn't that only DROP and CREATE?

DROP GRAPH <a>
DROP GRAPH <a>

gives one or two errors, but

DROP SILENT GRAPH <a>
DROP SILENT GRAPH <a>

gives none. At least if it follows the SQL defn. of SILENT.

- Steve

-- 
Steve Harris, CTO, Garlik Limited
1-3 Halford Road, Richmond, TW10 6AW, UK
+44 20 8439 8203  http://www.garlik.com/
Registered in England and Wales 535 7233 VAT # 849 0517 11
Registered office: Thames House, Portsmouth Road, Esher, Surrey, KT10 9AD
Received on Tuesday, 13 July 2010 13:54:35 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:43 GMT