20 likes | 134 Views
This document outlines the version history and control mechanisms for various resources within specified collections. It details the bindings between the main file (main.c) and its associated version history resources. The collection versioning is structured into various iterations (V1, V2, V3) of resources, including how bindings to version history records (VHRs) are managed. This ensures that although a collection can change, the mappings between source files and their respective version histories remain intact, facilitating organized version tracking and resource management.
E N D
Version Controlled Resource (main.c) Version History Resource (Collection src) Version History Resource (main.c) Version Controlled Collection (src) V1 V1 The Checked-In version of this collection is version three. V2 V2 DAV:Checked-in V3 Binding main.c V3 Binding main.c The collection version has a binding that maps the name main.c to the Version History Resource for main.c. It does not bind to a specific version or VCR for main.c The Version Controlled Collection has a binding to the VCR for main.c. DAV:checked-in V3 of main.c Version Controlled Collections
Version History Resource (for file a) VH19 Version History Resource VH14 Version History Resource (for file b) VH24 Version Controlled Resource a Version Controlled Resource b Collection Version V1 Collection Version V2 V1 V1 V2 V2 V3 V3 DAV:checked-in V3 of resource a DAV:checked-in V3 of resource b Version Controlled Collections Collection Version V2 has bindings to the Version History Resources VH19 and VH24. Version Controlled Collection /x DAV:checked-in Version-Controlled bindings The VCC has bindings to specific VCRs, these are not captured when the collection is checked-out and checked-in. Only bindings to VHRs are captured by new Collection Versions.