...
- Agenda bashing
- reminder for filling R9 high level requirements: https://wiki.onap.org/display/DW/ONAP+R9+Modeling+High+Level+Requirements
- still empty
- Ben would like the modeling team to join the use case realization call on May 3, to discuss the modeling high level reqs
- service IM call proposal:
- Chuyi is suggesting to merge service IM call with resource IM call or modeling subcommittee call, due to lack of topics
- will raise and discuss the topic tomorrow
- Xu: fine for merging with resource IM call, but afraid that may limit the time of individual topics' discussion; prefer new service model proposal be raised in modeling subcommittee call first, and then decide whether to discuss in Monday call or in a seperate/dedicated call
- reminder for filling R9 high level requirements: https://wiki.onap.org/display/DW/ONAP+R9+Modeling+High+Level+Requirements
- Model Proposals
- ETSI support for CNF model
- R9 DM proposal: https://wiki.onap.org/pages/viewpage.action?pageId=93011772
- aligned with SOL001 v4.2.1, package format is still under discussion
- information model is planned to have an update in R9
- lack resources, no code implementation plan for Istanbul release
- for backward compatibility, possibly only support v2.4.1 and v2.7.1 in the future
- 5G service / CPS model
- PNF instance model
- reverse engineering
- Topology model
- Proposal: https://wiki.onap.org/display/DW/Abstract+Topology+Model
- call information: https://lists.onap.org/g/onap-modelingsub/topic/abstract_topology_model/80876474?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,80876474
- today, 15:00 UTC
- could postpone to next week due to conflictit's proposed to have a general call for the topic, time and place TBD, may be at use case or resource IM call
- ORAN alliance issues will be presented
- has discussed several use cases, and working on basic concepts
- ETSI support for CNF model
- Modeling Documentation
- R6 readthedocs review:
- gendoc template improvement: ONAP Information Model - Gendoc Examples
- discussion whether the description only applies for a navigatable end of an association
- continue discussion later
- add relationship documentation to the UML guideline:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key ONAPMODEL-28 - UML principle wiki page:
- Principle and Guideline for Information Model Proposal Using Papyrus (Draft)
- review the updates to the Gendoc requirements part
- Michela suggest whether it's possible to add information of associations into the class definitions
- Xu will investigate it offline
- Michela suggest whether it's possible to add information of associations into the class definitions
- Using Papyrus for Modeling updates
- suggest to further discuss the version recommended after Jacqueline come back
- UML principle wiki page:
- R6 readthedocs review: