Re: [wsbpel] Issue - 82.3 - Proposal for vote

[Rania Khalaf <rkhalaf@watson.ibm.com>]

Hi everyone,

First phase of two-phase voting (content, then spec wording). I've
merged the previously named 'proposed changes' section into the main
text of this mail since this is the proposal.

--------------------------------------------------
AP1.1 refactoring, start.
-------------------------------

(add motivation in phase 2)

(consider what old text to bring in from spec and how to modify it to
introduce various aspects, especially regarding clarifications about
initialization of correlation sets and variable omission in phase 2).

ProfileURI:

- http://schemas.xmlsoap.org/ws/2004/03/business-process/abstract/ap11


Base Language subset
_____________________

.. This profile restricts the base in the following manner:

*  Allowing all expressions to be opaque except joinCondition. Please
note that the joinCondition is based on the transition conditions on
the incoming links. If the joinCondition is missing its default
value is the disjunction of the status of the incoming links.

* The only attributes that can be opaque are the attributes
"variable", "inputVariable" and "outputVariable", on
receive/invoke/reply/onMessage/onEvent (Note: bug fix based on Issue
97: fixing the consistency for elements onMessage and onEvent).

* Allowing opaque activity, as a bug fix for the two reasons
below. Note that its use elsewhere is superfluous since completions
in this profile allow adding new BPEL activities anywhere:

    -Allows for hiding an activity that is the source or target of
    -links.  Allows for using omission-shortcut in places like fault
    handlers etc (This had led to Issue 91).

* It is not clear whether BPEL function 'getVariableData' is allowed
(what's the new form of this with $ etc): Text disallows it, but
example uses it. Need to vote on this. Preference is to disallow
it. However, 'get VariablePropery' is still allowed.

* Activity <exit > is not allowed.

* Uses omission-shortcut for the opaque tokens above (allowed by all APs 
anyway).


Base Completions subset
_________________________

Places where new activities may be added are not explicitly defined in
processes in this profile. The permitted executable completions of
abstract processes in this profile include both 'Opaque Token
Replacement' and 'Addition of BPEL Constructs', but subsetting those
such that:

o Each process that is a valid executable completion of a process in
this profile MUST NOT:

   * add to
   * omit any of
   * or change the order (control dependency) of

any of the interactions along the partnerlinks already defined in the
abstract process, even if replacing opaque activities (including those
omitted with omission-shortcut, such as activity of a fault
handler). Note that this still allows for adding new interactions with
new partnerLinks (ie: partnerLinks added in the executable completion
but not present in the abstract process).

o It is not allowed to add copies in assigns whose 'to' is any of the
EPRs of the partnerLinks defined in the abstract process, because that
is equivalent to removing subsequent interactions with that partner.
Remember that 'opaque token replacement' also replaces opaque tokens
omitted through the omission-shortcut.


* In case new links are added in a completion to an activity in the
   abstract process itself, the join condition of the target activity
   can be modified but only by AND-ing or OR-ing the status of the new
   link with the original join condition defined in the abstract
   process. The addition of new links must not violate the first bullet
   above (regarding existing interactions)


( Note: The phrase 'even if .. ' sentence is pending whether opaque
activities get allowed. )