UML 1.4 NO IDEA Avatar
  1. OMG Issue

UML14 — 7.3.1 ElementImport

  • Key: UML14-224
  • Legacy Issue Number: 6168
  • Status: closed  
  • Source: SSA ( Art Culbertson)
  • Summary:

    The next to last sentence states: "A member may be further imported by other namespaces using element or member imports." What are member imports? Should this be package imports?

    Notation

    The difference between public import using <<import>> and private import using <<access>> is not explicitly stated, nor is an example of <<access>> given in the Examples part. My understanding is that <<import>> adds an element to importing namespace using public visibility, i.e., the imported element can be accessed without qualification within the importing namespace and any namespace the importing namespace encloses. My understanding of <<access>> is that it adds an element to the importing namespace using private visibility which does not allow the imported element to be further imported. Does the last sentence of the Description, "It is also possible to control whether the imported element can be further imported", refer to <<access>> element import?

  • Reported: UML 1.5 — Wed, 3 Sep 2003 04:00 GMT
  • Disposition: Resolved — UML 1.4.2
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT