UML 2.5 FTF Avatar
  1. OMG Issue

UML25 — Port should specialize featuringClassifier

  • Key: UML25-577
  • Legacy Issue Number: 7567
  • Status: closed  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    Apparently a structural feature can be on more than one classifier,
    because the multiplicity of /featuringClassifier is 1..*. Not all the
    subtypes of StructuralFeature narrow this to one, or change it to strong
    ownership (eg, Port).

    Is it intentional that structural feature have more than one
    featuringClassifier, and not be owned by that classifier? If not, Bran,
    please assign this to classes. Otherwise, it is problem for Ports as
    well.

  • Reported: UML 1.4.2 — Wed, 7 Jul 2004 04:00 GMT
  • Disposition: Resolved — UML 2.5
  • Disposition Summary:

    Discussion
    This issue has already been resolved by, or no longer applies to, the UML 2.5 Beta 1 specification.
    Disposition: Closed - No Change

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