- From: Andrew Woods <awoods@duraspace.org>
- Date: Mon, 15 Feb 2016 21:41:31 -0500
- To: Sergio Fernández <sergio.fernandez@redlink.co>
- Cc: public-ldpnext@w3.org
- Message-ID: <CADz=0UmZ6pHF0FZ37MQ1SQSnnsgx5mUwd3jqZOTaUUA_Av24tw@mail.gmail.com>
Hello Sergio, Do you happen to have thoughts on how this interaction model aligns with LDP sensibilities? https://docs.google.com/document/d/1wpEVG3fNUYWNSmNdNIwTHEujhg-CAQf3hLKszfjpNO4/edit?usp=sharing Also, Fedora4 currently does not create new versions of resources on every update, but instead allows clients to create a version (i.e. snapshot) of a resource on demand. Is this a pattern that is supported by Marmotta? If so, has there been any thought about how a POST request may fit into Memento's protocol? Regards, Andrew On Mon, Feb 15, 2016 at 5:29 AM, Sergio Fernández < sergio.fernandez@redlink.co> wrote: > Definitely get LDP supporting something like RFC7090 (aka Memento > Protocol) would be worth. In Apache Marmotta we already supporting it > http://marmotta.apache.org/platform/versioning-module.html but just as a > regular Linked Data resource, no LDP formalism at all. > > On Fri, Feb 12, 2016 at 11:34 PM, Andrew Woods <awoods@duraspace.org> > wrote: > >> Hello All, >> As an update from the community, I would like to bring to your attention >> work that has been taking place around the Fedora4 Repository LDP server >> implementation [1] which I believe should be of interest here. >> >> We are currently reexamining the services that Fedora4 offers with an eye >> towards: >> - establishing well-defined restrictions of Fedora4's LDP contract >> - incorporating versioning (Memento [2]) in an LDP-like pattern >> - incorporating non-RDF source fixity checking in an LDP-like pattern >> - incorporating authorization (WebAC [3]) >> >> It is important that these LDP extensions are defined, advertised, and >> discovered in a cohesive way, aligned with LDP practices in order to behave >> intuitively within the linked data Web. In that context, the feedback from >> LDPNext is vital. >> >> This email is an introduction to the initiative and an invitation to >> track our work-in-progress. >> >> - LDP interaction restrictions drafting: >> >> https://docs.google.com/document/d/1ad3MhTQWGof0IJ03yY5jVofCK8uO9yPKMVXVYq7a44o/edit?usp=sharing >> >> - LDP-like versioning drafting: >> >> https://docs.google.com/document/d/1wpEVG3fNUYWNSmNdNIwTHEujhg-CAQf3hLKszfjpNO4/edit?usp=sharing >> >> Currently, Fedora4 community discussions are taking place on the >> project-specific mailing list [4], but if there is interest, it may make >> sense to transfer some of that discussion to the public-ldpnext mailing >> list. Your feedback is appreciated. >> >> Regards, >> Andrew Woods >> Fedora4 Tech Lead >> >> [1] https://dvcs.w3.org/hg/ldpwg/raw-file/default/tests/reports/ldp.html >> [2] http://tools.ietf.org/html/rfc7089 >> [3] https://www.w3.org/wiki/WebAccessControl >> [4] https://groups.google.com/d/forum/fedora-tech >> > > > > -- > Sergio Fernández > Partner Technology Manager > Redlink GmbH > m: +43 6602747925 > e: sergio.fernandez@redlink.co > w: http://redlink.co >
Received on Tuesday, 16 February 2016 02:42:03 UTC