Issue 15121: Rethink implementation attribute in Send/Receive/Service Tasks (bpmn2-rtf) Source: Intalio, Inc. (Mr. Tammo van Lessen, tammo(at)intalio.com) Nature: Clarification Severity: Significant Summary: Currently, send/receive/service/user/business rule tasks have an "implementation" attribute. Based on the information in the spec and from the process orchestration subgroup call, this attribute shall identify the technology to be used for interaction. This can be Web Service, WS-HT or any other protocol/coordination protocol. While this makes sense for human tasks and business rule tasks, there are a couple of inconsistencies with Send/Receive/Service tasks. Here is why: - Receive Task has an implementation attribute, a message event has not. - A Receive Task and a subsequent Send Task that deal with messages defined within the same operation may have different values for the implementation attribute. This is however probably not intended. My proposed resolution is to remove the implementation attributes for send/receive/service tasks. We should discuss whether this information is really needed or whether it could be inferred by the implementationRef of the interface/operation tuple. The information might be needed to determine in which technology an interface/operation is implemented. See also http://www.osoa.org/jira/browse/BPMNFTF-519#action_15739 As an alternative, MessageEventDefinition would need such an attribute as well. Resolution: Revised Text: Actions taken: March 8, 2010: 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: 08 Mar 2010 16:39:00 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Tammo van Lessen Company: Intalio mailFrom: tammo@intalio.com Notification: Yes Specification: Business Process Model and Notation Section: 10.2.3, 10.4.5 FormalNumber: dtc/2009-08-14 Version: FTF Beta 1 for Version 2.0 Draft 1 RevisionDate: Feb 2010 Page: 135ff, 249 Title: Rethink implementation attribute in Send/Receive/Service Tasks Nature: Clarification Severity: Significant test: 3qw8 B1: Report Issue Description: Currently, send/receive/service/user/business rule tasks have an "implementation" attribute. Based on the information in the spec and from the process orchestration subgroup call, this attribute shall identify the technology to be used for interaction. This can be Web Service, WS-HT or any other protocol/coordination protocol. While this makes sense for human tasks and business rule tasks, there are a couple of inconsistencies with Send/Receive/Service tasks. Here is why: - Receive Task has an implementation attribute, a message event has not. - A Receive Task and a subsequent Send Task that deal with messages defined within the same operation may have different values for the implementation attribute. This is however probably not intended. My proposed resolution is to remove the implementation attributes for send/receive/service tasks. We should discuss whether this information is really needed or whether it could be inferred by the implementationRef of the interface/operation tuple. The information might be needed to determine in which technology an interface/operation is implemented. See also http://www.osoa.org/jira/browse/BPMNFTF-519#action_15739 As an alternative, MessageEventDefinition would need such an attribute as well.