Issue 15733: Intermediate Message Event can be source or target of Message Flow (bpmn2-rtf) Source: (, ) Nature: Revision Severity: Minor Summary: Chapter/Section 10.4.4. Page 259. Table 10.89. Row “Message”. It says: “The actual Participant from which the Message is received can be identified by connecting the Event to a Participant using a Message Flow …” COMMENTS: The description is devoted to both throw and catch Intermediate Message Events, but it is only described the Participant associated with the catch Event. SUGGESTION: It should say: “The actual Participant from which the Message is received or to which the Message is sent can be identified by connecting the Event to a Participant using a Message Flow …” Resolution: Revised Text: Actions taken: October 14, 2010: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 14 Oct 2010 23:43:18 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Eduardo Jara Employer: mailFrom: ejara@craftware.net Terms_Agreement: I agree Specification: BPMN 2.0 Beta 2 Section: 10.4.4 FormalNumber: dtc/2010-06-05 Version: 2.0 Doc_Year: 2010 Doc_Month: June Doc_Day: Day Page: 259 Title: Intermediate Message Event can be source or target of Message Flow Nature: Revision Severity: Minor CODE: 3TMw8 B1: Report Issue Description: ANTECEDENTS: Chapter/Section 10.4.4. Page 259. Table 10.89. Row .Message.. It says: .The actual Participant from which the Message is received can be identified by connecting the Event to a Participant using a Message Flow .. COMMENTS: The description is devoted to both throw and catch Intermediate Message Events, but it is only described the Participant associated with the catch Event. SUGGESTION: It should say: .The actual Participant from which the Message is received or to which the Message is sent can be identified by connecting the Event to a Participant using a Message Flow ..