Date:         Fri, 21 Jun 2002 11:06:03 -0400
Reply-To:     "Z39.50 Next-Generation Initiative" <[log in to unmask]>
Sender:       "Z39.50 Next-Generation Initiative" <[log in to unmask]>
From:         Ray Denenberg <[log in to unmask]>
Organization: Library Of Congress
Subject:      Re: sort parameter
Comments: To: "Z39.50 Next-Generation Initiative" <[log in to unmask]>
Content-Type: text/plain; charset=us-ascii

"LeVan,Ralph" wrote:

> They can still specify the record schema, even if they ask explicitly for
> zero records.  So use that schema parm.

I'm worried about making this too complicated, in particular, overloading the
schema parameter.  On the other hand, I certainly agree that the schema
parameter should rule, when records are requested.  Which would mean the
attribute would occur when no records are requested, and should be omitted when
not (also complicated).

But the record schema parameter is going to have to be described something
like:
Omitted if no records wanted, unless sort parameter is supplied and one or more
keys is an element path. If records are wanted (requestedRecords is supplied),
or sort parameter is supplied and one or more keys is an element path, and if
this parameter is omitted, then the server is to use its default record schema.

I'd like to hear what others think.  This could be simplified if we agree to a
single sort key type.

--Ray