Re: ldp-ISSUE-2 (BPR versioning): Do BPR versions get managed in a systematic, discoverable way? [Linked Data Platform core]

On Thu, 2012-10-04 at 16:52 +0100, Steve Battle wrote:
> We already use entity tags to ensure that we are updating the current
> version of a resource description. Can we extend this to allow access
> to earlier versions.
> e.g. GET http://example.com/myresource?etag=W/"123456789"

Also, are people familiar with Memento?
http://tools.ietf.org/html/draft-vandesompel-memento-04
http://mementoweb.org/

This might be something else where we don't want to prescribe a
mechanism within the ldp spec, but ought to consider compatibility and
potential problems when working with other common/proposed solutions.

cheers,

Kevin.


> > -----Original Message-----
> > From: Linked Data Platform (LDP) Working Group Issue Tracker
> > [mailto:sysbot+tracker@w3.org]
> > Sent: 20 September 2012 08:55
> > To: public-ldp-wg@w3.org
> > Subject: ldp-ISSUE-2 (BPR versioning): Do BPR versions get managed in a
> > systematic, discoverable way? [Linked Data Platform core]
> > 
> > ldp-ISSUE-2 (BPR versioning): Do BPR versions get managed in a systematic,
> > discoverable way? [Linked Data Platform core]
> > 
> > http://www.w3.org/2012/ldp/track/issues/2
> > 
> > Raised by: Andy Seaborne
> > On product: Linked Data Platform core
> > 
> > Do BPRs need to be versioned in a standardised way?
> > 
> > Is it one BPR-with-versions or many-BPRs-linked-by-versioning-information?
> > 
> > How does an app reliably find the "latest"?
> > 
> > How does an app discover all the versions for a single BPR?
> > 
> > 
> 
> 
>

Received on Thursday, 4 October 2012 16:01:32 UTC