- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 17 Sep 2012 11:13:23 -0400
- To: public-ldp-wg@w3.org
- Message-ID: <50573E13.4040609@openlinksw.com>
On 9/17/12 9:26 AM, Steve K Speicher wrote: > I have previously responded [1] to the request [2] for a review of "SPARQL > 1.1 Graph Store HTTP Protocol" [3] with member submission "Linked Data > Basic Profile 1.0" [4]. Here is an update with some suggested steps to > better the align the work of GSP with LDBP. > > > Background: > ---------------- > GSP, as its name implies, can be seen as a HTTP protocol definition on how > to interact with a quad (graph) store. The model, as seen as from HTTP > clients, can be that HTTP resources are equal to a graph. This is useful > for HTTP clients that known they are working with graph stores. LDBP > looks to abstract away the server storage model and focus on the protocol > for the lifecycle of HTTP resources and relationships (links and > containers). LDBP could be implemented with a graph store. > > > Summary Recommendation: > ------------------------------------ > It would be ideal if GSP was defined in the context of the LDBP and LDP > work. Due to its Last Call status, it may not be reasonable to be this > work "on hold". The reality is that many implementations of LDBP will be > based on graph stores, so having a specification within this context will > be useful. The question is whether there needs to be 2 separate > specifications: 1) HTTP access to graph store, independent of LDP 2) > Mapping of LDP specs to graph stores (SPARQL Update). > > I don't see the value in having 2 separate specifications. I'd recommend > leaving GSP as Last Call and have an open issue to align with LDP Last > Call. +1 [SNIP] > > Thanks, > Steve Speicher > IBM Rational Software > OSLC - Lifecycle integration inspired by the web -> > http://open-services.net > > > > -- 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 Monday, 17 September 2012 15:13:46 UTC