Lists Home |
Date Index |
- From: "Don Park" <email@example.com>
- To: <firstname.lastname@example.org>
- Date: Wed, 2 Sep 1998 06:39:57 -0700
>Interesting approach -- sort of the inverse of XSL -- but I suspect that in
>order to be useful it won't be so simple. In its simplest form, you'd only
>return the elements that you provided, serving only as an existence test,
>returning no other information. QBE at a minimum requires wildcards, and
>it would be interesting to find an appropriate set of wildcards.
At the simple level, fuzzy match of attribute values and text contents
should work pretty well. Any missing attribute or elements can be treated
At the complex level, scripting language for matching should work pretty
Here is an example:
<order department="electronics" salesperson="bob">
quantity > 10
Above XBE should return all order records for sales made at the electronics
department by Bob where product description 'contains' the string "CD-ROM"
and quantity exceeds 10. The scripting language refers to context elements
and attributes by name (order.department for attribute).
There are obvious rough spots but I think it has promises. Whether or not I
will invest time and effort into XBE is another question of course.
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/
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)