...
c) Encourage efforts in other SDOs to align with ONAP IM/DM implementation with their specifications (e.g. TOSCA NFV Profile and SOL001) development.
Thinh Nguyenphu: bullet 5c: beside encourage efforts, ONAP should define it own core IM/DM models and touchpoints. This concept has been accepted among SDOs (ONF, TMF, and 3GPP). My understanding is that each SDO has published their touchpoint specification. For ETSI NFV, https://docbox.etsi.org/ISG/NFV/Open/Publications_pdf/Specs-Reports/NFV-IFA%20024v2.1.1%20-%20GR%20-%20NFV%20IM%20External%20touchpoints.pdf. My recommendation: adding a new bullet 5d: defining the touchpoint and relations between ONAP core IM/DM with other organizations, such as ETSI NFV, TMF, ONF, 3GPP, etc.
6- When defining new constructs in ONAP Data model
...
c) Otherwise, derive directly from tosca.nodes.root
Thinh Nguyenphu: bullet 6 (a-e): I understand the desire and goal. However, it is not clear to me what is profile definition ONAP planning to use, such Simple YAML v1.2, TOSCA NFV Profile, or ONAP profile? Also, how ONAP plan to reuse or extend existing NFV types which are currently defined in TOSCA NFV Profile and/or SOL001?
5- When defining new properties, best effort to put properties on capabilities.
...
Alexander Vul - We should follow TOSCA guidelines in this regard. I believe, use of properties is equally applicable to both requirements and capabilities.
Thinh Nguyenphu: Agreed with Alex. I did not understand the purpose of bullet 5.
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.
Alexander Vul - Use of TOSCA guidelines should not be a "recommendation" but a "given". If we want to use TOSCA for data modeling approach, we have to follow the rules.
shitao li - agree
Thinh Nguyenphu: perhaps, the change should be:
When defining new Namespace, in order to avoid namespaces and types name types definitions collision, it is recommended that ONAP follows uses the rule and guidelines as described in the OASIS TOSCA Simple YAML Profile v1.2.
8- Create a (class) diagram which outlines ONAP DM relationship to TOSCA Simple Profile 1.2
...