comparing configurations and baselines
Geoffrey M. Clemm (gclemm@tantalum.atria.com)
Fri, 7 May 1999 15:24:57 -0400
Date: Fri, 7 May 1999 15:24:57 -0400
Message-Id: <9905071924.AA08762@tantalum>
From: "Geoffrey M. Clemm" <gclemm@tantalum.atria.com>
To: ietf-dav-versioning@w3.org
Subject: comparing configurations and baselines
To check whether configurations and baselines are just minor
variants of the same concept, I did a quick comparison. Other
than both being an RSR element (which they share with labels
and activities), they appear rather more different than alike:
A configuration is a versionable resource (not necessarily versioned).
A baseline is a revision (a deep revision of a baselined-collection).
A configuration can be created and manipulated without a workspace.
A baseline can only be created in the context of a workspace.
A configuration can be an RSR element.
A baseline can be an RSR element.
A configuration can be changed while it is in use by a workspace RSR,
and the revision selection of the workspace reflects that change.
A baseline can only be used in an RSR when it is checked in and is immutable.
A configuration supports create, get-member, and put-member operations.
A baseline only supports a create operation (CHECKIN).
A configuration can only contain revisions (a baseline is a kind of revision),
not other configurations.
A baseline can contain other baselines (i.e. for members of the
baselined-collection that are also baselined-collections).
A configuration can select revisions from an arbitrary set
of versioned-resources (but only one revision per versioned-resource).
A baseline must select exactly one revision of every member of
the baselined-collection.
Cheers,
Geoff