- From: Clemm, Geoff <gclemm@rational.com>
- Date: Tue, 18 Dec 2001 08:48:33 -0500
- To: ietf-dav-versioning@w3.org
From: Alison Macmillan [mailto:alison.macmillan@oracle.com] "Clemm, Geoff" wrote: > From: Alison Macmillan [mailto:alison.macmillan@oracle.com] > > I hadn't understood from the spec that the (collection) > version-history should imply a baseline, and so had not seen > how the version-controlled-binding could behave as a > "baseline-binding". > > A collection version history definitely does not imply a > baseline. But if a server supports both version-controlled > collections and baselines, then if a baseline B1 selects > collection version CV2 (say with name "x/y" relative to the root > of B1), and if CV2 has a version-controlled binding named "z" to > the collection version history CVH3, and if B1 has a subbaseline > B2, and if the root of B2 is a version of CVH3, then subbaseline > B2 will be located at "x/y/z" relative to the root of B1. > So, is it right that the DAV:baseline-collection can _itself_ be a VCR (for the above example, with DAV:checked-in a version of CVH3)? That's correct. Cheers, Geoff
Received on Tuesday, 18 December 2001 08:49:16 UTC