- From: Brian Korver <briank@xythos.com>
- Date: Thu, 9 Dec 2004 17:09:12 -0800
- To: 'webdav' <w3c-dist-auth@w3.org>
Julian, Ok, we know your vote for how live properties interact with bindings (as if we didn't know already ;-), but I think that in combination with Jim's point underscores the need for explicit text in the bind spec. -brian briank@xythos.com On Dec 8, 2004, at 5:57 AM, Julian Reschke wrote: > > 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 > >
Received on Friday, 10 December 2004 01:09:44 UTC