Unnecessary finding: Difference found in attribute name (introduction of isInterrupting and parallelMultiple)

[tstephen]

Consider this excerpt from the A.1.0 reference model

  <semantic:startEvent name="Start Event" id="_93c466ab-b271-4376-a427-f4c353d55ce8">

The Yaoqiang 2 model writes the same thing as:

  <semantic:startEvent id="_93c466ab-b271-4376-a427-f4c353d55ce8" isInterrupting="true" name="Start Event" parallelMultiple="false">

The xml-compare tool reports:

• Difference found in attribute name (isInterrupting is added in the vendor file)
• Difference found in attribute name (parallelMultiple is added in the vendor file)

These added attributes are the defaults listed in the BPMN spec as follows:

1. Page 245 (PDF 275) Table 10.87 – Start Event attributes

  isInterrupting: boolean = true
  This attribute only applies to Start Events of Event Sub-Processes; it is ignored for other Start Events. 

So adding isInterrupting is not a semantic difference and I propose it be suppressed. I do note that this is not an Event Sub-Process but the spec is clear that it will be ignored in such cases.

1. Page 237 (PDF 267) Table 10.82 – CatchEvent attributes and model associations

  parallelMultiple: boolean = false
  This attribute is only relevant when the catch Event has more than EventDefinition (Multiple).

Similarly I propose the parallelMultiple finding be suppressed.