Issue - 146 - Making tVariable Extensible

[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 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 - 146 - Making tVariable Extensible

Status: open
Categories: Syntax and validation
Date added: 15 Jul 2004
Submitter: Yaron Y. Goland
Date submitted: 15 July 2004
Description: The schema currently says:
<complexType name="tVariable">
<!-- variable does not allow extensibility elements
because otherwise its content model would be non-deterministic -->
	<attribute name="name" type="NCName" use="required"/>
	<attribute name="messageType" type="QName" use = "optional"/>
	<attribute name="type" type="QName" use = "optional"/>
	<attribute name="element" type="QName" use = "optional"/>
	<anyAttribute namespace="##other" processContents="lax"/>
</complexType> 
 Which means that one cannot add new values into tVariable. :Submitter's proposal: It is unclear to me why restricting the extensibility of tVariable is 
necessary to make the model deterministic. An ANY element would fit in 
just fine so we should add it.
Links: Yaron Y. Goland, 3 Mar 2004
Changes: 15 Jul 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 - 146 - [anything]" or is a reply to such a message. If you want to formally propose a resolution, please start the subject line "Issue - 146 - 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).