- From: Andy Seaborne <andy.seaborne@epimorphics.com>
- Date: Mon, 08 Aug 2011 13:37:27 +0100
- To: Lee Feigenbaum <lee@thefigtrees.net>
- CC: public-rdf-dawg@w3.org
I asked: """ Could someone provide the use case for this feature and why it should override USING/USING NAMED? """ What capability does having parameters at all for update give the client application? I really would like a concrete example we can discuss - the test cases tried to explore this. I see several interpretations of parameters: 1/ dataset is fixed at the start of the update request and the same is used for all WHERE clauses regardless of USING etc and of operations earlier in the request. 2/ The dataset structure is fixed, the contents of the graphs can change across operations within a request. 3/ The dataset for each operation is modified in some way by the params so it's the combination of the graph store and parameters that matters. Graph created by earlier operations in open request are visible in the dataset of a later operation. These are not independent and there are popssible variations. Andy
Received on Monday, 8 August 2011 12:38:00 UTC