- From: Howard N Smith <howard.smith@ontology.org>
- Date: Mon, 08 Dec 2003 13:20:24 +0000
- To: public-ws-chor@w3.org
>IMO the BPM space should consist of a stack of specifications, each targeting a well defined problem, In much the same way we approach the WS space. Rather than doing >everything inside WSDL or SOAP, we have specialized specifications that deal with specific issues, like security, reliable messaging, addressing, coordination, policies, portals, >management, etc. Similarly, we need to look at the BPM space as a space allowing for the existence of multiple specifications, and at specifications like BPEL/BPML as specialized >specifications in this space. They are important, but they are part of a larger picture. Trying to solve all problems in one specification, in my opinion, leads to less capable >specifications. Building a stack allows you target specific problems with the best possible tool, and combine all these tools into a powerful toolbox. +1 BPMS consolidates all the pieces along the lines of a set of explicit standards. It certainly could not be done in one specification. --- New Book - Business Process Management: The Third Wave www.bpm3.com Howard Smith/CSC/BPMI.org cell +44 7711 594 494 (operates worldwide, dial UK) office +44 20 8660 1963
Received on Monday, 8 December 2003 08:30:26 UTC