Next message: jamsden@us.ibm.com: "Re: Members of a collection"
From: Tim_Ellison@oti.com (Tim Ellison OTT)
To: esedlar@us.oracle.com (Eric Sedlar), ietf-dav-versioning@w3.org ('Delta V')
Message-ID: <2000Feb17.095200.1250.1478891@otismtp.ott.oti.com>
Date: Thu, 17 Feb 2000 09:57:04 -0500
Subject: Re: Auto version for workspaces
<eric>
This is a pretty critical feature. The other way to accomplish this is to
set auto-versioning on a per-collection basis via a new property on
collections. This might be preferable if versioning is associated with a
particular set of data rather than a particular user.
</eric>
You can already set auto-version on a collection, given that a collection is
a resource. However, if you are saying that there should be a "deep"
auto-version on a collection then I think that would be strange. In the
face of binds, that would mean that the path to a resource dictates whether
the resource is auto-versioned or not. It works, but I think it is a
confusing user model.
Tim