Next message: Clemm, Geoff: "RE: UNCHECKOUT"
To: ietf-dav-versioning@w3.org
Message-ID: <OF4350ACDA.C29EC172-ON852568E4.004817AD@ott.oti.com>
From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
Date: Fri, 19 May 2000 09:18:28 -0400
Subject: Workspaces as versionable resources
I would like to declare my dissatisfaction with workspaces as versionable
resources.
From what I can make out, the only reason that this was considered was to
provide a "snapshot" mechanism to capture the state of the workspace (and
in particular its target selections).
However, by making workspaces versionable, we also get into the quagmire of
selecting revisions/working resources of a workspace resource.
The obvious question is, when specifying (in a header) a URL to a versioned
workspace, which workspace is used to select revisions of the workspace and
versioned collections along the path?
...but it also permits structures that don't seem to have any useful
meaning, such as branching in workspace history.
We appear to have lost two useful concepts.
(1) Configurations, (which could be used to capture the state of a
workspace target selection),
(2) Deep versioning of collections
Tim