Issue 14022: Visibility and Import relationships (uml2-rtf) Source: Airbus Group (Mr. Yves Bernard, yves.bernard(at)airbus.com) Nature: Clarification Severity: Summary: Am I wrong or is there actually something inconsistent in the specification around the concept of "visibility"? As I underlined for the ballot 6 vote, the current specification explicitly states that Element/PackageImport has no impact on element visibility. Cf. my comments posted on the 27th of April about issue #11567: "According to the current definition of the visibility concept, my understanding is that it's neither necessary nor possible to use Import relationships to make an element "visible" (i.e. available). The specification explicitely states that : * an ImportedElement can only have a public visibility or no visiblity at all (cf. ElementImport, constraint #2) * (p111) : "The public contents of a package are always accessible outside the package through the use of qualified names. " * (p66): "The visibility of the ElementImport may be either the same or more restricted than that of the imported element. " Then, the only concrete effect of an Import relationship is to give the ability to refere to an element using its simple name rather than its qualified one." Nevertheless, and even if there is no impact on the resolution, I found this sentence in the discussion of issue #12833 (ballot 8) : ". The names of stereotypes or classes in a parent profile are not visible to a profile nested in that parent profile without a PackageImport" Resolution: Revised Text: Actions taken: June 23, 2009: received issue Discussion: End of Annotations:===== ubject: Visibility and Import relationships Date: Tue, 23 Jun 2009 11:01:59 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Visibility and Import relationships Thread-Index: Acnz4UQ+AoE5CXR8RS2GK8FTBgz+ZA== From: "BERNARD, Yves" To: X-OriginalArrivalTime: 23 Jun 2009 09:02:00.0299 (UTC) FILETIME=[44B9D3B0:01C9F3E1] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id n5N8xdSL001017 Hello all, Am I wrong or is there actually something inconsistent in the specification around the concept of "visibility"? As I underlined for the ballot 6 vote, the current specification explicitly states that Element/PackageImport has no impact on element visibility. Cf. my comments posted on the 27th of April about issue #11567: "According to the current definition of the visibility concept, my understanding is that it's neither necessary nor possible to use Import relationships to make an element "visible" (i.e. available). The specification explicitely states that : * an ImportedElement can only have a public visibility or no visiblity at all (cf. ElementImport, constraint #2) * (p111) : "The public contents of a package are always accessible outside the package through the use of qualified names. " * (p66): "The visibility of the ElementImport may be either the same or more restricted than that of the imported element. " Then, the only concrete effect of an Import relationship is to give the ability to refere to an element using its simple name rather than its qualified one." Nevertheless, and even if there is no impact on the resolution, I found this sentence in the discussion of issue #12833 (ballot 8) : ". The names of stereotypes or classes in a parent profile are not visible to a profile nested in that parent profile without a PackageImport" So, could we clarify that point, please ? Cheers, Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other then the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. From: "BERNARD, Yves" To: "uml25-ftf@omg.org" Date: Wed, 30 Jan 2013 13:36:44 +0100 Subject: [UML 2.5 FTF] #14022 is not obsolete Thread-Topic: [UML 2.5 FTF] #14022 is not obsolete Thread-Index: Ac3+5nYcb4sSnpjsToi4ooSWzNAkHQ== Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US X-Brightmail-Tracker: AAAAAgr+n5Ec4fwY X-Brightmail-Tracker: AAAAAA== The issue #14022 : .Visibility and Import relationships. is not obsolete since the controversial sentences remain almost identical in the v2.5 beta1 document. Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: Steve Cook To: "BERNARD, Yves" CC: "uml25-ftf@omg.org" Subject: RE: [UML 2.5 FTF] #14022 is not obsolete Thread-Topic: [UML 2.5 FTF] #14022 is not obsolete Thread-Index: Ac3+5nYcb4sSnpjsToi4ooSWzNAkHQAAQNGg Date: Wed, 30 Jan 2013 12:45:53 +0000 Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.166.18.101] X-Forefront-Antispam-Report: CIP:131.107.125.37;CTRY:US;IPV:CAL;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(189002)(365934001)(199002)(31966008)(49866001)(44976002)(47976001)(54316002)(63696002)(74662001)(46102001)(47446002)(47736001)(79102001)(77982001)(5343635001)(59766001)(15202345001)(74502001)(16796002)(4396001)(50986001)(5343655001)(20776003)(56816002)(55846006)(56776001)(16236675001)(16406001)(512954001)(54356001)(51856001)(33656001)(53806001)(76482001);DIR:OUT;SFP:;SCL:1;SRVR:BL2FFO11HUB022;H:TK5EX14HUBC103.redmond.corp.microsoft.com;RD:;MX:1;A:1;LANG:en; X-OriginatorOrg: microsoft.onmicrosoft.com X-Forefront-PRVS: 0742443479 X-Brightmail-Tracker: AAAAARzh/Bg= X-Brightmail-Tracker: AAAAAA== Yves Is this the controversial sentence: .Normal rules apply as to whether a referenced Stereotype is visible to users of the extending Profile.: a public import is needed to ensure that Stereotypes from other profiles are visible after applying the extending one.? If so then the issue should be moved to clause 12, I think. Or is it something else? -- Steve From: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] Sent: 30 January 2013 12:37 To: uml25-ftf@omg.org Subject: [UML 2.5 FTF] #14022 is not obsolete The issue #14022 : .Visibility and Import relationships. is not obsolete since the controversial sentences remain almost identical in the v2.5 beta1 document. Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: "BERNARD, Yves" To: Steve Cook CC: "uml25-ftf@omg.org" Date: Wed, 30 Jan 2013 14:39:29 +0100 Subject: RE: [UML 2.5 FTF] #14022 is not obsolete Thread-Topic: [UML 2.5 FTF] #14022 is not obsolete Thread-Index: Ac3+5nYcb4sSnpjsToi4ooSWzNAkHQAAQNGgAAGwN8A= Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US X-Brightmail-Tracker: AAAAAgr+n5Ec4fwY X-Brightmail-Tracker: AAAAAA== Steeve, Yes, it is. This one in conjunction with those from clause 7.4.3, sub-clause .Packageable Elements and Imports. which state: a. .The visibility of the ElementImport may be either the same or more restricted than that of the imported element.. b. .Conceptually, a Package import is equivalent to having an ElementImport to each individual member of the imported Namespace, unless there is a separately-defined ElementImport.. I agree: it should be moved to clause 12. Thanks, Yves From: Steve Cook [mailto:Steve.Cook@microsoft.com] Sent: mercredi 30 janvier 2013 13:46 To: BERNARD, Yves Cc: uml25-ftf@omg.org Subject: RE: [UML 2.5 FTF] #14022 is not obsolete Yves Is this the controversial sentence: .Normal rules apply as to whether a referenced Stereotype is visible to users of the extending Profile.: a public import is needed to ensure that Stereotypes from other profiles are visible after applying the extending one.? If so then the issue should be moved to clause 12, I think. Or is it something else? -- Steve From: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] Sent: 30 January 2013 12:37 To: uml25-ftf@omg.org Subject: [UML 2.5 FTF] #14022 is not obsolete The issue #14022 : .Visibility and Import relationships. is not obsolete since the controversial sentences remain almost identical in the v2.5 beta1 document. Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.