Issue 14761: Section 14.4 [BPEL mapping] Missing intermediate send event; mapping of participant ref (bpmn2-rtf)
Source: International Business Machines (Mr. Matthias Kloppmann, matthias.kloppmann(at)de.ibm.com)
Nature: Revision
Severity: Significant
Summary: Type: Technical

Description of issue:
1. The spec misses the mapping for intermediate message send events
2. The spec misses a mapping for send/receive events and tasks where the other party is specified not by a service-ref, but by a message flow to another participant.

Proposal:
1. Include that mapping into spec (see Visio)
2. Introduce text describing how BPEL partnerLink is derived from either serviceRef or participantRef; use [serviceRef | participantRef] or similar notation as abbreviation.

Resolution: 
Revised Text: 
Actions taken:
November 20, 2009: received issue
Discussion: 
The FTF agrees that there is a problem that needs fixing, but did not agree on a resolution. This is not an implementation issue so it is deferred to a future RTF.
Disposition: Deferred
End of Annotations:=====
s is issue # 14761

[OMG 14761] Section 14.4 [BPEL mapping] Missing intermediate send event; mapping of participant ref

##Source: IBM (Matthias Kloppmann, matthias-kloppmann@de.ibm.com)
##Original Issue: http://www.osoa.org/jira/browse/BPMN-344
##Original Info: (Severity: Significant - Nature: Revision)

Revision of Spec: Beta 1

Section(s) of Spec:
 
Raised by: Matthias Kloppmann

Sub-Team responsible: BPEL mapping

Type: Technical

Description of issue:
1. The spec misses the mapping for intermediate message send events
2. The spec misses a mapping for send/receive events and tasks where the other party is specified not by a service-ref, but by a message flow to another participant.

Proposal:
1. Include that mapping into spec (see Visio)
2. Introduce text describing how BPEL partnerLink is derived from either serviceRef or participantRef; use [serviceRef | participantRef] or similar notation as abbreviation.