On Nov 18, 2004, at 11:51 PM, Michael Kay wrote:
You would get extra flexibility by issuing an "abstract query" from
your
stylesheet and using a URIResolver to convert it to a concrete eXist
query.
The "abstract query" might be a URI such as
http://query/?citekeys= + $citekeys
which you could parse in your URIResolver using the methods available
on the
java.net.URI class.
There are two issues with the above approach. First, I can't code in
Java (and barely get by with XSLT!). Second, and more importantly, I'd
like to keep this a purely XSLT solution (indeed, it's why the
query-over-http approach to begin with).
I had thought about maybe having one parameter option -- say called
"bibdb" -- with possible options like: existxmldb, sru (a url-based
query thing from the library world), flatfile, indocument, and another
called "bibcollection", which would set could set either the collection
in the xml db, or the directory on the file system.
Bruce
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--