Message-ID: <39972718000028EB@mail0.mailsender.net> Date: Mon, 21 Aug 2000 21:11:18 +0100 From: "Tim Ellison" <tim@peir.com> To: "Boris Bokowski/OTT/OTI" <Boris_Bokowski@oti.com>, "Delta-V" <ietf-dav-versioning@w3.org> Subject: Re: are workspaces versionable? A workspace is a collection, versioned or otherwise. So, if your question is can a workspace collection be a versioned collection, the answer is 'yes'. Tim -- Original Message -- > From: jamsden@us.ibm.com > Workspaces are not versionable, but they can have associated baselines. > >A > server would not be able to automatically put them under version >control. > They are versioning meta-data. > >This makes it difficult to make use of the DAV:version-set of baselines, > >because there is no convenient way of finding out the root (or the >top-level elements) of that baseline, and the bindings to these top-level > >elements - their names - are not available. Or is there a way of >determining the names of the top-level elements in a baseline? One could, > >of course, create a workspace and merge the baseline into that workspace, > >but this requires clients who just want to browse a baseline to have write > >access to the server in question. > >Anyway, I think that the 07 draft is not clear on this point. Section 9.1 > >could be changed to clarify this: > >In the third sentence of 9.1. , add "non-versionable" as follows: >"A workspace is a non-versionable collection whose members are a set of > >related versionable resources, version selectors, and working resources." > > >