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

Geoff,

I thought that a version of a collection represented the state of
that collection at a certain point. So the version-controlled-binding-set=
,
which is a collection version property, contains the binding names
that correspond to the members of the collection at that version.
If collection /a has members b and c at a certain point, then the
version of the collection corresponding to this would have binding
names b and c.

Given a version of a VCR, a system can find that VCR. If our VCR is
collection /a and if we have binding names b and c in the collection
version, we can reconstruct /a/b and /a/c. Now we have enough to
create a new collection with members b and c.

I don't find that very strange. What is the difference between copying
a collection version to another collection, leading to a new version
controlled collection in the latter, and copying a version controlled
collection with a label header. Precondition must-select-version-in-histo=
ry
in section 8.7 results in some collection version to be used for the
copy. I could also have specified that collection version directly in
the request URI.

Regards,

Werner.

Geoffrey M Clemm wrote:
>=20
> It sounds like you are suggesting that the result of the copy depend on
> what is in the target of the copy?  That would be very strange "copy"
> behavior (i.e. the result of the copy should only depend on the source
> of the copy).  Collection versions are for use by "merge" and "update".
>=20
> Cheers,
> Geoff
>=20
> Werner Donn=E9 <[email protected]> wrote on 08/22/2006 10:59:59 AM:
>=20
>> 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 produ=
ce a
>> > sensible copy, since it only records the version history of its memb=
ers,
>> > 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
>> >
>> > [email protected] 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 versio=
n
>> >> to copy from.
>> >>
>> >> Regards,
>> >>
>> >> Werner.
>> >> --
>> >> Werner Donn=E9  --  Re
>> >> Engelbeekstraat 8
>> >> B-3300 Tienen
>> >> tel: (+32) 486 425803   e-mail: [email protected]
>> >>
>>
>> --
>> Werner Donn=E9  --  Re
>> Engelbeekstraat 8
>> B-3300 Tienen
>> tel: (+32) 486 425803   e-mail: [email protected]

--=20
Werner Donn=E9  --  Re
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803	e-mail: [email protected]