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 document.

Changes: 9 Oct 2003 - new issue

To comment on this issue, please follow-up to this announcement on the 
 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 message.

To add a new issue, 
see the issues procedures document (but the address for new issue submission is the sender of this announcement).