ebBP 12/30/2005: BPMN Diagram Descriptive Update (open)

[Monica J Martin <Monica.Martin@Sun.COM>]

As of today, I've received one additional comment on the BPMN diagrams 
proposed in draft and a suggestion to add annotations. I'll pend until 
Tuesday on any final changes.  In the interim, I'd appreciate if the 
team would think about these descriptive changes to Section 3.4.9.1 and 
annotations for the existing diagrams. Note, as of now we've used in 
Figure 7 and 8 an Inclusive Gateway, end messages (showing only one path 
is taken on a series of possible sequence flows) and allowed one Message 
Flow to occur.  We're still discussing whether the zero or all paths may 
be taken assumptions in BPMN for Inclusive Gateway are appropriate for 
what we wish to communicate.

Section 3.4.9.1
Change from:
Figure 7 presents an example of Document Flows and Business Signals 
within a Business Transaction. This Business Transaction has been 
represented in BPMN. As indicated for Figure 6, the BPMN v1.0 could be 
extended while changes to support Business Collaboration are considered 
by the BPMN team in the Object Management Group (OMG).  In a Business 
Collaboration, several possible (expected) paths may come into a 
Gateway. In BPMN v1.0, only Sequence Flows can come in or out of 
Gateways necessitating a slightly different representation of the 
possible paths for the Response shown. In order to represent those 
possible paths on an XOR gateway, the diagram in Figure 7 (and the 
upcoming Figure 8) would have to be extended from BPMN v1.0 to allow for 
multiple Message Flows in or out of a Gateway (where the standard BPMN 
uses Sequence Flow). In lieu of possible changes being considered by the 
BPMN team for BPMN v1.0 within OMG, the diagram has utilized 
intermediate messages with the actual business message providing the 
Response. In addition, business messages have been represented by a 
thicker blue message flow, while signals are green message flows.  These 
are allowed extensions in BPMN v1.0.

Change to:
Figure 7 presents an example of Document Flows and Business Signals 
within a Business Transaction. This Business Transaction has been 
represented in BPMN. As indicated for Figure 6, the BPMN v1.0 could be 
extended while changes to support Business Collaboration are considered 
by the BPMN team in the Object Management Group (OMG).  In a Business 
Collaboration, several possible (expected) paths of business messages 
may come into a Gateway. In BPMN v1.0, only Sequence Flows are allowed 
in to or out of Gateways necessitating a slightly different 
representation of the possible paths for the Response shown. In order to 
represent those possible paths on an OR gateway, the diagram in Figure 7 
(and the upcoming Figure 8) would have to be extended from BPMN v1.0 to 
allow for multiple business Message Flows in or out of a Gateway (where 
the standard BPMN uses Sequence Flow). In lieu of possible changes being 
considered by the BPMN team for BPMN v1.0 within OMG, the Response is 
visualized as:

    * An Inclusive OR where many paths could occur.
    * End event messages show those potential sequence paths (Sequence
      flows).
    * Conditions determine which path is taken.
    * On the path taken, the actual business message providing the
      Response is returned to the Requesting Business Activity.

In addition, business messages have been represented by a thicker blue 
message flow, while signals are green message flows.  These are allowed 
extensions in BPMN v1.0. Currently, business signals or messages are not 
differentiated in a standard way in this notation. Annotations describe 
what may occur on the Response (such as Order Cancel, Order Change or 
Order Accept).

===
Diagrams updated with annotations (see attached).

Section 3.4.9.8
Currently, no descriptive changes proposed. Questions outstanding to 
BPMN team.
Diagrams updated with annotations (see attached).

ebxmlbp-2.0.1-pr-updated-bpmn-flows-123005.zip