NIEM-UML 3.0 FTF Avatar
  1. OMG Issue

UMLNIEM3 — Inconsistent statements about aggregation

  • Key: UMLNIEM3-36
  • Legacy Issue Number: 19833
  • Status: closed  
  • Source: Model Driven Solutions ( Mr. Steve Cook)
  • Summary:

    Table 7.1 says “Aggregation may be used in NIEM-UML models but has no impact on the generated schema or conformance” while says about RoleOf properties: “Such a property must have aggregation=none”, says “If an «XSDProperty» property has kind=attribute, then its multiplicity must be 1..1, its aggregation must not be none and its type must be a data type representing a simple type”, says “A property in a PIM shall map to a corresponding property in the PSM with the same multiplicity and aggregation as the PIM property and with an owner and type (if any) that are the corresponding classifiers mapped from the PIM”, and 8.3.5 says “A RoleOf Property must be a reference (i.e., have aggregation=none)” .

  • Reported: NIEM-UML 3.0b1 — Wed, 16 Sep 2015 04:00 GMT
  • Disposition: Resolved — NIEM-UML 3.0
  • Disposition Summary:

    Aggregation is no longer required, document text adjusted.

    As aggregation is no longer relevant to NIEM-UML the statements may be clarified as follows:
    The statement in Table 7.1 is correct.
    The statement in is false.
    The statement in is logically true with respect to aggregation, but does not impact generation, since it is assumed part of the definition of an «XSDProperty». Multiplicity can be defined to be 0..0, 0..1, 1..1 and will impact generation of attribute definition.
    The statement in is true, even though the aggregation does not impact PIM to XSD transformation.
    The statement in 8.3.5 is false.

  • Updated: Tue, 11 Oct 2016 14:48 GMT