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: Babich, Alan <ABabich@filenet.com>
Date: Fri, 25 Jan 2002 15:17:13 -0800
Message-ID: <C3AF5E329E21D2119C4C00805F6FF58F08FE5A3E@hq-expo2.filenet.com>
To: www-webdav-dasl@w3.org

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

Then only the special cases (live properties which are known to be integers,
for example) would have to be in the QSD.

Received on Friday, 25 January 2002 18:22:02 UTC

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