Issue 9319: Unclear whether BPEL is part of Conformance (bpmn-ftf) Source: Adaptive (Mr. Pete Rivett, pete.rivett@adaptive.com) Nature: Uncategorized Issue Severity: Summary: Issue B) Unclear whether BPEL is part of Conformance Section 6.2 states "The BPMN specification supports for the following specifications is a normative part of the BPMN specification: BPEL4WS." but BPEL is not mentioned in the Conformance section 2 Resolution: Revised Text: a) Add the following paragraphs after paragraph 3: "This version of the specification does not specify a mechanism for exchange of BPMN diagrams. This version of the specification does not specify a mechanism for the exchange of the semantic model of a process depicted by a BPMN diagram." Note: Exchange of models of BPMN process semantics and diagrams is the subject of other ongoing standards activities. This version of the specification does not specify a normative mapping from BPMN to WSBPEL. Note: This version does provide a non-normative mapping from BPMN to WSBPEL, but the BPMN specification itself is known to be incomplete with respect to capturing all the required information for WSBPEL. So the mapping is insufficient, in any case." Section 2, page 1: b) Replace this section with the following text: "An implementation claiming conformance to this specification shall comply with all of the requirements set forth in subclauses 2.1, 2.2 and 2.3 below. 2.1 Visual Appearance A key element of BPMN is the choice of shapes and icons used for the graphical elements identified in this specification. The intent is to create a standard visual language that all process modelers will recognize and understand. An implementation that creates and displays BPMN Diagrams shall use the graphical elements, shapes and markers specified in clauses 8-10 as the diagrammatic elements that represent the specified concepts. Note: There is flexibility in the size, color, line style, and text positions of the defined graphical elements. The following extensions to a BPMN Diagram are permitted: o New markers or indicators MAY be added to the specified graphical elements. These markers or indicators could be used to highlight a specific attribute of a BPMN element or to represent a new subtype of the corresponding concept. (See also 2.4 below) o A new shape representing a kind of Artifact MAY be added to a Diagram, but the new Artifact shape SHALL NOT conflict with the shape specified for any other BPMN object or marker. o Graphical elements MAY be colored, and the coloring may have specified semantics that extend the information conveyed by the element as specified in this standard. o The line style of a graphical element MAY be changed, but that change SHALL NOT conflict with any other line style required by this specification. An extension SHALL NOT change the specified shape of a defined graphical element or marker. (e.g., changing a square into a triangle, or changing rounded corners into squared corners, etc.). 2.2 Structural Conformance An implementation that creates and displays BPMN diagrams shall conform to the specifications and restrictions in Clauses 9-10 with respect to the connections and other diagrammatic relationships between graphical elements. Where permitted or required connections are specified as conditional and based on attributes of the corresponding concepts, the implementation shall ensure the correspondence between the connections and the values of those attributes. In general, these connections and relationships have specified semantic interpretations, which specify interactions among the process concepts represented by the graphical elements. Conditional relationships based on attributes represent specific variations in behavior. Structural conformance therefore guarantees the correct interpretation of the diagram as a specification of process, in terms of flows of control and information. Throughout the document, structural specifications will be appear in paragraphs using a special shaped bullet: .. Example: .. A Task MAY be a target for Sequence Flow; it can have multiple incoming Flows. An Incoming Flow MAY be from an alternative path and/or a parallel paths. 2.3 Semantic Elements This specification defines many semantic concepts used in defining processes, and associates them with graphical elements, markers, and connections. To the extent that an implementation provides an interpretation of the BPMN diagram as a semantic specification of process, the interpretation shall be consistent with the semantic interpretation herein specified. Note -- The intent here is that a BPMN diagram used as a "workflow specification" will have the interpretation specified in this standard, somewhat extended or narrowed by the characteristics of the workflow system. Similarly, when a BPMN diagram used as a specification for the processes and interactions of software agents, any generated software will reflect the semantics of the diagram as specified in this standard, possibly narrowed or extended by the characteristics of the software implementation. 2.4 Attributes and Properties This specification defines a number of attributes and properties of the semantic objects represented by the graphical elements, markers, and connections. Some of these attributes are purely representational and are so marked, and some have required representations. Some attributes are specified as mandatory, but have no representation or only optional representation. And some attributes are specified as optional. For every attribute or property that is specified as mandatory, a conforming implementation SHALL provide some mechanism by which values of that attribute or property can be created and displayed. This mechanism SHALL permit the user to create or view these values for each BPMN object specified to have that attribute or property. Where a graphical representation for that attribute or property is specified as required, that graphical representation SHALL be used. Where a graphical representation for that attribute or property is specified as optional, the implementation MAY use either a graphical representation or some other mechanism. If a graphical representation is used, it SHALL be the representation specified. Where no graphical representation for that attribute or property is specified, the implementation MAY use either a graphical representation or some other mechanism. If a graphical representation is used, it SHALL NOT conflict with the specified graphical representation of any other BPMN object. 2.5 Extended and Optional Elements A conforming implementation is not required to support any element or attribute that is specified herein to be non-normative or informative. In each instance in which this specification defines a feature to be "optional", it specifies whether the option is in: o how the feature shall be displayed, o whether the feature shall be displayed o whether the feature shall be supported. A conforming implementation is not required to support any feature whose support is specified to be optional. If an implementation supports an optional feature, it SHALL support it as specified. A conforming implementation SHALL support any "optional" feature for which the option is only in whether or how it shall be displayed." Section 6.2, page 6: c) Change the heading to heading level 3 (i.e., make Section 6.1.1) d) Rename the heading to: "Abbreviations" e) Delete the first paragraph of the section. Actions taken: January 30, 2006: received issue April 19, 2007: closed issue Discussion: Resolution: Section 2 of the specification will be updated to clarify the conformance for BPEL and more general conformance considerations. End of Annotations:===== ubject: Issues on BPMN Date: Sun, 29 Jan 2006 21:17:59 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issues on BPMN Thread-Index: AcYlXIlAAqRKeKvQTICFTOCuE//pqQ== From: "Pete Rivett" To: Cc: These are ones I raised as part of my AB review, updated for the DAS numbering. Issue B) Unclear whether BPEL is part of Conformance Section 6.2 states "The BPMN specification supports for the following specifications is a normative part of the BPMN specification: BPEL4WS." To: bpmn-ftf@omg.org Subject: Proposed Resolution for Issue 9319 X-Mailer: Lotus Notes Release 7.0 HF242 April 21, 2006 From: Stephen A White Date: Thu, 19 Oct 2006 14:17:55 -0700 X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 7.0.1HF346 | August 4, 2006) at 10/19/2006 15:17:56, Serialize complete at 10/19/2006 15:17:56 This is intended for Ballot 4 http://www.bpmn.org/FTF/Issues/Issue%209319.htm Issue 9319: Unclear whether BPEL is part of Conformance Description: Issue B) Unclear whether BPEL is part of Conformance Section 6.2 states "The BPMN specification supports for the following specifications is a normative part of the BPMN specification: BPEL4WS." but BPEL is not mentioned in the Conformance section 2 Suggested Resolution: Resolved: Section 2 of the specification will be updated to clarify the conformance for BPEL and more general conformance considerations. Revised Text: Section 1, page 1: a) Add a new paragraph after paragraph 3: "This version of the specification does not specify a mechanism for exchange of BPMN diagrams. Furthermore, this version of the specification does not specify a mechanism for the exchange of the semantic model of a process depicted by a BPMN diagram." Section 2, page 1: b) Replace this section with the following text: "An implementation claiming conformance to this specification shall comply with all of the requirements set forth in subclauses 2.1, 2.2 and 2.3 below. 2.1 Visual Appearance A key element of BPMN is the choice of shapes and icons used for the graphical elements identified in this specification. The intent is to create a standard visual language that all process modelers will recognize and understand. An implementation that creates and displays BPMN Diagrams shall use the graphical elements, shapes and markers specified in clauses 9-10 as the diagrammatic elements that represent the specified concepts. Note: There is flexibility in the size, color, line style, and text positions of the defined graphical elements. The following extensions to a BPMN Diagram are permitted: New markers or indicators MAY be added to the specified graphical elements. These markers or indicators could be used to highlight a specific attribute of a BPMN element or to represent a new subtype of the corresponding concept. (See also 2.4 below) A new shape representing a kind of Artifact MAY be added to a Diagram, but the new Artifact shape SHALL NOT conflict with the shape specified for any other BPMN object or marker. Graphical elements MAY be colored, and the coloring may have specified semantics that extend the information conveyed by the element as specified in this standard. The line style of a graphical element MAY be changed, but that change SHALL NOT conflict with any other line style required by this specification. An extension SHALL NOT change the specified shape of a defined graphical element or marker. (e.g., changing a square into a triangle, or changing rounded corners into squared corners, etc.). 2.2 Structural Conformance An implementation that creates and displays BPMN diagrams shall conform to the specifications and restrictions in Clauses 9-10 with respect to the connections and other diagrammatic relationships between graphical elements. Where permitted or required connections are specified as conditional and based on attributes of the corresponding concepts, the implementation shall ensure the correspondence between the connections and the values of those attributes. In general, these connections and relationships have specified semantic interpretations, which specify interactions among the process concepts represented by the graphical elements. Conditional relationships based on attributes represent specific variations in behavior. Structural conformance therefore guarantees the correct interpretation of the diagram as a specification of process, in terms of flows of control and information. Throughout the document, structural specifications will be appear in paragraphs using a special shaped bullet: ? (a filled diamond) Example: ? A Task MAY be a target for Sequence Flow; it can have multiple incoming Flows. An Incoming Flow MAY be from an alternative path and/or a parallel paths. 2.3 Semantic Elements This specification defines many semantic concepts used in defining processes, and associates them with graphical elements, markers, and connections. To the extent that an implementation provides an interpretation of the BPMN diagram as a semantic specification of process, the interpretation shall be consistent with the semantic interpretation herein specified. Note -- The intent here is that a BPMN diagram used as a "workflow specification" will have the interpretation specified in this standard, somewhat extended or narrowed by the characteristics of the workflow system. Similarly, when a BPMN diagram used as a specification for the processes and interactions of software agents, any generated software will reflect the semantics of the diagram as specified in this standard, possibly narrowed or extended by the characteristics of the software implementation. 2.4 Attributes and Properties This specification defines a number of attributes and properties of the semantic objects represented by the graphical elements, markers, and connections. Some of these attributes are purely representational and are so marked, and some have required representations. Some attributes are specified as mandatory, but have no representation or only optional representation. And some attributes are specified as optional. For every attribute or property that is specified as mandatory, a conforming implementation SHALL provide some mechanism by which values of that attribute or property can be created and displayed. This mechanism SHALL permit the user to create or view these values for each BPMN object specified to have that attribute or property. Where a graphical representation for that attribute or property is specified as required, that graphical representation SHALL be used. Where a graphical representation for that attribute or property is specified as optional, the implementation MAY use either a graphical representation or some other mechanism. If a graphical representation is used, it SHALL be the representation specified. Where no graphical representation for that attribute or property is specified, the implementation MAY use either a graphical representation or some other mechanism. If a graphical representation is used, it SHALL NOT conflict with the specified graphical representation of any other BPMN object. 2.5 Extended and Optional Elements A conforming implementation is not required to support any element or attribute that is specified herein to be non-normative or informative. In each instance in which this specification defines a feature to be "optional", it specifies whether the option is in: how the feature shall be displayed, whether the feature shall be displayed whether the feature shall be supported. A conforming implementation is not required to support any feature whose support is specified to be optional. If an implementation supports an optional feature, it SHALL support it as specified. A conforming implementation SHALL support any "optional" feature for which the option is only in whether or how it shall be displayed." but BPEL is not mentioned in the Conformance section 2