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

Re: Comments on SPARQL 1.1 Update (4)

From: Steve Harris <steve.harris@garlik.com>
Date: Fri, 3 Sep 2010 12:02:36 +0100
Cc: SPARQL Working Group <public-rdf-dawg@w3.org>
Message-Id: <ECAD6067-2F37-4DC3-9379-23AF8F35E7B7@garlik.com>
To: Andy Seaborne <andy.seaborne@epimorphics.com>
On 2010-09-03, at 11:30, Andy Seaborne wrote:

> This comment is about the design of the update language syntax, not the document itself.
> 
> In Turtle and N-triples, simple concatenation of files (except for implicit base IRI in Turtle and local bNode naming) results in a single, combined data file that is legal Turtle / N-Triples.  The thing in Turtle that makes this possible is that @prefix and @base can appear anywhere between triple specifications and defines prefixes or base IRI from that point on in the file.  This isn't a widely used feature as far as I know but it's useful at times.
> 
> SPARQL Update does not have this property.  Currently, the prologue of BASE and PREFIX must be the first thing in the request.

Really?

I thought the intention was to be able to issue requests like:

PREFIX ...
INSERT ...
;
PREFIX ...
INSERT ...
;
...

if that's not the case then I for one support changing it so it is.

The further implication is that if you do:

PREFIX ...
INSERT ...
;
INSERT ...

the second INSERT gets to see PREFIXes defined in the first, is that intentional?

- 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 Friday, 3 September 2010 11:03:13 GMT

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