Hi, all,

Here is the proposal for discussion for issue 294.2: Clarification namespace usage in Abstract and Executable Process:

====================================== [a] At the end of Section: "13.1.1. URI",

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

The Abstract Process syntax is denoted under the following namespace:

urn:oasis:names:tc:wsbpel:2.0:process:abstract

-------------------------------------- add:

-------------------------------------- The Abstract Process namespace URI does not apply to <property>, <propertyAlias> and <service-ref> elements. That means, these elements are not declared in the Abstract Process namespace and MUST be always identified with Executable Process namespace URI, even when used in the context of Abstract Processes.

Similarly, any XPath function defined by this specification are always identified with Executable Process namespace URI, even when they are used in an expression in an Abstract Process.

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

[b] Also formally incorporated the text suggested in action item #74: http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/action_item.php?action_item_id=1434

After these paragraph:

-------------------------- The following XPath extension functions are defined by WS-BPEL and MUST be supported by a WS-BPEL implementation: . getVariableProperty, described below . doXslTransform, described in section 8.4. Assignment These extensions are defined in the standard WS-BPEL namespace.

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

Add clarification text on XPath extension function for other NS, as follows:

-------------------------- WS-BPEL processor MAY make XPath extension function of other namespace available. The declaration [editor todo: add xref here] does NOT cover those XPath extension functions and XPath functions of other namespace must be always understood by WS-BPEL processor. If unrecognized XPath function is used and if it is detected by static analysis, the process defintion MUST be rejected.

Also, the XPath extension functions, as always required by XPath semantics, MUST not perform any side-effect operations visible to the WS-BPEL process.

Thanks!