BPEL: Difference between revisions
No edit summary |
m (Reverted edits by Nicole80 (Talk) to last revision by Daniel K. Schneider) |
||
Line 17: | Line 17: | ||
* [http://en.wikipedia.org/wiki/Business_Process_Execution_Language Business Process Execution Language] (Wikipedia) | * [http://en.wikipedia.org/wiki/Business_Process_Execution_Language Business Process Execution Language] (Wikipedia) | ||
== Bibliography == | == Bibliography == |
Revision as of 21:40, 5 May 2010
Definition
Business Process Execution Language (BPEL), short for Web Services Business Process Execution Language (WS-BPEL) is an executable language for specifying interactions with Web Services. (Wikipedia)
“Web service interactions can be described in two ways. Executable business processes model actual behavior of a participant in a business interaction. Abstract business processes are partially specified processes that are not intended to be executed. An Abstract Process may hide some of the required concrete operational details. Abstract Processes serve a descriptive role, with more than one possible use case, including observable behavior and process template. WS-BPEL is meant to be used to model the behavior of both Executable and Abstract Processes.(Business Process Execution Language, retrieved jan 5 2009).”
Tools
See BPMN for a visual design tool.
In education
Karampiperis and Sampson argued that BPEL (or rather a graphical representation language) could be used to design learning designs/ pedagogical scenarios that then can be compiled into IMS Learning Design Level A Representations.
Links
- Business Process Execution Language (Wikipedia)
Bibliography
- P. Karampiperis and D.Sampson: "Towards a Common Graphical Language for Learning Flows: Transforming BPEL to IMS Learning Design Level A Representations", in Proc. of the 7th IEEE International Conference on Advanced Learning Technologies (ICALT 2007), ISBN: 9780769529165, pp. 798-800, Niigata, Japan, IEEE Computer Society, July 2007.