[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] If BPEL is the answer, what is the question?
Steven, I'm o-o-o on dial-up - so will check those links Tuesday. From the titles though - this seems to be yet more focus at the deep technical level rather than the implementation planning level. If we cannot understand who should be using these technologies, and what purpose they will serve for them - we can hardly expect much buy-in. The 'build it and they will come' story is worn out in post-1999 corporate IT - they need to understand the value proposition. 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<
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]