...
Michela Bevilacqua - backward compatibility guidelines to be progressed. What must be backward compatibility and how should be clarified .
3- Keep the distinction and consistency between Information model and its data model representation(s).
...
Alex Vul - We should say that the function and operation of the ONAP management platform is predicated on use of a single, common information model,
5- The modeling team should not define the feature requirements, but take requirements derived from use cases or architecture as input.
Alex Vul - Define what the "modeling team" is. Based on the community bylaws, we have Subcommittees and Projects. Where does the "modeling team" fit in?
maopeng zhang - Because modeling is not full or completely designed by the use cases and architecture, I think the requirement of modeling may consider coming from the projects in implication phrase as well.
6- Actively pursue participation from stakeholder projects in the modeling effort.
...
Thinh Nguyenphu (Unlicensed): Agreed with Alex. I did not understand the purpose of bullet 5.
maopeng zhang - Could the author provide the rule coming from or reason why we regard it as a guideline? I agree with Alex that basically we should TOSCA guidelines if the data model is used by TOSCA.
7- When defining new Namespace, in order to avoid namespaces and types name types definitions collision, it is recommended that ONAP uses the rule and guidelines as described in the OASIS TOSCA Simple YAML Profile v1.2.
...