Issue 15744: Table 8.14: Example for BPMN's extension mechanism is not schema-valid (bpmn2-rtf) Source: Camunda Services GmbH (Mr. Falko Menge, falko.menge(at)camunda.com) Nature: Revision Severity: Significant Summary: The example for BPMN's extension mechanism in Table 8.14 on page 61 (PDF 91) is not valid with respect to the XML Schema. The example uses Extension Elements that are already defined in BPMN as part of ioSpecification, namely dataInput, dataOutput, inputSet, and outputSet. To be valid BPMN, those elements must be contained in an 'extensionElements' element and reside in an own XML namespace. I'd suggest to use different Extension Elements to avoid confusion with existing BPMN elements. Resolution: Revised Text: Actions taken: October 15, 2010: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 15 Oct 2010 04:27:05 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Falko Menge Employer: camunda services GmbH mailFrom: falko.menge@camunda.com Terms_Agreement: I agree Specification: BPMN Section: 8.2.3 Extensibility FormalNumber: dtc/2010-06-05 Version: 2.0 Doc_Year: 2010 Doc_Month: June Doc_Day: Day Page: 61 (PDF 91) Title: Table 8.14: Example for BPMN's extension mechanism is not schema-valid Nature: Revision Severity: Significant CODE: 3TMw8 B1: Report Issue Description: The example for BPMN's extension mechanism in Table 8.14 on page 61 (PDF 91) is not valid with respect to the XML Schema. The example uses Extension Elements that are already defined in BPMN as part of ioSpecification, namely dataInput, dataOutput, inputSet, and outputSet. To be valid BPMN, those elements must be contained in an 'extensionElements' element and reside in an own XML namespace. I'd suggest to use different Extension Elements to avoid confusion with existing BPMN elements.