bind issue: bind-vs-hierarchy

[Julian Reschke <[e-mail]>]

Julian Reschke wrote:
> ...
> 2) bind-vs-hierarchy 
> (<http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-issues.html#issue.bind-vs-hierarchy>) 
> ...

I have added the following note to the introduction of Section 2:

-- snip --
       Note: the collection model described herein is not compatible with
       systems in which resources inherit properties based solely on the
       access path, as the ability to create additional bindings will
       cause a single resource to appear as member of several different
       collections at the same time.
-- snip --

Also, the section about the WebDAV ACL spec has been rewritten to make 
clear that it doesn't have a problem with multiple bindings; it now reads:

-- snip --
10.  Relationship to WebDAV Access Control Protocol

    Note that the WebDAV Access Control Protocol has been designed for
    compatibility with systems that allow multiple URIs to map to the
    same resource (see [RFC3744], Section 5):

       ...Access control properties (especially DAV:acl and DAV:
       inherited-acl-set) are defined on the resource identified by the
       Request-URI of a PROPFIND request.  A direct consequence is that
       if the resource is accessible via multiple URI, the value of
       access control properties is the same across these URI. ...

    Furthermore, note that BIND and REBIND behave the same as MOVE with
    respect to the DAV:acl property (see [RFC3744], Section 7.3).
-- snip --

Diffs, as usually, at 
<http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-latest.html> 
and <http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-issues.html>.

Feedback appreciated,

Julian