TAPI Call: 3 hours
Arturo Mayoral proposed to organize a virtual meeting, given the number and complexity of the items to be analyzed. Agreed to anticipate of one hour.
Tentatively proposed two sessions of 3 days / 6 hours (e.g. 1pm - 7pm CET)
Review/Consolidation of TR-548 RIA-Streaming
Nigel Davis draft would be ready but needs some work to correctly highlight the deltas. Presentation is postponed to next week - also considering that attendance today is still limited due to ITU-T meeting.
Karthik Sethuraman confirms the correctness of yang modules, but for the enumeration EQUIPMENT_OBJECT_TYPE (tapi-equipment.yang) in 2.1 branch. It has been generated as an identity and extends the base tapi-common:OBJECT_TYPE which is not present in 2.1 branch.
Andrea Mazzini corrected, will commit.
Karthik Sethuraman is using Visual Studio Code, which provides a well maintained yang editor plugin, useful to check consistency of modules. Note that Papyrus is no longer maintaining its yang editor.
Continue discussion on yang2oas tool - make exact point of the issues
Karthik Sethuraman notes that besides UML and yang, it is also necessary to review/validate the OAS/yaml modules when delivering TAPI. Consider that now there are more Resconf experts who can highlight deviations from compliance. In the room nobody knows about other open source tools converting yang to OAS.
Karthik Sethuraman There is an issue regarding node-edge-point and owned-node-edge-point, some manual editing is necessary.
Considering that ONF/TAPI is the only known user of the tool:
Brief review of the OAS open issues (in red the possible next steps)
(*) Agreed that JSON encoding is the most popular one, while XML no longer, hence it seems appropriate to recommend only JSON for TAPI.
Build agenda for next virtual meetings