- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 15 Jan 2003 19:42:10 +0100
- To: <www-webdav-dasl@w3.org>
- Message-ID: <JIEGINCHMLABHJBIGKBCGEDJGDAA.julian.reschke@gmx.de>
No, it shouldn't. An empty string is a defined property value. NULLs sort *before* defined values, including empty strings. Julian -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 -----Original Message----- From: www-webdav-dasl-request@w3.org [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Elias Sinderson Sent: Wednesday, January 15, 2003 7:29 PM To: www-webdav-dasl@w3.org Subject: Re: Issue with "Treatment of NULL Values" Hi, Should we also mention how empty properties are treated? A PROPFIND on an empty property would yield a 200 response (empty string), and should sort as NULL. Elias Jim Whitehead wrote: The draft currently says: "If a PROPFIND for a property value would yield a 404 or 403 response for that property, then that property is considered NULL." Shouldn't this say: "If a PROPFIND for a property value would yield any non-200 (OK) response for that property, then that property is considered NULL." Perhaps this should be 2xx. - Jim
Received on Wednesday, 15 January 2003 13:42:58 UTC