[wsbpel] Issue 13 - Updated Proposed Resolution]

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

  The proposal is to replace things with expressions and queries  from 
being an attribute to being an element. This would affect <from>, <to> , 
<propertyAlias>, and conditions.  This would gear up for using other 
languages for querying that may have a structured syntax. An example is 
the upcoming XQueryX, a proposal for XQuery using XML syntax.   The case 
for string queries is also shown below.

With elements instead of attributes, we can allow one to override the 
default query/expression languages locally. The proposal allows for  
optional query/expressionLanguage attributes on queries and conditions 
that can locally override the global default.

Current syntax:

<wsbp:from variable="ncname" part="ncname"? query="queryString"?/>

<wsbp:link ... transitionCondition="..." />
<wsbp:targets joinCondition="...">
.. the same for switch's case, and the whileCondition

Proposed syntax

<wsbp:from variable="ncname" part="ncname"?>
  <wsbp:query queryLanguage=".."?> ?      query goes here
  </wsbp:query>
</wsbp:from>

For example, an XPath 1.0 query would be encoded:

<wsbp:from variable="ncname" part="ncname"?>
  <wsbp:query>
  /shipNotice/ShipNoticeHeader/shipOrderID
  </wsbp:query>
</wsbp:from>

Conditions:

<wsbp:source ... >
      <wsbp:transitionCondition 
expressionLanguage=".."?>...</transitionCondition>?
</wsbp:source>

and

<wsbp:targets>
    <wsbp:joinCondition expressionLanguage="..."?>...</joinCondition> ?
     <wsbp:link.... />
</wsbp:targets>

.. the same for switch's case, and the whileCondition

his mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.