Date
Attendees
Agenda
- Administrative
- Call plan (schedule, leader)
- Review IISOMI Action Items
- Discussion items in Wiki pages
- Mapping Guidelines
- Check Martin work is represented in latest Guidelines.
- Feature/condition
- Improve uml2yang tool for “when” and “if-feature” statements.
- UML → YANG Mapping Tool update
- O-RAN cooperation
- Papyrus-Model2Doc further investigations?
- Papyrus Releases
- Consider a plan for convergence of ITU-T Q14/15, ONF Common IM and TAPI to 2020-06 (4.16) version
- Private GitHub
- Public GitHub
- Gendoc Issues
- Gendoc output for Interfaces, Operations, Associations, Abstractions
- Agenda of next call
- AOB
Discussion items
# | Time | Item | Who | Notes |
|---|---|---|---|---|
| 1 | 5 min | Admin: Call plan | All | Cancelled – IETF week Leader: Kam (Not available: Bernd) Cancelled – Vacation/Holiday Leader: ? (Not available: Bernd) |
| 2 | 30 min | Brief call due to misunderstanding on call start time. Hing-Kam Lam Xiang YUN Scott Mansfield Bernd Zeuner were present at 2m CET, Andrea Mazzini Scott Mansfield Bernd Zeuner at 3pm CET | Brief discussion on the
See also UML to YANG Mapping Guidelines In TAPI the issue was found due to the provisioning of routing constraint: at ConnectivityService creation, it is possible to specify a list (read/write) of UUIDs (read only) of Connections (read only) to be included or excluded in the ConnectivityService route. The list is read/write in the sense that items could be added or removed, while a given item cannot be modified. For further analysis - is there a legal YANG way to fulfil the use case? |
Action items
Overview
Content Tools
Activity