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

Re: workspaces

From: <Tim_Ellison@uk.ibm.com>
Date: Fri, 10 Nov 2000 15:39:32 +0000
To: Ross Wetmore <rwetmore@verticalsky.com>
cc: ietf-dav-versioning@w3.org
Message-ID: <80256993.00585A40.00@d06mta07.portsmouth.uk.ibm.com>


Simply that you shouldn't be allowed to create an overlap by binding a
member of one workspace to a member of another workspace, or create a
binding from a member of a workspace to, say, a parent of the workspace
since the workspace would become a member of itself.

However, since the delta-v spec cannot refer to the binding spec ("other
than as work in progress") it should be sufficient to say that workspaces
cannot be nested, and leave other binding issues for that work group<g>

Tim



Ross Wetmore <rwetmore@verticalsky.com> on 2000-11-10 02:24:58 PM

Please respond to Ross Wetmore <rwetmore@verticalsky.com>

To:   Tim Ellison/UK/IBM@IBMGB
cc:   ietf-dav-versioning@w3.org
Subject:  Re: workspaces




Tim_Ellison@uk.ibm.com wrote:
>
> The spec should say that workspaces cannot 'overlap', i.e., a workspace
> cannot be a member of another workspace, and ...

  ... bindings cannot be made outside the workspace.

  Can you clarify what is meant by the above? Bindings to/from what for
instance?

> Having multiple workpace 'parents' would confuse
> many things, including current activity, and make workspace semantics for
> single history selectors very time consuming to enforce.
>
> Tim

Cheers,
RossW
Received on Friday, 10 November 2000 11:06:35 GMT

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