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

Re: DAV:cannot-copy-collection-version precondition for COPY

From: Manfred Baedke <manfred.baedke@greenbytes.de>
Date: Tue, 22 Aug 2006 18:18:12 +0200
Message-ID: <44EB2E44.1010002@greenbytes.de>
To: werner.donne@re.be
CC: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>, ietf-dav-versioning@w3.org
Hi Werner,

taking into account the postcondition 
(DAV:must-not-copy-versioning-property) and the fact that the property 
DAV:version-controlled-binding-set is more or less all a collection 
version has to offer, there is nothing left to be copied.

Regards,
Manfred

Werner Donné wrote:
> A collection version has the names of its version controlled bindings
> and their version history. It is then possible to find the checked-in
> version of the members, which is what is used also when a collection
> is copied.
>
> Regards,
>
> Werner.
>
> Geoffrey M Clemm wrote:
>   
>> A collection version does not have enough information in it to produce a
>> sensible copy, since it only records the version history of its members,
>> not the versions.  So a collection version is useful for updating a
>> configuration, but is not useful for creating a new configuration
>> (that's what baselines are for).
>>
>> Cheers,
>> Geoff
>>
>> ietf-dav-versioning-request@w3.org wrote on 08/22/2006 06:34:16 AM:
>>
>>     
>>> Hi,
>>>
>>> Why should the request fail if the source is a collection version?
>>> It seems to me that any version is as good as the checked-in version
>>> to copy from.
>>>
>>> Regards,
>>>
>>> Werner.
>>> --
>>> Werner Donné  --  Re
>>> Engelbeekstraat 8
>>> B-3300 Tienen
>>> tel: (+32) 486 425803   e-mail: werner.donne@re.be
>>>
>>>       
>
>   
Received on Tuesday, 22 August 2006 16:18:33 GMT

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