Participants

@guochuyi @Thinh Nguyenphu (Unlicensed) @Kevin Scaggs @Xu Yang @lishitao @Andy Mayer Bob @Michela Bevilacqua

Agenda

Kevin take "color" as an example to describe the question of "dynamic of dynamic", which is to say the situation of a dynamic attribute with a value range, run time will be one of the values, how to give the information in design time and how to build the association between design time and run time.
1. Thinh suggests default value in data model that can be overwrited through the API to solve this problem.
2. This also bring the obstacle of how to express this right in papyrus.
3. Xu suggests to define a data type or other type that can be applied to both design time and run time to show they have the same range, or use a stereotype to give the description of what values can be.
4. This bring the question of how much we can model the resources in information model and how much should leave to data model?
Need clarify the differences between serviceProfile and configurableProperties, and how to use them. ConfigurableProperties should 0 to many not 0 to 1. ServiceProfile can be a group of attributes that will work together, for example SliceProfile in 3GPP. Kevin suggests to keep ServiceProfile as class, configurableProperties can be 2 to many in serviceProfile , and have a relationship between serviceProfile and serviceInstanceProfile.