OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Issue - 292 - Inconsistent statements regarding start activities


This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if a motion to open the issue is proposed and that motion is approved by the TC. A motion could also be proposed to close it without further consideration. Otherwise it will remain as "received".

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 version of the document entitled in the "Issues" folder of the WSBPEL TC document list - the next posting as a TC document 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 - 292 - Inconsistent statements regarding start activities

Status: received
Date added: 2 Jun 2006
Date submitted: 02 June 2006
Submitter: Thomas Schulze
Document: WS-BPEL 2.0 Committee Draft, section 5.5.
Description: Action Item #124 addresses a minor change in one of the statements regarding start activities. Because this is a normative change AI #124 will be closed and is addressed by this issue.

Section 5.5 currently states:

"A start activity is a <receive> or a <pick> activity annotated with a createInstance="yes" attribute. Each business process MUST contain at least one start activity. See section 10.4 for more details on start activities."

Section 13.1.3 (paragraph Omission) currently states:

"Note that it is allowed to omit the start activity in an Abstract Process as well (see section 13.1.3. Hiding Syntactic Elements, [5])."

Section 13.4.3 currently states:

"All start activities MUST be defined in a process of this Template Profile. That is, every IMA with a createInstance="yes" attribute that is added during Executable Completion MUST replace an opaque activity with template:createInstance="yes". No new start activity is allowed to be added during Executable Completion."

These statements are inconsistent. The first says that EACH business process must contain at least one start activity. That's not true for abstract processes.
Submitter's proposal: Change the text in section 5.5 to say:

"A start activity is a <receive> or a <pick> activity annotated with a createInstance="yes" attribute. Each executable business process MUST contain at least one start activity. See section 10.4 for more details on start activities."

Links: related to issue 247
Changes: 2 Jun 2006 - new issue

To comment on this issue (including whether it should be accepted), 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 - 292 - [anything]" or is a reply to such a message. If you want to formally propose a resolution to an open issue, please start the subject line "Issue - 292 - Proposed resolution", without any Re: or similar.

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


**********
This email originates from Steria Limited, registered office: Three Cherry Trees Lane, Hemel Hempstead, Hertfordshire HP2 7AH; Registration Number 2706218; www.steria.co.uk

This email and any attachments may contain confidential/copyright information and is only for the use of the addressee. You are prohibited from copying, forwarding, disclosing or otherwise using it in any way if you are not the addressee or responsible for delivery.

If you receive this email by mistake please advise the sender immediately.

If you are subject to the Freedom of Information Act then Steria requests that you consult with Steria prior to releasing any information contained within this email or any attachments.

Steria may monitor the content of emails within its network to ensure compliance with its policies and procedures.

This email and its attachments are subject to and do not create or vary any contractual relationship between Steria Limited and the recipient.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]