Decision: we use the existing one and "ignore" new proposed one.
Soposed to be an open call.
Kam sends clarification email Thanks!
Scott MansfieldTo present the YUMA123 platform (client/server development platform) in one of the next calls - moved to Apr17
Karthik Sethuraman: Create a separate wiki page for the action items and link this page to all meeting minutes Link to the wiki: IISOMI Action Items Action items should be used only for real action items Create an "action item" list only - to complex Result: create action item in meeting notes but don't use it for meeting leaders check minutes 2020-02-13.
What we saw of the “shared aggregation” of CurrentData at the ThresholdProfile was an unintended change when creating the v0.14 of the draft G.8052.1 model. It was probably caused by accidentally moving the mouse over the Aggregation field of the Properties pane and altered the aggregation setting from “none” to “shared”.
The actual association is like the following in G.8052.1 v0.13 (TD521R1/WP3 Feb. 2020) and also in the base G.8052 since many years ago. It was so at least since v2 of G.8052 (2016).
Also, the Navigation is “false” for the Member End “associatedCurrentData”. That means the ThresholdProfileAssociatedToCurrentData association is unidirectional navigable. That is, not bidirectional.