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

Some questions on Configurations

From: Kirmse, Daniel <daniel.kirmse@sap.com>
Date: Wed, 12 Dec 2001 12:22:10 +0100
Message-ID: <59357A260E15D311B5A60008C75D3530068B4722@dbwdfx13.wdf.sap-ag.de>
To: "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>
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). 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 pic below (taken from DeltaV draft 20) implies a 1:1 relationship of the
two concepts.


  +-------------------------------------+
  |Baseline-Controlled Collection       |<------+
  |/src                                 |       |
  |-------------------------------------|       |
  |DAV:version-controlled-configuration +---+   |
  +-------------------------------------+   |   |
                                            |   |
                                            |   |
  +-------------------------------------+   |   |
  |Version-Controlled Configuration     |<--+   |
  |/repo/vcc/128                        |       |
  |-------------------------------------|       |
  |DAV:baseline-controlled-collection   +-------+
  |-------------------------------------|
  |DAV:checked-in                       +-------+
  +-------------------------------------+       |
  |DAV:version-history                  +---+   |
  +-------------------------------------+   |   |
                                            |   |
                                            |   |
  +------------------------+                |   |
  |Baseline History        |<---------------+   |
  |/repo/blh/13            |                    |
  |------------------------+                    |
  |DAV:version-set         +----------------+   |
  +------------------------+    |   |   |   |   |
                                v   |   v   v   |
                                    |           |
  +------------------------+        |           |
  |Baseline                |<-------+-----------+
  |/repo/blh/13/ver/8      |
  |------------------------+     +--------------+
  |DAV:baseline-collection +---->|Collection    |
  +------------------------+     |/repo/bc/15   |
                                 +--------------+

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.  

But in my opinion the "component" baselines/configurations created that way
would be no subbaselines. Or would they be?
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.
So what is the way of creating subbaselines? My reading of the draft did not
reveal this fact to me (unfortunately).


Regards,
Daniel
Received on Wednesday, 12 December 2001 06:22:46 GMT

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