Issue - 242 - Remove required scope children

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 - 242 - Remove required scope children
Status: received

Date added: 21 Jan 2006

Categories: Scoping, Syntax

Date submitted: 20 January 2006

Submitter: Danny van der Rijn

Description: Arising from part (B) 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 204 : clarify the relationship between eventHandler and compensationHandler  completely.  Add the elements and attributes from scope (except suppressJoinFalure, isolated, and standard-elements for onAlarm) that are not currently on <onAlarm> and <forEach>

Rationale:  Extend the relevant rationale from Part A ( issue 241)

issue 241 : clarification of onevent resource resolution  was for onEvent.  This issue is for onAlarm and forEach

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 - 242 - [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 - 242 - 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).