Issue - 243 - serial and parallel forEach are different

This issue has been added to the wsbpel issue list with a status of "received".
The status will be changed to "open" if a motion to open the issue is proposed and that
motion is approved by the TC. A motion could also be proposed to close it without
further consideration. Otherwise it will remain as "received".

The issues list is posted as a Technical Committee document to the 
OASIS WSBPEL TC pages
on a regular basis. The current edition, as a TC document, is the most recent version of 
the document entitled  in the 
"Issues" folder of the WSBPEL TC document list
- the next posting as a TC document will include this issue.
The list editor's working copy, which will normally include an issue when it is announced, is available at 
this constant URL.

Issue - 243 - serial and parallel forEach are different 
Status: received

Date added: 21 Jan 2006

Categories: Scoping, Syntax

Date submitted: 20 January 2006

Submitter: Danny van der Rijn

Description: Arising from part (C) of [proposed resolution;MSG=200509/83] for  issue 120.2 and its discussion.
See http://lists.oasis-open.org/archives/wsbpel/200509/msg00083.html

Rescind issue 147.4 : Should there be a single activity or a serial & parallel activity? .  Re-resolve the other way:  I.e. separate activities for serial and parallel forEach.  
Part B (issue 242 : Remove required scope children ) would only apply to parellelForEach if B is accepted as well.

Rationale:  Serial and parallel forEach are semantically divergent.  They are getting more and more divergent syntactically.  
Cf.   issue 204,  issue 6.2,  issue 216,  issue 242, issue 227 : The messageExchange attribute doesn't handle parallel forEach , and probably others.  It is to the 
point where it is easier to make them different and point out the similarities, than it is to keep them the same and point out the differences. 

Changes: 21 Jan 2006 - new issue

To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the 
 list (replying to this message should automatically send your message to that list), or ensure
the subject line as you send it starts "Issue - 243 - [anything]" or is a reply
to such a message. If you want to formally propose a resolution to an open issue, please start the subject line 
"Issue - 243 - Proposed resolution", without any Re: or similar.

To add a new issue, 
see the issues procedures document (but the address for new issue submission is the sender of this announcement).