BPMN 2.0 FTF Avatar
  1. OMG Issue

BPMN2 — XML-Schema type for 'from' and 'to' elements in Data Assignment must not be abstract

  • Key: BPMN2-151
  • Legacy Issue Number: 14701
  • Status: closed  
  • Source: Oracle ( Ralf Mueller)
  • Summary:

    The XML-Schema type for elements "from" and "to" in complex type "tAssignment" is
    "tBaseElementWithMixedContent". However this type is declared abstract and forces to specify
    a xsi:type attribute for elements "from" and "to".
    The proposal is to use a non-abstract XML-schema type for "from" and "to" elements. A good
    candidate would be "tExpression" which is a non-abstract extension of "tBaseElementWithMixedContent":
    <xsd:complexType name="tAssignment">
    <xsd:extension base="tBaseElement">
    <xsd:element name="from" type="tExpression" minOccurs="1" maxOccurs="1"/>
    <xsd:element name="to" type="tExpression" minOccurs="1" maxOccurs="1"/>
    <xsd:attribute name="language" type="xsd:anyURI"/>

  • Reported: BPMN 2.0b1 — Thu, 19 Nov 2009 05:00 GMT
  • Disposition: Resolved — BPMN 2.0
  • Disposition Summary:

    1. Spec table 10.58
    a. Remove attribute "language".
    b. Modify attributes "from" and "to". Make both of type "Expression". Remove "body of the" from the attribute descriptions.
    2. XSD
    a. Remove attribute "language".
    b. Change the type of the "from" and "to" attributes in tAssignment to tExpression.
    c. Modify XSD snippet in Table 10.63 to match.
    3. UML metamodel
    a. Remove attribute "language".
    b. Change the "from" and "to" attributes in the Assignment class to be of type Expression.
    c. Replace Figure 10.61.
    Disposition: Resolved

  • Updated: Fri, 6 Mar 2015 20:57 GMT