W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > October to December 2001

Re: Some questions on Configurations

From: Tim Ellison <Tim_Ellison@uk.ibm.com>
Date: Wed, 12 Dec 2001 12:02:37 +0000
To: "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>
Message-ID: <OF3A274E49.17E8D3E1-ON80256B20.0040638D@portsmouth.uk.ibm.com>
"Kirmse, Daniel" <daniel.kirmse@sap.com> wrote:

> Hi, me again!
> 
> This time I have some questions concerning configurations.
> 
> 1.DeltaV differentiates a baseline-controlled collection and a
> version-controlled configuration. My understanding is that a
> collection C put under baseline-control becomes the root of a
> version-controlled configuration (VCC).

This is true.

> So puting a collection C under baseline-control means all
> resources subordinate to C will be part of the configuration
> rooted at C and theire last checked in version is captured
> in the baseline.

The baseline captures all version-controlled resources 'reachable' from C.

> The pic below (taken from DeltaV draft 20) implies a 1:1 relationship of 
the
> two concepts.

<<snip>>

> 2. What about creating "components"/subbaselines/subconfigurations.
> Because of the definition of a Configuration given in DeltaV
> one would assume that the components have to be created before
> the "component container" otherwise there would be a problem with
> the definition:
> 
>    A "configuration" is a set of resources that consists of a root
>    collection and all members (not just internal members) of that
>    root collection that are not members of another configuration.

Agreed.

> But in my opinion the "component" baselines/configurations created
> that way would be no subbaselines. Or would they be?

Yes.  Furthermore, the subbaselines are not constrained to capture parts 
of the namespace rooted by C, they can be disjoint.

> The only way of getting it straight (means creating components after
> the superior container was created) is that the container is created/put
> under baseline control first and then subtrees of the configuration
> put under baseline control on their own. But this would contradict
> with the definition as well.

No, the subbaselines have to be created first, and can be added to the 
DAV:subbaseline-set property of a checked-out version-controlled 
configuration.

> So what is the way of creating subbaselines? My reading of the draft did
> not reveal this fact to me (unfortunately).

The baseline is created using BASELINE-CONTROL, and they become 
subbaselines by virtue of being added to the DAV:subbaseline-set.

Regards,
Tim
Received on Wednesday, 12 December 2001 07:14:42 GMT

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