- From: Andy Seaborne <andy.seaborne@epimorphics.com>
- Date: Mon, 08 Aug 2011 19:57:49 +0100
- To: public-rdf-dawg@w3.org
The question is what happens within one request when there are two operations. In your example, it's really a subset of the graph store (as I understand it). In my example, the dataset is unchanging. No updates from the first operation are visible to in the second operation (neither changes of a graphs triples, not the set of named graphs). It's different from query because of multiple operations in one request. Andy On 08/08/11 16:27, Lee Feigenbaum wrote: > This seems like it would be well-handled by the semantics I'm intending > here -- the dataset is given in the protocol request, which is basically > as if it were given in USING/USING NAMED, at which points it's up to the > implementation as to how to get at the graphs (via Web dereference or > via local lookup or via something else entirely). > > Lee > > On 8/8/2011 10:16 AM, Andy Seaborne wrote: >> I'll add a use case then: >> >> The ability to pull in data from the web and use as dataset in an update >> request. >> >> Here we have a temporary datasets for the update request, which creates >> and extracts the data from within the request dataset and adds/deletes >> it from the graph store. >> >> The dataset graphs do not exist in the local graph store before, during >> or after the request. The entire WHERE part has been retargetted. >> >> Andy >> >> >
Received on Monday, 8 August 2011 18:58:32 UTC