Next message: Geoffrey M. Clemm: "Versioning TeleConf Agenda, 1/10/00 (Monday) 2-3pmEST"
Date: Mon, 10 Jan 2000 13:25:49 -0500
Message-Id: <10001101825.AA20789@tantalum>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: Baselines vs. labels
One way to understand the different revision selection mechanisms is
that they represent different levels of versioning support:
Level | Revision Selection Mechanism
------------------------|-----------------------------
Base Versioning | Labels
Activities | Configurations and Activities
Versioned Collections | Baselines and Activities
Therefore, although there a variety of revision selection mechanisms,
at each level, it is reasonably simple. A client would normally
work at just one of these levels, so a client is not faced with
the complexity, just the server.
Cheers,
Geoff
From: jamsden@us.ibm.com
Configurations are a generalization of baselines that allow users to choose
the revisions of versioned resources that are members to be selected by a
workspace. Baselines alone are not enough because they require versioned
collections.
"Eric Sedlar" <esedlar@us.oracle.com>@w3.org on 01/08/2000 02:42:46 PM
Thanks for pointing out the caching benefit of baselines, and the way a
shared activity can be used to modify them. My biggest beef is not with
baselines, but with the number of ways of seleting a set of revisions:
* baseline
* configuration
* shared activity (with RSRs specifying the revisions)
* label
If you are willing to get rid of configurations, let's get rid of them.