Lists Home |
Date Index |
- From: Dan Brickley <Daniel.Brickley@bristol.ac.uk>
- To: 'XML Dev' <firstname.lastname@example.org>
- Date: Sun, 14 Mar 1999 10:12:54 +0000 (GMT)
On Sat, 13 Mar 1999, Avi Rappoport wrote:
> I have a consulting client who is shipping around Boolean queries.
> The documents are not XML, but they are using XML for data transfer
> between the search form and the back-end search engine, and in the
> results listings. We would like to replace their proprietary query
> language (it looks like AltaVista's + and - system) with XML markup,
> because it seems cleaner and could be parsed with the rest of the
> I have read all 66 position papers at the QL '98 site
> <http://www.w3.org/TandS/QL/QL98/pp.html> and think that the proposed
> languages, such as XQL or XML-Query, are overkill for our needs. Do
> we have to go the whole query route or is there something lightweight
> that might handle it for us?
There's a different between using XML to ship queries around, and
querying XML. The majority of the XML-oriented position papers at the
Boston QL workshop were concerned with the latter, ie. finding things
within a real or hypothetical XML document or document set. For these to
be useful for your application, you'd need to 'pretend' that the
database queried by your back-end search engine was an XML document or
document collection. Which as you say might be overkill.
I'm not aware of anything lightweight that'd do what's needed here.
Maybe there's a document out there somewhere that describes the
Altavista-esque +/- format adopted by the various engines objectively
enough for it to be useful to ship queries around marked up as being of
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)