Mark,
This is very cool. When I was at TripleHop we did something very similar where
both query and results conformed to an XML Schema and we used XML over HTTP as
our main vehicle to do remote/federated searches with quick rendering with
stylesheets.
That however is the first piece of the puzzle. If you really want to go beyond
search (in the traditional sense) and be able to perform more complex
operations such as joines and iterations over items from the stream of XML
results you are getting you should consider implementing an XQuery Full-Text
engine with Lucene adopting the now standard XQuery language.
Here is the pointer to the working draft on the W3C working draft on XQuery 1.0
and XPath 2.0 Full-Text:
http://www.w3.org/TR/xquery-full-text/
Now I'm part of the task force editing this draft so your comments are very
much welcomed.
-- J.D.
--- Begin Message ---
After our recent discussions on this topic I've found some time to put
together a first cut of a SAX based Query parser, see here:
http://www.inperspective.com/lucene/LXQueryV0_1.zip
I've implemented just a few queries (Boolean, Term, FilteredQuery,
BoostingQuery ...) but other queries are fairly trivial to add.
At this stage I am more interested in feedback on parser design/approach
rather than trying to achieve complete coverage of all the Lucene Query
types or debating the choice of tag names.
Please see the readme.txt in the package for more details.
Cheers
Mark
___________________________________________________________
How much free photo storage do you get? Store your holiday
snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--- End Message ---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
