I was referring to the VERSION-CONTROL bullet in Peter's original message, i.e. VERSION-CONTROL with a version argument (which always creates a new version-controlled resource). For VERSION-CONTROL without a version argument (which never creates a new version-controlled resource), you are correct that it does not affect the state of the parent collection. Cheers, Geoff Julian wrote on 09/05/2003 05:54:12 PM: > > > From: w3c-dist-auth-request@w3.org > > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Geoffrey M Clemm > > Sent: Friday, September 05, 2003 8:12 PM > > To: 'w3c-dist-auth@w3c.org' > > Subject: Re: DAV:getlastmodified of collections > > > > > > > > Also, MOVE (on the collections containing the source and destination). > > Also, COPY (on the collections containing any new resources > > created by the > > COPY). > > One correction: VERSION-CONTROL affects the state of the collection > > containing the resource being created, not on the containing workspace > > (unless the workspace is the collection containing the resource). > > Hm. Does it affect the state of a parent collection if it (the collection) > isn't version-controlled? In this case the state of the collection IMHO > doesn't (or doesn't need to) change. > > > ... > > JulianReceived on Friday, 5 September 2003 18:03:09 UTC
This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:28 UTC