Issue 15537: Page 221. Nonexistent attribute “optional” mentioned (bpmn2-rtf) Source: (, ) Nature: Revision Severity: Significant Summary: It says “The “optional” attribute defines if a DataInput is valid even if the state is “unavailable”. The default value is false. If the value of this attribute is true, then the execution of the Activity will not begin until a value is assigned to the DataInput element, through the corresponding Data Associations.” Problem: The “optional” attribute of “DatInput” is mentioned, but it is not shown in any Table or Figure (in particular Figure 10.59, p. 221; and Table 10.59, p. 222). This paragraph should be removed; or the attribute “optional” should be added in Table 10.59 and Figure 10.59. Resolution: Revised Text: Actions taken: September 17, 2010: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 16 Sep 2010 21:34:32 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Eduardo Jara Employer: mailFrom: ejara@craftware.net Terms_Agreement: I agree Specification: BPMN 2.0 Beta 2 Section: 10.3.1 FormalNumber: dtc/2010-06-05 Version: 2.0 Doc_Year: 2010 Doc_Month: June Doc_Day: Day Page: 221 Title: Page 221. Nonexistent attribute .optional. mentioned Nature: Revision Severity: Significant CODE: 3TMw8 B1: Report Issue Description: It says .The .optional. attribute defines if a DataInput is valid even if the state is .unavailable.. The default value is false. If the value of this attribute is true, then the execution of the Activity will not begin until a value is assigned to the DataInput element, through the corresponding Data Associations.. Problem: The .optional. attribute of .DatInput. is mentioned, but it is not shown in any Table or Figure (in particular Figure 10.59, p. 221; and Table 10.59, p. 222). This paragraph should be removed; or the attribute .optional. should be added in Table 10.59 and Figure 10.59.