I think option 2 or option 3 can be considered. By the way, for Option2, in OPEN-O, for NFV part , the Naming is tosca.nodes.nfv.*, and for SDN part , it is tosca.nodes.sdn.*.
发件人: [email protected] [mailto:[email protected]] 代表 Lingli Deng 发送时间: 2017年8月28日 9:39 收件人: denghui (L) 抄送: [email protected] 主题: [onap-discuss] [modeling][sdc][so][vfc][vnfsdk]ONAP naming convention options I suggest we consider either option 2 or option 3. Thanks, Lingli ________________________________ Hello all We hadn’t have the time to discuss this yesterday teleconf based on the request from SDC, so I posted here to get more comments in the list regarding to ONAP Naming convention. OPENECOMP historically follow 1st option, and OPENO follow 2nd option. ● 1st: Openecomp: org.openecomp.* ● 2nd: OPEN-O: tosca.nodes.nfv.* ● 3rd : tosca.nodes.onap. ● 4th: ● standard part is based on TOSCA simple/TOSCA NFV ● Extension could be onap Thank you all for your comments. Best regards, DENG Hui
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
