> >The response will have the XSLT URL in it, which in turn has the database
> >URL.
> The stylesheet URL isn't always present and sometimes the stylesheet URL is
> relative to the Database URI - therefore not an entirely perfect answer to
> the problem.

If it's important that the URL is always there, you could define an
extension that returns the database URL and request it.

> >When trying to do sophisticated things with unsophisticated tools, it's
> >only to be expected that there will be problems.  Thin clients (aka dumb

> I know - it's just mildly irritating that the lack of a simple piece of
> functionality prevents them working.

It prevents saving all the information in one place, certainly. But that's
not something which the protocol addresses in much the same way that
Z39.50 doesn't include connection details in a presentResponse.

Rob

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