Writing a primer on how the message gets constructed, with/without CPA,
would set the stage for
defing the behavior for an MSI. This is a good idea, but I know I can not
volunteer at this point.
Scott Hinkelman, Senior Software Engineer
XML Industry Enablement
IBM e-business Standards Strategy
512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
, Fax: 512-838-1074
"Burdett, David" <> on 08/09/2001 10:50:39 AM
To: "'Collier, Timothy R'" <>, "'christopher
ferris'" <>
cc: , Martin W Sachs/Watson/IBM@IBMUS
Subject: RE: T2: ackRequested attribute in Via element
>>>It might be quite a job though, as it should include the BP, CPP/A, and
MSH teams.<<<
Good point. I have always thought that the MSH spec should be usable
WITHOUT
a CPP/A and BP, for example you might want to use it to communicate between
applications. So I think we really need two guides:
1. How to use ebXML Messaging
2. How to use ebXML Messaging, CPP/A and BP together.
... any volunteers ;)
David
-----Original Message-----
From: Collier, Timothy R [mailto:]
Sent: Tuesday, August 07, 2001 10:07 AM
To: 'christopher ferris'
Cc: ; Martin W Sachs
Subject: RE: T2: ackRequested attribute in Via element
A primer on how the message is constructed gets my vote. Especially, if
it
addresses how the security features are incorporated. It might be quite a
job though, as it should include the BP, CPP/A, and MSH teams.
Tim
-----Original Message-----
From: christopher ferris [mailto:]
Sent: Tuesday, August 07, 2001 7:33 AM
To: Martin W Sachs
Cc:
Subject: Re: T2: ackRequested attribute in Via element
<snip>
------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to:
------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to:
