UMLR — Visibility and Import relationships

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"