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

RE: QSD

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 28 Jan 2002 10:04:04 +0100
To: <www-webdav-dasl@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCEEFIDOAA.julian.reschke@gmx.de>
> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Jim Davis
> Sent: Sunday, January 27, 2002 10:45 PM
> To: www-webdav-dasl@w3.org
> Subject: RE: QSD
>
>
> At 11:30 AM 1/27/02 +0100, Julian Reschke wrote:
> >> From: www-webdav-dasl-request@w3.org
> >> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Jim Davis
>
> >> You are right to observe that QSD for basicsearch does not do this.
> >> I think that's okay.  basic search is, well, basic, and so is
> >> QSD.  I think
> >> it would be okay to release DASL with QSD as it is, that is,
> >> without making
> >> it any more powerful.
> >
> >Again: this is not true for the current draft.
>
> Julian, I do not understand what you mean.  What is not true?
>
> ...

Seems I didn't quote enough. I left out:

>>That said, the use case you propose is, I think, the ability for a server
>>to disclose how it handles properties (you call them "custom  properties",
>>but I am not sure if you mean live or dead, not that it matters much) *as
a
>>whole*, as opposed to on an individual basis.

That's what I added.
Received on Monday, 28 January 2002 04:04:41 GMT

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