> Envelope-to: [log in to unmask]
> Delivery-date: Tue, 29 Jun 2004 22:45:28 +0200
> Content-Type: text/plain; charset="us-ascii"
> Content-class: urn:content-classes:message
> X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
> X-MS-Has-Attach:
> X-MS-TNEF-Correlator:
> Thread-Topic: CQL binary terms (was Scan)
> Thread-Index: AcReFtnwHbgzOnUTT1Ovi8Iy7uY+SwAAUgcw
> Date: Tue, 29 Jun 2004 21:35:56 +0100
> Reply-To: "Z39.50 Next-Generation Initiative" <[log in to unmask]>
> Sender: "Z39.50 Next-Generation Initiative" <[log in to unmask]>
> From: "Matthew J. Dovey" <[log in to unmask]>
> Comments: To: "Z39.50 Next-Generation Initiative" <[log in to unmask]>
> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on bagel.indedata.dk
> X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham
>       version=2.63
> X-Spam-Level:
>
>
>
> > -----Original Message-----
> > From: Z39.50 Next-Generation Initiative [mailto:[log in to unmask]]
> > On Behalf Of Mike Taylor
> > Sent: Tuesday, June 29, 2004 9:21 PM
> > To: [log in to unmask]
> > Subject: Re: CQL binary terms (was Scan)
> >
> > > Date: Tue, 29 Jun 2004 17:15:38 +0100
> > > From: Robert Sanderson <[log in to unmask]>
> > >
> > > > I'm not too sure about this list either - but we definitely need
> > > > base64Binary and hexBinary (these being the two XML
> > Schema types for
> > > > binary information in XML) and possibly quotedPrintable.
> > >
> > > So, to put it all together:
> > >
> > > cql.base64
> > > cql.hex
> > > cql.quotedPrintable
> > > cql.content-type=""
> >
> > More or less.  I'm not familiar with hex, and would like to see a
> > brief justification for it before giving my daughter's hand.
>
> Because it is one of the two binary encoding types supported by XML
> Schema, so would be one of the two encodings used if you were passing
> binary data as the content of a XML element (as you might in fact be
> doing in an XML record schema that needs to have binary content), and
> would be supported by most XML toolkits.

OK, sounds good to me.  Is it just the obvious two-chars-per-byte
thing where "foo" is encoded as "666f6f"?

 _/|_    _______________________________________________________________
/o ) \/  Mike Taylor  <[log in to unmask]>  http://www.miketaylor.org.uk
)_v__/\  "A satisfied customer ...  We should have him stuffed" --
         Basil Fawlty, "Fawlty Towers"

--
Listen to free demos of soundtrack music for film, TV and radio
        http://www.pipedreaming.org.uk/soundtrack/