Issue 6256: UML2 Super / association end naming convention (uml2-superstructure-ftf) Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org) Nature: Uncategorized Issue Severity: Summary: To be consistent with the convention of other names in the spec, the names of Region::transitions, ActivityGroup::edgeContents, and ActivityGroup::nodeContents should be singular (i.e. Region::transition, ActivityGroup::edgeContent, and ActivityGroup::nodeContent). Resolution: Revised Text: Actions taken: September 18, 2003: received issue March 9, 2005: closed issue Discussion: Region::transition no longer has an ‘s’ at the end, while ActivityGroup::nodeContent and ActivityGroup::edgeContent no longer exist. These were all the result of a series of changes that occurred during the finalization work. Disposition: Closed, no change End of Annotations:===== ubject: UML2 Super / association end naming convention X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: Branislav Selic Date: Thu, 18 Sep 2003 18:18:46 -0400 X-MIMETrack: Serialize by Router on D25ML05/25/M/IBM(Release 6.0.2CF1|June 9, 2003) at 09/18/2003 18:18:48, Serialize complete at 09/18/2003 18:18:48 To be consistent with the convention of other names in the spec, the names of Region::transitions, ActivityGroup::edgeContents, and ActivityGroup::nodeContents should be singular (i.e. Region::transition, ActivityGroup::edgeContent, and ActivityGroup::nodeContent). Bran Selic IBM Software Group -- Rational Software 770 Palladium Drive Kanata, Ontario, Canada K2V 1C8 ph. (613) 591-7915 fax (613) 599-3912 e-mail: bselic@ca.ibm.com Reply-To: From: "Conrad Bock" To: "uml2ftf" Subject: Issue 6256 Date: Sun, 14 Dec 2003 21:05:11 -0500 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal Hi Bran, Issue 6256 should be assigned to state machines. The part of it about activities is duplicate with 6675. Thanks, OMG Issue 6256: Title: association end naming convention Source: International Business Machines (Mr. Bran Selic, mailto:%20bselic@ca.ibm.com) Summary: To be consistent with the convention of other names in the spec, the names of Region::transitions, ActivityGroup::edgeContents, and ActivityGroup::nodeContents should be singular (i.e. Region::transition, ActivityGroup::edgeContent, and ActivityGroup::nodeContent). Discussion: This is a shared issue. In statemachines Region::transitions will be changed to Region::transition as proposed. Disposition: Resolved. From: Eran Gery To: Branislav Selic Cc: Guus Ramackers , UML Superstructure FTF Subject: RE: SM resolutions for ballot 5 Date: Mon, 19 Jan 2004 11:28:02 +0200 X-Mailer: Internet Mail Service (5.5.2656.59) Bran See inline. -----Original Message----- From: Branislav Selic [mailto:bselic@ca.ibm.com] Sent: Sun, January 18, 2004 9:11 PM To: Eran Gery Cc: Guus Ramackers; UML Superstructure FTF Subject: Re: SM resolutions for ballot 5 Thanks, Eran. (BTW, please use my new e-mail address and get rid of the old Rational one: it is no longer valid. The new one is in this e-mail.) I have some feedback now, but may have some more later as I review the proposed resolutions in more detail later: Issue 6229: Can you please provide the proposed diagram in your resolution text. I am really sorry to be so fussy, but, according to the formal OMG rules, we vote on the EXACT text (and graphics) and not a description of it -- the same goes for graphics. I may make an exception of metamodel changes in some cases, but even those should, in principle, be explicit. [EG] I will fix that for the ballot. The question I have is whether in order to get feedback we can send out drafts that outline the resolutions, and the have the final thing in the ballot. Also in terms of process it is more efficient, as if the FTF pushes back on a resolution outline there's no point to spend the time and do all this fine tuning. Issue 6256: I guess this has to be completed with the activities changes. So, until Conrad provides the appropriate changes, I do not think this is closed. Also, are there not text changes accompanying this: in the description of the associations of the corresponding metaclasses. Those too should be included in the resolution text. Until those changes are in there, I cannot consider this solution adequate. [EG] OK - So I will remoe it from the ballot. Issue 6381: It would be nice if we had agreement from Alan Moore (who raised the issue) before we submitted this one for a vote. [EG] I believe I have well addressed Alan's request for clarification. Also, I do not see anything controvercial here. Nevertheless I will solicit his feedback on the proposal. Issue 6395: The problem with this resolution is that (a) it creates backward compatibility problems (at least for Rose RT users) and (b) I do not agree that changing the trigger is tantamount to changing a feature definition. In most cases, it changes the way that an event is handled in a given state -- it does not remove the operation. I would like more discussion on this resolution. [EG] I will remove it from ballot5 then. By definition it can't be a backward compatibility issue as inheritance was not specified in UML 1. So compatibility should not be part of the debate. To repeat, I apologize for being such a stickler to precise formats, but I think that this is the only way that we can ensure that there are no misunderstandings about what goes into the final text of the revised submission. I plan to enforce this discipline consistently throughout the process. Thanks, Bran Selic Distinguished Engineer IBM Rational Software 770 Palladium Drive Kanata, Ontario, Canada K2V 1C8 ph. (613) 591-7915 fax (613) 599-3912 e-mail: bselic@ca.ibm.com Eran Gery 01/18/2004 01:25 PM To: UML Superstructure FTF cc: Guus Ramackers , "Bran Selic (E-mail)" Subject: SM resolutions for ballot 5 Attached 11 proposed resolution for Statemachines. Most are trivial, few less... Thanks, Eran #### SM-proposals-ballot5.doc has been removed from this note on January 18, 2004 by Branislav Selic OMG Issue No: 6256 Title: UML2 Super / association end naming convention Source: International Business Machines (Mr. Bran Selic, bselic@ca.ibm.com) Summary: To be consistent with the convention of other names in the spec, the names of Region::transitions, ActivityGroup::edgeContents, and ActivityGroup::nodeContents should be singular (i.e. Region::transition, ActivityGroup::edgeContent, and ActivityGroup::nodeContent). Discussion: Region::transition no longer has an .s. at the end, while ActivityGroup::nodeContent and ActivityGroup::edgeContent no longer exist. These were all the result of a series of changes that occurred during the finalization work. Disposition: Closed, no change Conrad