...
Alexander Vul - Backward compatibility between releases is a MUST HAVE. Simply saying that we will "attempt" it is not good enough. Modeling requires up-front end-to-end planning and a backward compatibility strategy. We must have one as well, as part of this document.
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).
...
Alexander Vul - Define what a "modeling effort" is. Again, we have Subcommittees and Projects. Where does a "modeling effort" fit in? Observation - modeling is not an effort. Its a necessary part of building complex distributed systems. When we came together as a community, we had said that the Projects would be responsible for the creation of their own domain (information/data) models and/or model element applicable to them. We have also said that the Projects would coordinate with each through appropriate Subcommittees. We need to rationalize how the Modeling "team" and "effort" fit into this arrangement.
Michela Bevilacqua - Rephrasing proposal.... (inspired by ONF WoW)
It is expected that each ONAP project team that will use (and contribute to) the IM will provide a representative to ensure that the work of the modeling in the sub-comittee meets the needs of their project.
The modeling subcomittee will be responsible to maintain the IM and any common (TOSCA) constructs in GitHub.
Guidelines
1- Initially focus on a Unified Information Model in UML and its TOSCA construct representation for Service and Resource
...
Alexander Vul - I am still not clear on what the approach is. Are simply talking about terminology, or actual adoption/transference of information model elements from different sources into a single ONAP information model? For example a VNF descriptor can be built by taking elements of the IFA011 information together with information elements from other sources - ECOMP/others - and coalescing them into a single information model. I don't think talking about terminology is good enough.
Michela Bevilacqua . I agree
5- Identify the gaps in either information modeling (in terms of information elements) or data model (in terms of types/constructs) we need to fulfill the functional/non-functional requirements derived from the use cases and prioritize per release.
...