Re: [regrep] ebXML and Web Services: Is this a fair assessment?

[Duane Nickull <duane@yellowdragonsoft.com>]

I think that was Davdi that wrote that, not me ;-)

Chiusano Joseph wrote:

>Thanks Duane - that's much better!!!
>
>Joe
>
>David RR Webber wrote:
>  
>
>>Joe,
>>
>>Errr, no!
>>
>>I'd say something along these lines:
>>
>> (1) The ebXML initiative began while Web Services was in its infancy;
>>      therefore two models were developed around the foundation of
>>      XML and SOAP messaging.  The ebXML approach is collaboration-centric
>>      (CPA) while the web service model is point-services-centric (WSDL).
>>      While this distinction continues today significant blurring has taken
>>place
>>      leading to the ability to deploy both technologies in tandem.
>>
>>  (2) For example, the emerging OASIS Web Services Business Process
>>   Execution Language (WS BPEL) is centered on the Web Services hierarchy
>>   presented in WSDL (portType, operation, message, etc.) and networks of
>>   interacting services, while the ebXML  Business Process Schema
>>Specification (BPSS)
>>   is centered on the concept of business process patterns, workflows and
>>transactions between
>>   business collaboration partners.  Therefore BPSS is suited to defining
>>industry-wide patterns
>>   for collaborations, while BPEL is suited to discreet point services that
>>may be part of those
>>   collaborations.
>>
>>  (3) The ebXML Messaging Service (ebMS) specification, whose foundation is
>>SOAP,
>>        is now also being adapted to support WSDL interfacing as well.
>>
>>  (4) Many of the ebXML specifications have also incorporated Web
>>       Services mechanisms - one example is the inclusion of
>>       a WSDL definitions for the SOAP interface to ebXML Registry.
>>
>>Thanks, DW.
>>
>>----- Original Message -----
>>From: "Chiusano Joseph" <chiusano_joseph@bah.com>
>>To: <regrep@lists.oasis-open.org>
>>Sent: Tuesday, October 07, 2003 4:39 PM
>>Subject: [regrep] ebXML and Web Services: Is this a fair assessment?
>>
>>    
>>
>>>All,
>>>
>>>I was not involved in ebXML until after May 2001 (although I monitered
>>>various listservs prior to that), so I don't have as solid an
>>>appreciation as I would like regarding ebXML and Web Services. Can
>>>someone please tell me if the following is a fair assessment - my
>>>intention is to be as accurate as possible, and not controversial (I've
>>>numbered the points below for easy referral):
>>>
>>>(1) The ebXML initiative began before Web Services became prominent;
>>>therefore there are many aspects of ebXML that do not utilize Web
>>>Services to as full a potential as they may have otherwise.
>>>
>>>(2) For example, the emerging OASIS Web Services Business Process
>>>Execution Language (WS BPEL) is centered on the Web Services hierarchy
>>>presented in WSDL (portType, operation, message, etc.) while the ebXML
>>>Business Process Schema Specification (BPSS) is centered on the concept
>>>of "business documents".
>>>
>>>(3) An exception to this is the ebXML Messaging Service (ebMS)
>>>specification, whose foundation is SOAP.
>>>
>>>(4) However, many of the ebXML specifications have incorporated Web
>>>Services since their original version - one example is the inclusion of
>>>a SOAP interface to ebXML Registry in its 2.0 version.
>>>
>>>Thanks,
>>>Joe
>>>      
>>>
>>----------------------------------------------------------------------------
>>----
>>
>>    
>>
>>>To unsubscribe from this mailing list (and be removed from the roster of
>>>      
>>>
>>the OASIS TC), go to
>>http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php.
>>
>>To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php.
>>

-- 
***************************************************
Yellow Dragon Software - http://www.yellowdragonsoft.com
Web Services & ebXML Messaging / Registry Downloads
UN/CEFACT eBusiness Architecture/ ebXMl Technical Architecture 
Phone:   +1 (604) 738-1051 - Canada: Pacific Standard Time
Direct:  +1 (604) 726-3329