You're right. I was a little bit too hasty. Sorry.
I agree that when another response format is requested there are still
different recordSchemas possible, so a new parameter is needed. In fact
we did use such a parameter in a previous version of our SRU service for
server side XSLT transformations.
Van: SRU (Search and Retrieve Via URL) Implementors [mailto:[log in to unmask]]
Namens Ray Denenberg, Library of Congress
Verzonden: vrijdag 15 juni 2007 15:27
Aan: [log in to unmask]
Onderwerp: Re: June 18-19 meeting topics.... RSS
> From: "Theo van Veen" <[log in to unmask]>
> I know that there are also wishes to return Json as SRU response. It
> however possible to create this possible by an intermediate service
> effecting SRU and this might even be better. On the other hand it
> increase acceptance of SRU if the requested record schema's would
> responses like RSS, Json etc. without the SRU-envelope.
> I'm not offended either by allowing record schema's to cause SRU
> return non-SRU responses. I would however discourage the introduction
> another parameter if there is already a parameter (recordSchema) that
> use for this purpose.
Setting aside for the moment the other issues raised by this message, I
want to point out that recordSchema CANNOT be used for this purpose.