Next message: Tim Ellison/OTT/OTI: "RE: Labels"
From: "Eric Sedlar" <esedlar@us.oracle.com>
To: "Clemm, Geoff" <gclemm@rational.com>
Cc: "DeltaV (E-mail)" <ietf-dav-versioning@w3.org>
Date: Thu, 4 May 2000 00:56:40 -0700
Message-ID: <NDBBKNOGFKEBJOOOIOOLOEKPCAAA.esedlar@us.oracle.com>
Subject: RE: draft-ietf-deltav04.5 now available
OK Geoff, I have enough time to harass you about versioning again, so
hopefully you can give me some pointers to some of the changes in the
spec.
What happened to the notion of a baseline being a recursive snapshot
of a versioned collection? It now seems that the members of a baseline
need not be adjacent in URL space, e.g. if I do a GET on /a/b/c/d
with a baseline selected in my workspace, /a and /a/b/c might have
particular revisions selected in the baseline, but not /a/b or
/a/b/c/d.
Thanks,
Eric
-----Original Message-----
From: ietf-dav-versioning-request@w3.org
[mailto:ietf-dav-versioning-request@w3.org]On Behalf Of Clemm, Geoff
Sent: Tuesday, May 02, 2000 9:10 AM
To: DeltaV (E-mail)
Subject: draft-ietf-deltav04.5 now available
www.webdav.org/deltav has been updated to point to this draft.
This contains just a few updates based on recent email traffic.
In particular, "unreserved checkouts" have been added to advanced
versioning.
I did make a name change from "default workspace" to "request workspace",
since this simplified the text by removing the need to keep saying "if there
is not explicit Workspace header, the default workspace is used". Now
everything just says "the request workspace is used", and the term "request
workspace" is defined to mean "the workspace in the Workspace header,
or if none, a default workspace allocated by the server".
Cheers,
Geoff