Versioning TeleConf Notes, 5/10/99
Geoffrey M. Clemm (gclemm@tantalum.atria.com)
Mon, 10 May 1999 17:14:36 -0400
Date: Mon, 10 May 1999 17:14:36 -0400
Message-Id: <9905102114.AA00602@tantalum>
From: "Geoffrey M. Clemm" <gclemm@tantalum.atria.com>
To: ietf-dav-versioning@w3.org
In-Reply-To: <9905101359.AA10569@tantalum> (gclemm@tantalum.atria.com)
Subject: Versioning TeleConf Notes, 5/10/99
First a reminder: Design team members should make their reservations
at the Concord Colonial Inn ASAP!
At todays call, we mostly reviewed current status for design team
members that have missed some or all of the last few weeks' discussion
on configurations. In particular, we went over:
- why one might want "shallow configurations" (i.e. configurations
that provide a revision map for some versioned-collections, but does not
provide a revision map for *all* of the versioned-resources that are
members of the selected revisions of those versioned-collections).
- why one might want "deep configurations" (i.e. configurations that
*do* contain revision maps for all of the versioned-resources that are
members of the versioned-collection revisions selected by the configuration.
The basic reason for shallow configurations is that you commonly want
to "lock down" part of the namespace, but allow dynamic revision
selection to occur at the rest of the namespace, and at the leaves.
The basic reason for deep configurations is that you want to allow the
server to very efficiently create configurations that capture the full
state of some subtree rooted at some collection.
Cheers,
Geoff