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 - 74 - Ambiguity in join condition definition

The current spec says:

"If the explicit joinCondition is missing, the implicit condition requires
the status of at least one incoming link to be positive..."

I.e. if you don't specify any explicit join condition the implicit
condition is the ORing of the truth values of the incoming links.

Furthermore, the current spec says that

"The expression for a join condition for an activity MUST be constructed
using only Boolean operators and the bpws:getLinkStatus function (see
Expressions) applied to incoming links at the activity"

I.e. it is NOT possible to spec join conditions that refer to other
functions than getLinkStatus.

To avoid "mathematical subtleties" that can blow your mind (statements
about the empty set...), we need an explicit clarification for situations
where there are no incoming links at all.



Please respond to <ygoland@bea.com>

To:    <wsbpel@lists.oasis-open.org>
Subject:    RE: [wsbpel] Issue - 74 - Ambiguity in join condition

What is harmed if we allow join conditions on activities that don't have
links? Isn't it already possible to write a join condition that doesn't
refer to any form of link state in calculating its Boolean output?
    Just Curious,
 -----Original Message-----
 From: ws-bpel issues list editor [mailto:peter.furniss@choreology.com]
 Sent: Thursday, October 09, 2003 2:59 PM
 To: wsbpel@lists.oasis-open.org
 Subject: [wsbpel] Issue - 74 - Ambiguity in join condition definition

 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
 document with the title in the "Issues" folder of the WSBPEL TC document
 list - the next posting 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 - 74 - Ambiguity in join condition definition

 Status: open
 Date added: 9 Oct 2003
 Submitter: Dieter Roller
 Date submitted: 09 October 2003
 Description: The specs could possibly be interpreted in such a way that
 activities without an incoming link could also have a join condition. This
 is not the intended meaning.
 Submitter's proposal: Modify the first sentence in the second paragraph in
 section 12.5.1 as follows :
       Every activity that is the target of a link has an implicit or
       explicit joinCondition attribute associated with it; an activity
       that is not target of a link has no joinCondition attribute
       associated with it.
 Furthermore it may be helpful to have a similar sentence earlier in the
 Changes: 9 Oct 2003 - 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 - 74 - [anything]" or is a reply to such a

 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 mailing list (and be removed from the roster of
 the OASIS TC), go to

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