OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: MIME Envelope Optional?


Bob,

It depends upon what you mean by ebXML "payload". I like to distinguish
between business payload (content specific to the business process, that
is sourced externally from the MSH) and "payload" that is generated by the
MSH itself for its own purposes.

Cheers,

Chris

"Miller, Robert (GXS)" wrote:
> 
> Chris,
> 
> As I read the argument for disallowing any payload in the SOAP-ENV:Body, it
> was that then the ebXML data would always be in the same place.  This flowed
> from a concern that one might place the ebXML payload in EITHER the
> SOAP-ENV:Body or in an attachment.  As you note below, ebXML payloads
> containing acknowledgements etc would still show up in SOAP-ENV:Body.  So
> where is the eloquence in all that?  Eloquence is always placing the ebXML
> payload (if one exists) in SOAP-ENV:Body.  That is, eloquence in sense you
> use it is brought to the table by my proposal, not by the proposal to place
> the (user) ebXML payload in an attachment!
> 
> Cheers,
>         Bob
> 
> -----Original Message-----
> From: christopher ferris [mailto:chris.ferris@east.sun.com]
> Sent: Tuesday, February 27, 2001 1:16 PM
> To: Miller, Robert (GXS)
> Cc: ebXML Transport Mailing List
> Subject: Re: MIME Envelope Optional?
> 
> "Miller, Robert (GXS)" wrote:
> >
> > I did not here any discussion in Vancouver whether the MIME envelope might
> > be optional in cases where the message payload contained only XML syntax.
> > It seems logical to me that the MIME envelope would be optional in such
> > cases.
> >
> > Cheers,
> >         Bob
> >
> > ------------------------------------------------------------------
> > To unsubscribe from this elist send a message with the single word
> > "unsubscribe" in the body to: ebxml-transport-request@lists.ebxml.org
> 
> If we disallow any "payload" in the SOAP-ENV:Body element, as has been
> suggested and eloquently argued, then this would never be the case.
> 
> However, an acknowledgment, error (SOAP:Fault) or StatusData message
> which have no business "payload" *could* be sent absent the MIME
> packaging. Now the question becomes, is this what we want?
> 
> Cheers,
> 
> Chris
> 
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: ebxml-transport-request@lists.ebxml.org
begin:vcard 
n:Ferris;Christopher 
tel;work:781-442-3063
x-mozilla-html:FALSE
org:Sun Microsystems, Inc;XML Technology Development
adr:;;One Network Drive;Burlington;Ma;01824-0903;USA
version:2.1
email;internet:chris.ferris@east.Sun.COM
title:Sr. Staff Engineer
x-mozilla-cpt:;0
fn:Christopher Ferris
end:vcard


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC