W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2001

RE: Feature request for CHECKIN/OUT extension

From: John Hall <johnhall@evergo.net>
Date: Mon, 6 Aug 2001 15:12:10 -0700
To: "'Julian F. Reschke'" <julian.reschke@greenbytes.de>
Cc: <ietf-dav-versioning@w3.org>
Message-ID: <001e01c11ec4$d6d04040$0400a8c0@xythosjohnhall>
Well, I personally expect the CHECKIN URI to be the same as the CHECKOUT
URL.

Note that when using working resources (where this is a concern) that we
have a proposal with the following characteristics:

A CHECKOUT of a VCR with a <apply-to-version> will cause the working
resource to track the VCR from which it came, and a subsequent CHECKIN
of the working resource will checkin the working resource and update the
vcr.

That seemed to be what you were after, or did you hope for a broader
ability to do something like this?

> -----Original Message-----
> From: ietf-dav-versioning-request@w3.org 
> [mailto:ietf-dav-versioning-request@w3.org] On Behalf Of 
> Julian F. Reschke
> Sent: Monday, August 06, 2001 7:50 AM
> To: ietf-dav-versioning@w3.org
> Subject: Feature request for CHECKIN/OUT extension
> 
> 
> Feature request for CHECKIN/OUT extension
> 
> In many cases, a versioning-aware client might want to 
> display/include the URI of the version it's editing *while* 
> it's edited. For instance, a versioning aware editor might 
> include this as meta-information, or the author of a document 
> might want to know the URI of the version *before* it's 
> checked in. A well-known example is the W3C way of referring 
> to document versions in
> recommendations: it contains HREFs to "the current version", 
> to "this version" and to the "previous version". Something 
> like this is currently impossible with deltaV, as the version 
> URI is determined at the time of CHECKIN.
> 
> Proposal:
> 
> 1) Extend CHECKOUT to optionally return an "expected CHECKIN URI".
> 2) Extend CHECKIN to optionally use the "expected CHECKIN 
> URI", failing the request if it's not possible to checkin the 
> resource with the desired version URI (in which case a new 
> "expected CHECKIN URI" is returned).
> 
> Some possible strategies:
> 
> 1) Pass the information as proprietary live properties.
> 2) Pass the information as properties in the DAV: namespace, 
> and define the behaviour in the deltaV spec.
> 3) (preferred) Pass the information in the request/response 
> bodies of CHECKIN / CHECKOUT, such as:
> 
> CHECKOUT method:
> 
> >>REQUEST
> 
>   CHECKOUT /foo.html HTTP/1.1
>   Host: www.webdav.org
>   Content-Type: text/xml; charset="utf-8"
>   Content-Length: xxxx
> 
>   <D:checkout xmlns:D="DAV:">
>     <D:compute-expected-version-URI />
>   </D:checkout>
> 
> 
> >>RESPONSE
> 
>   HTTP/1.1 200 OK
>   Cache-Control: no-cache
>   Content-Type: text/xml; charset="utf-8"
>   Content-Length: xxxx
> 
>   <D:checkout xmlns:D="DAV:">
> 
> <D:expected-version-URI>http://repo.webdav.org/his/23/ver/32</
D:expected-ver
> sion-URI>
>   </D:checkout>
> 
>   (Note that we would need to define an (optional) response 
> body for CHECKOUT).
> 
> 
> CHECKIN method:
> 
> 
> >>REQUEST
> 
>   CHECKIN /foo.html HTTP/1.1
>   Host: www.webdav.org
>   Content-Type: text/xml; charset="utf-8"
>   Content-Length: xxxx
> 
>   <D:checkin xmlns:D="DAV:">
> 
> <D:expected-version-URI>http://repo.webdav.org/his/23/ver/32</
D:expected-ver
> sion-URI>
>   </D:checkin>
> 
> >>RESPONSE
> 
>   HTTP/1.1 201 Created
>   Location: http://repo.webdav.org/his/23/ver/32
>   Cache-Control: no-cache
> 
>   or
> 
> >>RESPONSE
> 
>   HTTP/1.1 409 Forbidden
>   Cache-Control: no-cache
>   Content-Type: text/xml; charset="utf-8"
>   Content-Length: xxxx
> 
>   <D:error xmlns:D="DAV:">
>     <D:cannot-assign-expected-version-URI />
> 
> <D:expected-version-URI>http://repo.webdav.org/his/23/ver/33</
D:expected-ver
> sion-URI>
>   </D:error>
> 
> 
> 
> 
> 
Received on Monday, 6 August 2001 18:12:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:42 GMT