Print

---

> In the past I have found that this query is legal and very ugly:
>  prox and/or <dc:title>and or</dc:title> and or

Here's the equally ugly XCQL output from my parser:

<triple xmlns="http://www.loc.gov/zing/cql/xcql/">
   <boolean>
     <value>and</value>
     <modifiers>
       <modifier>
         <type>or</type>
         <comparison>&lt;</comparison>
         <value>dc:title</value>
       </modifier>
     </modifiers>
   </boolean>
   <leftOperand>
     <searchClause>
       <index>cql.serverchoice</index>
       <relation>
         <value>scr</value>
       </relation>
       <term>prox</term>
     </searchClause>
   </leftOperand>
   <rightOperand>
     <searchClause>
       <prefixes>
         <prefix>
           <name></name>
           <identifier>and</identifier>
         </prefix>
       </prefixes>
       <index>or</index>
       <relation>
         <value>&lt;</value>
         <modifiers>
           <modifier>
             <type>dc:title</type>
             <comparison>&gt;</comparison>
             <value>and</value>
           </modifier>
         </modifiers>
       </relation>
       <term>or</term>
     </searchClause>
   </rightOperand>
</triple>


       ,'/:.          Dr Robert Sanderson ([log in to unmask])
     ,'-/::::.        http://www.o-r-g.org/~azaroth/
   ,'--/::(@)::.      Dept. of Computer Science, Room 805
,'---/::::::::::.    University of Liverpool
____/:::::::::::::.  L5R Shop: http://www.cardsnotwords.com/
I L L U M I N A T I