W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2012

Endpoint connected to Web update then query

From: Arthur Keen <AKeen@algebraixdata.com>
Date: Thu, 23 Aug 2012 22:39:59 +0000
To: W3C SPARQL Working Group <public-rdf-dawg@w3.org>
Message-ID: <50D49403-3693-42E5-91AF-903692717434@algebraixdata.com>
I promised  feedback to the WG on the issue that Andy brought up, where an endpoint is serving up RDF from the web and receives an update followed by a query.  Current implementations have three different ways of handling this:

1)  Allow the update and execute the query on the updated data,
2)  Allow the update and execute the query on the original data from the web,
3)  Refuse the update since the data is from the web and therefore read only.

We have not started implementing update yet and here is my take on this:

If an endpoint is configured to retrieve data from the web, then it should be treated as read-only and the endpoint should not allow local updates to that data.  The user should make their own local copy of the data and update that local copy.  Unless I am missing some important use cases, for example the endpoint owns the web data and is staging updates for the web.

If however, the SPARQL WG decides to allows local updates to that read only web data data and the administrator of the endpoint configures this behavior, then our endpoint will process the update query (nondestructively) and the subsequent query will be executed on the newest version of the data.

If the standard allows these 3 different behaviors, then a user should be able to discover which behavior is being followed.

Received on Thursday, 23 August 2012 22:41:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:07 UTC