Non-versioned resources in versioned col
Tim Ellison OTT (Tim_Ellison@oti.com)
Tue, 16 Nov 1999 11:00:04 -0500
From: Tim_Ellison@oti.com (Tim Ellison OTT)
To: ietf-dav-versioning@w3.org (ietf-dav-versioning)
Message-ID: <1999Nov16.105600.1250.1386384@otismtp.ott.oti.com>
Date: Tue, 16 Nov 1999 11:00:04 -0500
Subject: Non-versioned resources in versioned col
<jra>
Currently, a versioned collection cannot contain an unversioned resource.
This is one of the issues we haven't resolved yet. A revision of a
versioned collection should minimally create a version of the namespace. It
seems that the state of the resources accessed through that namespace
should be independent. However, it would not be possible to create a
baseline of a revision of a versioned collection that contained references
to unversioned resources.
An issue with the language above: a resource is not actually created in a
versioned collection, its created in some server-dependent private store,
and a binding is added to the collection. So in this case, the versioning
of the collection and the resource can be independent. Its only the binding
that needs to be fixed in the revision.
</jra>
Agreed. Once reason for only allowing versioned resources in versioned
collections is that you would not have to make special cases of them for
deep operations (such as baselining) -- however, there are other dimensions
such as working resources that might throw a wrench in the works.