Robin,
Below is an example of a BizTalk document. While this is a well formed XML
document, the only way that I was able to parse this structure was by
applying a style sheet and manipulating the data prior to running through
the parser.
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";>
<SOAP-ENV:Header>
<eps:endpoints SOAP-ENV:mustUnderstand="1"
xmlns:eps="http://schemas.biztalk.org/btf-2/endpoints";
xmlns:agr="http://www.trading-agreements.org/types/";>
<eps:to>
<eps:address xsi:type="agr:department">Book
Orders</eps:address>
</eps:to>
<eps:from>
<eps:address xsi:type="agr:organization">Book
Lovers</eps:address>
</eps:from>
</eps:endpoints>
<prop:properties SOAP-ENV:mustUnderstand="1"
xmlns:prop="http://schemas.biztalk.org/btf-2-0/properties";>
<prop:identity>uuid:74b9f5d0-33fb-4a81-b02b-5b760641c1d6</prop:identity>
<prop:sentAt>2000-05-14T03:00:00+08:00</prop:sentAt>
<prop:expiresAt>2000-05-15T04:00:00+08:00</prop:expiresAt>
<prop:topic>http://electrocommerce.org/purchase_order/</prop:topic>
</prop:properties>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<po:PurchaseOrder
xmlns:po="http://electrocommerce.org/purchase_order/";>
<po:Title>Essential BizTalk</po:Title>
</po:PurchaseOrder>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Brad
-----Original Message-----
From: Robin Anson [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 25, 2001 4:48 PM
To: [EMAIL PROTECTED]
Subject: Re: xmledi-group Digest for 24 Apr 2001 in hour 22:00
Brad, Rachel
Thanks for forwarding your interchange of ideas to the list, it was most
instructive.
One point that particularly concerned me was when Brad wrote:
>However, run a BizTalk document through Xerces, or whichever parser you
>like-validating or not-and it will choke, unless it is MS's BizTalk parser.
>A BizTalk message looks nothing like XML Version 1.0. Whereas an X12 850
and
>an 810 are clearly of the same standard.
Now I haven't looked closely at BizTalk DTDs and software, I follow the
development of XML/EDI very much at a high level. This comment though rings
major alarm bells to me. Could you, Brad, or someone else give me a more
detailed explanation of how BizTalk fails to look like XML Version 1.0 and
why a BizTalk message must be run through a BizTalk parser?
Robin Anson
eCommerce Consultant
PO Box 572, Eltham, Victoria, Australia 3095
email: [EMAIL PROTECTED]
tel: 04 1938 1900
Every exit is an entry somewhere.
- Tom Stoppard
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
