- From: Tim Ellison <Tim_Ellison@uk.ibm.com>
- Date: Thu, 27 Sep 2001 14:27:44 +0100
- To: ietf-dav-versioning@w3.org
Yes, all modifications to the baseline collection are illegal -- in many
implementations the collection will be a 'virtual' reflection of the
contents of the baseline. Clearly there is already the mechanism within
DAV to disallow these methods (e.g., supported method set) but calling them
regular version-controlled resources is misleading -- they are in no way
'regular'.
Regards,
Tim Ellison
Java Technology Centre, MP146
IBM UK Laboratory, Hursley Park, Winchester, UK. SO21 2JN
tel: +44 (0)1962 819872 internal: 249872 MOBx: 270452
Peter Raymond
<Peter.Raymond@merant.co To: ietf-dav-versioning@w3.org
m> cc:
Sent by: Subject: Legal operations on members of a Baseline
ietf-dav-versioning-requ Collection...
est@w3.org
2001-09-27 10:42 AM
Please respond to Peter
Raymond
Hi,
The Baseline Collection captures the state of resources that were in the
Baseline-Controlled Collection when the Baseline was created or when the
Version-Controlled Configuration checked-in.
In my opinion the resources in the Baseline Collection should be frozen
(since they just capture state), but, the specification only seems to
disallow CHECKOUT of a member of this collection.
Section 12.11 defines (in precondition
DAV:must-not-update-baseline-collection)
that CHECKOUT cannot be done on a member of a Baseline Collection.
Shouldn't
other operations, eg COPY, MOVE, PUT, DELETE, PROPPATCH also be prevented
on
members of a baseline collection?
If these methods can be done on members of the baseline collection then
the baseline is not stable and can be changed without checking out the
Version-Controlled Configuration...this seems odd....
Regards,
--
Peter Raymond - MERANT
Principal Architect (PVCS)
Tel: +44 (0)1727 813362
Fax: +44 (0)1727 869804
mailto:Peter.Raymond@merant.com
WWW: http://www.merant.com
Received on Thursday, 27 September 2001 09:33:14 UTC