WS-BPEL 2.0 Updates for the Second Public Review

[Dieter Koenig1 <dieterkoenig@de.ibm.com>]

My collection of editorial updates for the second public review.

As soon as the 2nd PR is running, I would submit them together as one
editorial issue, unless there are any objections.

Kind Regards and Happy Holidays
DK


Change "<onMessage> activity" to "<onMessage> event"
5.2. The Structure of a Business Process
The optional messageExchange attribute is used to associate a <reply>
activity with a <onMessage> activity event.


Add missing <copy> element
8.4. Assignment
Complex document transformation.

   <assign>
     <copy>
      <from>
         bpel:doXslTransform("urn:stylesheets:A2B.xsl", $A)
      </from>
      <to variable="B" />
     </copy>
   </assign>


Fix wrong label in Figure 3
12.4.2. Process State Usage in Compensation Handlers
In Figure 3 in 12.4.2., the CH of scope "S2" is "CH(S2)" and not "CH(S3)".


Clarification of termination behavior
12.6 Termination Handlers
The behavior of a fault handler for a scope C begins by disabling the
scope's event handlers and implicitly terminating all activities enclosed
within C that are currently active (including all running event handler
instances).
(...)
The forced termination of a scope begins by disabling the scope's event
handlers and terminating its primary activity and all running event handler
instances.


Replace "##BPELopaque" by "##opaque"
13.1.3. Hiding Syntactic Elements
(2 occurrences need to be changed)


Drop "-then"
13.3.4. Subset of the Executable Completions Allowed in the Base

Conditions that affect the flow of control such as transition conditions,
“if-then” or “while” expressions, among others, can have such an effect on
the order of interactions.

New branches to an existing “if-then-else” activity, unless it has no
“else” branch, and the new branch is added after all existing branches.


Replace wrong namespace in extension declaration
13.4.5. Extensions and Document Usage

     <extension
         namespace="http://example.com/bpel/some/extension
http://docs.oasis-open.org/wsbpel/2.0/process/abstract/simple-template/2006/08
"
         mustUnderstand="yes" />


Add missing <copy> element
13.4.5. Extensions and Document Usage
      <assign>
         <documentation>
            Transform one of these 3 appraisal request into our own
            format.
         </documentation>
       <copy>
         <opaqueFrom/>
         <to variable="commonRequestVar" />
       </copy>
      </assign>


Drop reference to non-existent XML grammar
13.4.6. Syntactic Validity

The Process Template Profile provides an XML grammar (see section Appendix
E. XML Schemas) to support syntax validation beyond that provided by the
common base Schema.