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: RE: [wsbpel] Issue - 268 - Proposal to vote

Suggest to add: "This constraint MUST be enforced statically " to the end of Mark's proposal.

The XML Schema alone cannot enforce this constraint *completely*, due to the mixed content that we need to support.


Alex Yiu

From Mark Ford <mark.ford@active-endpoints.com>
Sent Mon 5/1/2006 10:57 AM
To wsbpel@lists.oasis-open.org
Subject RE: [wsbpel] Issue - 268 - Proposal to vote

This issue was agreed to in the April 24-28 meeting but was lacking the exact spec text. The formal proposal for this issue is to adopt the following change into Section 8.4's description of the literal variant:
The fifth from-spec variant returns values as if it were a from-spec that selects the children of the <literal> element in the WS-BPEL source code. Those return values MUST consist of EIIs or Text Information Items (TIIs) only.
The fifth from-spec variant returns values as if it were a from-spec that selects the child of the <literal> element in the WS-BPEL source code. This value MUST be a single EII or Text Information Item (TII) only.
The schema also needs to change to only allow a single element within the <literal>

From: Mark Ford [mailto:mark.ford@active-endpoints.com]
Sent: Tuesday, April 25, 2006 8:32 AM
To: wsbpel@lists.oasis-open.org
Subject: RE: [wsbpel] Issue - 268 - Support for multiple children within literal variant

The specification text that allows for multiple child elements within a literal came from the pdf attached to the proposed resolution for Issue 125: Literal and Expression Assignment Semantics.
What's interesting though is that the text of the email exchanges between Alex and Yuzo in the above link refer to the literal having a single EII or TII as I am proposing below.
From the emails:
Yuzo writes:
 Can we say:
 a <literal> from-spec can be treated as if it were a from-spec that
 selects the child of the <literal> element, be it a TII or an EII?
Alex responds:
 Yes, we can say that: the <literal> returns either an EII or TII.
I don't see any discussion in the minutes from Oct 12 or 19 that detail how the resolution went from allowing a single child to multiple children.

From: ws-bpel issues list editor [mailto:peter.furniss@erebor.co.uk]
Sent: Friday, April 21, 2006 6:11 PM
To: wsbpel@lists.oasis-open.org
Subject: [wsbpel] Issue - 268 - Support for multiple children within literal variant

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 - 268 - Support for multiple children within literal variant

Status: received
Date added: 21 Apr 2006
Date submitted: 20 April 2006
Submitter: Mark Ford
Description: The literal variant of the copy operation currently allows support for multiple child elements like so:
    <literal xmlns:foo="http://example.com"> 
The issue is that this <literal> will always generate a bpel:selectionFailure when used since it results in multiple EII's (see Section 8.4.1 3rd paragraph)

I discussed this with Danny and Alex briefly during the Stuttgart face to face and the only scenario offered was that an extensibleAssign or some other extension activity would be able to handle the multiple children without an exception. Even with this scenario, I don't see why we should provide support for multiple children when it cannot be used by the core language. If an extensibleAssign wants to provide this behavior then perhaps it could also provide its own version of a <literal>.
Submitter's proposal: I propose that we drop support for multiple child elements within a literal due to this issue. The value of the literal should be restricted to a single EII or a single TII or empty. I also propose adding a statement that this MUST be caught during static analysis.
Changes: 21 Apr 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 - 268 - [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 - 268 - 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).

--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

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