Issue 14878: Visibility and permissions for Data Objects and Properties must be described (bpmn2-ftf)
Source: Ataway (Mr. Mariano Benitez, mariano(at)benitez.nu)
Nature: Revision
Severity: Significant
Summary: We should be clear in the spec the places/actions that can read and write on a DataObject or Property.


For example: is it valid to update an activity property in another activity? We should be extensive in this, otherwise it will be left to vendor interpretation and this can create confusion.

This was discussed in the BPMN 2.0 FTF in December 2009.
Resolution: Under section 10.3.1 Data Modeling, paragraphs name "Lifecycle and Visibility" clearly defines the visibility and permissions for Data Object and Properties.
Hence, this issue is already answered in the specification, and no change is required.
Disposition: Closed, No Change
Revised Text: 
Actions taken:
December 17, 2009: received issue
October 21, 2010: closed issue
Discussion: 

End of Annotations:=====
iler: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 23 Dec 2009 14:54:18 -0500
To: bpmn2-ftf@omg.org
From: Juergen Boldt <juergen@omg.org>
Subject: OMG Issue Created 14877




From: webmaster@omg.org
Date: 17 Dec 2009 11:18:03 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report

*******************************************************************************
Name:          Mariano Benitez
Company:       Oracle
mailFrom:      mariano.benitez@oracle.com
Notification:  No
Specification: BPMN 2.0
Section:       14.2
FormalNumber:  DTC-09-08-14
Version:       Beta
RevisionDate:  Aug 09
Page:          392
Title:         Execution semantics for Data Objects and Properties must be enhanced to properly describe concurrent modification situations
Nature:        Revision
Severity:      Significant
test:          3qw8
B1:            Report Issue

Description:

Does it make sense to describe the runtime behaviour of updating DataObjects and/or Properties by different executions? 

Should we leave this up to interpretations by implementers? Should we describe the expected behaviour or multiple executions updating the same DataObject/Property. This is specially important for multi-instance activities