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 - 282 - Achieve consistency in extension container element

This issue has been added to the wsbpel issue list with a status of "resolved". The TC agreed to accept the issue and agreed the resolution before it was added to the issues list. It has been added to the issue list purely for tracking purposes.

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 - 282 - Achieve consistency in extension container element

Status: received
Date added: 5 May 2006
Categories: Language Extension
Date submitted: 05 May 2006
Submitter: Simon D Moser
Description: During the San Jose F2F, we encountered an inconsistency in Section 12.7

The xml syntax for extension elements so far has a *, as shown below:

<process ...>
          <extension namespace="anyURI" mustUnderstand="yes|no"/>*
All other container elements in BPEL (variables, partnerLinks etc) have a "+".
Resolution: This issue was opened and resolved during the San Jose F2F

In order to achieve consistency, extension should also move to "+".

(This was applied to 5.2 during the ftf but the change also needs applying to the XSD )

Changes: 5 May 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 - 282 - [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 - 282 - 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).

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