Issue 11677: precisions about the Signal Event (bpmn-rtf) Source: Axway Software (Mr. Sylvain Astier, sastier@axway.com) Nature: Uncategorized Issue Severity: Summary: I would appreciate some precisions about the Signal Event. Initially we intended not to have any data associated with it. Yet it has some properties. I think it makes sense; we indeed need to associate technical information such as the Name or Id of the instance that raised it, as well as its TimeStamp. I want to make sure those are not supposed to be business data. Also I think this part is under specified, we need to further explain what kind of mechanism should be used to "listen" to such events, (publish/subscribe pattern ?) as well as how long such messages are supposed to be kept alive. For instance on Figure 10.48 (Adobe 322) what is supposed to happen if "B Completed" is raised before the upper sub process is ready to receive it ? Resolution: Revised Text: Actions taken: November 18, 2007: received issue Discussion: End of Annotations:===== m: "Astier Sylvain" This is issue # 11677 precisions about the Signal Event I would appreciate some precisions about the Signal Event. Initially we intended not to have any data associated with it. Yet it has some properties. I think it makes sense; we indeed need to associate technical information such as the Name or Id of the instance that raised it, as well as its TimeStamp. I want to make sure those are not supposed to be business data. Also I think this part is under specified, we need to further explain what kind of mechanism should be used to "listen" to such events, (publish/subscribe pattern ?) as well as how long such messages are supposed to be kept alive. For instance on Figure 10.48 (Adobe 322) what is supposed to happen if "B Completed" is raised before the upper sub process is ready to receive it ?