RE: Issue with "Treatment of NULL Values"

My rationale is it would leave things more open for future extensions in the
2xx space. But, it's not a strong opinion.

- Jim

> -----Original Message-----
> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Julian Reschke
> Sent: Tuesday, January 14, 2003 9:37 AM
> To: Jim Whitehead; www-webdav-dasl@w3.org
> Subject: RE: Issue with "Treatment of NULL Values"
>
>
>
> I thought about that as well, but I really couldn't find a case where a
> property would be present and would be reported with a 2xx status
> that isn't
> actually 200.
>
> --
> <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 Jim Whitehead
> > Sent: Tuesday, January 14, 2003 6:24 PM
> > To: www-webdav-dasl@w3.org
> > Subject: RE: Issue with "Treatment of NULL Values"
> >
> >
> >
> > > 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 Tuesday, 14 January 2003 12:48:07 UTC