The XPDL specification states for activity boundary connections: The Intermediate Event MUST NOT be a target for Sequence Flow; it cannot have an incoming Flow
Let there be a timer event connected to the boundary of an activity. As I see from the specification and the example processes there is no connection between the activity and the event without the NodeGraphicsInfo which indicates the event is connected to the activity boundary. In the example process (Discussion Cycle Subprocess) there is a timer event scheduled with the start of the activity "Moderate E-mail Discussion". From a technical perspective: How is the connection semantics between activity and event? How does a workflow system imorting the process know that activity and event are related and the timer should be scheduled if the activity is started without respecting the graphical representation? Is there any explicit information inside the WorkflowProcess-Element about this connection?

Any help or further advice is appreciated!