[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] implicite links of the runtime engine (was: Implicit <sequence> macro)
The point about the Pi emulation of data was clearly rhetorical ;-) The key point I was trying to make was that minimality is in the eye of the beholder, and does not lead to a unique result. The merger of the block structured and graph oriented control regimes is actually a unique and useful characteristic of BPEL in that it puts to bed a perennial debate in this area. I think the cost in feature overhead is pretty minimal for that benefit. Satish -----Original Message----- From: Assaf Arkin [mailto:arkin@intalio.com] Sent: Wednesday, June 25, 2003 8:57 AM To: Maciej Szefler Cc: Satish Thatte; Ron Ten-Hove; Eckenfels. Bernd; wsbpel@lists.oasis-open.org Subject: Re: [wsbpel] implicite links of the runtime engine (was: Implicit <sequence> macro) Well said. arkin Maciej Szefler wrote: >There is a big difference in degree between emulation of sequence with flow and emulation of XML using pi calculus. For one BPEL does not express pi, so to do so would involve expanding the spec (whereas eliminating sequence reduces the spec). Second, for the purposes of business processes, where the notion of structured data is integral to the definition, it is only natural to not have to model XML data using a slew of pi processes: doing so would unnecessarily complicate the implementation of the BPEL engines and make direct reporting against process state impossible (while eliminating sequence marginally simplifies implementation, and has no impact on direct reporting capabilities). This philosophy amounts to "as simple as possible, keeping in mind the problem domain". > >-Maciej Szefler > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]