W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > September 2011

Re: Auto: public-rdf-dawg-comments@w3.org autoreply

From: David Booth <david@dbooth.org>
Date: Thu, 22 Sep 2011 19:48:55 -0400
To: public-rdf-dawg-comments <public-rdf-dawg-comments@w3.org>
Message-ID: <1316735335.29437.15725.camel@dbooth-laptop>
A brief follow-up on comment #1 of this message:
http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2011Jul/0017.html
(excerpted below).

> 1. Please either add capability for virtual graphs or keep the COPY, ADD
> and MOVE shortcuts, to enable standard SPARQL to be used more
> efficiently as a rules language and in data production pipelines.  COPY,
> ADD and MOVE operations cost almost nothing to implement, and they help
> with efficiency.  By "virtual graph" I mean a graph that consists of the
> merge of a particular set of named graphs -- a very important capability
> for efficient data production pipelines.

I have also found that I rely on these graph operations in developing
SPARQL update scripts, as they allow me to conveniently perform
inserts/deletions on a temporary graph, and then ADD, COPY or MOVE that
temporary graph to the production graph.  The pattern looks like this:


  DROP SILENT GRAPH tempGraph:
  CREATE GRAPH tempGraph:

  INSERT { GRAPH tempGraph: {
    ...  # Lots of complex SPARQL
  } } ;

  # ADD GRAPH tempGraph: to productionGraph:
  DROP GRAPH tempGraph:

The ADD operation allows me to very easily put this into production by
merely uncommenting that single line.  Again, I think these graph
operations are worth keeping in the spec.

Thanks!

-- 
David Booth, Ph.D.
http://dbooth.org/

Opinions expressed herein are those of the author and do not necessarily
reflect those of his employer.
Received on Thursday, 22 September 2011 23:49:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 22 September 2011 23:49:30 GMT