TT AvData Teleconference 2021 April 23

Details

2020-April-23, 9:00-10:30 UTC, Microsoft Teams

DONE - Jan: To move the content of the revised code list repository to a new branch of wmo-im/iwxxm-codelists
IN PROGRESS - ALL: validate branches, Choy will ask/assign team members to validate branches when ready
IN PROGRESS - Anna: follow up on email options for public consultation
IN PROGRESS - Anna: help organize GitHub issues alignment with FT branches

There are branches for each report type for visual comparison/understanding of changes. FT2021-2-dev should be used for technical verification. Choy reminded all that as EA is the master source, merging into the master branch will only happen when the final release candidate has been approved and the team has confirmed the outputs of EA posted in a new branch for final checking.
Choy briefed the last bit of changes involving SIGMET and AIRMET which received initial consensus across the team.
Jan pointed out that for WC and WV SIGMET the word AND is now being used to describe the OBS and FSCT of a second (and may be more?) batch of CB cloud in a WC SIGMET and VA cloudl in a WV SIGMET. This provides intrinsic connection between an observed batch of cloud and its future evolution which cannot be adequately represented by the existing SIGMET schema. Choy indicated that this will get into complicated situations involving the evolution of the clouds (splitting, merging, dissipation, generation, etc.). As there has been no such thing before, this may eventually lead to a discussion with broader participants that could completely change what the team think is a good representation according to past experience. Choy invite Jan to pass on the discussion he has with ICAO Secretariat for the team to study. The team will continue the discussion and propose changes in #209 with a view to complete all changes next week.

Post RC1 schema to schemas.wmo.int/iwwxm, with a copy of the code lists in RDF
Don't need to provide updates to manual yet
Send email out to google group (need to get clarity on email group option) and request that comments be sent to wis@wmo.int and we can open (or add to) issues in GitHub as needed
Ask Greg (WMO) and Jun (ICAO) to see if they have email lists to send out for public consultation
They will have one month to review and provide feedback

Mark has based on Jan's CSV FT2021-2-Base prepared revisions to them FT2021-2. Further revisions to include required code tables for Version 2021-2 is required.
Anna forwarded Mark Hedley's view that inviting team members to develop the necessary scripts for CSV ==> TTL may be better (Anna please advise if this correctly reflects your discussion with Mark).
Choy remarked that it would be even more important to have scripts for CSV ==> RDF so that we could revise the code lists and have the RDFs ready for evaluation (e.g. public consultation, Fast Track, etc.). We can always provide a PDF or otherwise to indicate proposed changes to the code lists for review as what have been done by other teams, without using the Codes Registry test site for this purpose.
Jan will take a look at the conversion scripts. As the changes for FT2021-2 are minor, Choy will manually create the revised RDFs for evaluation.

ALL: Choose a branch to validate, self assign in issues and capture notes in issues in the last week of April in respective issues (https://github.com/wmo-im/iwxxm/issues?q=is%3Aissue+is%3Aopen+label%3ApublicConsultation). Hopefully we could make all necessary changes within the week and come to a conclusion that the distribution is fit-for-public consultation by 30 April.
Jan, Choy and interested: To finalize the issues involving WC and WV SIGMET within this week
Choy: To finalize changes with regard to the code lists and prepare the corresponding RDF files for evaluation

Apologies