Next message: Clemm, Geoff: "RE: Versioning TeleConf ... 2pm-3pm EST"
Date: Tue, 12 Sep 2000 16:42:46 -0400 (EDT)
Message-Id: <200009122042.QAA05627@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: Naive question
From: Tim_Ellison@uk.ibm.com
How do you refer to a version selector rather than the version it selects?
(i.e. to PROPFIND/PROPPATCH it's properties)
A version selector has a URL which is different from the URL
of any particular version. When you do a PROPFIND/PROPPATCH on a
version selector URL, you operate on the properties of the version
selector. When you do a PROPFIND/PROPPATCH on a version URL,
you operate on the properties of the version.
Note though that all the dead properties of a version selector
correspond (i.e. have the same value) as those of the version that
is that target of that version selector.
Further note that if you use a Target-Selector header with a
PROPFIND/PROPPATCH request, you operate on the properties of
the selected version, and *not* on the properties of the
version selector.
From: "Jim Amsden/Raleigh/IBM" <jamsden@us.ibm.com>
You can't. PROPFIND returns the properties of both.
PROPFIND returns the properties of whatever resource you
applied it to. In particular, the live properties of a version
selector can be different from those of its target version.
A while back, we modeled version selectors as a "redirector"
that redirected methods to the version, but that was a
good while ago, before we looked carefully at modeling
versioned collections.
Note that we can
create version selectors with VERSION-CONTROL, but DELETE doesn't
actually say you can delete them.
You can use DELETE to delete a version selector.
DELETE of a version is undefined.
That is correct, but DELETE of a version selector is defined.
DELETE on a version selector should just delete the version selector,
but then we have a special case where the version selector is accessed
as a resource itself.
A version selector is always accessed as a resource itself.
A Target-Selector header can be used to redirect a request
from a version selector to the specified version, but without
a Target-Selector header, a method applied to a version selector
URL is applied to the version selector resource.
Remember the BIND/DELETE/UNBIND arguments? Geoff?
Yes, we used to need this kind of argument when we modeled
version selectors as redirectors, but we don't need them
any more, now that we don't model them that way anymore.
Cheers,
Geoff