2023-10-16 ET-W2AT Meeting

1

Mr Jeremy TANDY

Chair

Yes

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

No

1

1. Resolve any “urgent” issues [https://github.com/orgs/wmo-im/projects/30/views/1?filterQuery=status%3AUrgent ]

   1. Simple NC/DCPC data sharing in data-and-metadata-flows https://github.com/wmo-im/wis2-guide/issues/29 << easy to resolve I think

   2. clarify GDC population at startup https://github.com/wmo-im/wis2-guide/issues/9 << more complex, and relates to how data is published about (mostly) static datasets.

(Jeremy) https://github.com/orgs/wmo-im/projects/30/views/2 to work on this GitHub project.

• Discussionhttps://github.com/wmo-im/wis2-guide/issues/29

  • (Rémy) GitHub should be consistent with the new WIS2 guide architecture https://wmo-im.github.io/wis2-guide/

  • (Tom) where to share the WIS2 guide details?

  • (Kai) detail level needs to be somewhere to refer to. simple data sharing needs to be removed. (Agreed)

  • (Rémy) WIS2 material to be available, not in the guide nor in annex. Guide needs to be user-centric and implementation centric. Specification to be kept for availability but to be published in the Guide. For example, WIS2 node registration documents, is to showcase which level of details to be included in the WIS2 guide.

  • (Baudouin) graphs is readable. But don’t put everything in one diagram if there are conditions.

  • (Actions), visual code, markdown,(Xiaoxia) to open an issue in WIs2 guide repository to decide which methods to be used to publish the diagram. (Assign to Tom)

  • (Jeremy) users include: data consumers, those operating wis2node or operating global services

  • (Tom) principles, reference implementation, repo (WIS2 Architecture) descriptions will help. Detailed technical blueprints go along side with implementation (where to publish)

  • (Weiqing) WIS2 guide needs to be approved by INFCOM? (Enrico: YES, but EC not need)

  • (Tom) maybe we need a separated guide, such as WIS2 Architecture implementation guide?

  • (Rémy) discussion for document location is not urgent.

• https://github.com/wmo-im/wis2-guide/issues/9

  • (Jeremy) to treat metadata as data at the same level

  • (Rémy) to publish zip file by GDC, all the wis2nodes, GB, GC can receive the notification. Each component in WIS2 needs a broker. Each entity needs a local broker.

  • (Enrico) GDC, GC, a local broker needs to be known. Needs to be registered.

  • (Tom) GDC needs a daily report to be published. GDC has a local broker. And GB subscribes to GDC. Guide to be updated accordingly.

  • (Action) Jeremy to update the issue.

  • (Action) Tom To start identifying different reports.

  • (Rémy): currently, there are other two repos. One is WIS2 monitoring (more on implementation), the other one is wis2-metric-hierarchy (a follow-up on Topic Hierarchy). Whether to create a New Repo-WIS2 alerting. Rémy will prepare presentation to trigger the discussion on WIS2 monitoring and alerting.

  • (Weiqing) Who decides the duration of data being cached?

    • (Hassan) tech regulation, by default, at least 24 hours

  • (Action) Jeremy to create an issue for node notification repo.

• merge country and centre-id

  • (Rémy) needs to agree on one approach to move forward

  • (Tom) there will be guidance on name convention of merging country and centre-id

  • (Jeremy) it will be good to have some examples in the comments

  • (Action) Tom will finalize the proposal within TT-WISMD and then present it for approval in ET-W2AT

2

Prioritise Issues for resolution at the face-to-face ET-W2AT meeting [https://github.com/orgs/wmo-im/projects/30/views/1?filterQuery=status%3A%22For+ET-W2AT+meeting+%28Nov+2023%29%22 ]

Not discussed

3

Agree agenda for face-to-face ET-W2AT meeting, November 13-15th.

Not discussed