TT AvData Teleconference 2021 Mar 31

Details

2020-March-31, 12:30-14:00 UTC, Microsoft Teams

Agenda (draft)

1. Review previous actions
2. IWXXM 3.1-dev
3. Update on IWXXM code list repository organization
4. Finalize version table for MoC vI.3 
5. Schedule next meeting
6. AOB

 Minutes (draft) 

Review previous actions 

• [DONE] Jan: complete the CSVs for IWXXMCodeLists repo - Available for review here. The new repository has two main directories CSV and TTL, the latter of which is suppose to hold the TTL files generated by scripts. The CSVs has normalized tables (e.g. added description column). Dmitry said this was easier to read than using RDF files. The meeting invite Jan to bring the content into a new branch in wmo-im/iwxxm-codelists.
• All: Review requirements for Weather Objects and WAFS SIGWX Forecast at https://github.com/blchoy/iwxxm-testbedOne/wiki/DN-2019_01-P2 - Choy would go through the design in the latter part of the meeting.

 Status of IWXXM 3.1-dev draft

• Choy was still updating the validation page. While he had implemented most the changes mentioned, they were not yet committed on GitHub for the team to review. More work had to be done on AIRMET and SIGMET. Deliverables include: RC1 (of schemas) to "users" and wait for 4 weeks for comments and then RC2 is sent out to NFPs as part of FT-2021-2.

• Enrico raised his concern with regard to the way the IWXXM model, schemas and GitHub repository were maintained. He pointed out that for other teams managing TDCF individual change request would be identified with an issue and a corresponding branch would be created to handle the change. Choy indicated that it would be difficult follow this practice as it would be difficult to isolate individual change in a schema. Having said that, it did not mean that the team could not handle each IWXXM package (e.g. METAR/SPECI) individually as they were separate XML/GML schemas and individual UML package can be exported/imported through XMI. In fact, for a new version of IWXXM, IWXXM packages requiring changes could be handled in separate branches and dealt with by different team members. Choy would take the preparation of IwXXM 2021-2 as an opportunity to establish an example workflow for others to comment.

• Choy went through summary on https://github.com/wmo-im/iwxxm/wiki/Validation:-IWXXM-2021_2RC1. Choy will add details about backward compatibility of the change (to help assess if the revisions will be considered major or minor). Choy provided a deeper dive into the details of the new package for WAFS SIGWX.

• The team recognized the timeline of deliverables and would work hard to meet the targets:

1. 22 of April: send out RC1 to users for comment
2. 25 May: create RC2 based on user comments
3. 24 June: finalize all RC2 changes to IWXXM
4. 15 July: sent out to NFPs for FT-2021-2

• The team re-confirm the look of the finalize version table for MoC I.3:

IWXXM Version	METAR/SPECI	TAF	SIGMET	AIRMET	Tropical Cyclone Advisory	Volcanic Ash Advisory	Space Weather Advisory	WAFS SIGWX Forecast	IWXXM Code Tables
1.1	1.1	1.1	1.1	n/a	n/a	n/a	n/a	n/a	?
2.1	2.1	2.1	2.1	2.1	2.1	2.1	n/a	n/a	?
3.0	3.0	3.0	3.0	3.0	3.0	3.0	3.0	n/a	?
2021-2	3.1	3.0.1	-	-	-	-	-	1.0	2021-2

• There was a discussion on whether there would be a need to issue a new version of IWXXM when there is an update to the code tables only (see the table in post in which IWXXM 2033-2 was issued due to a code table change). The meeting considered that this is NOT necessary so the version table would not need the "IWXXM Code Tables" column.

Update on IWXXM code list repository organization

• (see review of actions)

AOB

Decisions 

• The version table does not need to have the "IWXXM Code Tables" column.

Actions

• Jan: To move the content of the revised code list repository to a new branch of wmo-im/iwxxm-codelists
• Choy: To demonstrate how to manage changes at package level, and adjust the validation page accordingly.

Attendees

• BL Choy
• Mark Oberfield
• Dirk Zinkhan
• Ján Körösi
• Yann Genin
• Anna Milan
• Xiaoxia Chen
• Enrico Fucile