BPMN2 — Misleading copy/paste para regarding Properties

In the Lifecycle and Visibility section of Properties, the second para is misleading. The Para starts with "The visibility of a Property" this may lead to the misconception that Properties have depictions, which they don't. The para also refers to Process as flow elements and the scope example below does not really present the concept very well.

Beta 1, August 2009 (pdf version)
(a) Page 183
Change: "A DataObject has a well-defined lifecycle, with resulting visibility constraints."
to
"A DataObject has a well-defined lifecycle, with resulting access constraints."
(b) Page 184
Change: "Data Object elements are visible in a Process diagram."
to
"Data Object elements are visually displayed on a Process diagram."
(c) Page 186
Change heading "Lifecycle and Visibility"
to "Lifecycle and Accessability"
Change: "The visibility of a Data Object is driven by its lifecycle. "
to
"The accessibility of a Data Object is driven by its lifecycle. "
Change:
"Data object 1" is visible to: "Process A," "Task A," "Sub-Process A," "Task B," "Sub-Process B," "Sub-Process C,"
"Task C," and "Task D."
"Data object 2" is visible to: "Sub-Process A" and "Task B."
"Data object 3" is visible to: "Sub-Process B," "Sub-Process C," "Task C," and "Task D."
"Data object 4" is visible to: "Sub-Process C" and "Task C."
to
"Data object 1" can be accessed by: "Process A," "Task A," "Sub-Process A," "Task B," "Sub-Process B," "Sub-Process C," "Task C," and "Task D."
"Data object 2" can be accessedby: "Sub-Process A" and "Task B."
"Data object 3" can be accessed by: "Sub-Process B," "Sub-Process C," "Task C," and "Task D."
"Data object 4" can be accessed by: "Sub-Process C" and "Task C."
(d) Page 188
Change
"Properties, like Data Objects, are item-aware elements. But, unlike Data Objects, they are not visible within a Process diagram."
to
"Properties, like Data Objects, are item-aware elements. But, unlike Data Objects, they are not visually displayed on a Process diagram."
Change
"Property elements are NOT visible in a Process diagram."
to
"Property elements are NOT visually displayed on a Process diagram."
(e) Page 189
Change heading "Lifecycle and Visibility"
to "Lifecycle and Accessability"
Change
"The visibility of a Property is driven by its lifecycle. The data within a Property can only be accessed when there is guaranteed to be a live Property instance present.
As a result, a Property can only be accessed by its parent Flow Element or, when its parent Flow Element is a Process or Sub-Process, then by the immediate children
of that Process or Sub-Process."
to
"The accessibility of a Property is driven by its lifecycle. The data within a Property can only be accessed when there is guaranteed to be a live Property instance
present. As a result, a Property can be accessed by its parent Process, Sub-process or Flow Element. In case the parent is a Process or Sub-Process, then a property
can be accesses by the immediate children (including children elements) of that Process or Sub-Process."
(f) Page 190
Change
The Properties of "Process A" are visible to: All elements (including children elements) of this Process
The Properties of "Sub-Process A" are visible to: "Sub-Process A" and "Task B."
The Properties of "Task C" are visible to: "Task C."
to
The Properties of "Process A" are accessible by: "Process A", "Task A", "Sub-Process A", "Task B", "Sub_Process B", "Sub-Process C", "Task C" and "Task D"
The Properties of "Sub-Process A" are accessible by: "Sub-Process A" and "Task B."
The Properties of "Task C" are accessible by: "Task C."
(g) Page 191
Change
"The DataInput is an item-aware element. DataInput elements may appear in a Process diagram to show the inputs to the Process as whole, which are passed along as
the inputs of Activities by DataAssociations"
to
"The DataInput is an item-aware element. DataInput elements are visually displayed in on a Process diagram to show the inputs to the Process as whole, which are
passed along as the inputs of Activities by DataAssociations."
(h) Page 193
Change
"The DataOutput is an item-aware element. DataOutput elements appear in a Process diagram to show the outputs of the Process as whole, which are passed along
from the outputs of Activities by DataAssociations."
to
"The DataOutput is an item-aware element. DataOutput elements are visually displayed on a Process diagram to show the outputs of the Process as whole, which are
passed along from the outputs of Activities by DataAssociations. "
Table 10.57 - DataAssociation model associations
Change
"Specifies an optional transformation expression. The actual scope of visible data for that expression is defined by the source and target of the specific data association
types."
to
"Specifies an optional transformation expression. The actual scope of accessible data for that expression is defined by the source and target of the specific data
association types."
(j) Page 202
Change
"The source of such a DataAssociation can be every item-aware element visible to the current scope, e.g., a Data Object, a Property or an Expression."
to
"The source of such a DataAssociation can be every item-aware element accessible in the current scope, e.g., a Data Object, a Property or an Expression."
Change
"The DataOutputAssociation can be used to associate a DataOutput contained within an ACTIVITY with any item-aware element visible to the scope the association
will be executed in. The target of such a DataAssociation can be every item-aware element visible to the current scope, e.g, a Data Object, a Property or an
Expression."
to
"The DataOutputAssociation can be used to associate a DataOutput contained within an ACTIVITY with any item-aware element accessible in the scope the
association will be executed in. The target of such a DataAssociation can be every item-aware element accessible in the current scope, e.g, a Data Object, a Property
or an Expression."
(k) Page 203
Change
"The visibility to the Expression language is defined based on the entities visibility to the Activity that contains the expression. All elements visible from the enclosing
element of an XPath expression must be made available to the XPath processor."
to
"The accessibility by the Expression language is defined based on the entities accessibility by the Activity that contains the expression. All elements accessible from the
enclosing element of an XPath expression must be made available to the XPath processor. "
Disposition: Resolved