RE: Manifest Element - Where located?

["Miller, Robert (GXS)" <Robert.Miller@gxs.ge.com>]

I think the ebXML model results in at most 'one (eb)XML message' in the
payload!  An ebXML message may include non-ebXML attachments, and need not
include an ebXML message. 

Of course, that ebXML message may imbed pointers to attachments, which it
might want to do if there was significant need to 'escape' 'special
characters'.  BTW, if the ebXML essage is a conforming XML message, moving
it to a separate MIME body part does not resolve the 'special character'
problem.  If identified as an XML message (so that it will be passed to an
XML parser) it must still conform to XML syntax rules. 

Bob Miller

-----Original Message-----
From: ian.c.jones@bt.com [mailto:ian.c.jones@bt.com]
Sent: Monday, February 26, 2001 12:12 PM
To: ebxml-transport@lists.ebxml.org
Subject: RE: Manifest Element - Where located? - 2


All,

	Here is the corrected version of the text I just e-mailed.  Hit send
before running the spell check sorry!

	I am concerned about having "real" payload in the body as we then
have inconsistent handling of payloads.  So, if you have one XML message you
COULD put it in the body provided you do not need any special characters
etc. BUT if you need special characters or more than one message what do you
do? Put them all in attachments, put the first in the body, etc.  IMHO we
should Keep It Simple, all payloads in the attachments as they are not for
the MSH it just needs to pass them on and leave all the MESH "stuff" in the
SOAP header and body as needed.

Ian Jones


Ian Jones
Email: ian.c.jones@bt.com  
 


------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-transport-request@lists.ebxml.org