RE: CHECKIN to update a VCR ...

> From: ietf-dav-versioning-request@w3.org 
> [mailto:ietf-dav-versioning-request@w3.org] On Behalf Of Clemm, Geoff
> Sent: Friday, June 22, 2001 12:02 PM
> To: 'DeltaV (E-mail)'
> Subject: RE: CHECKIN to update a VCR ...
> 
>    From: John Hall [mailto:johnhall@evergo.net]
> 
>    However, Geoff's proposal said that I had to let the 
> client modify the contents of this property.
> 
> Note that the revised proposal no longer allows the client to 
> do so (it is a protected property, maintained by the server).

Great, we agree and I'll edit out this part of the conversation.

> I'd go even farther ... you cannot modify or delete the 
> property (i.e. it is protected).  You can of course delete 
> the working resource if you are no longer interested in it.

Also agreed.

> One reason I'd rather not have it on the CHECKIN is that this 
> reintroduces the error cases (i.e. the specified URL is not a 
> VCR, the working resource is not checked-out from a version 
> in the version history of the VCR, etc.)

Ok.

>    So my full proposal, based on Geoff's, would be:
> 
>    CHECKOUT postcondition:
>    If CHECKOUT is sent with the "apply-to-version" element, then the
>    working copy will have "apply-to-VCR href-of-VCR" set.
> 
> Yup.
> 
>    If "apply-to-VCR" is set, then this field will be updated 
> if the VCR is moved.

> 
>    CHECKIN poscondition:
>    A CHECKIN of a working copy with the "apply-to-VCR" 
> property set will
>    update the VCR associated with the working copy.  If this isn't
>    possible, an error "FILL-IN-HERE" is generated if this 
> isn't possible.
> 
> Yup.

Please define "FILL-IN-HERE"

Received on Friday, 22 June 2001 17:12:18 UTC