- From: Peter Raymond <Peter.Raymond@merant.com>
- Date: Fri, 14 Sep 2001 09:26:11 +0100
- To: "Clemm, Geoff" <gclemm@rational.com>, ietf-dav-versioning@w3.org
- Message-ID: <20CF1CE11441D411919C0008C7C5A13B02968E86@stalmail.eu.merant.com>
Hi, [Peter Wrote:] >> Finally, section 10.2 defines a "Collection Version Resource" and >> this says that a collection version captures bindings to VCRs. But >> later in section 14 a version controlled collection is defined as >> having bindings to version histories (VHRs). I think section 10 is >> misleading and section 14 is correct. [Geoff Responded:] >Where in section 14 does it say that a version-controlled >collection has bindings to version histories? A working collection >has bindings to version histories, but a version-controlled collection >has bindings to version-controlled resources, not version histories. > >Note that a collection version is very different from a version-controlled >collection (just as a version is very different from a version-controlled >resource). Yes, what you said matches how I thought Version Controlled Collections work, but does not match the specification. A Version Controlled Collection DOES have bindings to Version Controlled Resources and this is fine, I understand this and it makes sense. A Collection Version (for example the DAV:checked-in version of the Version Controlled Collection) has bindings to Version Histories. But the issue I was reporting was that section 10.2 defines the bindings of a COLLECTION VERSION to be bindings to Version Controlled Resources. This is incorrect and does not match what you said in your reply. I propose we make two changes: 1. It takes some time to understand section 14, it would have helped if the diagram was complete and showed that /x is a Version Controlled Collection, and that V2 of VH14 is a Collection Version. 2. The current text of 10.2 says: Collection Version Resource A "collection version resource", or simply "collection version", captures the content, dead properties, and version-controlled bindings of a version-controlled collection (see Section 14). A version-controlled binding is a binding to a version-controlled resource..... I propose we make this clearer and say: Collection Version Resource A "collection version resource", or simply "collection version", captures the content, dead properties, and bindings to the Version History Resources identified in the the version-controlled bindings of a version-controlled collection (see Section 14). A version-controlled binding is a binding to a version-controlled resource. A binding of a collection version is a binding to a version history resource. Regards, Peter Raymond - MERANT.
Received on Friday, 14 September 2001 04:27:40 UTC