Issue - 276 - language in 12.3.3.1 addressing name uniqueness for target scope/activities of <compensateScope>

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 - 276 - language in 12.3.3.1 addressing name uniqueness for target scope/activities of <compensateScope>
Status: received

Date added: 3 May 2006

Date submitted: 03 May 2006

Submitter: Charlton Barreto

Description: Section 12.3.3.1, Compensation of a Specific Scope, states in paragraph 3 that 

All scopes and activities directly nested in a scope (i.e. not within a nested scope) MUST be uniquely named. If the value of the target attribute specified on a compensateScope activity does not resolve to a unique scope or activity name in the same scope as the compensateScope activity, the WS-BPEL definition MUST be rejected from processing. This requirement MUST be statically enforced.

However, this does not reflect the resolution to issue 162 : Unique Activity Names for Compensate  in [1] as amended by [2] in a manner consistent with Section 10.1. We need to properly reflect that the restrictions on name uniqueness for scopes and invoke activities apply specifically to those referenced by a <compensateScope> activity. 

[1] Dieter Koenig1, 11 Dec 2004

[2] Issue 162 in Minutes of ftf, 14-16 December 2004

Submitter's proposal: To resolve this, we need to delete the paragraph 3 of Section 12.3.3.1 and replace it with the following:

The names of all named activities immediately enclosed in a scope must be unique (see section 10.1. Standard Attributes for Each Activity). The target attribute of a <compensateScope> activity MUST refer to a scope or an invoke activity with a fault handler or compensation handler. The referenced activity MUST be immediately enclosed by the scope containing the FCT-handler with the <compensateScope> activity. If these requirements are not met then the WS-BPEL process MUST be rejected. These requirements MUST be statically enforced."

Changes: 3 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 - 276 - [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 - 276 - 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).