Meeting 2023 05 05 - wmo-im/tt-wismd GitHub Wiki
Date/Time
Friday 05 May 2023 12h - 13h30 UTC
Location
MS Teams
Attendees
Name | Agency | GitHub handle | Attendance |
---|---|---|---|
Mr Tom KRALIDIS (Lead) | MSC | @tomkralidis | X |
Mr Guillaume AUBERT | EUMETSAT | @gaubert | X |
Mr Xinqiang HAN | CMA | @Amienshxq | |
Ms Hanane KAMIL | Météo Maroc | @hananeKamil | |
Mr Ioannis MALLAS | ECMWF | tbd | |
Mr Ian MCDONALD | EUMETSAT | @McDonald-Ian | |
Mr Steve OLSON | NOAA | @solson-nws | X |
Mr Ján OSUSKY | HMEI | @josusky | |
Mr David PODEUR | MF | @davidpodeur | X |
Ms Antje SCHREMMER | DWD | @antje-s | X |
Ms Julia SEILAND | DWD | @jsieland | X |
Mr Kentaro TSUBOI | JMA | @ktsuboi-jma | |
Ms Anna MILAN | WMO | @amilan17 | X |
Mr Dave Berry | WMO | X |
Agenda
- Previous meeting minutes and actions (all)
- Secretariat updates (WMO)
- OGC API - Records updates (Tom)
- WCMP2
- WCMP2/WNM analysis (Anna)
- PRs
- KPIs (Julia): https://github.com/wmo-im/wcmp2/pull/93
- issues (all)
- data policy/licensing/copyright: https://github.com/wmo-im/wcmp2/issues/4#issuecomment-1444359402
- provider types: https://github.com/wmo-im/wcmp2/issues/66
- type enumeration: https://github.com/wmo-im/wcmp2/issues/49
- WIGOS integration: https://github.com/wmo-im/wcmp2/issues/19
- implementation updates round table (all)
Notes
- Tom opened the meeting and there were no actions to review;
- Anna mentioned that there have been discussions about the relationship b/t WIS/WIGOS metadata and systems;
- Tom provided a status update on OGC API records: There has been a boost of activity on the OGC SWIG looking at Q3 of this calendar year for approval by OGC; last week there was an OGC sprint in Lausanne; publication of metadata goes through a pub/sub approach and it's moving away from harvesting; we might still need harvesting in WIS2 in order to federate with other catalogs, like oceans and cryo; in WIS1 we used OAIPMH, and for WIS2 we will implement the requirements defined by OGC; regarding API searches there will be a faceted/aggregation approach; there was a lot of discussion around tooling and the record model; the model has some updates to align with STAC; the roles have changed... so we will need to update the way the contact property is represented and we need to define the roles in the WCMP2 specification probably with code lists; (Guillaume) how does the harvesting affect the metadata, they are separate right? (Tom) yes (Guillaume) will we need to develop vocabulary for these facets? (Tom) the discovery catalogs will need to support facets and there should be guidance on how to implement the aggregations in the catalog; (Guillaume)ok, so will this group specify which values should be used as facets? (Tom) they should be in the requirements in the specification and it will be a controlled vocabularies and validated; (Guillaume) what is the timeline and how do we keep this alignment? (Tom) I think we need to have a final version of WCMP2 ready for INFCOM-3 in spring of 2024; (Antje) regarding facets are topics for the search engines that facilitate the drill down and we should have a fixed amount of values; Perhaps it will be enough to have some suggestions for possible facets and not make it a fixed list; ACTIONs: Antje share a document and Tom will open an issue for facets
- Anna presented a study on inconsistencies (powerpoint) ACTION: Anna open two issues to remove W2TH where discussed
- Julie presented her work on the revisions to KPIs, mostly to align with WCMP2; Julie will continue with some minor revisions and next will implement in pywcmp; (Antje) for the KPI implementation it would be helpful to have all of the errors directly in the output and where it originated from;
- Tom presented the most recent solution for https://github.com/wmo-im/wcmp2/issues/4. (Antje) how do represent a service that is providing core and recommended data? (Tom) moving from service oriented approach to dataset approach, services should be discoverable through the dataset (Antje) e.g. OGC mapserver where the service is open to all, but one must login to access recommended data (Tom) ACTION: open issue to add a requirement that if resource-type is "dataset", then need to include wmo:dataPolicy property and this will go into the abstract test suite; (Anna) there is an open issue in WIS2-Guide including a recommendation for Global services to have WCMP2 records for them with a resource-type of "service". (team) all agree with new proposal for data policy as captured in the issue; ACTION: Tom will make PR
- The team discussed provider types: https://github.com/wmo-im/wcmp2/issues/66. ACTION Guillaume will do an investigation on the roles and what could be applicable for WCMP2; (Antje) it would be useful to reuse the properties in the contacts, such as address;
- The team looked at https://github.com/wmo-im/wcmp2/issues/49; ACTION: Anna will review spec to see if it's clearer now
- Tom presented issue 19
- next meeting
Actions
- @tomkralidis open an issue on facets for GDC
- @antje-s share a document on facets
- @amilan17 open two issues to remove W2TH where discussed: https://github.com/wmo-im/wcmp2/issues/95 and https://github.com/wmo-im/wis2-notification-message/issues/43
- @tomkralidis open issue to add a requirement that if resource-type is "dataset", then need to include wmo:dataPolicy property and this will go into the abstract test suite
- @tomkralidis open PR to include resource type "service"
- @gaubert investigate options for role codelists
- @amilan17 will review WCMP2 in hopes of closing issue #49