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

RE: Call for Participation: new internet draft for WebDAV SEARCH method

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sat, 26 Jan 2002 12:08:38 +0100
To: <www-webdav-dasl@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCAEEGDOAA.julian.reschke@gmx.de>
> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Lisa Dusseault
> Sent: Saturday, January 26, 2002 2:26 AM
> To: Babich, Alan; www-webdav-dasl@w3.org
> Subject: RE: Call for Participation: new internet draft for WebDAV
> SEARCH method
> I already understood how a server might specify like, eq or no searching
> support for a given, specified property.  I still don't see how DASL QSD
> would show whether a server supports like, eq or no search support for
> *unspecified* properties.
> You say the server could advertise each custom property, I say that's
> infeasible.

I agree with Lisa, because this means that on a non-schema constrained
search scope, a server would first have to visit every single resource to
discover every dead property.

Even if it did that, two resources may have the same dead property with a
different datatype (!).

Besides, a search client can benefit from knowing whether the property list
is exhaustive. If it isn't, it *may* offer a way to specify "arbitrary"
properties, while it could block that otherwise.

This being said: the issue is old and I think the current draft already
covers this. So please don't argue about what a previous draft said about
it -- refer to the current one.

Received on Saturday, 26 January 2002 06:09:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:22:42 UTC