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

Re: workspaces

From: Ross Wetmore <rwetmore@verticalsky.com>
Date: Mon, 20 Nov 2000 12:56:33 -0500
Message-ID: <3A1965D1.6463344F@verticalsky.com>
To: Tim_Ellison@uk.ibm.com
Cc: ietf-dav-versioning@w3.org
The answer was, "no,  not really". 

The example was the three overlapping circles, and 7 different
workspace combinations. If a member was added or dropped from
one team, then everyone's workspaces might need to be updated
which is as complicated a process as either of the checkin or
refresh examples.

I think it is necessary to consider a many-to-one relationship
between workspaces and version selectors, even though I admit
it would be a lot simpler in some implementations to just have 
a one-to-one. However, it is a lot better to do the implementation
right, than complicate every end-user scenario with cumbersome
or impractical workarounds.

The key point is that the current protocol should not build in 
elements which prohibit this and will require a complete reversal
of the spec at some point in the future, such as a requirement 
that a DAV:workspace property in a version selector be single 
valued. The current spec should allow extension to many-to-one 
in cases like this even if it does not currently define/require 
the extension.


Tim_Ellison@uk.ibm.com wrote:
> > The use for this was to insure consistent versions
> > across several workig teams without requiring either
> > each team to poll for changes, or each checkin to poll
> > for and update all affected workspaces.
> Would it be possible for all teams to share a common workspace containing
> resources that must be kept consistent?
> Regards,
> Tim
Received on Tuesday, 21 November 2000 04:35:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:46 UTC