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

RE: Definition of a configuration

From: Clemm, Geoff <gclemm@rational.com>
Date: Mon, 29 Oct 2001 09:53:46 -0500
Message-ID: <3906C56A7BD1F54593344C05BD1374B104AC75EE@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
   From: Peter Raymond [mailto:Peter.Raymond@merant.com]

   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).

The best way to think of the DAV:version-controlled-configuration
property on a non-version-controlled resource is that it indicates
the VCCn that the non-VCR would become a member of when it is
put under version control.  One way this property would be used was
if you were running against a server that required an explicit
client checkout of a VCCn in order to change it, the DAV:v-c-cn 
property on the non-VCR would tell you what VCCn you would have
to check out before you could apply VERSION-CONTROL to that non-VCR.

   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.

This is now a topic in the FAQ (in the "Properties" section).

Received on Monday, 29 October 2001 09:54:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:47 UTC