1 | "Urgent" Assignment of topics for multidisciplinary datasets Assignment of topics for multidisciplinary datasets · Issue #38 · wmo-im/wis2-guide Notification mechanism on updated data Notification mechanism on updated data · Issue #9 · wmo-im/tt-nwpmd Clarify broker protocol elements clarify broker protocol elements · Issue #5 · wmo-im/wis2-guide WP8.2 WIS2 -> GTS Gateway WP8.2 - WIS2 -> GTS Gateway · Issue #9 · wmo-im/wis2pilot KPIs for the transition from GTS to WIS2 KPIs for transition from GTS to WIS2 · Issue #20 · wmo-im/wis2-guide Lifecycle management of discovery metadata in WIS2 Lifecycle management of discovery metadata in WIS2 · Issue #85 · wmo-im/wis2pilot Non-functional performance measures need to be defined Non-functional performance measures need to be defined · Issue #23 · wmo-im/wis2-guide (or at least start defining them) GTS -> WIS2 Gateway will operate a decision made, but ET-W2AT should confirm how to operate.
| | Discussion 1.Assignment of topics for multidisciplinary datasets Assignment of topics for multidisciplinary datasets · Issue #38 · wmo-im/wis2-guide The topic_hierarchy will only be used to identify a channel for pub/sub. When a dataset is applicable under multiple domains, the data producer should choose one domain (that is a best fit) and use the WCMP2 metadata record for further descriptions.
(Timo): In general, MQTT best practice is to publish the message with two (multiple) topics. (Rémy): Please provide supporting evidence of this MQTT best practice.
2. Notification Mechanism on updated data Notification mechanism on updated data · Issue #9 · wmo-im/tt-nwpmd Decision: properties.operation is included in the notification message Decision: value= create/update/delete, if multiple update messages are received, compare by pub_time Action: write an AsciiDoc describing why and how and make in available on github. Agreed that WIS2 Guide will be a collection of all individual AsciDoc
3. Clarify broker protocol elements clarify broker protocol elements · Issue #5 · wmo-im/wis2-guide Agreed that: MQTT experts advice is required to select the right parameters Action: (Remy) to check with Verne MQ for their advice to selecting the parameters Action (TBC): (Peng) to discuss with EMQX experts for possible suggestion about the parameters selection
4. WP8.2 WIS2 to GTS gateway WP8.2 - WIS2 -> GTS Gateway · Issue #9 · wmo-im/wis2pilot TTAAii and CCCC to be added in the message to make it easy to do the mapping from WIS2 to GTS This will not be included in the WIS2 Notification Message standard. It will be included in the GTS → WIS2 transition document. Data provider who wants to stop dissemination on GTS shall use the GTS properties as described in GitHub issue #24 add property for TTAAii · Issue #24 · wmo-im/wis2-notification-message Who will operate those gateways? Considering there is no volunteer for the Gateway, a proposed solution is for one or two RTHs per region to do the gateway from WIS2 to GTS. Action: Hassan will collect all RTH contact points; organize meetings with potential RTH providers and prepare one page for this.
5. KPIs for the transition from GTS to WIS2 KPIs for transition from GTS to WIS2 · Issue #20 · wmo-im/wis2-guide (Kai) DWD metrics include number of observations received in DWD and WIS2 network per station and per country. There is a need to develop metrics: names of metrics and their purpose. (Enrico) High-level KPIs, not too technical, for communication to EC/Cg is needed to get started. For example, the number of Members disseminating data in GTS but not WIS2; the number of Members migrating to WIS2 Action: (Enrico) to provide a drafted version of high-level KPIs to be submitted to INFCOM-3
8. GTS to WIS2 gateway DWD: all data received in GTS are published the Global cache using the topic cache/a/wis2/xxg/gts_to_wis2_dwd/TTAAii New data is only available in WIS2 Decision: DWD to run GTS to WIS2 Gateway during transition Action: (Kenji) to check internally the possibility of providing the GTS to WIS2 Gateway by JMA
|