Issue 6310: UML2 Super/Profiles (uml2-superstructure-ftf) Source: The MathWorks (Mr. Alan Moore, alan.moore(at)mathworks.co.uk) Nature: Uncategorized Issue Severity: Summary: In figure 446, only packages that specialise Constructs::Package can contain a Profile Application. Whereas I think that the packages to which we need to apply profiles are those packages that specialise Kernel::Package Resolution: Revised Text: Actions taken: October 9, 2003: received issue March 9, 2005: closed issue Discussion: Well, Kernel is defined in the infrastructure, and construct is build in the superstructure. So I believe it is the way around : the opposite. Disposition: Closed, no change End of Annotations:===== From: "Moore, Alan" To: "'issues@omg.org'" Cc: "Branislav Selic (E-mail)" , "'DESFRAY Philippe'" Subject: UML2 Super/Profiles Date: Thu, 9 Oct 2003 11:31:45 +0100 X-Mailer: Internet Mail Service (5.5.2653.19) In figure 446, only packages that specialise Constructs::Package can contain a Profile Application. Whereas I think that the packages to which we need to Issue 6310: UML2 Super/Profiles (uml2-superstructure-ftf) Click here for this issue's archive. Source: ARTISAN Software Tools (Mr. Alan Moore, alan.moore@artisansw.com) Nature: Uncategorized Issue Severity: Summary: In figure 446, only packages that specialise Constructs::Package can contain a Profile Application. Whereas I think that the packages to which we need to apply profiles are those packages that specialise Kernel::Package Proposed correction Kernel is obtained by having merged Constructs and other packages. Every Kernel package is a construct package. So the present solution is more general, and ha the advantage to provide the exact same text for infra and superstructure. Discussion : Well, Kernel is defined in the infrastructure, and construct is build in the superstructure. So I believe it is the way around : the opposite. Disposition : Closed, no change. Issue 6310: UML2 Super/Profiles (uml2-superstructure-ftf) Click here for this issue's archive. Source: ARTISAN Software Tools (Mr. Alan Moore, alan.moore@artisansw.com) Nature: Uncategorized Issue Severity: Summary: In figure 446, only packages that specialise Constructs::Package can contain a Profile Application. Whereas I think that the packages to which we need to apply profiles are those packages that specialise Kernel::Package Proposed correction Kernel is obtained by having merged Constructs and other packages. Every Kernel package is a construct package. So the present solution is more general, and ha the advantage to provide the exact same text for infra and superstructure. Discussion : Well, Kernel is defined in the infrastructure, and construct is build in the superstructure. So I believe it is the way around : the opposite. Disposition : Reject. Subject: RE: Ballot 7 (official version -- please vote on this!) Date: Mon, 16 Feb 2004 04:23:12 -0500 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Ballot 7 (official version -- please vote on this!) Thread-Index: AcPrcBWp1nNUlAD9ThyUgPjB9KCZQAI96bfA From: "Pete Rivett" To: "Branislav Selic" , X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id i1G9BBrh028937 Adaptive votes YES to all the proposed resolutions, except 6310 and 6354 to which it votes NO. While I agree 6310 should be 'closed no change' the resolution text below is not only technically incorrect about where kernel is defined, but does not make sense as English, and formal resolutions should not be a statement of belief: "Well, Kernel is defined in the infrastructure, and construct is build in the superstructure. So I believe it is the way around : the opposite." The resolution to Issue 6354, about notation ambiguity, although it states that 'typically' the specific problem won't arise (I don't know how we can judge 'typical' for a new notation), in effect includes the claim that ambiguous diagrams are not a problem since tools and the metamodel will know the difference: "The difficulty is merely one of parsing a graphical document." This is what I object to: for most people UML is *only* about a notation for communicating designs, and the 'graphical document' is all they see: so it's poor humans who will be 'parsing' the diagrams and trying to work out what's going on. We should not forget this. Especially for a new UML addition which people will initially be unfamiliar with. For future reference 6350 is borderline: the resolution makes no attempt to state where the changes need to be made - is it just to the diagram on which the issue was raised? "The multiplicity of the end at CollaborationOccurrence should be changed to "0..1". Note that the resolutions to 6014, 6016, 6022, 6023 (referring to 'as specialized'), while correct now, will not be correct if we adopt the consensus for package merge which will remove all these nasty specializations. I suggest that we hold off voting on any similar issues until the package merge solution has been formally resolved. -------- I know we're supposed to raise problems at the draft stage. But in this case 23 new issues were added in draft 2 with only 7 hours between the draft and the issued ballot. This might be good for perceived FTF productivity but not for resolution quality IMHO. (I missed reading the resolution text for 6310 in 1st draft I admit since I could see from reading the issue that it would be 'closed no change'). Pete Pete Rivett (mailto:pete.rivett@adaptive.com) Consulting Architect, Adaptive Inc. Dean Park House, 8-10 Dean Park Crescent, Bournemouth, BH1 1HL, UK Tel: +44 (0)1202 449419 Fax: +44 (0)1202 449448 http://www.adaptive.com ________________________________ From: Branislav Selic [mailto:bselic@ca.ibm.com] Sent: Wednesday, February 04, 2004 4:37 PM To: uml2-superstructure-ftf@omg.org Cc: mu2i-ftf@omg.org; ocl2-ftf@omg.org Subject: Ballot 7 (official version -- please vote on this!) OK, after a bit of to and fro, here is the official version of ballot 7 for voting purposes. It has a total of 36 proposed issue resolutions (not 38 as I had promised). I have excluded from it all items that have even a whiff of contention -- but it is still your responsibility to look at each proposed resolution and decide if you agree with it. Remember, once we have voted on an issue, there is no going back, so please make sure you do this right. The official ballot opens in 26 minutes and goes on for two weeks. During that time, you can change your vote. After that you cannot. 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 apply profiles are those packages that specialise Kernel::Package.