Issue - 237 - Proposal for vote

[Danny van der Rijn <dannyv@tibco.com>]

Remove the <then> element from the <if> construct.  This will make the <if> syntax more internally consistent with <elsif> and <else> not having any element to wrap the activity. 

The only places that the current draft of the spec references <then> is in XML pseudo-schema, examples and the schema itself (not in the draft) - there is no prose to change:

6.2:
change to:
<if standard-attributes>
     standard-elements
     <condition expressionLanguage="anyURI"?>
          ... bool-expr ...
     </condition>
     <then>
          activity
     </then>
     <elseif>*
        <condition expressionLanguage="anyURI"?>
          ... bool-expr ...
        </condition>
        activity
     </elseif>
     <else>?
        activity
     </else>
</if>

12.2
change to:
<if standard-attributes>
     standard-elements
     <condition expressionLanguage="anyURI"?>
          ... bool-expr ...
     </condition>
     <then>
          activity
     </then>
     <elseif>*
        <condition expressionLanguage="anyURI"?>
          ... bool-expr ...
        </condition>
        activity
     </elseif>
     <else>?
        activity
     </else>
</if>

and

<if xmlns:inventory="http://supply-chain.org/inventory"
    xmlns:FLT="http://example.com/faults">
     <condition>
        bpws:getVariableProperty('stockResult','level') > 100
     </condition>
     <then>
    <flow>
        <!-- perform fulfillment work -->
    </flow>
     </then>
     <elseif>
       <condition>
        bpws:getVariableProperty('stockResult','level') >= 0
       </condition>
    <throw faultName="FLT:OutOfStock"
         variable="RestockEstimate"/>
     </elseif>
     <else>
    <throw faultName="FLT:ItemDiscontinued"/>
    </else>
</if>


16.1.3, note that the pcode wouldn't change
receive shipOrder
if
    condition shipComplete
         send shipNotice
    else
         itemsShipped := 0
         while itemsShipped < itemsTotal
        itemsCount := opaque // non-deterministic assignment
                // corresponding e.g. to
                // internal interaction with
                // back-end system
        send shipNotice
        itemsShipped = itemsShipped + itemsCount


change example
...
    <if>
      <condition>
bpws:getVariableProperty('shipRequest','props:shipComplete')
      </condition>
        <then>
      <sequence>
        <assign>
           <copy>
              <from variable="shipRequest" property="props:itemsCount"/>
              <to variable="shipNotice" property="props:itemsCount"/>
          </copy>
        </assign>
        <invoke partnerLink="customer"
            portType="sns:shippingServiceCustomerPT"
            operation="shippingNotice"
            inputVariable="shipNotice">
             <correlations>
            <correlation set="shipOrder" pattern="out"/>
             </correlations>
        </invoke>
       </sequence>
    </then>
...



ws-bpel issues list editor wrote:

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 - 237 - Does <if> need <then>

Status: received
Date added: 1 Dec 2005
Categories: Syntax
Date submitted: 01 December 2005
Submitter: Danny van der Rijn
Description: The <then> element in the <if> construct is superfluous. We should remove it.
Changes: 1 Dec 2005 - new issue

---

To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the wsbpel@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - 237 - [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 - 237 - 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).

--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php