W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > April to June 2006

GData: an approach to update

From: Dan Connolly <connolly@w3.org>
Date: Tue, 25 Apr 2006 17:57:40 -0500
To: RDF Data Access Working Group <public-rdf-dawg@w3.org>
Message-Id: <1146005860.27608.995.camel@dirk.w3.org>

On GData, SPARQL update, and RDF Diff/Sync
http://dig.csail.mit.edu/breadcrumbs/node/131

Submitted by connolly on Tue, 2006-04-25 16:38. :: SPARQL |
authorization | RDF | XML

The Google Data APIs Protocol is pretty interesting. It seems to be
based on the Atom publishing protocol, which is a pretty straightforward
application of HTTP and XML, so that's a good thing.

The query features seem to be less expressive than the SPARQL protocol,
but GData has an update feature, while the SPARQL update issue is
postponed. Updating at the triple level is tricky. I helped TimBL refine
Delta: an ontology for the distribution of differences between RDF
graphs a bit, and there's working code in cwm. But I haven't really
managed to use it in practical settings. My PDA's calendar has an XMLRPC
service where I can update a whole record at a time, just like GData. I
assume caldav does likewise.

The GData approach to concurrency looks quite reasonable. I haven't
studied the authentication mechanism. I hope to get to that presently.

tags: diff sync sparql calendar web+architecture


-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E
Received on Tuesday, 25 April 2006 22:57:49 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:26 GMT