BPMN2 — Hexagons and message flow linked to activities

Filed for soaML: It should be possible to link hexagons (conversations /
communications) to activities. This would mean messages flow from
within the activity, which could be calls or subs. The hexagon can be
expanded to show message flow connected to the activity, including calls
and subs.

Conversation links are groupings of message flows, so they can be linked
to activities and events just as message flow can. The resolution
supports conversation links to activities and events, but not message
flow to conversation nodes a requested by the issue. This restriction
is only by textual constraint, if a future RTF would like to loosen it.
Conversation Link is added to the metamodel to simplify implementation
of this resolution. The notation for conversation links is changed to a
double lines, to distinguish them from sequence flows when used with
activities and events. The forked line end notation for conversation
links ("crow's feet") is removed to simplify usage and implementation,
since it is redundant with participant multiplicity notation.
The resolution assumes the resolution of 14654.
Refer to attached document
Issue+531+figures-v3.doc
for figures.
In the BPMN Core Structure chapter, Message Flow subsection, in the
figure The Message Flow Class Diagram, rename MessageFlowNode to
InteractionNode, add ConversationNode as a subclass, and its association
to Participant. See first figure in attached document.
In the BPMN Core Structure chapter, Message Flow subsection, in the
table Message Flow attributes and model associations:

• replace "MessageFlowNode" with "InteractionNode" in the first two
  rows, both columns.
• In the first two rows, right column, at the end of the sentences,
  add "of a Message Flow".
  In the BPMN Core Structure chapter, Message Flow section, Message Flow
  Node subsection:
• Change the title of the subsection to Interaction Node
• In the two paragraphs of the subsection, replace the two occurrences
  of "MessageFlowNode" in each paragraph with "InteractioNode".
• In the first paragraph, delete the portion of the sentence starting
  with "and thus" to the end of the sentence.
• At the end of the first paragraph, add the sentence "The
  InteractionNode element is also used to provide a single element for
  source and target of Conversation Links, see chapter XXXCollaboration.
  In the Collaboration section, in the figure Classes in the Collaboration
  package, add ConversationLink and InteractionNode and their associations
  and generalizations to other elements, see second figure in the attached
  document.
  In the Collaboration chapter, Participants section, in the figure The
  Participant Class Diagram, change the name of the MessageFlowNode
  metaclass to InteractionNode. See third figure in attached document.
  In the Collaboration section, in the table Collaboration Attributes and
  Model Associations, after the row for conversations, insert a new row:
• conversationLinks: ConversationLink [0..*]
  This provides the Conversation Links that are used in the
  Collaboration.
  In the Collaboration chapter, Conversations section, at the end of the
  first paragraph, add the sentence "In particular, processes can appear
  the participants (pools) of conversation diagrams, to show how
  conversations and activities are related."
  In the Collaboration chapter in the Conversation Link section (was
  CommunicationLink before resolution of 14654), after
  the figure A Conversation Link element, insert a new figure captioned
  "The Conversation Link Class Diagram", showing ConversationLink and
  related classes, see the fourth figure in the attached document.
  After the above new figure, insert:
  The Conversation Link element inherits the attributes and model
  associations of BaseElement (see Table XX). Table XXXX presents the
  additional attributes and model associations for the Conversation Link
  element:
  then insert a table with the caption "Conversation Link attributes and
  model associations", and two columns headed "Attribute Name" and
  "Description/Usage" with the rows:
  name : String [0..1]
  Name is a text description of the Conversation Link.
  sourceRef: ConversationLinkNode
  The ConversationLinkNode that the Conversation Link is connecting
  from. A Conversation Link MUST connect to exactly one
  ConversationNode. If the sourceRef is not a ConversationNode, then
  the targetRef MUST be a ConversationNode.
  targetRef: ConversationLinkNode
  The ConversationLinkNode that the Conversation Link is connecting
  to. A Conversation Link MUST connect to exactly one
  ConversationNode. If the targetRef is not a ConversationNode, then
  the sourceRef MUST be a ConversationNode.
  In the Collaboration chapter in the Conversation Link section (was
  CommunicationLink before resolution of 14654), delete
  the figure Where Conversation Links are derived in the metamodel, and
  the paragraph after it (the last one in the section) and replace it with:
  Processes can appear in the participants (pools) of Conversation
  diagrams, as shown in Figure XXXX. The invoicing and ordering
  conversations have links into activities and events of the process in
  the Order Processor. The other two conversations do not have their
  links "expanded". Conversation links into activities that are not
  send or recieve tasks indicate that the activity will send or receive
  messages of the conversation at some level of nesting.
  After the above text, insert a figure captioned "Conversation links to
  activities and events" with the contents of the fifth figure in the
  attached document.
  In the Collaboration chapter, in the XML Schema section, in the table
  for Collaboration XML schema, under the conversations element, insert a
  new line:
  <xsd:element ref="conversationLink" minOccurs="0" maxOccurs="unbounded"/>
  In the Collaboration chapter, in the XML Schema section, after the table
  for Conversations, insert a new table, captioned "ConversationLink XML
  schema" containing:
  <xsd:element name="conversationLink" type="tConversationLink" substitutionGroup="rootElement"/>
  <xsd:complexType name="tConversationLink">
  <xsd:complexContent>
  <xsd:extension base="tBaseElement">
  <xsd:attribute name="name" type="xsd:string" use="optional"/>
  <xsd:attribute name="sourceRef" type="xsd:QName" use="required"/>
  <xsd:attribute name="targetRef" type="xsd:QName" use="required"/>
  </xsd:extension>
  </xsd:complexContent>
  </xsd:complexType>
  In the Overview chapter, BPMN Scope section, Uses of BPMN subsection,
  figure An example of a Conversation diagram, on the lines coming out of
  the hexagons (the conversation links):
• Change the line style to double thin lines.
• Remove the forking on the participant ends of the lines.
  In Collaborations chapter, Conversation section, figure A Conversation,
  figure Conversation diagram depicting several conversations between
  Participants in a related domain, change the figure in the same way as
  the figure above.
  In Process chapter, Activities section, Sub-Processes subsection, Ad-Hoc
  Sub-Process subsubsection, in the bullet just above figure An Ad-Hoc
  Sub-Process with data and sequence dependencies, after "Conversation
  Links" insert "(graphically)".
  In Collaborations chapter, Conversation section, figure A Conversation
  diagram, on the lines coming out of the hexagon (conversation links),
  change the line style to double thin lines.
  In Collaborations chapter, Conversation section, figure Conversational
  view choreographies, on the lines coming out of the hexagon
  (conversation links), change the line style to double thin lines.
  In Collaborations chapter, Conversation section, COnversation Link
  subsection:
• First paragraph, replace the second sentence with "Conversation
  links MUST be drawn with double thin lines.".
• In figure A Conversation Link element:
• On the lines coming out of the hexagon:
• Change the line style to double thin lines.
• Remove the forking on the participant ends of the lines.
• Remove the text annotation on the lower right (the one that
  says "The Conversation Link source is forked if there are
  multiple connections").
  Disposition: Resolved