- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Tue, 20 Nov 2012 07:43:24 -0500
- To: public-ldp-wg@w3.org
- Message-ID: <50AB7AEC.7050600@openlinksw.com>
On 11/19/12 6:48 PM, Wilde, Erik wrote: > we're building a service and as such, we cannot expose implementation details. we want to allow and encourage LDP implementation on non-RDF back-ends. so what we can expose is the service surface including the interactions it affords, but assuming that service internals are RDF would go too far. This is the central thrust of confusion that needs clarification. At this juncture, the assumption is that LDP is all about RDF based Linked Data. > > imagine Atom(Pub) would have specified XQuery for querying feeds assuming every implementation would run an XML DB and manage its data in XML. this would have made way too many assumptions about service internals and greatly dimished the service's value as an implementation-agnostic way for managing collections. See my comment above. This is a critical item that should be resolved in the conceptual overview and guide for this effort. Clearly, there are divergent opinions on this critical point. -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Tuesday, 20 November 2012 12:43:47 UTC