-
Key: BPMN2-265
-
Legacy Issue Number: 15082
-
Status: closed
-
Source: International Business Machines ( Ms. Suzette Samoojh)
-
Summary:
Extending via inheritancy is problematic using the BPMN xsd format.
The presence of the 'any' element on tBaseElement creates issues if you create subclasses that reside in a non-BPMN namespace. You cannot add elements to the subclass without violating the Unique Particle Attribution (UPA) rule in XML Schema (http://www.w3.org/TR/2004/PER-xmlschema-1-20040318/structures.html#non-ambig)
-
Reported: BPMN 2.0b1 — Wed, 24 Feb 2010 05:00 GMT
-
Disposition: Resolved — BPMN 2.0
-
Disposition Summary:
(a) Update tBaseElement and tBaseElementWithMixedContent in the XSD (see Semantic-Snippet.xsd attached to this issue)
(b) Update the XSD snippets (Table 8.17) in the spec
Disposition: Resolved -
Updated: Fri, 6 Mar 2015 20:57 GMT
BPMN2 — Extending via inheritancy is problematic using the BPMN xsd format
- Key: BPMN2-265
- OMG Task Force: BPMN 2.0 FTF