Skip to content

Meeting 2026 01 22

Jump to bottom
Tom Kralidis edited this page Jan 26, 2026 · 15 revisions

Date/Time

Thursday 22 January 2026 14h - 16h UTC

Location

MS Teams

Attendees

Team

Name Affiliation/Country GitHub handle Attendance
Tom KRALIDIS (Chair) Canada/ECCC @tomkralidis X
Lance BRAASCH Scripps @lancebraasch X
Gao CHEN NASA @gaochen-larc X
Markus FIEBIG NILU @markusfiebig X
Jörg KLAUSEN MeteoSwiss @joergklausen X
Thomas LATTER WMO / OceanOps --- X
Thinesh SORNALINGAM Canada/ECCC @thineshsornalingam X
Alex VERMEULEN ICOS --- ---
Lucia CAPPELLITTI MeteoSwiss --- X
Anna MILAN WMO Secretariat @amilan17 X

Guests

Name Affiliation/Country GitHub handle Attendance
Enrico Fucile WMO Secretariat / WIS --- X
David Berry WMO Secretariat / WIS --- X
Luis Nunes WMO Secretariat / WIGOS --- X

Agenda

  • Tom – Open the kickoff meeting
  • Roundtable introductions
  • Anna
    • Timeline and meeting schedule
    • Work space overview
  • Jörg: WMDR2
    • Why are we developing WMDR2 and what does it entail
    • Overview of prior developments on WMDR2
  • Tom: WMDR2 bootstrap
    • Architecture of new system
    • WCMP2 development and result
    • WMDR2 framework that is in place
  • Wrap up

Notes (DRAFT)

  • Tom opened the team with a welcome to all
  • Round table introductions
  • Anna explained that the timeline for this ad-hoc team is short in order to have a deliverable for INFCOM-4 by June 2026. The team will meet every two weeks and the minutes will be posted on the GitHub wiki. All topics, questions, reviews and change management will be addressed through GitHub issues and issue branches.
  • Jörg presented on WMDR2
    • Gao talked about how it's important to have enough details to different the instruments and time series
    • Tom noted that there will be a phased approach. The WMDR2 standard and schema naturally supports extensibility over time and the first pass will be a minimal version or core version of WMDR1
  • Tom presented WMDR2 bootstrap
    • Gao asked how the spatial geometries would be represented over time, e.g. ship data and Tom responded that it would need to be looked at in more depth.
    • Jörg asked if the link relations are from a controlled vocabulary and Tom responded that they are from IANA link relations vocabulary and WCMP2 added some extensions e.g. station and stations; we may need a link relation defined for a deployment in WMDR2.
    • Jörg asked about the governance of extensions moving forward and how to deter possible divergences when supporting multiple disciplines. (Tom) In WCMP2 the domains define extensions and the TT-WISMD will support structure and coordination (Enrico) The new approach is agile, starting with a solid core or minimum viable product (MVP) and then engaging with the domains for extensions and additions (Gao) Different communities will use the same thing, but they may have different meanings, this will need to be reconciled (Jörg) WMO governance through an ET to coordinate domains to ensure interoperability (Tom) WMDR2 core should have broad interoperability to cover 80% of the use cases and then a more focused interoperability scan be developed within domain specific extensions. Need to start small with a core that has an extension mechanism. (Anna) Reminder to the team to not get derailed on the outlying 20-30% use cases (Jörg) Concerned that WMDR2 core will not be able to cover 80% in such a short time.
    • (Anna) what are plans for export and conversion from OSCAR Surface and WMDR1 to OSCAR Surface Next Gen and WMDR2?(Tom) conversion tool not in scope for this ad-hoc team, however, there should be a lossless movement of metadata from one system to the other.
    • (Thinesh) The "tombstone" metadata should cover 80% of the use cases and or MVP. What is the path forward for defining the elements? And what do we do with the other stuff? (Tom) We should look at the mandatory fields first in our next meeting and we need to coordinate with the architecture team on what to do with the other stuff. Addressing the "other stuff" can also be addressed through phases. Unlike WCMP2 we are not going to start from scratch.
    • (Jörg) For migration, need to consider information that is not encoded in the XML records but is in OSCAR/Surface, e.g. documents and images; the saved content that is not migrated to WMDR2 will get age and stale (Tom) WMDR1 can be imported into OS2 and we should not manage this content, but WMDR2 can link to the original XML record and as such that the pictures and documents can also be addressed through links WMDR2.
    • (Jörg) who is allowed to issue PRs? (Tom) anyone and the team can review
    • (Jörg) What happens with conditional elements? (Tom) these can be refactored option requirements classes as needed.
    • (Anna) We are at the end of the meeting. All are invited to open issues for questions and discussion topics to work asynchronously;
  • COB, round table of last comments

Actions

Next meeting

2026-02-04

Clone this wiki locally