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: Lisa Dusseault <lisa@xythos.com>
Date: Fri, 25 Jan 2002 15:44:42 -0800
To: "Babich, Alan" <ABabich@filenet.com>, <www-webdav-dasl@w3.org>
Message-ID: <HPELJFCBPHIPBEJDHKGKEEOGDEAA.lisa@xythos.com>
It could always be me...
As I recall, the DASL spec for QSD says that every searchable property must
be listed in the QSD info.  But what if custom properties are searchable?
There is an unlimited number of possible custom properties, putting them all
in the QSD is infeasible.

But it's not quite right to leave them out of the QSD either.  One server
might allow substring matches of custom properties, another server might
only allow exact match searching, a third might not allow searching on
custom properties at all.  It would be nice if each of these three servers
could advertise how they support searching custom properties.

I didn't see a way in DASL QSD to do this.

Lisa

> -----Original Message-----
> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Babich, Alan
> Sent: Friday, January 25, 2002 3:17 PM
> To: www-webdav-dasl@w3.org
> Subject: RE: Call for Participation: new internet draft for WebDAV
> SEARCH method
>
>
> Lisa:
>
> The search rules are the exactly same whether the properties are
> listed in a
> Query Schema or not. If you don't have a Query Schema, you can search just
> fine if you guess the name of a property to search on, or if you have some
> other way to know the name of a property. There is nothing different about
> the search, whether or not there is QSD.
>
> Perhaps I'm being dense today, but I completely don't get it as
> to how "QSD
> could become a *lot* more manageable ...". Perhaps you would try to
> enlighten me. Thanks.
>
> Alan Babich
>
> -----Original Message-----
> From: Lisa Dusseault [mailto:lisa@xythos.com]
> Sent: Friday, January 25, 2002 3:00 PM
> To: Babich, Alan; 'Julian Reschke'; www-webdav-dasl@w3.org
> Subject: RE: Call for Participation: new internet draft for WebDAV
> SEARCH method
>
>
>
> > That is not the same thing as saying that every repository would be
> > organized enough to provide a query schema. Providing QSD has to be
> > optional. Document management systems could easily provide access to the
> > data dictionary they already have. But other repositories, e.g., file
> > systems, might not have a centralized query schema.
>
> You're right, but it's a little worse than that.  Systems where custom
> metadata could be anywhere (e.g. *any* dav system should support custom
> props) can't provide a complete query schema.
>
> However, QSD could become a *lot* more manageable with the simple
> feature of
> allowing the server to specify their behaviour as follows:  "for any
> property not otherwise mentioned in the QS, searching follows these
> rules..."
>
> Then only the special cases (live properties which are known to
> be integers,
> for example) would have to be in the QSD.
>
> Lisa
>
Received on Friday, 25 January 2002 18:46:19 GMT

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