Re: [wsbpel-spec-edit]issues 222,224,225,157

Title: [wsbpel-spec-edit]issues 222,224,225,157

Hi Vinky,

I guess the "duplication" you mentioned is referring to the 3-section
structure (core, abstract, exec) in BPEL 1.1 spec. 

Per passed resolution of Issue 82 and open issue 158, I guess we would
like to collapse into a two section structure (exec and abstract).
(Abstract process is a super set of exec process)

http://www.choreology.com/external/WS_BPEL_issues_list.html#Issue158

The example you mentioned is just a tip of ice-berg of this 3-to-2
collapse work.

I hope I have provided more context. 

Regards,

Alex Yiu

Mehta, Vinkesh (US - Austin) wrote:

  
  
  
  
  

  
  
Hello,
  

  
I have finished adding edits for
issues 222 ,224,225 &157 as described in the approved proposal. 
  

  
On 157 proposal there were 2
examples with errors. I have corrected these errors ( Alex has verified
the change).
  

  
Other than that for 222, as
mentioned earlier, I would like to do some more cleanup. We can discuss
this in tomorrows meeting.

  
The 'correlation consistency
constraint' information has been duplicated in two places in the
document.
  

   - Section 10.2
  

   - Section 14.3
  

  
I believe the Section 10.2
information is stale ( eg: it is missing information regarding
bpws:correlationViolation).
  

  
Is there any reason why it is
duplicated? Can I change section 10.2 to reference 14.3 and remove the
duplicate information from 10.2?

  
Regards,
  

  -Vinky
  

  

  

  

  

  

  

  

  
Vinkesh O. Mehta 
  

  Manager
  

  Deloitte
Consulting LLP
  

   
  

  Tel: 
+1 512 226 4261
  

  Main:
+1 512 691 2300 
  

  Fax:
+1 512 480 1261 
  

  Mobile:
+ 1 512 750 2006 
  

  
  
  

  www.deloitte.com 
  

   
  

  400
West 15th Street, Suite 1700
  

  Austin,
TX 78701-1648
  

  USA
  

  

  

  

  

  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]