Re: [wsbpel-spec-edit] call today 9:30 PDT

[Prasad Yendluri <pyendluri@webmethods.com>]

To save some time on the call, I thought I would volunteer to take some of the issues.
Looking through the issues, I believe Alex already took care of 37, 75, 94 and 114.
Also I guess we already applied 105 sometime back (though we just closed the issue at SFO f2f).

That leaves 1, 10, 34, 43, 44, 84, 126 and 128.

Working top down and leaving issues that are better handled by others, I can do 10,43 and 44.

Thanks, Prasad

------- Original Message --------

Subject:	[wsbpel-spec-edit] call today 9:30 PDT
Date:	Wed, 14 Jul 2004 08:26:32 -0700
From:	Satish Thatte <satisht@microsoft.com>
To:	bpel spec <wsbpel-spec-edit@lists.oasis-open.org>

Sorry about being tardy with this.  I have been swamped - vacations have
evil consequences.  We have a lot of issues to incorporate.  Once we
finish with this we are charged with producing a clean draft.  The focus
today should be on making a schedule for the resolved issues (list
below).  I realize that there is unfinished technical resolution
business related to Issue 10.

Satish

Issue 1
Permeability of scopes

Issue 10
Serialization of compensation

Issue 34
Dependency on Proprietary Specifications

Issue 37
Initiating Correlation Set More Than Once

Issue 43
Setting up Periodic Alarms

Issue 44
portType is duplicated on Invoke activity and partnerLinkType

Issue 75
Locally Scoped partnerLink declarations

Issue 84
Require Static Analysis Description & List

Issue 94
Allow both "compensate" and other activities in compensation or fault
handler

Issue 105
XML namespaces used in spec and examples need to be defined

Issue 114
Multiple Correlation Sets

Issue 126
Event Handlers with local partnerLinks & Correlation Sets

Issue 128
WS-I BP Incompatible WSDL Import