W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2003

RE: Resolving RFC2518 issue 55 ("DISPLAYNAME")

From: Lisa Dusseault <lisa@xythos.com>
Date: Tue, 2 Dec 2003 11:16:08 -0800
To: "'Julian Reschke'" <julian.reschke@gmx.de>, "'Webdav WG'" <w3c-dist-auth@w3c.org>
Message-ID: <001301c3b908$bdeb7eb0$75c990c6@lisalap>

I haven't heard any objection to this, and I think it's a good idea,
so I'm going to add it to RFC2518bis as things stand.


> -----Original Message-----
> From: w3c-dist-auth-request@w3.org 
> [mailto:w3c-dist-auth-request@w3.org] On Behalf Of Julian Reschke
> Sent: Monday, November 24, 2003 8:29 AM
> To: 'Webdav WG'
> Subject: Resolving RFC2518 issue 55 ("DISPLAYNAME")
> Hi,
> looking at <http://www.webdav.org/wg/rfcdev/issues.htm>, the 
> discussion 
> back in 2000 
> <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
and the recent mailing list discussion 
I'd like to propose:

1) Deprecate DAV:displayname: clearly, we don't have interoperability 
(some servers treat it as a dead property with or without a default upon 
resource creation, some servers treat is as live property based on the 
last path segment). Clients can not rely on the property being present 
(mod_dav, SAP) or being writable (IIS, Sharemation?, Slide?).

2) As the RFC2518-stated intent was to provide a *description* of the 
resource (which clearly isn't useful when it's always the same as the 
last path segment after un-escaping), I'd propose to add a *new* dead 
property to RFC2518bis called DAV:description which covers this. All 
existing servers that support dead property (thus all RFC2518-compliant 
servers) will automatically support this property, thus it can safely 
added to RFC2518bis.

Regards, Julian

<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Tuesday, 2 December 2003 14:16:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:28 UTC