> I don't think we disagree that much.


> >All we need to do is tell the client that the term is part of a thesaurus,
> >which thesaurus, and a link to that thesaurus (be it an index in the same
> >database, or a separate database).  Then we have Mike's ZThes in both
> The "termId" as I call it, will in my proposal be used to "link to the
> thesaurus". Perhaps the only difference in our view is that I would like
> the termId to be used as parameter in SRU rather than creating a http
> link.

Okay, I must have misinterpreted your comments about the client not
needing to know about a second database. How does the client get to the
thesaurus via termId?  Surely it needs to know the location?

Assuming that the information comes back on the term, rather than in
Explain as I concede that a single term or index may reference multiple
thesauri, the way I would see it happening is:

  <value>Tolkien, John</value>
  <displayTerm>J.R.R. Tolkien</displayTerm>
      <useTerm>Tolkien, J.R.R.</useTerm>

This tells the client which thesaurus the term is from.  Then if the
client has a local copy it can use it.  It gives the location of a server
which has that thesaurus available, which may be the originating server,
and it gives the term to use when searching using ZThes.

From there you can retrieve all of the information about Tolkien. If EAC
is available, then possibly including his bibliography and biographical
information as well as dates and all the normal bits and pieces.
If it was a subject from the LCSH, then you'd retrieve all the information
about alternate, broader, narrower terms and what not.


      ,'/:.          Rob Sanderson ([log in to unmask])
  ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    Twin Cathedrals:  telnet: 7777
____/:::::::::::::.              WWW: