Re: Notes from 5/3/99 Versioning TeleConf
Edgar Schwarz (Edgar.Schwarz@de.bosch.com)
Tue, 4 May 1999 12:43:43 +0200 (MESZ)
Date: Tue, 4 May 1999 12:43:43 +0200 (MESZ)
From: Edgar Schwarz <Edgar.Schwarz@de.bosch.com>
To: ietf-dav-versioning@w3.org
In-Reply-To: <9905032039.AA06833@tantalum>
Message-ID: <Pine.GHP.4.05.9905041228400.3928-100000@hpmx15.bk.bosch.de>
Subject: Re: Notes from 5/3/99 Versioning TeleConf
On Mon, 3 May 1999, Geoffrey M. Clemm wrote:
> - Configurations
>
> There was basic agreement with the proposed approach to configurations,
> but the following issues were still outstanding:
>
> Jim further suggested that the configuration revision actually *be* this
> collection.
That's something im doing in practice for SCM. A configuration for my
purposes is just a file containing a list of files with a revision id.
Or do I miss something.
> I'm a little more hesitant about that, since I'm concerned that there
> will be other "collections" that we will want to associate with a
> configuration revision. I don't have anything particular in mind yet,
> but I'm still concerned that something will turn up.
But it would be a elegant and simple solution.
> We then discussed the "create a configuration revision without using
> a workspace" issue. Chris indicated that the "configuration workspace"
> described in the agenda makes sense, but is concerned that there are
> complexities associated with introducing another flavor of workspace,
> since we already have "checkout-token workspaces" and "version-selection
> workspaces".
I think that there should be configurations without any need for a
workspace, activity or other thing.
As I already wrote before I think that configurations are necessary
already in level 1 versioning to make level 1 useful. So let's make them
as simple as possible.
> Jim Amsden suggested that we just allow a list of revisions to be
> specified when creating the configuration revision. My concern with
> this approach is that the server should confirm that the list of
> revisions is a "legal" configuration (e.g. that it specifies at most
> one revision of each versioned-resource, and that it selects a
> revision of each internal member of a collection revision),
I have to think about that. Are these restrictions really necessary ?
Regards, Edgar
--
Edgar.Schwarz@de.bosch.com ON/EMS1, 07191/13-3382 Niklaus Wirth:
Privat kann jeder soviel C programmieren oder Videos ansehen wie er mag.
Albert Einstein: Mach es so einfach wie moeglich, aber nicht einfacher.