Issue 9321: compliance level to cover core elements/simple business modeling (bpmn-ftf) Source: Adaptive (Mr. Pete Rivett, pete.rivett@adaptive.com) Nature: Uncategorized Issue Severity: Summary: The start of section 8 has the following which suggests 2 levels of compliance; however this opportunity has been missed in the conformance section: "First, there is the list of core elements that will support the requirement of a simple notation. These are the elements that define the basic look-and-feel of BPMN. Most business processes will be modeled adequately with these elements. Second, there is the entire list of elements, including the core elements, which will help support requirement of a powerful notation to handle more advanced modeling situations." Resolution: Revised Text: Actions taken: January 30, 2006: received issue April 19, 2007: closed issue Discussion: See issue 9319 for disposition 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: Issue D) There should be a compliance level to cover core elements/simple business modeling The start of section 8 has the following which suggests 2 levels of compliance; however this opportunity has been missed in the conformance section: "First, there is the list of core elements that will support the requirement of a simple notation. These are the elements that define the basic look-and-feel of BPMN. Most business processes will be modeled adequately with these elements. Second, there is the entire list of elements, including the core elements, which will help support requirement of a powerful notation to handle more advanced modeling situations." Date: Fri, 09 Jun 2006 16:29:07 -0400 From: Ed Barkmeyer Reply-To: edbark@nist.gov Organization: NIST User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en, fr, de, pdf, it, nl, sv, es, ru To: Stephen A White CC: bpmn-ftf@omg.org Subject: corrected BPMN FTF Ballot #1 X-MailScanner-Information: Please contact postmaster@mel.nist.gov for more information X-MailScanner: Found to be clean X-MailScanner-SpamCheck: X-MailScanner-From: edbark@nist.gov X-Spam-Status: No Steve, I wrote: Issue 9320: BPEL Mapping Extraction to Appendix: Duplicate: This is a duplicate Issue since another Issue (9319) will address this topic. No. On the OMG website, Issue 9320 is about conformance of an interchange format. Issue 9321: BPEL Mapping Extraction to Appendix: Duplicate: This is a duplicate Issue since another Issue (9319) will No. On the OMG website, Issue 9321 is about a compliance point for the simple business modeling subset. I noticed, belatedly, that you corrected the titles in the revised ballot "with descriptions". But these No votes still stand. I think what has happened is that you are assuming that the resolution of 9319 will rewrite the entire conformance clause, and in so doing resolve these two issues. But 9319 is about BPEL conformance only. These issues are not duplicates. Whether they are actually resolved in Issue 9319 will depend on what the text of the resolution of 9319 looks like. And it is probably premature to ballot these two issues until the replacement conformance text is on the ballot. Issue 9322: BPEL Mapping is Hard to Follow: Duplicate: This is a duplicate Issue. This Issue is closely related to Issue 9139. As the moving of BPEL text is accomplished, recommendations for making the text clearer will be identified. No. On the OMG website, Issue 9322 is titled "BPEL is over-pervasive". And the resolution should really read: "Resolved in Issue 9139." And the explanation is that all the BPEL stuff is to be pulled out of the document, wherever it may be, and moved to the Annex, with occasional Notes in the text to refer to BPEL considerations. I will revise this No to a Yes But... Here you corrected the title, but the text of the resolution still goes with Issue 9323. It is non-responsive to 9322. That is, I agree with the resolution, but the text needs to be different in the FTF report. -Ed -- Edward J. Barkmeyer Email: edbark@nist.gov National Institute of Standards & Technology Manufacturing Systems Integration Division 100 Bureau Drive, Stop 8263 Tel: +1 301-975-3528