Re: Non-versioned resources in versioned collections
Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Fri, 10 Dec 1999 00:51:58 -0500
Date: Fri, 10 Dec 1999 00:51:58 -0500
Message-Id: <9912100551.AA03049@tantalum>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
In-Reply-To: <1999Nov16.105600.1250.1386384@otismtp.ott.oti.com>
Subject: Re: Non-versioned resources in versioned collections
From: Tim_Ellison@oti.com (Tim Ellison OTT)
... One 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.
The working resources don't throw much of a wrench. The versioned
resource from which the working resource is checked out is what is
bound into the versioned collection. The working resource is just
something that the workspace provides you as the target of that
versioned resource. So having working resources visible in versioned
collections is compatible with the statement that only versioned resources
can be members of versioned collections.
Cheers,
Geoff