W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > October to December 2001

RE: Workspaces and File&Folder Hierarchy

From: Kirmse, Daniel <daniel.kirmse@sap.com>
Date: Wed, 12 Dec 2001 09:26:29 +0100
Message-ID: <59357A260E15D311B5A60008C75D3530068B4720@dbwdfx13.wdf.sap-ag.de>
To: "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>
Thanks so far! But what about this:

>But I agree with Alan that the most important thing about a workspace
>is that it has at most one versioned-controlled resource for a given
>version history.

But it is still possible to have a version tree (not a single line of
descent of versions for the only VCR in the workspace)??? Well it would
produce a ambiguity, wouldn't it? And then there is no unambigious merge or
baselining can take place. So I would rather understand it that way, that
you should have a <checkin-fork><forbidden> behavior for the versions. With
that it would be possible that more than one developer checks out a given
version but at check in time they would be forced to do an explicit merge
and the single line of descent and the unabiguity would be kept.

(was that understandable???)

regards
Daniel

>-----Original Message-----
>From: Clemm, Geoff [mailto:gclemm@rational.com]
>Sent: Dienstag, 11. Dezember 2001 16:53
>To: Ietf-Dav-Versioning (E-mail)
>Subject: RE: Workspaces and File&Folder Hierarchy
>
>
>   From: Alan Kent [mailto:ajk@mds.rmit.edu.au]
>
>   On Mon, Dec 10, 2001 at 04:36:03PM +0100, Kirmse, Daniel wrote:
>
>   > is it allowed to have a Workspace containing a File&Folder
>   > Hierarchy (i.e. a copy of a subtree of the webdav resource tree)?
>
>   Yes. I think a really nice thing about DeltaV is that it allows
>   versioning of containers (directories). Its not mandatory, but
>   certainly is supported. I would suggest having a bit of a read.
>
>   To me the only special thing about a workspace is that it imposes
>   additional constraints on that you are only allowed to check out
>   one version of a resource under it. (Note, you could have multiple
>   bindings of URLS to the same resource, but they would be the same
>   version of that resource).
>
>Yes, as Alan says, a Workspace can have a File/Folder (WebDAV would
>call it a Resource/Collection) hierarchy below it (a Workspace is
>just a special kind of collection).
>
>Another special thing about a Workspace is that you can
>associate a "current-activity" with that workspace, to simplify
>activity-based checkouts.  Also, you have an easy way to identify
>all checkouts in a workspace (without doing a depth propfind),
>and you can tell whether a resource is a member of a workspace by
>looking at its DAV:workspace property.
>
>But I agree with Alan that the most important thing about a workspace
>is that it has at most one versioned-controlled resource for a given
>version history.
>
>Cheers,
>Geoff
>
Received on Wednesday, 12 December 2001 03:27:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:43 GMT