Re: [wsbpel-spec-edit] Fw: [wsbpel] Issue 190 - Wrong Spec Text

Thanks very much for taking care of
these so quickly. 

Regards, Diane

IBM  Emerging Internet Software Standards



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

Prasad Yendluri <>

01/11/2006 06:01 PM

Please respond to

pyendluri

To

Diane Jordan/Raleigh/IBM@IBMUS,


cc



Subject

Re: [wsbpel-spec-edit] Fw:
[wsbpel] Issue 190 - Wrong Spec Text

Folks,

I just checked in the changes for issues 162 and 190. 

162: added the clarification text "(i.e.
not within a nested scope)" for directly nested scopes text.

190: fixed up the footnote per Dieter's note.

Regards,

Prasad

Prasad Yendluri wrote:

Hi Diane,

Does anyone have the pen at this point? If not, I can take the pen to do
both the 162 one and this one. Both are very minor and I should take care
of it pretty quickly.

Regards,

Prasad

Diane Jordan wrote:

Peter, 

Please put this one back on the work queue for the spec editing team.  

Thanks as always for your help with the list. 

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 01/11/2006 12:36 PM -----

Dieter Koenig1 <>

01/11/2006 09:59 AM

To



cc

Subject

[wsbpel] Issue 190 - Wrong
Spec Text

The issue 190 resolution resulted in the introduction of the

exitOnStandardFault attribute on process and scope. In section 6.2, the

bullet list refers to a footnote that excludes joinFailure from the

standard fault handling:

"bpws:joinFailure generally represents a modeling error and hence
is

excluded from other standard faults in this case"

This footnote is wrong. It must read:

"bpws:joinFailure does not represent a modeling error and hence is
excluded

from other standard faults in this case"

This minor change should be handled by the spec editing team.

Kind Regards

DK

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

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