Issue - 248 - clarification the namespace nature of child element under <extensionActivity>

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

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 - 248 - clarification the namespace nature of child element under <extensionActivity>

Status: received
Date added: 20 Mar 2006
Categories: Syntax
Date submitted: 20 March 2006
Submitter: Kwok Lun Yiu
Description:

In the Yaron's proposal of issue 111 : Extension Activities for <extensionActivity> (amended by me to change the name from extensionActivityWrapper to extensionActivity), the spec text does not explicitly say namespace nature of that child element (i.e. "##any", "##other" or ... ?).

In the XSD in Yaron's proposal, it seems to refer to "##any" the default of namespace attr of xsd:any.

We should stay the namespace expectation explicitly in the spec text and reflect that in the spec text.
Submitter's proposal: I would propose to use "##other".
Changes: 20 Mar 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 - 248 - [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 - 248 - 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).