W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2001

Re: re-use of version URL's

From: Geoffrey M. Clemm <geoffrey.clemm@rational.com>
Date: Fri, 5 Jan 2001 16:37:37 -0500 (EST)
Message-Id: <200101052137.QAA00248@tantalum.atria.com>
To: ietf-dav-versioning@w3.org

   From: "Mark A. Hale" <mark.hale@interwoven.com>

   There appears to be agreement in the fact that we want URL's to have
   longevity.  Furthermore, this longevity applies to what I want to classify
   as resources that can be baselined.  (Since I am new to WebDAV, I hope that
   I am not opening up a can of worms by using the term 'baseline'.  In the
   context here, it is a resource that is stable and has longevity).

To avoid confusion, let's call them "stable resources" rather than
"baselineable resources".

   There are implementation possibilities where version URL's can be
   reused. (I am not trying to judge the quality of the
   implementations and the impact on either client of server
   functionality.  Merely an acknowledgement that these
   implementations are feasible.) The example I posted earlier was
   centered on the concept of a temporary space.

   I propose that we instead use something to the effect 'MUST NOT re-use
   version-controlled resource URL's for resources which can be baselined'.

As Greg pointed out, I think you meant "version URL", not
"version-controlled resource URL" here.  This doesn't get us anywhere
because the fact that a URL is a version URL (i.e. appears
in a DAV:version or DAV:checked-out, etc. properties) is exactly
the way that a client determines whether or not the URL
is stable, so this is basically telling a client that
"a version URL is stable unless it isn't".  Not very useful (:-).

Cheers,
Geoff
Received on Friday, 5 January 2001 16:38:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:39 GMT