Next message: Geoffrey M. Clemm: "Re: propfind on a stable URL"
Date: Sun, 21 May 2000 00:18:10 -0400 (EDT)
Message-Id: <200005210418.AAA09319@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: Working resources in basic versioning
From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
But if you have a stable URL to a revision of the versioned
resource, then I would assume it is good 'for all time' -- since
the namespace of the stable URL is effectively outside that of the
dynamic URLs.
I still don't understand all the characteristics of a stable URL --
or what it represents.
The definition of a stable URL has undergone some mutation, so some
confusion here is understandable. Currently, it just means a URL that
identifies a particular revision (it is unaffected by Target-Selector
or Workspace headers).
We used to have a stronger definition (i.e. the URL was guaranteed
to always identify that revision), but there were complaints that
this was too hard for some servers to implement, so we weakened it.
So now a server can play URL games and just extend the name of the
versioned resource in funny ways, e.g. the stable URL for rev23 of
versioned resource "/a/b/c.html" could be "/a/b/c.html;rev23".
Cheers,
Geoff