- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 20 Mar 2006 15:20:27 +0100
- To: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
- CC: Jason Crawford <nn683849@smallcue.com>, w3c-dist-auth@w3.org
Geoffrey M Clemm wrote: > > I agree that Jason's suggested rewording is clearer. > > Cheers, > Geoff OK; new proposed text; based on Jason's text and proposal: 15.2. displayname Property Name: displayname Purpose: Provides a name for the resource that is suitable for presentation to a user. Value: Any text. Protected: SHOULD NOT be protected. Note that servers implementing [RFC2518] might have made this a protected property as this is a new requirement. COPY/MOVE behaviour: This property value SHOULD be preserved in COPY and MOVE operations. Description: The property contains a description of the resource that is suitable for presentation to a user. This property is defined on the resource, and hence SHOULD have the same value independent of the Request-URI used to retrieve it (thus computing this property based on the Request-URI is deprecated). While generic clients will be able to use the value of the DAV: displayname property for display to end users, client UI designers must understand that the method for identifying resources is still the URL. In particular, there is no guarantee whatsoever that the values of this property are unique for each member of a collection. Also note that changes to DAV:displayname do not issue moves or copies to the server, but simply change a piece of meta-data on the individual resource. <!ELEMENT displayname (#PCDATA) >
Received on Monday, 20 March 2006 14:21:59 UTC