One thing to do is to use base64 encoding. It you're validating against Schema, you could type it as xs:string or xs:base64Binary. I'm guessing it should be embedded in a CDATA section - I don't know whether base64 would contain any "<" or other characters that might mess up the parse.
---------------------------------------------------------------------------- ---- Mark Feblowitz [t] 617.715.7231 XML Architect [f] 617.495.0188 Frictionless Commerce Incorporated [e] [EMAIL PROTECTED] 400 Technology Square, 9th Floor Cambridge, MA 02139 http://www.frictionless.com -----Original Message----- From: Cliff Rowley [mailto:[EMAIL PROTECTED] Sent: Monday, April 29, 2002 11:26 AM To: [EMAIL PROTECTED] Subject: Re: AW: unparsed data in XML << File: ATT31742.txt >> << File: ATT31743.txt >> >Then I need to do two steps for encode and decode. I�d like to transport >this exactly so as is. I trued it with NDATA but it doesn�t work. Perharp I >didn`t use that right. Are you familiar with that? If I remember correctly (it happens sometimes), there was a discussion a little while back on one of the Xerces lists on this subject. I can't recall what the solution was - or if the original poster even shared it, but I do recall talk of UUENCODE, and I remember someone saying that there is currently no standard for binary transfer using XML. Have you tried searching the archives? Sorry I can't be much use. Cliff Rowley Tel: +44 (0) 1206 514263 Email: [EMAIL PROTECTED] Web: http://www.onsea.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
