>> It certainly will be impossible given a URL as a start. Now, well need
>> URL + PROTOCOL.
> At present we only need one URL since both SRU and SRW must support the
> GET form of Explain (even though there is a SOAP based form).
Well, that too. :) And no one has proposed that this be dropped, so there
is (still) no issue.
Quoth the base profile:
"The Explain record describing the server must be available at the base
URL and also via the 'explain' operation."
> My proposal to extend the Explain service to return multiple Explain
> records was to maintain this single URL for bootstrap even if we added
> SRU POST and even if the SRU (GET/POST) and SRW services were on
> different endpoints (which may in turn be on different endpoints to the
> single bootstrap URL).
What you're describing is commonly called a Registry ;) and is both
unnecessary and unhelpful in this case. If you have 3 end points for
version 1.0 and 3 end points for version 1.1 and 3 end points for version
1.2, then you have to return 9 different but practically identical explain
records? Uhhh... No thanks. If you have different end points, each end
point has its own explain operation which does exactly what it says on the
tin. It explains how to use this particular service.
Again, if you want links to related services of any protocol at any URL,
put them in <links>.
,'/:. Dr Robert Sanderson ([log in to unmask])
,'--/::(@)::. 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