- From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
- Date: Tue, 16 Mar 2004 16:22:50 -0500
- Cc: ietf-dav-versioning@w3.org
Either interpretation is OK with me. Do you (or anyone else) want this to be added? Cheers, Geoff Alison wrote on 03/12/2004 01:04:43 PM: > Section 13.3.1 of the spec says: > > > 13.3.1 DAV:unreserved > > This property of a checked-out resource indicates whether the > > DAV:activity-set of another checked-out resource associated with the > > version history of this version-controlled resource can have an > > activity that is in the DAV:activity-set property of this checked-out > > resource. > > The activity feature adds a checkout precondition: > > > (DAV:one-checkout-per-activity-per-history): If there is a request > > activity set, unless DAV:unreserved is specified, another checkout > > from a version of that version history MUST NOT select an activity in > > that activity set. > > Should this precondition also cover the case where the checkout request > includes an activity and specifies DAV:unreserved, but the checkout > should fail because a checked-out resource already exists, with > DAV:unreserved false, and a DAV:activity-set value that contains the > checkout request activity?
Received on Tuesday, 16 March 2004 16:23:19 UTC