TT AvData Teleconference 2023 Jul 27
2023-Jul-27, 13:00-14:00UTC, Webex
- Welcome
- Outcome of MIE/10:
- Items for discussion:
- In a recent discussion on the interoperability between WIS2 and (MET-)SWIM, there are several interesting findings (see Draft Guidance on Technical Specification of WIS2):
- The IT parts (infrastructure adopted, protocol used) are basically the same.
- However the difference in underpinning concept (Resource Oriented Architecture (ROA) Vs Service Oriented Architecture (SOA)) made the configuration and operation of the two very different.
- WIS2 has a Global Catalogue for users to search for datasets while SWIM has a Registry for users to search for information services.
- WIS2 has a Global Cache containing datasets that can be retrieved via req/rep. Dataset links are made available through Dataset discovery metadata (via Global Catalogue) as well as data notification messages (via Global Brokers with pub/sub). This arrangement is similar to Tier 1 (B2B) exchange in MET-SWIM.
- In previous discussions, the need of "MET Service Provider Registry" in addition to the SWIM registry (see diagram was brought up. This registry is in fact equivalent to the WIS2 Catalogue which contains information on available resources (datasets).
- It seems that a natural way to move forward, is to retain both Tier 1 and 2 arrangements, with global exchange of legacy/core MET information through regional brokers in Tier 1, and direct access to providers' pub/sub and req/rep servers in Tier 2, in the end-state MET-SWIM environment.
- In a recent discussion on the interoperability between WIS2 and (MET-)SWIM, there are several interesting findings (see Draft Guidance on Technical Specification of WIS2):
TBI
- Matt Wagner
- BL Choy