Date:         Fri, 13 Feb 2004 18:18:44 +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:      xScanClause
Comments: To: "Z39.50 Next-Generation Initiative" <[log in to unmask]>
Content-Type: TEXT/PLAIN; charset=US-ASCII

There is some potential confusion about xScanClause currently.

xQuery in searchRetrieveResponse/echoedRequest  contains XCQL
 elements searchClause or triple.

xScanClause in scanResponse/echoedRequest -is- a searchClause, and hence
contains index, relation and term.

Eg:
Per schema:
<srw:xScanClause>
  <xcql:index>dc.title</xcql:index>
  <xcql:relation>=</xcql:relation>
  <xcql:term>fish</xcql:term>
</srw:xScanClause>

I would expect, ala xQuery:
<srw:xScanClause>
  <xcql:searchClause>
     ...
  </xcql:searchClause>
</srw:xScanClause>


My server, implemented without reference to the schema (as it didn't
exist at the time), embeds a searchClause into xScanClause.
I, personally, find this confusing that xQuery contains a searchClause
(or triple) but xScanClause contains index and crew, but will fix my
implementation to the schema.

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