wsbpel message

Subject: Issue - 84 - Require Static Analysis Description & List

From: ws-bpel issues list editor<peter.furniss@choreology.com>
To: wsbpel@lists.oasis-open.org
Date: Wed, 5 Nov 2003 19:26:54 +0000

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 - 84 - Require Static Analysis Description & List

Status: open
Date added: 5 Nov 2003
Submitter: Yaron Goland
Date submitted: 22 October 2003
Document: Main Spec
Description: BPEL's semantics depend on the use of static analysis before run time in order to prevent entire classes of errors, errors whose existence the spec assumes to be impossible at runtime and therefore makes no provisions to handle. Unfortunately the static analysis requirements as currently defined in the BPEL spec are implicit rather than explicit which makes portability very difficult as implementers have no way to be sure they have completely implemented all the static analysis steps the spec relies on.
Submitter's proposal: The BPEL spec be required to explicit define all static analysis checks that BPEL's semantics depend on in the text of the standard.

Add an appendix, much like the existing fault summary appendix, that will provide a single checklist of all static analysis requirements with a brief description of their function.
Changes: 5 Nov 2003 - 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 - 84 - [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).