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

RE: issue: unprecise wording in appendix A (three-valued-logic)

From: Jim Whitehead <ejw@cse.ucsc.edu>
Date: Tue, 14 Jan 2003 09:18:16 -0800
To: <www-webdav-dasl@w3.org>
Message-ID: <AMEPKEBLDJJCCDEJHAMICEPHGCAA.ejw@cse.ucsc.edu>

I think it would help interoperability to add a sentence (or 1-2 short
examples) that stated how DASL implementations should treat
empty/"undefined" DAV properties.

Frankly, I can see myself not getting this right...

- Jim

> -----Original Message-----
> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Julian Reschke
> Sent: Tuesday, October 22, 2002 7:20 AM
> To: www-webdav-dasl@w3.org
> Subject: issue: unprecise wording in appendix A (three-valued-logic)
>
>
>
> In [1] the current draft says:
>
> "If a property in the current resource under scan has not been set to a
> value (either because the property is not defined for the current
> resource,
> or because it is null for the current resource), then the value of that
> property is undefined for the resource under scan."
>
> However, WebDAV properties never have a "null" value. They may be empty,
> such as
>
> 	<foo xmlns="bar" />
>
> or
>
> 	<foo xmlns="bar"></foo>
>
> but that's just a string value with length 0.
>
> Proposal: just remove that sentence.
>
>
>
>
> [1]
> <http://greenbytes.de/tech/webdav/draft-reschke-webdav-search-late
st.html#rf
c.section.A.p.3>
--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Tuesday, 14 January 2003 12:22:32 GMT

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