TT Protocols 3 2021

Minutes – TT-Protocols 3-2021

09/06/2021 – 12-13h (Geneva time)

Present

• Peter Silva (lead)
• Antje Schremmer (DWD)
• David Podeur (Météo France)
• Ian MCDONALD (EUMETSAT)
• Jan Osusky (IBL)
• Enrico Fucile (WMO)
• Timo Pröscholdt (WMO)

Agenda and Minutes

1. Opening

• Team welcomes new JMA participant, Mr Ren OZEKI @ren-ozk.
• Briefing on recent activities regarding Global Multi-hazard Alert System

A recent meeting between the Chair of SC-IMT in INFCOM and Chair and Co-Chair of the Expert Team on the Global Multi-hazard Alert System (ET-GMAS) in SERCOM, discussed the role of INFCOM, and TT-Protocols in particular in the development of GMAS. GMAS will adopt MQP for dissemination of alerts, in CAP format. ET-GMAS and TT-Protocols to work together interactively and directly to resolve a number of issues, especially question of embedding of alerts in the notification and considering OID as a basis for the topic tree. Github issues have already been created. SERCOM will require INFCOM assistance in helping Members transition to MQP based dissemination. Pilot projects will be stood up to validate dissemination of CAP via MQP. Pilot projects will require specifications to work against, the task team can help in starting with the drafting process. The task team expressed a desire to follow the progress of the pilot projects and agreed to have a standing agenda item for pilot project. At the same time, WIS 2.0 pilot projects can be followed using their Confluence pages

2. The team discussed the following issues, with details recorded in the linked github discussion.

• #40 Formalizing Recommendations/Standards: team approves the approach of using a subfolder in the repository, using restructured text. The specs will ultimately go into the WIS manual, but the immediate aim is to provide specifications that can be validated by pilot projects. closed & approved
• #36 Embedding of content in notifications: The team agreed to allow embedded content in the message structure up to a maximum file limit. This limit will be determined after further testing at a later point in time. closed & approved
• #37 will OID help with defining topic trees: The team came to the conclusion that the use of OID there could be an advantage for defining topics outside the current topic tree and decided to consider the use of OID at a later point in time.

The issues #10 list of MQP and #18 API call will be considered in the next meeting

3. AoB

• the team agreed to meet again in a months time