Next in thread → Next in month →

RE: [wsbpel-spec-edit] current status and next call

From
Mehta, Vinkesh \(US - Austin\) <>
Date
2005-12-13T15:35:54+00:00
ID
Thread
RE: [wsbpel-spec-edit] current status and next call
Diane, 

 

OK, I have the pen now. I 
will work on 82.2.

 

regards,

-Vinky

From: Diane Jordan 
[mailto:]
Sent: Tue 12/13/2005 7:20 AM
To: 

Subject: Fw: [wsbpel-spec-edit] 
current status and next call

My apologies - my calendar got messed up and I didn't realize we were due 
for a call last week.  Lets plan to have our call next week on our usual 
schedule - next Tues Dec. 20.  Fortunately, we've kept the pen moving. 
 Here are the notes from the last call:   

Paco is working on 82.3, 99, 107, 109 
Assaf (if 
available) to complete 209 and 214 when Paco is done   

Alex will do 6.2 and 204, and fix the 
error he found: grammar mistake for <onAlarm> (repeatEvery can be used on 
its own) 
Vinky will 
do 82.2 
Alexandre 
will do 230, 233 

Vinky, you are next, then Alexandre.   

I'd like to plan to get the latest version posted to the 
web site early next week so that folks will have some time to review it before 
the face to face in Jan - its sooner than it seems!   

Regards, Diane
IBM  Emerging Internet Software 
Standards

(919)254-7221 or 8-444-7221, Mobile: 
919-624-5123, Fax 845-491-5709

----- Forwarded by Diane Jordan/Raleigh/IBM on 12/13/2005 08:13 AM 
----- 

  
  

    Alex Yiu 
      <> 
      
12/13/2005 04:08 AM 

    
      
        
        

          
            
To

          Alex Yiu 
            <> 
        

          
            
cc

          Diane 
            Jordan/Raleigh/IBM@IBMUS, Assaf Arkin <>, 
            , , 
            Alex Yiu <> 
        

          
            
Subject

          Re: Fw: 
            [wsbpel-spec-edit] Notes from Nov 22 
      call

      
        
        

          
          

Hi all,

I have applied the following changes: 

  
Fixing XSD to allow: (a) other URI in 
  importType (b) repeatEvery to be used standalone 
  
Applied Issue 6.2 and Issue 
  204

Pen is available. Who is 
next?

Thanks!

Regards,
Alex Yiu

Alex Yiu 
wrote: 

Diane,

Thanks! I got the pen. "Roger" 
.... :-) 

Regards,
Alex Yiu

Diane Jordan wrote: 

Thanks Assaf and Peter.   

Alex, 
I 
think the pen goes to you now - here are my notes from the last 
call: 
Alex will do 6.2 and 204, and fix the error he found: grammar mistake for 
<onAlarm> (repeatEvery can be used on its own) 

Let us know if this is ok. 
  
Thanks. 
 
Regards, Diane
IBM  Emerging Internet Software 
Standards

(919)254-7221 or 8-444-7221, Mobile: 919-624-5123, Fax 
845-491-5709

----- Forwarded by Diane Jordan/Raleigh/IBM on 12/05/2005 11:21 PM 
----- 

  
  

    Assaf Arkin <> 
      
12/05/2005 10:30 PM 
      

    

      
        
        

          
            
To

          Peter 
            Furniss <> 
        

          
            
cc

          Francisco 
            Curbera/Watson/IBM@IBMUS, Diane Jordan/Raleigh/IBM@IBMUS,  
        

          
            
Subject

          Re: [wsbpel-spec-edit] 
            Notes from Nov 22 call

      
        
        

          
          

Peter,

You can mark both 209 
and 214 as fixed.

For 214, I added the following text in 
13.5.1:

When using the <fromPart> elements, each <fromPart> 
element constitutes 
a declaration of a variable of that name within an 
implicit scope 
associated with the event handler. The variable type is 
derived from the 
type of the corresponding message part.

This makes 
the use of fromPart element and variable attribute 
consistent: both declare 
the named variable in the onEvent implicit 
scope using the message 
type/element (variable attribute) or message 
part type (fromPart 
element).

Assaf

Peter Furniss wrote:

