[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [wsbpel] Issue 241 - Proposal for Vote
Hi all, [A] Here is the updated proposal for vote after factoring in Mark Ford's comment about disallowing explicit declaration of variables. PDF version: http://www.oasis-open.org/apps/org/workgroup/wsbpel/download.php/17037/wsbpel-specification-draft.241_proposal_v3.pdf MS Word version: http://www.oasis-open.org/apps/org/workgroup/wsbpel/download.php/17036/wsbpel-specification-draft.241_proposal_v3.doc Here is the highlight of changes in the proposal compared with the one that I sent on Monday: ------------------------ Variables referenced by variable attribute or <fromPart> element are implicitly declared in the associated scope of <onEvent>. If variable of the same name is declared explicitly in the associated scope, it would be considered a case of duplicated variable declaration and MUST be reported as error during static analysis. If variable attribute is used in the <onEvent>
element, either
messageType or element attribute MUST be provided in <onEvent>
element. This semantics MUST be enforced during static analysis. [B] A reminder: one more normative changes we need to make (but not a part of the PDF) is to amend/clarify resolution of Issue 123 in a very minor way as follow: From: "This resolution follows the same scoping rules as variable and correlationSet resolution." To: "This resolution follows the same scoping rules as correlationSet resolution." Thanks! Regards, Alex Yiu |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]