MOF 2.4 RTF Avatar
  1. OMG Issue

MOF24 — Semantics and ownership of link slots needs clarification

Open Closed All
  • Key: MOF24-78
  • Legacy Issue Number: 17169
  • Status: closed  
  • Source: Model Driven Solutions ( Mr. Steve Cook)
  • Summary:

    Who owns LinkSlots? When an association end is owned by a Classifier, are there two slots for its instances (one for the link and one for the element) or only one?
    In the abstract semantics there is a concept called LinkSlot, which is shown as weakly aggregated (white diamond) by AssociationInstance. White diamond has not meaning in this context. Is it possible that a LinkSlot may be owned either by the link or by the adjacent instance, depending on “navigability”?
    The following sentence appears to be key: “Where the feature is a navigable end, then the ClassInstance Slot is consistent with the Link slot.” The reference to "navigable" is surely incorrect. What does "consistent" mean?

  • Reported: MOF 2.4.1 — Thu, 23 Feb 2012 05:00 GMT
  • Disposition: Resolved — MOF 2.4.2
  • Disposition Summary:

    LinkSlots are owned by the AssociationInstance. Update diagram 15-1 to show this
    correctly.
  • Updated: Mon, 20 Apr 2015 17:34 GMT