> Date: Thu, 11 Mar 2004 09:34:28 +0100
> From: Janifer Gatenby <[log in to unmask]>
>
>> When used with SRU, the prefix 'c30_rt-' should be put before any
>> parameter name
>
> I don't understand this.  The extension only applies to response and
> the response data in SRU is identical to SRW?

Hi Janifer,

In SRW and SRU, servers may include extensions in their responses only
in response to the corresponding extensions in the requests.  So in
order to get the "currentTerm" extraTermdata out of an SRU server, you
need to include an explicit request in the SRU request URL.

That request parameter must begin with "X-", like all extension
parameters (right, Rob?  You didn't say this in your document), and
thereafter Rob's spec says that parameter names associated with this
extension should begin with "c30_rt-", as a sort of crude namespaceing
mechanism to prevent this extension colliding with another
independently invented one from elsewhere.  (It took me a while to get
it, but I think this is a cryptic way of saying "Cheshire version 3.0,
Requested Term extension" ... at first, I thought it was line noise
:-)

As it happens, there's only one element in this namespace,
"markRequestedTerm", so putting it all together, the SRU request
parameter needs to be
        X-c30_rt-markRequestedTerm

(Rob's example has
        c3o_rt-mark_RequestedTerm
which I think is wrong for two reasons: the missing "X-" prefix and
the extraneous underscore.)

 _/|_    _______________________________________________________________
/o ) \/  Mike Taylor  <[log in to unmask]>  http://www.miketaylor.org.uk
)_v__/\  "The passage is through; not over, not by, not around but
         through" -- Cherrie Moraga

--
Listen to my wife's new CD of kids' music, _Child's Play_, at
        http://www.pipedreaming.org.uk/childsplay/