Skip
repetitive navigational links
L-Soft  -  Home of  the  LISTSERV  mailing list  manager LISTSERV(R) 14.5
Skip repetitive navigational links
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (June 2002)Back to main ZNG pageJoin or leave ZNGReplyPost a new messageSearchProportional fontNon-proportional fontLog in
Date:         Fri, 21 Jun 2002 10:13:45 -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: > Sort doesn't make any sense in the first case, and should be accompanied by > a request for records in the second case. I don't understand, for either case. I thought the primary reason people want a sort parameter is to specify a priori the order of records in the result set. Why wouldn't that apply in the case where a query is submitted, but no records are desired in that response? Secondarily, I thought we decided that we could supply a sort parameter and a result set id (no query) to mean sort existing result set. Why wouldn't that alone be a meaningful request (without asking for records)? --Ray


Back to: Top of message | Previous page | Main ZNG page

LISTSERV.LOC.GOV CataList email list search Powered by LISTSERV email list manager