Issue 17169: Semantics and ownership of link slots needs clarification (mof2core-rtf)
Source: Model Driven Solutions (Mr. Steve Cook, steve-c(at)modeldriven.org)
Nature: Enhancement
Severity: Significant
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?
Resolution: LinkSlots are owned by the AssociationInstance. Update diagram 15-1 to show this
correctly.
Revised Text: see pages 44 of ptc/2014-09-35 for details
Actions taken:
February 23, 2012: received issue
April 6, 2015: closed issue
Discussion: 


End of Annotations:=====

m: webmaster@omg.org
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Steve Cook
Employer:        Microsoft
mailFrom:        steve.cook@microsoft.com
Terms_Agreement: I agree
Specification:   MOF
Section:         15
FormalNumber:    formal/11-08-07
Version:         2.4.1
Doc_Year:        2011
Doc_Month:       August
Doc_Day:         Day
Page:            54
Title:           Semantics and ownership of link slots needs clarification
Nature:          Enhancement
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue


Description:


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?