Issue 15901: Subclasses of Interaction Node (Task vs. Activity) (bpmn2-rtf)
Source:  (, )
Nature: Clarification
Severity: Significant
Summary: According to the Message Flow Class Diagram (Figure 9.14), Interaction Node has four subclasses: Participant, ConversationNode, Task and Event. 


However, according to page 124:
Of the types of InteractionNode, only Pools/Participants, Activities, and
Events can be the source of a Message Flow. 


The question now is, whether Task or Activity should be the subclass of Interaction Node.

Suggestion: The Message Flow Connection Rules on page 44 specify that Message Flows can also connect to Sub-Processes. Therefore, I think it is necessary to define that Activity is a subclass of InteractionNode. 

Resolution: 
Revised Text: 
Actions taken:
December 15, 2010: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 15 Dec 2010 09:41:27 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Christine Natschlaeger
Employer:        Software Competence Center Hagenberg GmbH
mailFrom:        Christine.Natschlaeger@scch.at
Terms_Agreement: I agree
Specification:   Business Process Model and Notation (BPMN)
Section:         9.3
FormalNumber:    dtc/2010-06-05
Version:         2.0
Doc_Year:        2010
Doc_Month:       June
Doc_Day:         05
Page:            123f
Title:           Subclasses of Interaction Node (Task vs. Activity)
Nature:          Clarification
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue


Description:


According to the Message Flow Class Diagram (Figure 9.14), Interaction Node has four subclasses: Participant, ConversationNode, Task and Event. 


However, according to page 124:
Of the types of InteractionNode, only Pools/Participants, Activities, and
Events can be the source of a Message Flow. 


The question now is, whether Task or Activity should be the subclass of Interaction Node.

Suggestion: The Message Flow Connection Rules on page 44 specify that Message Flows can also connect to Sub-Processes. Therefore, I think it is necessary to define that Activity is a subclass of InteractionNode.