-
Key: BPMN2-195
-
Legacy Issue Number: 14772
-
Status: closed
-
Source: BPM Advantage Consulting ( Dr. Stephen White)
-
Summary:
Beta 1: Section 2 Conformance [Specification]: Explicitly define BPMN compliance criteria, with focus on "model" (as defined above) portability between tools.
##Source: IBM (Stephen A. White, wstephe@us.ibm.com)
##Original Issue: http://www.osoa.org/jira/browse/BPMN-301
##Original Info: (Severity: Significant - Nature: Enhancement)This is number 4 of 12 issues submitted by Bruce Silver
Explicitly define BPMN compliance criteria, with focus on "model" (as defined above) portability between tools. What elements and attributes MUST be supported. There can and should be multiple levels here. You don't have to certify it if you are explicit enough and connect it with #3 above. There will be no shortage of available tools that can check compliance.
-
Reported: BPMN 2.0b1 — Fri, 20 Nov 2009 05:00 GMT
-
Disposition: Resolved — BPMN 2.0
-
Disposition Summary:
Close this issue as a duplicate.
The resolution of issue 14240 will resolve this issue
Disposition: Duplicate -
Updated: Fri, 6 Mar 2015 20:57 GMT
BPMN2 — Section 2 Conformance [Specification]: Explicitly define BPMN compliance criteria, with focus on "model"
- Key: BPMN2-195
- OMG Task Force: BPMN 2.0 FTF