Dr Robert Sanderson wrote:
> On Tue, 21 Dec 2004, Adam Dickmeiss wrote:
>> Mike Taylor wrote:
>>>> One explain record represents one service interface to one database,
>>>> one database and any number of services which access it. It's already
>>> I agree.
>> What is it that that makes multiple serverInfo so complicated?
> <serverInfo protocol="SRW/U">
> <serverInfo protocol="FTP">
> Would be a perfectly legal, if semantically impossible, Zeerex record.
>> serverInfo is ortoghonal to to indexInfo, schemaInfo etc.. And Z39.50
>> supports CQL.. So that's the deal?
> Zeerex supports more than just Z39.50 and SRW/U, and it has always taken
> the position that one record represents one type of interface to one
Except for SRW/U?
>> I'd like to see how I publish multiple transports on a single URL (YAZ
>> deliberately try to support both SRW and SRU at the same URL, for
> I don't see why you think this is a problem?
If you can announce the two transports SRW / SRU in one protocol
attribute, that solves it. But, IMHO not an elegant solution.
> In the Z39.50 service you publish the record for the Z39.50 service in
> IR-Explain---1. In the SRW/SRU you publish the SRW/U record at the base
Yep. So two explain documents for a SRW/SRU/Z39.50 server that features
exactly the same resource behind it (Z39.50 supports CQL+XML), due to
> Or you have a registry that has all of the records in it.
I don't. So no need to mention that again :-)
> ,'/:. Dr Robert Sanderson ([log in to unmask])
> ,'-/::::. http://www.o-r-g.org/~azaroth/
> ,'--/::(@)::. Dept. of Computer Science, Room 805
> ,'---/::::::::::. University of Liverpool
> ____/:::::::::::::. L5R Shop: http://www.cardsnotwords.com/
> I L L U M I N A T I