UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — Operation::ownedParameter should be ordered in XMI?

Open Closed All
  • Key: UML22-177
  • Legacy Issue Number: 9241
  • Status: closed  
  • Source: Fulcrum Analytics, Inc. ( Richard Vermillion)
  • Summary:

    In the latest XMI file (included as part of Ballot 12) the
    ownedParameter attribute of Core::Constructs::Operation redefines
    Core::Constructs::BehavioralFeature::ownedParameter – I'm assuming
    that this redefinition is a result of the merge of Basic.

    However, in Operation, the ownedParameter attribute is not ordered.

    Since both BehavioralFeature::ownedParameter and
    Core::Basic::Operation::ownedParameter are ordered, it seems strange
    for Core::Constructs::Operation's not to be ordered. A check of the
    drafts and ballots does not seem to address this issue or explain why
    it would be the case. Is it a mistake?
  • Reported: UML 2.0 — Sun, 15 Jan 2006 05:00 GMT
  • Disposition: Resolved — UML 2.2
  • Disposition Summary:

    Infra::Core::

    {Basic,Constructs}

    ::Operation::ownedParameter

    {isOrdered=true}

    in UML 2.2 CMOF.
    Revised Text:
    None.
    Disposition: Closed No Change
  • Updated: Fri, 6 Mar 2015 20:58 GMT