W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2003

RE: DAV:displayname with versions

From: Julian Reschke <julian.reschke@greenbytes.de>
Date: Mon, 11 Aug 2003 20:28:42 +0200
To: "Lisa Dusseault" <lisa@xythos.com>, "'Geoffrey M Clemm'" <geoffrey.clemm@us.ibm.com>, <ietf-dav-versioning@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCKECKICAA.julian.reschke@greenbytes.de>

> From: ietf-dav-versioning-request@w3.org
> [mailto:ietf-dav-versioning-request@w3.org]On Behalf Of Lisa Dusseault
> Sent: Monday, August 11, 2003 7:10 PM
> To: 'Geoffrey M Clemm'; ietf-dav-versioning@w3.org
> Subject: RE: DAV:displayname with versions
>
>
>
> Sure, every version must have the displayname property so you can get it
> with PROPFIND.  However, no specification requires that to be either

Nope. DAV:displayname is an *optional* property:

"If present, the property contains a description of the resource that is
suitable for presentation to a user."

It's perfectly OK not to have it when it was never explicitly set.

> writable or protected on a version, so on some servers it won't
> be writable.

Yes, but the specification still says "...contains a description of the
resource that is suitable for presentation to a user...". So no matter how a
server implements it's protected DAV:displayname property, it still must
suit this purpose. Just copying the last path component of the request URL
(that's what IIS does) doesn't satisfy this requirement.

> Also no specification requires it to be either static or dynamic, so it's
> possible on some servers that the property would be protected, and it
would
> change whenever the value on the VCR changed.

Yes (unfortunately).

> ...

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Monday, 11 August 2003 14:30:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:44 GMT