Issue 16554: Underspecification of ChoreographyLoopType (bpmn2-rtf)
Source:  (, )
Nature: Revision
Severity: Critical
Summary: The loop types of choreography activities do not provide any information about: (1) the "hard-coded" cardinality of the loop (how often is the loop repeated) or (2) the expression that must be evaluated during the choreography enactment based on the data contained in the messages exchanged up to that point during the enactment. In the latter case, specifying the expression is not enough: for reasons of enforceability, it should be possible to specified which participant(s) must evaluate the expression.
Resolution: 
Revised Text: 
Actions taken:
September 16, 2011: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 16 Sep 2011 09:44:24 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Michele Mancioppi
Employer:        IAAS, Stuttgart University
mailFrom:        michele.mancioppi@iaas.uni-stuttgart.de
Terms_Agreement: I agree
Specification:   Business Process Model and Notation (BPMN)
Section:         11.4.5
FormalNumber:    formal/2011-01-03
Version:         2.0
Doc_Year:        2011
Doc_Month:       January
Doc_Day:         03
Page:            335
Title:           Underspecification of ChoreographyLoopType
Nature:          Revision
Severity:        Critical
CODE:            3TMw8
B1:              Report Issue


Description:

The loop types of choreography activities do not provide any information about: (1) the "hard-coded" cardinality of the loop (how often is the loop repeated) or (2) the expression that must be evaluated during the choreography enactment based on the data contained in the messages exchanged up to that point during the enactment. In the latter case, specifying the expression is not enough: for reasons of enforceability, it should be possible to specified which participant(s) must evaluate the expression.