Re: Non-versioned resources in versioned collections
jamsden@us.ibm.com
Mon, 13 Dec 1999 07:15:36 -0500
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <85256846.00437EBD.00@d54mta03.raleigh.ibm.com>
Date: Mon, 13 Dec 1999 07:15:36 -0500
Subject: Re: Non-versioned resources in versioned collections
But the error Tim points out still needs to be handled. You shouldn't be
able to create a baseline of a collection that has checked out members.
What revision would the baseline pick? The same error could be detected if
a versioned collection contains an unversioned resource. The problem this
avoids is the base case of creating a resource in a versioned collection.
We don't currently have a method that creates a resource or collection as
versioned, we can only change the state of an unversioned resource to
versioned with the VERSION method.
"Geoffrey M. Clemm" <geoffrey.clemm@rational.com>@w3.org on 12/10/99
12:51:58 AM
Sent by: ietf-dav-versioning-request@w3.org
To: ietf-dav-versioning@w3.org
cc:
Subject: Re: Non-versioned resources in versioned collections
From: Tim_Ellison@oti.com (Tim Ellison OTT)
... One reason for only allowing *NON*? 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