Date:         Tue, 17 Feb 2004 11:58:12 +0000
Reply-To:     "Z39.50 Next-Generation Initiative" <[log in to unmask]>
Sender:       "Z39.50 Next-Generation Initiative" <[log in to unmask]>
From:         Robert Sanderson <[log in to unmask]>
Subject:      RecordSchema
Comments: To: "Z39.50 Next-Generation Initiative" <[log in to unmask]>
Comments: cc: [log in to unmask]
In-Reply-To:  <[log in to unmask]>
Content-Type: TEXT/PLAIN; charset=US-ASCII

> We will echo the record schema exactly as it has been requested. But
> there may be a difference between  info:srw/schema/1/dc-v1.1 with
> maximumRecords=1 and info:srw/schema/1/dc-v1.1 with maximumRcords>1
> while both are exactly conform the same schema.

Let's be clear about what the spec says, and why.

In searchRetrieveRequest, the recordSchema parameter can be either the
full URI or the explain advertised short name.  This is for the same
reason as other short names.
(service.html)

In searchRetrieveResponse/records/record, the recordSchema field must be
the URI, otherwise a client is forced to know the mapping from explain to
process the response.
(records.html)

In searchRetrieveResponse/echoedRequest the recordSchema field should be
identical to that which was received on the request.
(sru.html)

BTW the example on the sru page is wrong, the element should be
<echoedSearchRetrieveRequest> not just <echoedRequest> ala 1.0.


Rob


--
      ,'/:.          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