> Thanks, but I was looking for the exact use of extraRequestData in SRU
> and I can only find it for SRW. I'm lost on the relation between the
> x-prefix and extraResponseData.
I hadn't written it because there wasn't any agreement yet on it :)
"The profile designer should also include a parameter name beginning with
'x-' for use with SRU. The SRW/U protocol will never include an official
parameter with a name beginning with 'x-'. It is suggested, but not
required, that the parameter name be x- followed by an identifier for the
profile, followed by the name of the element. For example
'x-theo-onSearchFail' for <theo:onSearchFail>.
If the contents of the parameter is an XML structure, then the profile
designer should also specify how to encode this structure for SRU.
This may simply be to escape all of the special characters, but the
designer could also create a string encoding form with rules as to how
to generate the XML in much the same fashion as the relationship
between CQL and XCQL."
I don't think anyone disagrees with this, right? It's when the server
receives an unknown x- parameter and needs to echo the query back where
there's no firm consensus?
> Will the information from the above link be copied to the ZING
> webpages? I prefer to have only a single website to point
> our implementors to.
I expect so. I've incorporated Ray and Jannifer's changes back into my
own copy, so I can send them all to be posted easily enough.
,'/:. Dr Robert Sanderson ([log in to unmask])
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. Nebmedes: http://nebmedes.o-r-g.org:8000/
I L L U M I N A T I