Legacy Issue Number: 14700
Source: Object Management Group ( Mariano Benitez)
Since it inherits from a base element with mixed content, it does not need to define itself as mixed.
From: firstname.lastname@example.org created: Tue, 19 May 2009 11:47:40 -0500 (CDT)
The 'mixed' setting does not need to be redeclared. It is transitively inherited. tExpression inherits it from tBaseElementWithMixedContent. tFormalExpression also (and thus it does not need to be redeclared there).
So there's a minor consistency issue (with tFormalExpression), but no technical issue to my knowledge.
[Reducing the severity based on this information.]
From: mariano.benitez created: Tue, 19 May 2009 12:23:01 -0500 (CDT)
suggest to defer but agree the resolution (remove mixed=True from tFormalExpression)
From: mariano.benitez created: Thu, 6 Aug 2009 09:20:03 -0500 (CDT)
Testing notification scheme
Reported: BPMN 2.0b1 — Thu, 19 Nov 2009 05:00 GMT
Disposition: Resolved — BPMN 2.0
Table 8.68, page 103 (133 pdf): remove attribute 'mixed="true"' in the tFormalExpression complex type definition.
Updated: Fri, 6 Mar 2015 20:57 GMT