Issue - 275 - "immediately enclose" and compensation

This issue has been added to the wsbpel issue list with a status of "resolved". The TC
agreed to accept the issue and agreed the resolution before it was added to the issues list.
It has been added to the issue list purely for tracking purposes.

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 - 275 - "immediately enclose" and compensation
Status: received

Date added: 2 May 2006

Date submitted: 02 May 2006

Submitter: Alex Yiu

Description: We passed the motion to use the wording "immediately enclose" consistently in chapter 12. Such as replace "enclosed immediately" to "nested immediately". Its definition is: 

For the purpose of specifying the semantics of <compensate> and <compensateScope>, a scope, A is considered to immediately enclose another scope, B, if B is enclosed in A and B is not enclosed in any other scope or FCT-handler that is itself enclosed in the outer scope A.  Other structured activities (e.g. <sequence> or <forEach>) and event handlers enclosed in A do not affect the concept of immediate enclosure.

FCT-Handler is defined as the collection of fault, compensation, termination handler.

Changes: 2 May 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 - 275 - [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 - 275 - 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).