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

RE: How to enforce the preconditions regarding modifying a baseli ne collection

From: Clemm, Geoff <gclemm@rational.com>
Date: Thu, 11 Oct 2001 08:42:42 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B10488C433@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
Yes, I agree that it is  worth formalizing this extension.
As we get more experience with multiple implementations, we
will be able to better identify which extensions need to
be standardized for interoperability.

Cheers,
Geoff

-----Original Message-----
From: Peter Raymond [mailto:Peter.Raymond@merant.com]

It's not only "can never checkout" it's also..."can never COPY into
this collection", "can never MOVE out of or into this collection".
The Baseline Collection itself is not VERSION-CONTROLLED and as such
does not need to be checkedout to be modified.  I agree it is
something for an extension.  I may propose an extension to the
baseline feature to make the behaviour of working baselines, the
protection of the baseline collection, and the behaviour of deleteing
various resources (eg how to un-baseline-control) etc.  I agree with
all your answers to my recent questions about the baseline feature.  I
just feel we need to capture them somewhere more "concrete" than
simply in a e-mail thread otherwise different vendors may miss some of
these "subtle" points.  P.S.  I also like the VCCl and VCCn
abbreviations and will use those in future.
Received on Thursday, 11 October 2001 08:43:16 GMT

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