- From: Lisa Dusseault <lisa@osafoundation.org>
- Date: Thu, 3 Feb 2005 16:08:41 -0800
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>, webdav <w3c-dist-auth@w3.org>
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. Lisa On Feb 3, 2005, at 2:57 PM, Julian Reschke wrote: > Lisa Dusseault wrote: >> This is fine with me for BIND, and I think the same is also true of >> REBIND and UNBIND. > > How is UNBIND relevant here? > > Best regards, Julian > > > -- > <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Friday, 4 February 2005 00:09:06 UTC