Clients should not rely on the question mark to be the and of base-url,
not in SRU, not in OpenURL and not in any other service requiering a
base-url, as there may be implementation specific reasons to construct
your own base-url's. The request part starts with the first pararmeter
and not with "?". The base-url in Zeerex should imply everything that
the server defines as base-url and this should imply either "?" or "&"
and in some cases it may even be "/".
I do not see what such a restriction would be good for. In my view we
have:
url=baseurl + request
and not
url=baseurl + "?" + request
Theo
>>> [log in to unmask] 3-12-03 12:10:24 >>>
> I don't think we should care about local extensions: the use of the
> x-prefix is a local responsibility. We have to keep in mind that
some
> "local extensions" are just part of the base-url. For example:
> http://krait.kb.nl/cgi-zoek/srw.pl?
> and
> http://krait.kb.nl/cgi-zoek/srw.pl?flg=sru&
> are considered two different services. The parameter flg=sru is not
> considered a local extension parameter but a part of the base-url
> pointing to another SRU-service.
I disagree. The base URL for the service is anything up to the ?
After
the ? are parameters for the service. The reason being that for SRW,
you
would post to ... srw.pl not srw.pl?flg=sru. In the explain document
you
would put srw.pl not srw.pl?flg=sru, as (a) that's what ZeeRex says has
to
go there and (b) clients will expect to append ?(params) onto the end.
> Where can I find the current specs for 1.1? I have deleted too many
My copy is at:
http://srw.o-r-g.org/new/
--
,'/:. 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
|