2022 01 27 TT WIGOSMD 18

Task Team WIGOS Metadata (TT-WIGOSMD-18)

Date and Venue

27 Jan 2022, 1300-1430 UTC
MS Teams

Attendees

Team Members  

Name	Present
Jörg Klausen (Switzerland Chair TT-WIGOSMD)	X
Tom Kralidis (Canada ET-Metadata Chair)
Gao Chen (USA)	X
Lara Ferrighi (Norway)	X
Rainer Maerz (Germany)
Ying Wang (China)	X
Juan Bianchi (Argentina)	X

WMO Secretariat  

Name	Present
Enrico Fucile	X
Anna Milan	X
Xiaoxia Chen
Rodica Nitu
Igor Zahumensky
Lize Anthonin (OceanOPS)
Johanna Korhonen
Magali Krieger (OceanOPS)
Washington Otieno.	X

Collaborators

Name	Present
Franziska Stürzl	X
Jitze van der Meulen (KNMI)
John Eyre (UK MetOffice)	X

Agenda

• Welcome [jkl, 5’]
• Acceptance of minutes [jkl, 2’]
• Secretariat Updates [am, 10’]
  • status of FT22-1
  • timeline for FT22-2
  • collaboration matrix spreadsheet
  • GitHub training
• Discuss https://github.com/wmo-im/wmds/issues/190 (John Eyre)
• Other as needed

Notes

• Minutes were accepted.

• Anna talked about the FT22-1 status: waiting for final edits on units table. Will then share with chairs of WIGOS related teams in WMO.

• Anna is offering GitHub training on Feb 10 for editing and managing branches in the WMDS project.

• John Eyre presented his findings on https://github.com/wmo-im/wmds/issues/190;

  • John presented on the status using presentation to JET-EOSDE (JKL) the issue with 3D issues is related, because it relates to the information model, e.g. total column is adding the geometry to a variable; by using the new information model these concerns can be resolved. (JE) short or long term? (JKL) short. This will require a difference between the info model, the codes and the applications use. The combination of 3 things make up a name. This will support alignment with OSCAR requirements. The problem is that we still have the variable tables divided up into different domains. We agreed to combine these into one table and reconcile duplicate codes. We can't do this until the registry is capable of taking this on board. We need a space to begin setting up version 2 of the code lists. We need a transition plan. (JE) this sounds like longer term. (JKL) we need a github space for version 2 development. And then we need a concept for transition with background capability.

  • (GC) we should start with the information model first (JE) it doesn't make sense to have different variable names, but it's important to recognize that there are diff requirements.

  • (WO) in hydrology, we are developing variables, e.g. (?) should we propose different variables or one? (JKL) they are the same variable...(?)

  • (AM) this is a major change and it probably needs to be approved at the congress level first with coordination with the WIGOS program. (JE) this will need some examples for the proposal (JKL) is this really a big deal? the split was done by the team then and it was never approved by Congress. I don't think its really radical. But I do agree that we should bring it to INFCOM or even SC-IMT. (JE) a short paper stating the plan with examples (LF) I like the idea of putting the model and variables into practice

  • (LF) there is a project in RDA that is splitting variables into concepts and CF will adopt this. Should we see if this approach is interoperable with their approach? See webpage (JKL) we should make sure that we are compatible (Lara) ACTION: I can get in touch with my contact.

  • (GC) we should avoid using the term (?), use enhanced capability instead? (AM) but the downstream affects on the applications will be significant (JKL) yes, and this is why versioning is important, but I like the thinking of 'evolution' instead of 'breaking change' (GC) the vocabulary of the change is important and has an effect. And we should make sure that V2 doesn't block V1 or vice versa(?)

• (JKL) wrap up and actions. the spreadsheet discussed in Issue 190? (yes) See Elios Cloud document (JKL) We need to make this spreadsheet more managable by eliminating the matchups and narrowing the scope or broken down into several worksheets or categories. (ACTION) Franziska will chunk it up into manageable bites (AM) we might want to submit distinct issues to address different issues.

• (JKL) ACTION: we should all look at the link: https://github.com/wmo-im/wmds/wiki/The-idea-and-concept-behind-WMDS about evolution towards V2 of the Information Model. This needs to be compared to the RDA document and discuss as needed. If their model covers our needs, then we should try to adopt it. Alternatively, we should convince them to meet our needs. And then there is the issue of governance for long term management. (Lara) this is a work in progress, but I'm not sure that we need to be in 100 percent alignment, but knowing how they map would be helpful or learning from their ideas.

• (GAO) what is the status of the issue #298 (AM) It's going through FT22-1. ET-UAM will have an opportunity for final review before NFP review.

• (AM) Briefly presented the Collaboration Matrix spreadsheet and asked team to fill out.

Actions

• All: Review The-idea-and-concept-behind-WMDS
• All: Review RDA's approach for vocabulary management: https://www.rd-alliance.org/group/interoperable-descriptions-observable-property-terminology-wg-i-adopt-wg/wiki/i-adopt-0
• Lara: Reach out to contact at RDA who is working on developing concepts for CF standard names
• Franziska: organize John Eyre's results on issue190 into manageable categories

Next meeting

17 Feb 2022 1300-1430 UTC