- From: Lee Feigenbaum <lee@thefigtrees.net>
- Date: Mon, 08 Aug 2011 11:27:19 -0400
- To: Andy Seaborne <andy.seaborne@epimorphics.com>
- CC: public-rdf-dawg@w3.org
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 15:28:09 UTC