Eric Johnson wrote:
My take is that displayname is a "live" server property, not a dead one, though.
That means, as I read it, that it is up to the server to do whatever the heck it wants with it.
The "default" value of the display name would seem to be the name of the file decoded from the URL into standard Unicode (and then re-encoded into the proper character set for XML). On a MOVE, then, if the destination indicates a new file name for the last portion of the URL at the destination, then having a "displayname" using the name at the old location seems _really_ odd to me.
That's right. If the server maintains the display name, it should maintain it while copy/move too.
If you want a "displayname" that has the properties you describe - that is, it doesn't change on move/copy - why not just add a dead property to the resource in question that is specific to your application?
I don't use displayname as description. But the RFC does. The point I want to say was that clients should not use displayname to build uri's.
Stefan
-- +--------------------------------------------+ | | | Stefan L�tzkendorf | | | | Institut f�r Terminologie und | | angewandte Wissensforschung (itaw) GmbH | | | | Sitz: Georgenstr. 35 | | 10117 Berlin | | Tel.: ++49 (030) 30 86 20 84 | | Fax : ++49 (030) 30 86 20 87 | | | +--------------------------------------------+
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
