Issue 14876: UML interface operations do not match BPMN interface operations (bpmn2-rtf)
Source: Tekgensis (Mr. Mariano Benitez, mariano(at)benitez.nu)
Nature: Revision
Severity: Critical
Summary: Currently interface operations in BPMN follow a "Document" model where all the arguments are wrapped in a single "Message" in and out of the operation.
But in UML, interface operations follow the "RPC" model, where arguments are independent and each one has the "In, Out, InOut" classifier.
This difference creates several problems when trying to relate/map BPMN and UML operations. Another side effect of the BPMN message model is that you cannot use simple data associations to fill the arguments of a service call. Since the operation is a single type, we have to use transformations to target the arguments (in my case we hide this complexity from the end user, and probably every vendor will do the same.


So, if the FTF wants to have a reasonable integration with SoaML, we should fix this issue. The proposal is to adopt the UML model, with separate arguments instead of a single document in and out. 
We understand this is a major change, and a migration path from the Beta spec to the final one is a mandatory requirement.
Resolution: 
Revised Text: 
Actions taken:
December 17, 2009: received issue
Discussion: 
The FTF agrees that there is a problem that needs fixing, but did not agree on a resolution and deferred its resolution to a future RTF/FTF.
Disposition: Deferred
End of Annotations:=====

m: webmaster@omg.org
Date: 17 Dec 2009 10:34:51 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:          Mariano Benitez
Company:       Oracle
mailFrom:      mariano.benitez@oracle.com
Notification:  No
Specification: BPMN 2.0
Section:       8.4
FormalNumber:  DTC-09-08-14
Version:       Beta
RevisionDate:  Aug 09
Page:          108
Title:         UML interface operations do not match BPMN interface operations
Nature:        Revision
Severity:      Critical
test:          3qw8
B1:            Report Issue


Description:


Currently interface operations in BPMN follow a "Document" model where all the arguments are wrapped in a single "Message" in and out of the operation.
But in UML, interface operations follow the "RPC" model, where arguments are independent and each one has the "In, Out, InOut" classifier.
This difference creates several problems when trying to relate/map BPMN and UML operations. Another side effect of the BPMN message model is that you cannot use simple data associations to fill the arguments of a service call. Since the operation is a single type, we have to use transformations to target the arguments (in my case we hide this complexity from the end user, and probably every vendor will do the same.


So, if the FTF wants to have a reasonable integration with SoaML, we should fix this issue. The proposal is to adopt the UML model, with separate arguments instead of a single document in and out. 
We understand this is a major change, and a migration path from the Beta spec to the final one is a mandatory requirement.