Next message: Clemm, Geoff: "Versioning TeleConf Agenda, 5/8/00 (Monday) 2pm-3pm EST"
Message-ID: <65B141FB11CCD211825700A0C9D609BC02B492E0@chef.lex.rational.com>
From: "Clemm, Geoff" <gclemm@Rational.Com>
To: "DeltaV (E-mail)" <ietf-dav-versioning@w3.org>
Date: Mon, 8 May 2000 01:00:17 -0400
Subject: RE: draft-ietf-deltav04.5 now available
A baseline is now a snapshot (i.e. version) of a workspace.
If you create a workspace which contains
a versioned collection and all of its
members, a baseline of that workspace will be a recursive
snapshot of that versioned collection. Is there something you
wanted to do with versioned collections that this would not
support?
Cheers,
Geoff
-----Original Message-----
From: Eric Sedlar [mailto:esedlar@us.oracle.com]
Sent: Thursday, May 04, 2000 3:57 AM
To: Clemm, Geoff
Cc: DeltaV (E-mail)
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