Business Process Modeling Language: Difference between revisions

Revision as of 10:53, 17 February 2018

Latest revision as of 21:43, 3 January 2025

(7 intermediate revisions by 6 users not shown)

Line 1:

{{Cleanup rewrite|date=March 2023}}

'''Business Process Modeling Language''' ('''BPML''') is an [[XML]]-based language for [[business process modeling]].

It was maintained by the Business Process Management Initiative (BPMI) until June 2005 when BPMI and OMG ([[Object Management Group]]) announced the merger of their respective Businessbusiness Processprocess Management (BPM)management activities to form the ''Business Modeling and Integration Domain Task Force'' (BMI DTF)[http://www.omg.org/bpmn/]. It is deprecated since 2008. BPML was useful to [[Object Management Group|OMG]] in order to enrich [[Unified Modeling Language|UML]] with process notation{{Citation needed|date=January 2017}}.

BPML was useful to [[Object Management Group|OMG]] in order to enrich [[Unified Modeling Language|UML]] with process notation{{Citation needed|date=January 2017}}.

== History ==

BPML, a [[subset | superset]] of [[BPEL]], was implemented by early stage vendors, such as Intalio Inc., but incumbents such as [[IBM]] and [[Microsoft]] did not implement BPML in their existing workflow and integration engine implementations like ''[[BizTalk'']] or ''Websphere''[[WebSphere]]. They pushed for the simpler language BPEL.

In view of the lack of market acceptance, the BPMI dropped support of BPML in favor of BPEL4WS.<ref>{{cite book|last1=Havey|first1=Michael|title=Essential Business Process Modeling|date=August 2005|publisher=O'Reilly Media|isbn=978-0-596-00843-7|url=https://books.google.com/books?id=RFBHCaMtlfIC&pg=PA145&lpg=PA145&dqq=%22BPML%22+%22BPMI%22&sourcepg=bl&ots=wXbKP-lYF1&sig=7W96SdJ19LZTHubAfj-egjQH1JY&hl=en&sa=X&ved=0ahUKEwiAjpHy4cTRAhXIHxoKHQKzDkAQ6AEITjAI#v=onepage&q=%22BPML%22%20%22BPMI%22&f=falsePA145|accessdate=15 January 2017}}</ref><ref>{{cite web|last1=Gur|first1=N.|title=BPMN, BPEL, BPML and XPDL, an attempt to make some order in the business modeling jungle|url=https://blogs.sap.com/2007/01/03/bpmn-bpel-bpml-and-xpdl-an-attempt-to-make-some-order-in-the-business-modeling-jungle/|website=blogs.sap.com|accessdate=15 January 2017}}</ref>

Following the merger of BPMI and OMG, BPML willhas bebeen definitively deprecated in 2008, with OMG's adoption of [[BPDM]].<ref>{{cite web|last1=Dice|title=BPML|url=https://www.dice.com/skills/BPML.html|website=dice.com|accessdate=15 January 2017}}</ref>

== Application ==

BPML was designed as a formally complete language, able to model any process, and, via a BPMS ([[business process management]] system), deployed as an executable software process without generation of any software code. This is not possible with BPEL, since BPEL is not a complete process language. In practice BPEL is often used in conjunction with Java to fill in the "missing" semantics. In addition, BPEL is often tied to proprietary implementations of workflow or integration broker engines. Whereas, BPML was designed, and implemented, as a pure concurrent and distributed processing engine. It was designed to be semantically complete according to the [[Pi-calculus]] formal representation of computational processes.

It was designed to be semantically complete according to the [[Pi-calculus]] formal representation of computational processes.

BPEL and BPML are examples of a trend towards [[process-oriented programming]]. BPEL and BPML herald the concept of a BPMS as an IT capability for management of business processes, playing a role similar to a [[Relational database management system|RDBMS]] for business data.

== See also ==

* [[Business Process Execution Language]] (BPEL)

* [[Business Process Model and Notation]] (BPMN)

* [[Business process modeling]]

* [[workflowWorkflow]]

* [[workflowWorkflow engine]]

== References ==

Line 26 ⟶ 25:

[[Category:Workflow languages]]

[[Category:XML markup languages]]