default workspace vs. set-default method vs. default label

Geoffrey M. Clemm (gclemm@tantalum.atria.com)
Sun, 14 Mar 1999 15:35:05 -0500


Date: Sun, 14 Mar 1999 15:35:05 -0500
Message-Id: <9903142035.AA17060@tantalum>
From: "Geoffrey M. Clemm" <gclemm@tantalum.atria.com>
To: ietf-dav-versioning@w3.org
Subject: default workspace vs. set-default method vs. default label


In order to provide interoperability, the level-1 technique for
"setting the default revision" of a versioned-resource should work
when applied to a versioned-resource being maintained by a level-2
server.

If a level-2 server uses a default workspace, with the
revision-selection-rule of the default workspace determining default
revision selection, then one would have to provide a "set-default"
method for level-1, and in general, a "set-default" might fail
against an arbitrary revision-selection-rule.

So from my perspective, the best choice is to get rid of the notion of
a "default workspace", and stick with the notion of a "default label".
Then you just set the default label when you want to adjust the
default revision of any particular versioned-resource, and you require
that CHECKIN automatically move the default label to the new
revision, if predecessor of the new revision is the current default
revision.

Cheers,
Geoff