- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Thu, 25 Jul 2013 10:59:12 -0400
- To: public-rww@w3.org
- Message-ID: <51F13D40.8080001@openlinksw.com>
On 7/25/13 10:29 AM, Sebastian Tramp wrote: > On Thu, Jul 25, 2013 at 04:21:35PM +0200, Jürgen Jakobitsch SWC wrote: > > If someone is interested in a node.js implementation of LDP, node_ldp is your > friend: https://github.com/AKSW/node_ldp > (sorry jürgen for capturing the thread :-) Time to make a Turtle document that describes the existing LDP implementations :-) Kingsley > > Best regards > > Sebastian Tramp > >> hi, >> >> just wrote the following to the ldp mailing list (not the ldp-wg one) >> (maybe i find someone here to join the project) >> >> >> i just started with another implementation of the LDP recom. >> it is based on the servlet API and will be realized as a simple >> serlvet that needs to extended (analog to HttpServlet) to fit whatever >> datasource. >> the main logic will go into a GenericLDPServlet. Extensions of this >> servlet will need to implement something like a dereference or a sparql >> method. >> >> the main motivation behind this approach is to create a ldp impl that >> a broad audience is able to install on an existing environment (tomcat, >> jboss, websphere, any compliant servlet container) and to make the logic >> behind ldp (post, get, put, delete,...) datasource independent. it will >> only be necessary to implement methods like dereference or sparql >> specific to a certain datasource (i'll start with a reference impl based >> on openrdf's sesame). >> >> i put online the source of the ultra alpha sandbox online at github [1]. >> take a look a GenericLDPServlet [2] to get an idea where i want to go. >> >> i'd really appreciate any comments on this approach and would be happy >> if someone would like to join. >> >> wkr jürgen >> >> [1] https://github.com/turnguard/com-turnguard-ldp >> [2] >> https://github.com/turnguard/com-turnguard-ldp/blob/master/com-turnguard-ldp-utils/com-turnguard-ldp-utils-servlet/src/main/java/com/turnguard/ldp/utils/servlet/base/GenericLDPServlet.java >> >> On Wed, 2013-07-24 at 21:05 +0200, Melvin Carvalho wrote: >>> FYI: Linked data platform is going to last call. It's a way to >>> remotely store and change data using the common HTTP verbs of GET PUT >>> DELETE. And also it allows for 'containers' of resources, which >>> operate in a similar way to directories in a file system. >>> >>> ---------- Forwarded message ---------- >>> From: Steve Speicher <sspeiche@gmail.com> >>> Date: 24 July 2013 20:10 >>> Subject: LDP 1.0 editor drafts ready for Last Call >>> To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org> >>> >>> >>> All, >>> >>> >>> I believe I have covered all outstanding editor tasks that we agreed >>> upon prior to going to "Last Call" [1]. The draft is available [2] >>> and will have the change history removed prior to publication. >>> >>> >>> I will go forward now with requesting publication. >>> >>> >>> [1] - http://www.w3.org/2013/meeting/ldp/2013-07-22#resolution_2 >>> [2] - https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html >>> >>> I should also note that the vocabulary document [3] is current with >>> the draft. >>> [3] - https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.ttl >>> >>> >>> >>> >>> - Steve Speicher >>> >>> -- 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 Thursday, 25 July 2013 14:59:34 UTC