Next message: Tim Ellison/OTT/OTI: "Re: Why do we need working resource ids ?"
Date: Tue, 30 May 2000 12:15:52 -0400 (EDT)
Message-Id: <200005301615.MAA23894@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: Workspaces as versionable resources
From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
<geoff>
A baseline is a "deep revision" only if the workspace selects
revisions of all the members. So a baseline is as deep or shallow as you
want to make it (based on what revisions you have selected for that
workspace).
</geoff>
<tim_2>
Agreed. Therefore we have lost the operation that would do the deep walk
of a collection in a workspace and capture it in a snapshot. In the new
world, we would need to have something like
SET-TARGET /colln/
Target-Selector: http://foo/source_workspace
Workspace: http://foo/destination_workspace
Depth: infinity
...
followed by
MKBASELINE /baseline
Workspace: http://foo/destination_workspace
...
<tim_2/>
I wouldn't say that we have "lost the operation", but rather that
it now requires two requests, while before it could be done in one.
I believe the commonest use case will be one where you are making
a series of deep revisions of a collection over time, so that once you have
populated a workspace with a versioned collection, you can continue to use
that same workspace for subsequent baselines of that collection.
Cheers,
Geoff