This document specifies ONAP modeling design principles and guidelines for release 2+.
...
1- Requirements driven and prioritization per release
2- Based on existing implementation and
...
attempt to
...
maintain backward compatibility
3- Keep the distinction and consistency between Information model and its data model representation(s).
...
c) If direct use of OASIS Simple YAML Profile 1.2 normative node types is not possible, extend/derive from existing node types or create new ones as appropriate
7- When defining new Namespace, in order to avoid namespaces and types name types definitions collision, ONAP follows the rule and guidelines as described in the OASIS TOSCA Simple YAML Profile v1.2.
...