Next message: Tim Ellison/OTT/OTI: "LOCK and versioned resources"
Date: Wed, 31 May 2000 17:34:12 -0400 (EDT)
Message-Id: <200005312134.RAA25772@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: workspaces as collections
From: jamsden@us.ibm.com
<tim/> Given that we are allowed to define the (opaque) working
resource id to look like a URL, there is nothing to stop the server
using the working resource URL as its id, so let's drop the working
resource id and simplify the description.
<jra> I think this is what I was missing, using the working
resource or revision URL in the Target-Selector. If that is the
plan, then I'm all for it.
</jra>
OK, it looks like we're almost there. The last step is to realize
that once you have a working resource URL or revision URL, you just
use it as the request URL. The versioned resource URL is irrelevant
(or at least, redundant) once you have a working resource URL or
revision URL for use as the request-URL, so there is no reason to
encumber the request with a Target-Selector header. It also allows us
to get rid of the Destination-Target-Selector header altogether.
Cheers,
Geoff