---
title: "6 Additional Information"
chapter: "6 Additional Information"
source: "OMG BPMN 2.0.2 — formal/2013-12-09"
pages: "16-18"
---

> 6 Additional Information · páginas 16-18 · [índice](README.md)


<a id="sec-6"></a>
# 6 Additional Information


<a id="sec-6-1"></a>
## 6.1 Conventions


The sub clause introduces the conventions used in this document. This includes (text) notational conventions and notations for schema components. Also included are designated namespace definitions.


<a id="sec-6-1-1"></a>
### 6.1.1 Typographical and Linguistic Conventions and Style


This International Standard incorporates the following conventions:


- The keywords “MUST,” “MUST NOT,” “REQUIRED,” “SHALL,” “MUST NOT,” “SHOULD,” “SHOULD NOT,” “RECOMMENDED,” “MAY,” and “OPTIONAL” in this document are to be interpreted as described in RFC-2119.

- A term is a word or phrase that has a special meaning. When a term is defined, the term name is highlighted in bold typeface.

- A reference to another definition, sub clause, or specification is highlighted with underlined typeface and provides a link to the relevant location in this International Standard.

- A reference to a graphical element is highlighted with a bold, capitalized word and will be presented with the Arial font (e.g., **Sub-Process**).

- A reference to a non-graphical element or BPMN concept is highlighted by being italicized and will be presented with the Times New Roman font (e.g., *token*).

- A reference to an attribute or model association will be presented with the Courier New font (e.g., Expression).

- A reference to a WSBPEL element, attribute, or construct is highlighted with an italic lower-case word, usually preceded by the word “WSBPEL” and will be presented with the Courier New font (e.g., WSBPEL *pick*).

- Non-normative examples are set off in boxes and accompanied by a brief explanation.

- XML and pseudo code is highlighted with mono-spaced typeface. Different font colors MAY be used to highlight the different components of the XML code.

- The cardinality of any content part is specified using the following operators: <none> — exactly once [0..1] — 0 or 1 [0..*] — 0 or more [1..*] — 1 or more

- Attributes separated by | and grouped within { and } — alternative values <value> — default value <type> — the type of the attribute


<a id="sec-6-1-2"></a>
### 6.1.2 Abbreviations


The following abbreviations are used throughout:


| This abbreviation | Refers to |
| --- | --- |
| WSBPEL | Web Services Business Process Execution Language (see WSBPEL). This abbreviation refers specifically to version 2.0 of this International Standard. |
| WSDL | Web Service Description Language (see WSDL). This abbreviation refers specifically to the W3C Technical Note, 15 March 2001, but is intended to support future versions of the WSDL specification. |


<a id="sec-6-2"></a>
## 6.2 Structure of this Document


Clause 1 discusses the scope of the document and provides a summary of the elements introduced in subsequent clauses of the document. Clause 7 introduces the **BPMN** Core that includes basic **BPMN** elements needed for constructing various **Business Processes**, including **collaborations**, *orchestration* **Processes** and **Choreographies**. Elements needed for modeling of **Collaborations**, *orchestration* **Processes**, **Conversations**, and **Choreographies** are introduced in Clauses 8, 9, 10 and 11, respectively. Clause 13 introduces the **BPMN** visual diagram model. Clause 14 defines the execution semantics for **Process** *orchestrations* in **BPMN 2.0**. Clause 14 discusses a mapping of a **BPMN** model to WS-BPEL that is derived by analyzing the **BPMN** objects and the relationships between these objects. Exchange formats and an XSLT transformation between them are provided in Clause 15.


<a id="sec-6-3"></a>
## 6.3 Acknowledgments


<a id="sec-submitting-organizations"></a>
#### Submitting Organizations


The following companies are formal submitting members of OMG:


- Axway

- International Business Machines

- MEGA International

- Oracle

- SAP AG

- Unisys


<a id="sec-supporting-organizations"></a>
#### Supporting Organizations


The following organizations support this International Standard but are not formal submitters:


- Accenture

- Adaptive

- BizAgi

- Bruce Silver Associates

- Capgemini

- Enterprise Agility

- France Telecom

- IDS Scheer

- Intalio

- Metastorm

- Model Driven Solutions

- Nortel

- Red Hat Software

- Software AG

- TIBCO Software

- Vangent


<a id="sec-special-acknowledgments"></a>
#### Special Acknowledgments


The following persons were members of the core teams that contributed to the content of this International Standard: Anurag Aggarwal, Mike Amend, Sylvain Astier, Alistair Barros, Rob Bartel, Mariano Benitez, Conrad Bock, Gary Brown, Justin Brunt, John Bulles, Martin Chapman, Fred Cummins, Rouven Day, Maged Elaasar, David Frankel, Denis Gagné, John Hall, Reiner Hille-Doering, Dave Ings, Pablo Irassar, Oliver Kieselbach, Matthias Kloppmann, Jana Koehler, Frank Michael Kraft, Tammo van Lessen, Frank Leymann, Antoine Lonjon, Sumeet Malhotra, Falko Menge, Jeff Mischkinsky, Dale Moberg, Alex Moffat, Ralf Mueller, Sjir Nijssen, Karsten Ploesser, Pete Rivett, Michael Rowley, Bernd Ruecker, Tom Rutt, Suzette Samoojh, Robert Shapiro, Vishal Saxena, Scott Schanel, Axel Scheithauer, Bruce Silver, Meera Srinivasan, Antoine Toulme, Ivana Trickovic, Hagen Voelzer, Franz Weber, Andrea Westerinen and Stephen A. White. In addition, the following persons contributed valuable ideas and feedback that improved the content and the quality of this International Standard: im Amsden, Mariano Belaunde, Peter Carlson, Cory Casanave, Michele Chinosi, Manoj Das, Robert Lario, Sumeet Malhotra, Henk de Man, David Marston, Neal McWhorter, Edita Mileviciene, Vadim Pevzner, Pete Rivett, Jesus Sanchez, Markus Schacher, Sebastian Stein, and Prasad Yendluri.