Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

\uD83D\uDDD3 Date

13:00-15:00 UTC

\uD83D\uDC65 Participants

ET-W2AT

No

Name

Role

Present (yes/no)

1

Mr Jeremy TANDY

Chair

No

2

Mr Rémy GIRAUD

Member

Yes

3

Mr Pablo Jose LOYBER

Member

No

4

Ms FATIMA SABAI

Member

No

5

Mr Peng  WANG

Member

No

6

Mr Tom KRALIDIS

Member

Yes

7

Mr Kenji TSUNODA

Member

No

8

Dr Baudouin RAOULT

Member

Yes

9

Mr Thorsten BÜSSELBERG

Member

No

10

Ms Dana OSTRENGA

Member

Yes?

Experts

  • Wirt Kai-Thorsten (DWD)

  • Simon Elliott (EUMETSAT)

WMO Secretariat

\uD83D\uDDE3 Discussion topics

Item

Item

Presenter

Notes

1

Review of actions from the last meetings

Hassan

Hassan summarized all the actions from the previous meetings on June 26 and September 4 and updated the progress on them.

  • Notification mechanism on updated data

  • Clarify broker protocol elements

  • GTS to WIS2 Gateway

  • WIS2 to GTS Gateway

discussion

  • GTS to WIS2 Gateway

    • (Tom) it is good to keep this specification in the transition document, in the notification message specification document. MQTT explorer gets flooded by GTS to WIS2 gateway. Propose: to have a option , gts_to_wis2_gateway to be at higher level of topic hierarchy, e.g, in parallel to wis2 or higher

      • (Kai) gts_to_wis2_gateway can be set at any level as needed

      • (Rémy) Prefers the current proposal. When it is not possible to deal with the large amount of message notification by MQTT explorer, we need to consider changing the architecture.

      • Action: (Hassan) Merge GTS property and GTS to WIS2 Gateway provider jobs into one ascii doc.

2

"merging" country and centre-id into one unique name

All

3

Lifecycle management of discovery metadata in WIS2 https://github.com/wmo-im/wis2pilot/issues/85

✅ Action items

⤴ Decisions

  • Notification mechanism on updated data: two solutions (with operation property vs no operation property but with a relation link) to be decided

  • No labels