>I have marked 
82.3, 99, 107 and 109 as In spec as of 30 November.
>
>There are 
notes against 209 and 214 (see
>http://www.choreology.com/external/WS_BPEL_issues_list.html#edit_table)
>that these resolutions were included but aren't quite right. 
Are these
>qualifications correct or have they 
>been sorted 
out.
>
>
>scores now are 14 open, 9 resolution proposed, 4 
received, and 12
>resolved-needing-editing, 229 finished. Nearly there 
!
>
>Peter
>
>-----------------------------------
>Chief 
Scientist
>Choreology Ltd
>web: www.choreology.com   
<-- now with Cohesions 3.0 available for
>download 
!
>
>email:   
>phone:   +44 20 8313 1833
>mobile:  +44 7951 
536168
>
>
>
>  
>
>>-----Original 
Message-----
>>From: Francisco Curbera [mailto:]
>>Sent: 30 November 2005 21:34
>>To: Diane 
Jordan
>>Cc: 
>>Subject: Re: [wsbpel-spec-edit] Notes from Nov 22 
call
>>
>>
>>I completed my edits, sorry it took 
longer than I
>>anticipated. Incorporating 107 into 82 was a bit 
messier than 
>>expected and I had to draft Rania to help me make sense 
of it 
>>all. The pen goes to Assaf, I 
believe.
>>
>>Paco
>>
>>
>>
>> 
                      
                      
                 
>> 
                      
                      
                      
 
>>                 
     Diane               
                    

>>                   
                      
                      
     
>>             
         Jordan/Raleigh/IB       
 To:       
>><>                   
    
>>           
>> 
                    
 M@IBMUS                  cc: 
           
>>       
                      
                      
                 
>> 
                      
                      
  Subject:  
>>[wsbpel-spec-edit] Notes from Nov 22 call 
                    

>>           
>>     
                 11/22/2005 01:24 
                      
 
>>                 
                      
                      
       
>>           
           PM           
                      
     
>>             
                      
                      
           
>>       
                      
                      
           
>>       
                      
                      
                
 
>>
>>
>>
>>
>>
>>Attendees: 
 Alexandre, Prasad, Dieter, Alex, Vinky, Diane
>>
>>Work 
plan:
>>Paco is working on 82.3, 99, 107, 109
>>Assaf (if 
available) to complete 209 and 214 when Paco is
>>done Alex will do 6.2 
and 204, and fix the error he found: 
>>grammar mistake for 
<onAlarm> (repeatEvery can be used on its 
>>own) Vinky will do 
82.2 Alexandre will do 230, 233 As usual 
>>when you complete an 
assignment please send an email alerting 
>>the team that the pen 
should go to the next person in the list.
>>
>>Other 
discussion:
>>
>>   Dieter is working on the proposals to 
vote for the
>>compensation related
>>   
issues.
>>   Vinky reported that 84 doesn't look very big - he's 
found 
>>8-10 instances
>>   of static analysis checking 
mandated by the spec.
>>   125 is complete in the spec 
now.
>>   I will start investigating bugzilla and/or the action 
item 
>>list on the
>>   subgroup web site for tracking 
editorial to do's (like the grammar
>>   mistake Alex found). 
 Will have a suggestion by the first 
>>meeting in
>> 
  Jan.  Fall back will be a spread sheet.  Here is one I've 

>>been using
>>   (which requires manual merge with 
issues list editing work list) :
>>   Oasis is moving to a new 
document retention system.  This seems to
>>   include 
improvements in the storage and url's for 
>>documents which 
we
>>   will look forward to.  At present, unless one of this 
team 
>>sees a good
>>   reason, for the editing itself 
I'd suggest we stick with 
>>our current
>>   environment 
on source forge rather than trying to switch horses -
>>   
however, if you have a different view, please let us know 
>>as I 
haven't
>>   tried to research the new system and am just reacting 
to 
>>the possible
>>   disruption any change can 
entail.
>>
>>For those who are celebrating it, happy 
thanksgiving - to all
>>others, have a happy day anyway. Regards, Diane 
IBM  Emerging 
>>Internet Software Standards  (919)254-7221 
or 
>>8-444-7221, Mobile: 919-624-5123, Fax 
845-491-5709
>>
>>
>>
>>#### issues for 
editing team nov 22.xls has been removed from
>>this note on November 
30, 2005 by Francisco Curbera
>>
>>   
 
>>
>
>
> 
 
>

 

This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, you should delete this message. 

Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
Next in thread → Next in month →