OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsbpel] Issue - 147 - Error in description of the resolution



The error seems to have originated in the notes I kept during the meeting.  During the disucssion, Alex proposed an amendment to the schema based on an email he wrote - you accepted as friendly.  I cut and pasted the relevant portion of the email (at Alex's direction) into the notes I was keeping on the board at the meeting (attached below).  It included the statement "Note: the parallel attribute is now dropped.", however, it may be the cut and paste was not accurate.      
The full text of Alex's email is here: http://www.oasis-open.org/apps/org/workgroup/wsbpel/email/archives/200505/msg00176.html
It might be good to get confirmation from Alex that this was a chair error.  ;-)  
This is the file I had up on the board at the meeting to keep track of amendments -
Here is the relevant text for 147:
Issue 147
Motion:  Adopt proposal from Yaron for 147
Second: Alex
With amendments:
Amendment – change proposal so that no fault is thrown when start value is larger than final value and do not iterate
Amendment: Leave forEach to have variable declared on implicit scope ala event handlers – update 204 to include forEach in its resolution.  
 
Amendment:  make link behavior for forEach the same as for while (section 12.5, last paragraph).  
Accepted as friendly amendment.  

Amendment:  Alex email regarding schema:
Note: the parallel attribute is now dropped.]

    <complexType name="tIterator">
        <complexContent>
            <extension base="bpws:tExtensibleElements">
                <sequence minOccurs="0">
                    <element name="startCounterValue"
                             type="bpws:tExpression"/>
                    <element name="finalCounterValue"
                             type="bpws:tExpression"/>
                </sequence>
            </extension>
        </complexContent>
    </complexType>
 
Accepted as friendly amendment.

Amendment
Remove language in proposal that specified the use of number and round xpath functions for xpath 1.0 expressions.  
Accepted as friendly amendment.  

Do not allow minoccurs=0.  Make start and final mandatory.  This results in getting rid of iterator wrapper.
Accepted with no objections.


Amendment:
1. Eliminate serial for each, remove attributes, etc related to it.
Second – Harvey
Does not pass

 2. Do not allow minoccurs=0.  Make start and final mandatory.  This results in getting rid of iterator wrapper.
Second - Yuzo
Passes with no objections.
Amendment to amendment:  Do not allow minoccurs=0 only.  
Second – Alex
Amendment to amendment does not pass.

Amendment:  consider description in counter proposal from Dieter to consider the use of iterator variables instead of counter variables.  Sub issues can be created to add details if necessary based on discussion.  
Friendly amendment:  change to consider the use of alias based iterator variables.  
Amendment – not passed.

Amendment – issue 147.4:  move yaron’s proposal, w/o name.
Amend: Alex – change to have two activities
Amendment to amendment does not pass
Amendment to 147 not required – base proposal includes appropriate text

 Amendment – call activity “for”
Does not pass (means 147.1 is adopted)

Issue 147.3 – describes current proposal
Amendment – change proposal so that no fault is thrown when start value is larger than final value and do not iterate
Second – Danny
Yaron accepts as friendly amendment

Issue 147.6 – proposal says a non-extended version of the forEach activity MUST include both start and final counter values.   No change

Issue 147.5 – 147 proposal requires the child be a scope and that the counter variable be defined implicitly on that scope.  

If 204 gives us a different solution then we can always come back later and amend.

Amendment: Leave forEach to have variable declared on implicit scope ala event handlers – update 204 to include forEach in its resolution.  
Friendly amendment.
 

Regards, Diane
IBM  Emerging Internet Software Standards
drj@us.ibm.com
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123, Fax 845-491-5709



"Yaron Y. Goland" <ygoland@bea.com>

06/13/2005 06:28 PM
Please respond to
ygoland

To
wsbpeltc <wsbpel@lists.oasis-open.org>, "Furniss, Peter" <peter.furniss@choreology.com>, "Fletcher, Tony" <Tony.Fletcher@choreology.com>
cc
Subject
[wsbpel] Issue - 147 - Error in description of the resolution





I think there has been a miscommunication about what was decided at the
F2F. The group explicitly voted to keep the parallel attribute, not as
reported in the issues list.

                Thanks,

                                 Yaron

--------------------------------------------------------------------------------

Join CEO Alfred Chuang and CTO Mark Carges on June 15 for a unique online
event, giving you the first look at a new category of enterprise software
built specifically for Service-Oriented Architecture (SOA).

Register Now.  It's Free!

http://www.bea.com/events/june15

---------------------------------------------------------------------
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


motions june 1.doc



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]