Next message: Geoffrey M. Clemm: "Re: Questions on activities"
Message-ID: <F3B2A0DB2FC1D211A511006097FFDDF501B537C0@BEAVMAIL>
From: Henry Harbury <Henry.Harbury@merant.com>
To: ietf-dav-versioning@w3.org
Date: Mon, 10 Apr 2000 13:09:29 -0700
Subject: Initializing a new workspace using an RSR
Assuming static workspace behavior (draft 4.2), I think it would be useful
to use the old concept of an RSR to (optionally) initially populate a new
workspace when created.
The RSR could be passed in the header of a MKWORKSPACE method. The
workspace would then be populated using this RSR, and the RSR could then
persist as a protected property of the workspace for later use/reference.
The workspace would then follow the "static" behavior for revision selection
(using the SET-DEFAULT-REVISION method associated with that workspace).
This would greatly simplify the use-case for creating workspaces on-the-fly
based on labels/activities/baselines/etc. It might be useful to define a
difference report of the current selection of a static workspace and what
the originating RSR would select at the time of the report. This would give
the client a way to "remember" what that particular workspace was intended
for (based on its initialization RSR), and what is currently different
between that RSR and that active workspace's selection.
Comments?
-- Henry.