Issue 10341: Where are tokens queued?                                                                                                                                                                                (bpmn-ftf)
Source: NIST (Mr. Conrad Bock, conrad.bock@nist.gov conradb@cme.nist.gov)
Nature: Uncategorized Issue
Severity: 
Summary: In the following process, assume mulitple tokens are being fed to A
  from upstream (<X> = exclusive OR split, <+> = AND Join):


               |------|
   ----> A -- <X>    <+> --> B
               |------|


  I assume two executions of A are required for each execution of B (if
  not, correct the parts of the spec that imply this).


  Where are tokens queued up that don't have a matching one to get
  through the AND join?  BPMN should indicate where the queuing happens,
  because it affects execution.  If queuing is at the the exclusive-OR
  split, then conditions could change over time and the guard could
  direct the token to a different path after the token as been queued a
  while.  Or token could queue at the join, and only be tested by the
  guards once.
Resolution: Suggested Resolution:
Close, No Change: This issue is out of scope for the RTF and will be addressed by the response to
the BPMN 2.0 RFP.
Revised Text: None
Disposition: Closed, deferred
Revised Text: 
Actions taken:
September 5, 2006: received issue
July 18, 2008: closed issue
Discussion: 
Defer: While the Issue may be valid, it represents potentially significant modifications. Thus,
this Issue will be deferred and handled by work on a later version of BPMN.

End of Annotations:=====
eply-To: <conrad.bock@nist.gov>
From: "Conrad Bock" <conrad.bock@nist.gov>
To: "'BPMNFTF'" <bpmn-ftf@omg.org>
Subject: RE: XOR split / AND join combination, issue to file
Date: Tue, 5 Sep 2006 16:44:21 -0400
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Aca/spZu6KbL2DV7SKODNHba9eAloQAE1RqgAr5RuFA=
X-MailScanner-Information: Please contact postmaster@mel.nist.gov for more information
X-MailScanner: Found to be clean
X-MailScanner-SpamCheck: 
X-MailScanner-From: conrad.bock@nist.gov
X-Spam-Status: No




Hi Juergen,


Could you file this BPMN issue so the ascii diagram is preserved?


Thanks,


Conrad



  Title: Where are tokens queued?


  In the following process, assume mulitple tokens are being fed to A
  from upstream (<X> = exclusive OR split, <+> = AND Join):


               |------|
   ----> A -- <X>    <+> --> B
               |------|


  I assume two executions of A are required for each execution of B (if
  not, correct the parts of the spec that imply this).


  Where are tokens queued up that don't have a matching one to get
  through the AND join?  BPMN should indicate where the queuing happens,
  because it affects execution.  If queuing is at the the exclusive-OR
  split, then conditions could change over time and the guard could
  direct the token to a different path after the token as been queued a
  while.  Or token could queue at the join, and only be tested by the


To: bpmn-ftf@omg.org
Subject: Proposed Resolution for Issue 10341
X-Mailer: Lotus Notes Release 7.0 HF242 April 21, 2006
From: Stephen A White <wstephe@us.ibm.com>
Date: Tue, 5 Dec 2006 08:13:35 -0500
X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 7.0.2HF32 | October 17, 2006) at
 12/05/2006 06:13:36,
        Serialize complete at 12/05/2006 06:13:36



This is intended for Ballot 5 
Issue 10341: Where are tokens queued? 
Description: 
  
In the following process, assume mulitple tokens are being fed to A from upstream (<X> = exclusive OR split, <+> = AND Join): 
|------| 
----> A -- <X> <+> --> B 
|------| 
I assume two executions of A are required for each execution of B (if not, correct the parts of the spec that imply this). 
Where are tokens queued up that don't have a matching one to get through the AND join? BPMN should indicate where the queuing happens, because it affects execution. If queuing is at the the exclusive-OR split, then conditions could change over time and the guard could direct the token to a different path after the token as been queued a while. Or token could queue at the join, and only be tested by the guards once. 
  
Suggested Resolution: 
  
Defer: While the Issue may be valid, it represents potentially significant modifications. Thus, this Issue will be deferred and handled by work on a later version of BPMN. 
  
Revised Text: None 

  guards once.