Issue - 97 - Optional Variable References in Abstract Processes

[ws-bpel issues list editor<peter.furniss@choreology.com>]

This issue has been added to the wsbpel issue list. The issues list is posted as a Technical Committee document to the OASIS WSBPEL TC pages on a regular basis. The current edition, as a TC document, is the most recent document with the title in the "Issues" folder of the WSBPEL TC document list - the next posting will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.

Issue - 97 - Optional Variable References in Abstract Processes

Status: open
Date added: 10 Feb 2004
Submitter: Dieter Koenig
Date submitted: 10 February 2004
Document: BPEL4WS 1.1 (May 5, 2003) and WSBPEL Working Draft 1 (Nov 23, 2003)
Description: Section 15.1. has a statement about making variable references optional in abstract
processes: "To simplify these common cases it is permissible, in abstract processes, to omit
the variable reference attributes from the <invoke/>, <receive/>, and <reply/> activities."

Consequently, for abstract processes, these references must also be optional in the <onMessage> and <onEvent> elements.
Submitter's proposal: For abstract processes, make variable references optional in the <onMessage> and <onEvent> elements.
Changes: 10 Feb 2004 - new issue

---

To comment on this issue, please follow-up to this announcement on the wsbpel@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - 97 - [anything]" or is a reply to such a message.

To add a new issue, see the issues procedures document (but the address for new issue submission is the sender of this announcement).