Groups - New Action Item #0011 Editing team - Clarify small gap...

[monica.martin@sun.com]

OASIS Web Services Business Process Execution Language (WSBPEL) TC member,

Ms Monica Martin has created a new action item.

Number: #0011
Description: Editing team - Clarify small gap...
Owner: Mr Alexandre Alves


Comments:
Ms Monica Martin  2006-02-08 17:22 GMT
email 8 February 2006
[start]
We dictate static enforcement for those MEP that are not part of BP v1.1. But, we allow BP v1.1 configuration to be disabled. This creates a seeming gap. I am not saying we should necessarily allow these MEP but when not constrained by BP v1.1, this leaves the door open however. Should we not be specific in the case where WS-I BP v1.1 is used or regardless if the profile is enabled? I've proposed a minor editoral change assuming the latter.

Potential change from:
Finally a WS-BPEL processor MUST reject a WS-BPEL that refers to a portType that contain solicit-response or notification operations as defined in the WSDL 1.1 specification, this requirement MUST be statically enforced

Potential change to:
Regardless if the WS-I BP v1.1 profile configuration is enabled, a WS-BPEL processor MUST reject a WS-BPEL that refers to a portType that contain solicit-response or notification operations as defined in the WSDL 1.1 specification, this requirement MUST be statically enforced.

I believe our intent was to specify the allowed MEP (request-response and one-way MEP) regardless of whether BP v1.1 is enabled. Thanks. 
[end]

Approved TC teleconference call 8 February 2006
Email reference: http://www.oasis-open.org/apps/org/workgroup/wsbpel/email/archives/200602/msg00017.html

View Details:
http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/action_item.php?action_item_id=1219



PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

- OASIS Open Administration