Issue 18717: Annex B summary table (uml25-ftf) Source: (, ) Nature: Clarification Severity: Significant Summary: It would probably help implementers of Annex B if it had something like the tables in BPMN's DI that show example graphics, the metaclasses involved, and some notes on how they're used, see the BPMN spec (http://www.omg.org/spec/BPMN/2.0/PDF), starting at Table 12.8 (Depiction Resolution for Loop Compensation Marker) in Section 12.3 (Notational Depiction Library and Abstract Element Resolutions). Resolution: Revised Text: Actions taken: May 15, 2013: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 15 May 2013 09:15:20 -0400 To: Subject: Issue/Bug Report X-Brightmail-Tracker: AAAAAR16K/s= X-Brightmail-Tracker: AAAAAA== ******************************************************************************* Name: Raphael Barbau Employer: NIST mailFrom: raphael.barbau@nist.gov Terms_Agreement: I agree Specification: Unified Modeling Language Section: Annex B FormalNumber: ptc/12-10-24 Version: 2.5 beta 1 Doc_Year: 2012 Doc_Month: October Doc_Day: 01 Page: Title: Annex B summary table Nature: Clarification Severity: Significant CODE: 3TMw8 B1: Report Issue Remote Name: antlia.mel.nist.gov Remote User: HTTP User Agent: Mozilla/5.0 (Windows NT 5.1; rv:20.0) Gecko/20100101 Firefox/20.0 Time: 09:15 AM Description: It would probably help implementers of Annex B if it had something like the tables in BPMN's DI that show example graphics, the metaclasses involved, and some notes on how they're used, see the BPMN spec (http://www.omg.org/spec/BPMN/2.0/PDF), starting at Table 12.8 (Depiction Resolution for Loop Compensation Marker) in Section 12.3 (Notational Depiction Library and Abstract Element Resolutions). From: "Bock, Conrad" To: "uml25-ftf@omg.org" Date: Thu, 30 May 2013 15:42:51 -0400 Subject: RE: UML DI, Annex B table, 18717 Thread-Topic: UML DI, Annex B table, 18717 Thread-Index: Ac5dbXJpmgNHLHonRI2gqS6ZHSizXg== Accept-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US X-Virus-Scanned: amavisd-new at omg.org P.S. Attached is the kind of table we're thinking of for UML DI. What do people think? Conrad -----Original Message----- From: Maged Elaasar [mailto:melaasar@ca.ibm.com] Sent: Friday, May 10, 2013 1:32 PM To: Bock, Conrad Cc: uml25-ftf@omg.org Subject: Re: UML DI, Annex B table I think this would definitely be useful as a complement to DI. In a way, it is a less formal DG mapping. -----Original Message----- From: Bock, Conrad Sent: Thursday, May 09, 2013 2:31 PM To: uml25-ftf@omg.org Subject: UML DI, Annex B table UML diagram interchangers, I was wondering if it might be help implementers of Annex B if it had something like the tables in BPMN's DI that show example graphics, the metaclasses involved, and some notes on how they're used, see the BPMN spec (http://www.omg.org/spec/BPMN/2.0/PDF), starting at Table 12.8 (Depiction Resolution for Loop Compensation Marker) in Section 12.3 (Notational Depiction Library and Abstract Element Resolutions). What do you think? Conrad UML DI table.pdf UML DI table.pdf From: "Bock, Conrad" To: "uml25-ftf@omg.org" CC: "Raphael Barbau (raph85@gmail.com)" Date: Tue, 9 Jul 2013 09:29:14 -0400 Subject: RE: Draft resolutions for Ballot 7, Annex B, 18717 Thread-Topic: Draft resolutions for Ballot 7, Annex B, 18717 Thread-Index: Ac58ptNPMnzKRK3eTyy42myfcUpyXw== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Virus-Scanned: amavisd-new at omg.org Bran, These changes will be in the next version. > (3) The degree of indentation between different indentation levels > in the middle column is too tight, making it difficult to > distinguish them. I suggest using either increasing it and/or using > different bullet markers for different levels. Fixed this by using dashes. > (done) (4) Please use true guillemets and not the doubled-up "<" and > ">" characters (this is a reference manual, after all) Fixed, thx. > (2) It seems to me that it would be better to use UML element names > for the middle column rather than the names of the DI elements, > since the latter are not defined in the UML spec (thus, making the > UML spec dependent on the DI spec). As it stands, this looks more > like a table that belongs in the DI spec than the UML spec. I replied before, but to restate, UML is dependent on DI, at least for implementers of Annex B. Many of elements in an interchange file will be instances of DI classes. This avoids making a subclass of DI classes for every UML notational element. > (1) It is stated that the left column contains examples of the > notations, but they are, in fact, some combination of example and a > generic meta-notation. That is, in many cases, the text in the > figures refers to "meta-labels"such as "multiplicity", "property > name", rather than actual user-defined text. However, in other cases > (even within a single example), instead of the meta-labels actual > example text is used. Furthermore, it is not possible to distinguish > between a meta-label and an actual keyword such as the compartment > header names in a classifier. This is rather informal and likely to > be confusing. I think that it is possible to define some conventions > that will at least allow readers to distinguish between a keyword, a > meta-label (e.g., enclose them between angle brackets), and a > user-defined example text. The update will have the compartment headings corrected, and guillemets around where keywords are in the diagram. The left column space is too small for real examples, and using real example names would obscure the metaclass, so the names of the meta concepts are used, sometimes as substrings, but not the exact metaclass name string, so it won't be confused with metaclass names. Sometimes a number is added at the end when the same metaelement is used more than once. Can discuss more on the call. Conrad From: "Bock, Conrad" To: "Manfred R. Koethe" , "uml25-ftf@omg.org" Date: Fri, 12 Jul 2013 21:15:00 -0400 Subject: RE: Draft resolutions for Ballot 7, Annex B, 18717, checkin Thread-Topic: Draft resolutions for Ballot 7, Annex B, 18717, checkin Thread-Index: Ac5/ZdlmYKYzc2fORoSQ0mIekHoaRQ== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Virus-Scanned: amavisd-new at omg.org Manfred, et al, The update to 18717 (UML DI table) per the telecon is checked in as "UML DI table 20130712.doc" (also in odt and pdf if needed). The images seem to take awhile to open, but eventually do. Conrad Subject: Re: Draft resolutions for Ballot 7, Annex B, 18717, checkin From: "Manfred R. Koethe" Date: Fri, 12 Jul 2013 18:25:33 -0700 Cc: "uml25-ftf@omg.org" To: "Bock, Conrad" X-Mailer: Apple Mail (2.1508) X-Provags-ID: V02:K0:grO9FYVjvlfOYvCSr/cUYyYgCuD9TEhBDMdW/gVmuIG ODpNKaoz0fIu2WTqbEFsY1NedkzOGF+sXVCUp8RmhlCqLQA+L/ eF3gKfcUtC5NSygB3FtCht5hlECPpIONnDW7gf/KXqwRWmhB1T DoSDFxg1HSyJysrdAcJ6pAaOyjg+8ovfviNn4SHzvdu3rOjo3L pESCLP6QRbLU2fAAumv0Q/n0lWGs3Aa09nQBApI2XZGKymQNvT faBqW5ITBrh6BiQuiwoUMr28fg6nYdZT+c18454hIqIFP+Y7Th ABypox9T1UMLP6NtxWk+GPxB4MG9znxJDeXufWwIs3QoulSO5b jvYXxI6ezK6NEZKMpLF6SbEryVjOx4p7EEmP2/RbCKpGg4AACV W5EmvibosJwxg== X-Virus-Scanned: amavisd-new at omg.org Thanks, Conrad. Have a nice weekend, Manfred On Jul 12, 2013, at 18:15 , "Bock, Conrad" wrote: Manfred, et al, The update to 18717 (UML DI table) per the telecon is checked in as "UML DI table 20130712.doc" (also in odt and pdf if needed). The images seem to take awhile to open, but eventually do. Conrad --------------------------------------------------------------- Manfred R. Koethe 88solutions Corporation tel: +1 (510) 246 8611 fax: +1 (815) 550 2086 mailto: koethe@88solutions.com web: http://www.88solutions.com --------(Model-Driven Modeling Solutions)--------