W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2002

RE: Workspaces, Baseline-Control und auto-version, MKCOL

From: Clemm, Geoff <gclemm@rational.com>
Date: Fri, 11 Jan 2002 08:30:36 -0500
Message-ID: <3906C56A7BD1F54593344C05BD1374B1056E139C@SUS-MA1IT01>
To: "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>
   From: Kirmse, Daniel [mailto:daniel.kirmse@sap.com]

   Suppose a workspace WS with uri /ws that is under baseline-control
   and the auto-version property of the version controlled collection
   representing the baseline controlled workspace WS is set to
   checkout-checkin.

I think you mean the "version-controlled configuration" here, not
the "version-controlled collection".

   Now suppose a MKCOL request on uri /ws/folder. With that "directory"
folder
   is created within the workspace WS. Does the creation of this folder
cause a
   new baseline to be created within the baseline-history of the vcc
   representing WS?

   I assume it would do, if so is it a MUST or a SHOULD? From my reading I
   assume MUST.

The creation of a folder does not trigger the creation of a
new baseline (baselines track the state of version-controlled resources).
So you would have to change the version-controlled state of the
workspace to see the creation of a new baseline (e.g. CHECKIN, 
VERSION-CONTROL, UPDATE, or MERGE to the workspace)

But if your server automatically puts resources under version control
when they are created (including collections), and if DAV:auto-version
is appropriately set on /ws, then the MKCOL would result in the creation
of a new version of /ws, and the placing of /ws/folder under version
control, which would result in a new baseline (containing the new
version-controlled collection, /ws/folder).

Cheers,
Geoff
Received on Friday, 11 January 2002 08:31:39 GMT

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