Re: [ebxml-dev] ebXML vs Web Services

>>Nazlihasri: I'm seeking for some opinions in comparing ebXML and Web Services. 
>>>>From my reading, some might claim that Web Services is more suitable 
>>for an ad-hoc business collaboration which means partners are more 
>>loosely coupled. For example there is no standard on how to cope with 
>>potential failure conditions. Technically speaking, I do think that 
>>Web Services providers can offer tight coupling services as well. 
>>
mm1: Some would say that the important point is if these technologies 
can support a SOA.  For example, in ebBP (aka ebXML BPSS), the 
technology is neutral to service routines but can support the use of web 
services through the in-work OperationMapping constructs.  ebBP 
maintains the loosely-coupled nature inherent in the ebXML architecture 
[1].   Others also would advocate that with the modularization changes 
anticipated in ebMS v3.0, that the differences in the technologies are 
converging.  Thanks. On your question on ad-hoc business collaboration, 
that is the exception rather than the rule. Because of the obligations 
and responsibilities involved,  I don't see that changing in the 
near-term. That is not to say, the enterprise processes that support 
business collaboration or external events that could 'feed into' a 
business collaboration can not be dynamic in nature. Thanks.


[1] The loose coupling is a key tenet of SOA. That, as you indicated, 
does not preclude tighter coupling but it is not a constraint.