- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 04 Feb 2005 21:27:28 +0100
- To: Lisa Dusseault <lisa@osafoundation.org>
- CC: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>, webdav <w3c-dist-auth@w3.org>
Lisa Dusseault wrote: > > Let's say the user creates resource 'myresume.doc' and puts it into a > collection 'http://example.org/~lisa/public/'. Further, let's say that > the public nature of this collection involves inherited permissions > which make the new document publicly readable. > > In step 2, the user does a BIND to also bind 'myresume.doc' into > 'http://example.org/~lisa/career/'. This new location is a private > folder, but let's assume that 'myresume.doc' remains publicly readable > because of its membership in the public folder. (This is where the BIND > language would come in but this behavior seems consistent with that.) > > In step 3, when the user does UNBIND and removes the binding into the > public collection, does the document remain public? That's the question > for which I'm looking for additional specification requirements. I guess all we can say is that we don't know, just like for MOVE, BIND and REBIND. But if this is the case for UNBIND, it also applies to DELETE. So should we state that? Best regards, Julian -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Friday, 4 February 2005 20:28:12 UTC