Next message: Geoffrey M. Clemm: "Re: LOCK and versioned resources"
Date: Fri, 2 Jun 2000 09:38:34 -0400 (EDT)
From: Michael Skowronski <michael@box.systrix.com>
To: Tim Ellison/OTT/OTI <Tim_Ellison@oti.com>
cc: ietf-dav-versioning@w3.org
Message-ID: <Pine.LNX.4.10.10006020938270.31114-100000@box.systrix.com>
Subject: Re: LOCK and versioned resources
On Fri, 2 Jun 2000, Tim Ellison/OTT/OTI wrote:
> The intention of a LOCK is to ensure that (1) the resource
> content/properties and (2) request-URI/target-sector are protected by the
> lock token owner.
>
> So if we have a versioned collection (/foo/) and versioned data container
> (/foo/bar), the effect of taking out a lock as follows:
>
> LOCK /foo/bar
> Target-Selector: tested
> Workspace: http://whatever/mywksp
>
> means that the target of the request should be protected in both ways
> described above.
>
> The implications are that:
> (a) the default target for /foo/ in /mywksp cannot be changed (using
> SET-TARGET),
> (b) the binding /foo/ and /foo/bar cannot be changed (using MOVE/DELETE),
> and (c) the label "tested" cannot be moved/removed from the revision it is
> presently on (using LABEL).
>
> I surprised myself with point (c) -- but I think this is what we want.
>
> [Note that if the revision labeled "tested" is the default target for that
> resource in /mywksp, and if I hadn't provided the Target-Selector:, then
> point (c) would not apply (i.e., the label could be (re)moved)]
>
> Comments?
> Tim
>