[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: No Subject
As to the reply vis the other OASIS spec's - I'm afraid this is not the kind of positive thinking I am trying to foster. OASIS has many good technologies and the smart thinking is to leverage and extend, not conflict. Again - customers are looking at investing in OASIS standards - so why would they buy something where the developers cannot even agree? Notice that BUSINESS CONTEXT is a recurring thread across all the OASIS specifications - so one simple question that needs answering is - how does BPEL support the business context mechanism that the rest of the OASIS TC's are now looking to support? BTW - BPSS and BPEL are IMHO potentially very complimentary if you understand the solution spaces they are aimed at. I've used BPSS - and it works great - and is easy for its audience to understand and deploy. I've also created some tools for BPML. I'm looking for those same answers for BPEL - to understand who will see this as a key tool and what new ground this is looking to cover? Which comes back to the key point - if we don't know who the audience is, what the value proposition is and what the solution architecture is - then other people are not going to be able to answer those questions for us, right? Cheers, DW. ================================================ Message text written by "Steven Forgey" >David, I'm not sure what level of context you want, but here are 3 links that provide an introductory context (business, technical, competitive) to BPEL: * Web Services Orchestration: a review of emerging technologies, tools, and standards (2003-02-03): http://devresource.hp.com/drc/technical_white_papers/WSOrch/WSOrchestration .pdf * BPEL4WS - Composition and Orchestration (2002-12-09): http:// <http://www.infosys.tuwien.ac.at/Teaching/Courses/IntAppl/PDF/BPEL4WS.pdf> www.infosys.tuwien.ac.at/Teaching/Courses/IntAppl/PDF/BPEL4WS.pdf * Commentary and news on the competitive shifts taking place around BPEL standardization: http://www.stencilgroup.com/ideas/briefs/2003/04/politics/ With respect to other OASIS efforts, IMO the primary potential conflict is between the BPEL family of specs and the ebXML family of specs: * BPEL vs. BPSS * DIME with WS-Attachments vs. SOAP with Attachments * WS-Coordination & WS-Transaction vs. BTP * UDDI vs. ebXML Registry Steven Forgey Business Engineer SeeBeyond< --=_alternative 0052372285256D24_= Content-Type: text/html; charset="us-ascii" <br><font size=2 face="sans-serif">In deference to the Oasis process, we need to ask that discussions of the specification not start before the first meeting of the technical committee (May 16). The document was provided early to give everyone a chance to become familiar with it. It won't be officially submitted until our first conference call. </font> <p><font size=2 face="sans-serif">Please "hold that thought". ;-) <br> Thanks.<br> Regards, Diane<br> IBM Dynamic e-business Technologies<br> drj@us.ibm.com<br> (919)254-7221 or 8-444-7221, Mobile: 919-624-5123<br> </font> <p> <br> <br> <table width=100%> <tr valign=top> <td> <td><font size=1 face="sans-serif"><b>David RR Webber - XML ebusiness <Gnosis_@compuserve.com></b></font> <p><font size=1 face="sans-serif">05/11/2003 05:46 PM</font> <br> <td><font size=1 face="Arial"> </font> <br><font size=1 face="sans-serif"> To: "Steven Forgey" <SForgey@SeeBeyond.com></font> <br><font size=1 face="sans-serif"> cc: "John Evdemon" <jevdemon@microsoft.com>, Diane Jordan/Raleigh/IBM@IBMUS, "BPEL TC" <wsbpel@lists.oasis-open.org></font> <br><font size=1 face="sans-serif"> Subject: RE: [wsbpel] If BPEL is the answer, what is the question?</font> <br></table> <br> <br> <br><font size=2 face="Courier New">Steven,<br> <br> I'm o-o-o on dial-up - so will check those links Tuesday.<br> <br>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]