Issue - R12 - Isolated Scopes

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 - R12 - Isolated Scopes
Status: received

Date added: 20 Sep 2006

Date submitted: 20 Sep 2006

Submitter: Dieter Koenig1

Description: The first paragraph of Section 12.7. reads as follows:

The isolated attribute of a scope, when set to "yes", provides control of concurrent access to shared resources: variables, partner links, and control dependency links. Its default value is "no". Such a scope is called an isolated scope.

The last two sentences suggest that a scope with the default value "no" for the isolated attribute is called an isolated scope, which is not the intention.

Submitter's proposal: Reverse the order of the last two sentences of this paragraph and revise the new last sentence.

The isolated attribute of a scope, when set to "yes", provides control of concurrent access to shared resources: variables, partner links, and control dependency links. Such a scope is called an isolated scope. The default value of the isolated attribute is "no".

Changes: 20 Sep 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 - R12 - [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 - R12 - Proposed resolution", without any Re: or similar.

To add a new issue, 
see the issues procedures document