RE: Definition of a configuration

Hi,

So we have this "concept" called a configuration which is ALL resources
rooted
at a collection (with Depth:infinity) and we have a concept called a
"version-controlled 
configuration" which is all VERSION-CONTROLLED resources rooted at a
collection which 
is captured in a baseline.

I think the terminology is a little odd because every member of the
configuration has 
the DAV:version-controlled-configuration property even though some of the
members of 
the configuration are not in the "version-controlled configuration" (eg they
are not 
version-controlled).

I know it's too late to change this, but feel we should have some
explanation of this 
available somewhere, eg in the FAQ, use case doc or somewhere.  It would
have been very 
easy for me to miss this subtle point and incorrectly code the property to
ONLY appear 
on version-controlled resources.

Regards,
--
Peter Raymond - MERANT
Principal Architect (PVCS)
Tel: +44 (0)1727 813362
Fax: +44 (0)1727 869804
mailto:Peter.Raymond@merant.com
WWW: http://www.merant.com



-----Original Message-----
From: Clemm, Geoff [mailto:gclemm@rational.com]
Sent: 29 October 2001 12:45
To: ietf-dav-versioning@w3.org
Subject: RE: Definition of a configuration


A "configuration" is just a concept defined by the spec
(i.e. the definition quoted below).  It always existed in
WebDAV, but didn't have a name (it was the "Depth:infinity
state of a collection").  You manipulate it with
standard operations like PUT/MKCOL/DELETE/COPY (a Depth:Infinity
copy allows you to copy an entire configuration from one spot
to another).

Cheers,
Geoff

-----Original Message-----
From: Alison Macmillan [mailto:alison.macmillan@oracle.com]
Sent: Monday, October 29, 2001 5:37 AM
To: Clemm, Geoff
Cc: ietf-dav-versioning@w3.org
Subject: Re: Definition of a configuration


"Clemm, Geoff" wrote:

>    From: Edgar@EdgarSchwarz.de [mailto:Edgar@EdgarSchwarz.de]
>
>    ...I would change the definitions Peter cites:
>
>      "A configuration is a set of resources that consists of a root
>       collection and all version-controlled members of that root
collection
>       except those resources that are members of another configuration"
>
>      "A baseline is a version resource that captures the state of each
>       member of a configuration."
>
> This would not allow you to talk about non-version-controlled
> configurations.  I think this would be unfortunate, since it is
> a useful concept even if you aren't doing versioning.
>

I didn't think non-version-controlled configurations were defined by the
spec.
How do you create and restore such a configuration?