Re: [Bug 3] Bindings draft should specify if all properties MUST have same value on all bindings

Jim Whitehead wrote:
> Seems to me we already have an example of a live property that varies
> depending on the binding used to access it -- DAV:displayname. On servers
> where this just reflects the binding name of the resource, it seems like it
> would vary depending on the binding used to access it.

This is a known issue with servers that indeed implement DAV:displayname 
that way; for instance discussed in 
<http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-issues.html#bind_properties>.

My position is, that a server that implements DAV:displayname as 
computed property based on the binding name is simply poorly 
implemented; DAV:displayname is defined to be "...a description of the 
resource that is suitable for presentation to a user" 
(<http://greenbytes.de/tech/webdav/rfc2518.html#PROPERTY_displayname>), 
not a repetition of the last path segment.

Apache/moddav and many other serves get this right; and I expect the 
same will apply to any server that actually supports multiple bindings.

Best regards, Julian


-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760