Re: Notes from DAV WG meeting

John,

My note was probably confusing. I actually wanted to know how versioning and
configuration management could be separated in the context of Web-DAV
collections and advanced collections. As you say (and as my note says),
there are existing products which make this distinction and hence it could
be argued that configuration management should be a layered functionality on
version control (see note below). However, I need clarification on (by
perhaps the version control design team) how this separation is to be
achieved if the plan is to allow versioning of collections and members of
collections when a member could be part of different collections and could
evolve independently of the collection.

Note: A similar discussion to this happened long time ago in the list. At
that time, Jim Whitehead also mentioned the fact that configuration
management is actually achieved in different ways in different
products(configuration relative naming, labels, etc.). This issue might also
have to be considered.

Personally, I would actually like to see both configuration management and
version control to be designed together because of Web-DAV collections and
advanced collections. Whether we make configuration management optional is
an orthogonal decision.

-----Original Message-----
From: John Stracke <francis@netscape.com>
To: WebDAV WG <w3c-dist-auth@w3.org>
Date: Monday, August 31, 1998 7:40 PM
Subject: Re: Notes from DAV WG meeting


>Chris Kaler wrote:
>
>> if you look at many of the versioning products available today,
>> the line between CM and basic versioning is hard to draw.
>
>That doesn't mean that it has to be that way.  Existence proof: CVS.
>
>--
>/======================================================================\
>|John (Francis) Stracke    |My opinions are my own. | S/MIME supported |
>|Software Retrophrenologist|===========================================|
>|Netscape Comm. Corp.      |The problem with any unwritten law is that |
>|francis@netscape.com      | you don't know where to go to erase it.   |
>\======================================================================/
>New area code for work number: 650
>
>
>

Received on Monday, 31 August 1998 20:43:13 UTC