Next message: Juergen Reuter: "Re: draft-ietf-deltav04.5 now available"
From: Edgar@EdgarSchwarz.de
Date: Sat, 20 May 2000 16:05:08 +0200
Message-Id: <200005201405.QAA02320@msheas02.msh.de>
To: ietf-dav-versioning@w3.org
Cc: Edgar@EdgarSchwarz.de
Subject: Re: Workspaces as versionable resources
Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com> wrote:
> I would like to declare my dissatisfaction with workspaces as versionable
> resources.
Me too. I'm not sure what you win with that.
> We appear to have lost two useful concepts.
I don't know whether we lost them.
> (1) Configurations, (which could be used to capture the state of a
> workspace target selection),
> (2) Deep versioning of collections
Isn't that just called a revision of a collection now ? Where we assume
that all members of the collection must also be revisions.
But whatever we call it. I want "deep versioning of collections".
What I'm not sure about is, whether WebDAV wants to help with SW development.
Should it be good for that too ? Can you base stuff like in CVS, Clearcase or
PVCS Dimensions on WebDAV ?
BTW, I just try to implement workspaces for my Oberon System. At the moment
I imagine a workspace being similar to a Clearcase view (Hi Geoff :-) with
a config spec (rsr) of checked out, newest revision.
Then a second vote concerning UNCHECKOUT:
Good: CHECKOUT abort It concernes something that was done with CHECKOUT
Acceptable: UNCHECKOUT Even it's creating another method.
No,no: CHECKIN abort CHECKIN should be about a new version. This relation
would be rather farfetched in this case.
--
edgar@edgarschwarz.de http://www.edgarschwarz.de
* DOSenfreie Zone. Running Native Oberon. *
Make it as simple as possible, but not simpler. Albert Einstein