- From: Jim Amsden <jamsden@us.ibm.com>
- Date: Tue, 4 Sep 2001 19:17:32 -0400
- To: ietf-dav-versioning@w3.org
Me to.
"Tim Ellison" <tim@peir.com>
Sent by: ietf-dav-versioning-request@w3.org
09/04/2001 05:59 PM
To: "DeltaV" <ietf-dav-versioning@w3.org>
cc:
Subject: RE: No recommendation for how to make a resource unversioned
I agree.
> -----Original Message-----
> From: ietf-dav-versioning-request@w3.org
> [mailto:ietf-dav-versioning-request@w3.org]On Behalf Of Lisa Dusseault
> Sent: 04 September 2001 19:39
> To: DeltaV
> Subject: No recommendation for how to make a resource unversioned
>
>
>
> Given the controversy and the problems with every method that's been
> suggested to make a resource unversioned, I suggest that the DeltaV
draft
> should be silent on the question. That means striking the non-normative
> note on how clients might achieve this with COPY, DELETE, MOVE (a
> problematic approach because COPY creates a new resource, and thus
> initializes all sorts of new-resources stuff like default ACLs,
> creationdate, owner, access history).
>
> I think we'll need to deal with this issue in the future, but it can
wait.
>
> lisa
>
Received on Tuesday, 4 September 2001 19:18:14 UTC