- From: David Wood <david@3roundstones.com>
- Date: Mon, 26 Mar 2012 16:40:42 -0400
- To: Tim Berners-Lee <timbl@w3.org>
- Cc: Leigh Dodds <leigh@ldodds.com>, David Booth <david@dbooth.org>, Jeni Tennison <jeni@jenitennison.com>, public-lod community <public-lod@w3.org>
Hi all, On Mar 26, 2012, at 13:27, Tim Berners-Lee wrote: > On 2012-03 -26, at 06:18, Leigh Dodds wrote: > >> >> I may be misreading you here, but I'm not against unambiguous >> definition. My "show what is actually broken" comment (on twitter) was >> essentially the same question as I've asked here before, and as Hugh >> asked again recently: what applications currently rely on httprange-14 >> as it is written today. That useful so we can get a sense of what >> would break with a change. So far there's been 2 examples I think. > > For me, the fact that you can use the URI of a document on the web > to refer to that document is so built into the semantic web architecture for the last 12 > years that it has been implicit in everything I have coded or designed, > haven't been aware of where I have used it and where not. > It it is really difficult for me to measure which bits would > The SWAP project, CWM has that built in -- the URI of the document > something was read from is kept in the quad store as provenance > for every triple read in. The same with the tabulator store. > The tabulator offers different views of objects as a function of the classes > the are in, and it infers things from HTTP 200s and content types. > It would have to be re-engineered of course, something I'm prepared > to do in the cause of progress, but I feel it had better be something which > adds bath water without throwing out the baby. Yes, we would rework our software as well in the name of progress. Just so everyone hears me say it ;) James and I consider discoverability to be utterly critical to the way Linked Data should work. To that end, we have recently added a REST API [1] to Callimachus [2] that makes use of HTTP OPTIONS, GET, POST, PUT, PATCH and DELETE to provide a discoverable and navigable set of CRUD operations on all content, including naturally RDF content. [3] and [4] are the sections most generally applicable to the Linked Data community. Regards, Dave [1] http://code.google.com/p/callimachus/wiki/REST_API [2] http://callimachusproject.org/ [3] http://code.google.com/p/callimachus/wiki/REST_API#Browsing_Content [4] http://code.google.com/p/callimachus/wiki/REST_API#CRUD_Operations_on_RDF_Content > > Tim > > PS: Missed the tweet
Received on Monday, 26 March 2012 20:41:11 UTC