Issue 14730: Initializing and updating properties is not straight-forward (bpmn2-rtf)
Source: International Business Machines (Mr. Matthias Kloppmann, matthias.kloppmann(at)de.ibm.com)
Nature: Revision
Severity: Minor
Summary: From examples meeting on 2009.03.26:
When creating the looping example for <a href="http://www.osoa.org/jira/browse/BPMN-281" title="V0.5.6: Section 10.3 Data [Data]: Assignments not defined"><strike>BPMN-281</strike></a>, it is not obvious how to initialize properties. Also, updating a property via a dataInputAssociation or dataOutputAssociation is unnecessarily complicated because sourceRef and targetRef are currently mandatory elements, but not really applicable for properties.
Proposal:
(1) Introduce a new entity "initializationAssignment" (or better name) as a contained element for property (and data object for symmetry reasons), which has the same structure as assignment, but with an optional "to" element.
(2) Make dataInputAssociation::sourceRef and ::targetRef optional, likewise dataOutputAssociation::sourceRef and ::targetRef.
Comments:
From: trickovic created: Tue, 7 Apr 2009 04:00:15 -0500 (CDT)
As per 4/6 BPMN 2.0 meeting: Defer <a href="http://www.osoa.org/jira/browse/BPMN-471" title="Initializing and updating properties is not straight-forward">BPMN-471</a>.
Resolution:
Revised Text:
Actions taken:
November 20, 2009: received issue
Discussion:
This issue can be handled by an RTF.
Disposition: Deferred
End of Annotations:=====
s is issue # 14730
[OMG 14730] Initializing and updating properties is not straight-forward
##Source: IBM (Matthias Kloppmann, matthias-kloppmann@de.ibm.com)
##Original Issue: http://www.osoa.org/jira/browse/BPMN-471
##Original Info: (Severity: Minor - Nature: Revision)
From examples meeting on 2009.03.26:
When creating the looping example for BPMN-281, it is not obvious how to initialize properties. Also, updating a property via a dataInputAssociation or dataOutputAssociation is unnecessarily complicated because sourceRef and targetRef are currently mandatory elements, but not really applicable for properties.
Proposal:
(1) Introduce a new entity "initializationAssignment" (or better name) as a contained element for property (and data object for symmetry reasons), which has the same structure as assignment, but with an optional "to" element.
(2) Make dataInputAssociation::sourceRef and ::targetRef optional, likewise dataOutputAssociation::sourceRef and ::targetRef.
Comments:
From: trickovic created: Tue, 7 Apr 2009 04:00:15 -0500 (CDT)
As per 4/6 BPMN 2.0 meeting: Defer BPMN-471.