W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > January to March 2003

RE: Issue with "Treatment of NULL Values"

From: Babich, Alan <ABabich@filenet.com>
Date: Wed, 15 Jan 2003 11:27:45 -0800
Message-ID: <FBEB6CC95F05FC49A9446D797F7ADE570B6A92@hq-ex2kpo1.filenet.fn.com>
To: "Julian Reschke" <julian.reschke@gmx.de>, <www-webdav-dasl@w3.org>
I believe Julian is correct.
 
Alan

	-----Original Message-----
	From: Julian Reschke [mailto:julian.reschke@gmx.de] 
	Sent: Wednesday, January 15, 2003 10:42 AM
	To: www-webdav-dasl@w3.org
	Subject: RE: Issue with "Treatment of NULL Values"
	
	
	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 <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 14:28:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:09 GMT