- From: Alexandre Bertails <alexandre@bertails.org>
- Date: Mon, 22 Sep 2014 20:02:45 -0400
- To: Kuno Woudt <kuno@frob.nl>
- Cc: public-ldp-comments@w3.org
Hi Kuno, On Sun, Sep 21, 2014 at 6:58 AM, Kuno Woudt <kuno@frob.nl> wrote: > Hello, > > I recently learned about LD Patch through #swig on freenode IRC. I have > read http://www.w3.org/TR/2014/WD-ldpatch-20140918/ , which raised the > following question: > > Is there any way to include metadata about the patch in the PATCH > request? LD Patch is just a format. There is no metadata *inside* it. But you may consider having metadata about the document. Read below. > > If I have a public dataset which accepts changes from my users, I would > like to keep some kind of log of these changes. Such a log would > include information like who made the change, when the change was made, > and why the change was made. "why" would be a comment from the user > describing their reason for making this change. I believe LDP would give the right architecture for your use-case. For example, you could have your patches sitting in an LDP Container, as LDP accepts non-RDF data as well. You could then attach metadata about it, which is also handled by the platform. The "who" and "when" would be derived from the HTTP interactions, so this would easily be maintained by the server. The "why" is trickier. You could attach this information _after the fact_. Or you could pass this information through the HTTP headers during the PATCH, but I have no idea which one would be adequate. I hope this helps, Alexandre > > -- > Kuno Woudt > kuno@frob.nl >
Received on Tuesday, 23 September 2014 00:03:17 UTC