RE: [ebxml-msg] AS4 issues

["Pim van der Eijk" <pvde@sonnenglanz.net>]

AS4 is not sufficient for those current users of ebMS 2.0 (possibly looking for an upgrade path to a newer protocol) that are using ebMS more in an SOA style, including (asynchronous) request/response exchanges, than in a pure One Way document exchange style.  (BTW the START protocol submitted to the BDX TC has the same limitation as AS4. START follows the CEN BII concept of business transactions, which are all One Way.).  

I also see your point.  To support Two Way,  a conformant MSH only needs to enable some control over presence and value of RefToMessageId element.  This is trivial for any ebMS 3.0 implementation. So perhaps it will be implemented even though AS4 doesn't use it,because supporting it is so easy. We'll have to see what parts of ebMS 3.0 vendors will implement.   But AS4 is likely to be the first profile of ebMS 3.0 that vendors will support, and for some, it may be the only profile, so that's why I raised the issue. 

-----Original Message-----

At any rate, I think we should resist the temptation to expand the AS4 profile. ebMS3 profiles are available with additional functionality. And using AS4 for cloud interconnect (for example) may benefit from having a mix that spans ebMS3 core (part 1) functionality and selected ebMS 3 advanced (part 2) functionality. Or so it seems to me.