Versioning Teleconference
Sept. 27, 1999

Present: Geoff Clemm, Jim Whitehead, Jeff McAffer, Tim Ellison, Brad Sergeant
Minutes recorded by Jim Whitehead.

The teleconference had a sequence of discussions on various issues.

The first topic discussed was check-out "deep", check-in "deep", and
baselines.  In particular, why do you need a baseline?  A check-in
(deep) of a collection creates a baseline.

One rationale for having a baseline was highlighted by the following
scenario.  A user checks-in a collecion.  How, later, does that user
re-create the exact membership, including revisions, of the collection
at the time it was checked-in?  Time-based revision selection rules
won't cut it, since there can be branches, and the time-based
selection doesn't differentiate between branches. Could potentially
use labels, but introducing a new concept, the baseline, is better.

Discussion of adding and removing items from a configuration.  A
configuration is a set of version identifier/revision pairs, and since
the version identifiers aren't URLs (a URL for a versioned resource is
mapped to a version identifier), it is somewhat more difficult to
identify configuration members to add or remove. There was some
discussion that the complete set of operations on configurations needs
to be fleshed out.

Discussion of getting the I-D done by the Oct. 22nd deadline.  Aiming
for getting a draft out by the 13th, so there can be some review
before the final draft is submitted.