Date: Fri, 25 Aug 2000 17:42:22 -0400 (EDT) Message-Id: <200008252142.RAA05212@tantalum.atria.com> From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com> To: ietf-dav-versioning@w3.org Subject: Re: postcondition for PUT From: "Boris Bokowski/OTT/OTI" <Boris_Bokowski@oti.com> First question, regarding 5.4: "If the PUT creates a new resource, it is server defined whether it is under version control." If a server chooses to put files under version control automatically, what is the effect of a PUT? Does this create a new history resource, a new version (implicit CHECKIN...) in that history resource, and a version selector at the request URL which selects the new version? Yes, it would just appear as if the server had automatically applied a VERSION-CONTROL request following the creation of the new resource. A subsequent PROPPATCH, issued by a client before issuing VERSION-CONTROL, would fail in this case. Therefore, a client would have to issue a PROPFIND on the newly created resource first, to find out whether it is a version selector or not. The same applies to versioned collections (12.6) Yes, unless the server automatically sets the DAV:auto-version property for the new version selector, in which case the PROPPATCH would create a new revision (assuming it was a PROPPATCH to a dead property ... it is up to the server what happens to a live property). Cheers, Geoff