Date
11:00-12:30UTC
Agenda
1. Introductions
2. How will ET-W2AT work; what are its priorities?
Prioritisation: Technical Regulations for INFCOM2*
Engagement with other Expert Teams
Confluence
Regular meetings
Discussion: agree working methods and routine meeting cadence.
* INFCOM2 now delayed from Feb 2022 until Nov 2022
3. Evolution not revolution
Aim: to make the “entry ticket” for WIS2 participation as simple as possible
Discussion: what are the key technical blockers to participation in WIS1?
Discussion: what should we prioritise for our approach in transition from WIS1 to WIS2?
4. Shared services for GISCs
Why shared services?
Discussion: feasibility of a shared service approach.
Discussion: how should we approach organising the GISC community for shared service provision?
5. Underpinning functions that impact all WIS Centres
Providing access to data: Web services not GTS
Metadata and catalogues: Simple data publication and better discovery
Real-time notifications: Evolution of GTS - pub-sub messaging and phase out routing tables
QoS, performance monitoring, cybersecurity: How do we know WIS2 is working?
Discussion: what are the key changes from WIS1? (we all need to be on the same page)
Discussion: have we missed anything? (is this list complete)
6. Where do we need draft Tech Regs for INFCOM2
See https://wmo-teams.atlassian.net/wiki/spaces/WIS2/pages/164397103/Plan#INFCOM2%3A
Discussion: agree the priority topics for Tech Reg development
7. Organising ET-W2AT to get the work done
Discussion
8. Next meeting
Participants
Dale Hubbard
Background information
Our priority is preparing draft Technical Regulations - concrete technical specifications that will help Members begin to design their contributions to WIS 2.0.
Following discussion with Remy, we've created a list of the priority topics. See the WIS2 Confluence pages (you should all have access):
A number of other, lower priority topics are identified as discussion items. We'll get to these if we have time. We may be able to cover these in an INF paper for INFCOM2. Which means no need for translation, and a few extra weeks of working time.
We have also captured the current thinking about the architecture of WIS 2.0. This is also published on Confluence.
Our overriding aim with WIS 2.0 is to make participation easier while still delivering the vision of WIS. For those not familiar with WIS 2.0, please see the attached presentation that provides a very short overview with some links to more detailed documentation. Check out the presentation notes for more detail.
Back on the Confluence pages, you will see several topics covered in further detail:
· Real-time notifications via pub/sub messaging
· Quality of Service / performance monitoring
Please read this material. Nothing is approved yet (it's up to ET-W2AT to make those recommendations) - but I think the proposals do provide a great start.
I encourage you to use the comment functions with Confluence to ask questions and contribute your ideas etc. Alternatively, just edit the Confluence pages themselves - but please to mark your additions with you name so that we can see where changes are coming from.
Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
Add Comment