> A reason for not putting the database information into the xslt is to make
> the xslt independent of the SRU target. One script accesses a lot of
> Where each database is a separate URL and thus probably a separate process,
> it is very easy to include the database information in the response.

Then process the Explain record for it?  But as I said in response to
Theo, this /is/ hard when you don't control the state of the client, or
the server, or the protocol.

Otherwise we might as well include the whole ZeeRex file in echoedRequest.
(Which is certainly possible, but not a route I'd like to go down)

As far as unrequested stylesheet processing instructions go, I think we
should explicitly say that they're allowed, but may be ignored (because we
can't prevent clients from ignoring them anyway, and we don't want to
force all clients to implement all of XSL)

Rob

--
      ,'/:.          Dr Robert Sanderson ([log in to unmask])
    ,'-/::::.        http://www.o-r-g.org/~azaroth/
  ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    Nebmedes:  telnet: nebmedes.o-r-g.org 7777
____/:::::::::::::.                WWW: http://nebmedes.o-r-g.org:8000/
I L L U M I N A T I