W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > April to June 2009

RE: Reflections on Update

From: Seaborne, Andy <andy.seaborne@hp.com>
Date: Fri, 8 May 2009 17:24:59 +0000
To: Kendall Clark <kendall@clarkparsia.com>
CC: SPARQL Working Group <public-rdf-dawg@w3.org>
Message-ID: <B6CF1054FDC8B845BF93A6645D19BEA362D15FCAF1@GVW1118EXC.americas.hpqcorp.net>


> -----Original Message-----
> From: Kendall Clark [mailto:kendall@clarkparsia.com]
> Sent: 8 May 2009 18:08
> To: Seaborne, Andy
> Cc: SPARQL Working Group
> Subject: Re: Reflections on Update
> 
> On Fri, May 8, 2009 at 12:58 PM, Seaborne, Andy <andy.seaborne@hp.com>
> wrote:
> 
> > A possible core:
> >
> > CLEAR
> > INSERT DATA { triples }
> > DELETE DATA { triples }
> > MODIFY DELETE { template } INSERT {template } WHERE { pattern }
> >
> >
> > And later:
> >  Graph management
> >  Graph store
> >  Multi graph operations
> 
> I like this idea and I really like this division; my suggestion would
> be, for the sake of compromise, to put the "And later" bits out of
> scope for this round of SPARQL standardization, in order to get to
> more stuff like time-permitting bits.
> 
> I think this is in-keeping with the Charter, which says "Insert,
> update, and delete: building on SPARQL to modify RDF data stores,
> including using HTTP Post" -- I certainly didn't think graph
> management, store, multi-graph ops were included in that when my org
> voted on the Charter. FWIW.

It comes from
http://www.w3.org/Submission/2008/SUBM-SPARQL-Update-20080715/

which the charter mentions.

	Andy

(and for clarity: I'm not proposing changing the decision of the WG on the overall feature set we decided at the F2F).


> 
> Cheers,
> Kendall
Received on Friday, 8 May 2009 17:26:28 GMT

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