RE: [wsbpel] Issue 289 - final resolution

Thanks Chris.

Alex - do you agree with this?  Will
you be able to incorporate it when you apply 289?    

We haven't planned another editing pass
before the (hopeful) approval next week.  I'd like to have all the
known action items addressed in the version that we start the review with
if possible.  Of course, its always possible there may be more corrections
found that must be addressed before public review but we can hope for the
best.  ;-)   

Regards, Diane

IBM  Emerging Internet Software Standards



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

"Chris Keller"
<> 

08/17/2006 03:26 PM

Please respond to

<>

To

Diane Jordan/Raleigh/IBM@IBMUS

cc

Subject

RE: [wsbpel] Issue 289 - final resolution

Hi Diane,

 

One place needs to change for
this resolution is the following text in section 8.4.1 which states that
the service-ref element is in the WS-BPEL namespace:  Not sure if
this warrants an action item, or just something not to miss in the 289
resolution application.

 

“When using the partnerLink
variants of from-spec and to-spec with a non-partnerLink variant of the
respective from-spec and to-spec in a <copy> operation, the partnerLink
variants should be treated as if they produce an rvalue and lvalue of an
EII whose [local name] is “service-ref” and [namespace name] is the WS-BPEL
namespace.”

 

This should be change to:

 

“When using the partnerLink
variants of from-spec and to-spec with a non-partnerLink variant of the
respective from-spec and to-spec in a <copy> operation, the partnerLink
variants should be treated as if they produce an rvalue and lvalue of an
EII whose [local name] is “service-ref” and [namespace name] is the service
reference namespace (full URI here?).”

 

- Chris

 

From: Diane Jordan [mailto:]

Sent: Thursday, August 17, 2006 12:40 PM

To: 

Subject: [wsbpel] Issue 289 - final resolution

 

Issue 289 was resolved as proposed in http://www.oasis-open.org/apps/org/workgroup/wsbpel/email/archives/200608/msg00051.html

with the following changes: 

friendly amendment:  Change sentence to:  " The
WS-BPEL XML Schemas offer supplementary normative XML syntax details, such
as details regarding extensibility of a WS-BPEL process definition, as
long as those XML syntax details do not violate explicit normative descriptive
text. 

Also, use cap S for  schema to be consistent with rest of spec 

(Mark to open action item for one other case)

friendly amendment drop sentence:  A
summary of the additional constraints can be found in Appendix B. Static
Analysis requirement summary.

  

Regards, Diane

IBM  Emerging Internet Software Standards



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