Next message: Geoffrey M. Clemm: "Re: Working resources in basic versioning"
Date: Sun, 21 May 2000 00:10:14 -0400 (EDT)
Message-Id: <200005210410.AAA09304@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: Locking
From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
Section 2.3 has interesting sumer semantics when read literally.
It states explicitly that locks only apply to URLs with the same
target selector value.
That is not the semantics that I would expect. Useful locking
would protect the path that I took to the resource (so that others
cannot move it out from underneath ne) and protect the resource
bound at that path. If others can modify the resource via some
other access mechanism (i.e. a different target selector) then the
lock would appear not to be as useful, since it cannot be used to
avoid lost updates.
Revisions cannot be modified, so the resource the revision selected
by a particular target selector cannot be modified by a change via
some other target selector.
Working resources can be modified, but that are only identified by
a single target selector (i.e. the working resource id), so again,
the value of one target selector will not be modified by a change
made via another target selector.
Cheers,
Geoff