- From: Erik Wilde <dret@berkeley.edu>
- Date: Tue, 04 Jun 2013 22:13:00 -0700
- To: public-ldp@w3.org
- CC: Kingsley Idehen <kidehen@openlinksw.com>
hello kingsley. On 2013-06-04 15:17 , Kingsley Idehen wrote: > On the assumption that we both agree there is no such thing as > unstructured data: > HTTP (Hypertext Transfer Protocol) transfers Data. > RDF (Resource Description Framework) enables you describe and > understand Data. > RDF based Linked Data enables you describe, understand, and refer to > Data by combining the items above. now that sounds really great, but it really is a bit generic. would you mind spelling out for alexandre and me how a client that has no prior knowledge of LDP will, when it encounters text/turtle LDP resources, be able to figure out which links to follow with which interactions (GET/PUT/POST/PATCH), what to send as request payload, and what that is going to do in terms of LDP protocol semantics? thanks! cheers, dret.
Received on Wednesday, 5 June 2013 05:13:29 UTC