Information Mediator Working Group Meeting memos

Meeting Day/Time: Thursday biweekly 10:00 UTC / 12:00 CET, check Slack channel

Thursday, June 26th, 2025

Attendees:
Maksim Ovtsinnikov
Aleksandr Reitsakas
Farai Mutero
Bashar Abdul Qayiume

Agenda/discussion points:

1. Maksim gave an overview of the Q2 2025 spec release
2. Maksim will get in touch with NIIS as soon as Q2 2025 version is published to start the self-assessment process
3. Maksim briefly covered the topics for the Q3 2025 spec release:
* Pub-sub implementation review and update
* Creating IM BB implementation guide
* Replacing Service Directory with Registry BB

Thursday, June 12th, 2025

Attendees:
Maksim Ovtsinnikov
Aleksandr Reitsakas
Tõnis Pihlakas
Bashar Abdul Qayiume

Agenda/discussion points:
1. Discussion of IM-138: Analysis of Registry BB spec in light of using Registry as IM BB Service Catalogue implementationProposed
2. Discussion on the changes to the specification in light of IM-138: Analysis of Registry BB spec in light of using Registry as IM BB Service Catalogue implementationProposed
3. Discussion on the scope of the next release

TODO before next meeting:
1. Maksim to interview Payment BB working group regarding pub-sub (Arnold was on leave during week 24)
2. Aleksander to work on IM-136: Analyze Nortal PoC pub-sub implementation vs. current IM spec, create a document that describes the differencesProposed
3. Maksim to do changes in the spec regarding X-Road compliance

Next meeting: Thursday, 26th of June, 12:00 CET

Thursday, June 5th, 2025

Attendees:
Maksim Ovtsinnikov
Aleksandr Reitsakas
Tõnis Pihlakas

Agenda/discussion points:

1. Review and discussion of Information Mediator - Pub/Sub use cases
2. Review and discussion of Information Mediator - pub/sub implementation examples and ideas
3. Defining tasks for next time (see Jira)
4. Next meeting: Jun 12, 2025

Thursday, May 22nd, 2025

Attendees:
Maksim Ovtsinnikov
Aleksandr Reitsakas
Tõnis Pihlakas

Agenda/discussion points:
* Pub-sub / X-Road compliance related changes to the specification + possible re-design of the technical solution?
** TO-DO:
a) analyze Nortal PoC vs. current spec: Aleksandr
b) describe a couple of use-cases for pub-sub (e.g. near-real-time delivery; fan out; asynchronous reply): Tõnis
c) explore existing pub-sub products: Maksim
* Decentralized architecture (current approach) vs. ESB vs. API gateway. We should elaborate more on this topic in the specification. Where?
** Maksim to share thoughts on X-Road vs. ESB
** X-Road and API gateway: Tõnis, Aleksandr.
** Rate limiting. Should it be part of the IM spec scope? Reverse proxy; nginx;.. SLA management is the broader topic here.
* Service catalogue vs. Registry BB. Service catalogue could implement Registry, because it is a Registry in nature.
** TO-DO: analyze Registry BB spec and get an understanding whether we can use it as-is. If not, maybe Registry BB needs to be updated? - Bashar will do this.
* Central/control BB or finding the right place for Central Server in the specification?
* More distant future: harmonizing IM BB specification with the data spaces concept

TODO: Maksim to create new sprint in Jira for the next 2 weeks and tasks.


Next meeting: Thursday, June 5th, 2025 @ 10:00 UTC / 12:00 CET
https://calendar.app.google/pbsNwi94DqqCCw2x7

Thursday, May 8th, 2025

Attendees:
Maksim Ovtsinnikov
Tõnis Pihlakas
Eric Ramirez
Anita Mittal
Bashar Abdul Qaiyume
Jihene Louati
Vivek Manoharan
Tanvir Quader
Taavi Toomere

Agenda

1. Short introduction of Maksim and his role
2. Introduction round-table
3. Overview of short-term and long(er)-term plans with GovStack IM BB specification
4. Questions round
5. Wrap-up.

Next meeting: Thursday, May 22nd, 10:00 UTC

Action items before next meeting:
1. Participants join Slack channel
2. Participants review the current status of the specification
3. Maksim to find the Facilitator / Technical Lead for the working group
4. Maksim to start working on updating specification (re-labeling the requirements, making pub-sub / asynchronous message exchange requirements optional)

Wednesday, March 29th, 2023

Attendees:

1. @Taylor Downs

2. @Aleksander Reitsakas

3. Ramkumar

Agenda

Next Steps & Action Items

Wednesday, March 22nd, 2023

Attendees:

1. @Taylor Downs

2. @Tonis Pihlakas

3. Ramkumar

Agenda

1. @Tonis Pihlakas wondering about API authentication

   1. Keycloak

   2. https://www.id.ee/en/article/trust-services-authentication-services/

   3. https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/39QVhd0jD6S29Isr7KGF/architecture-and-nonfunctional-requirements/6-onboarding#6.2-api-gateways - Ramkumar points to this doc to explain the auth/api gateway strategy.

Action Items

Wednesday, March 1st, 2023

Attendees

1. Aleksander

2. Tõnis

3. Taylor

4. Ramkumar

Team Focus

We need to define service APIs so we can validate candidate applications to play the role of Information Mediator.

Agenda

1. API for Registering Members/Applications with the IM

   1. @Taylor Downs “Are there two different applications with two different APIs that must be defined? The central-server and the security-server?”

   2. For the purposes of this conversation, we assume that a central-server has already been deployed and a security-server is already running and in communication with that central server. Now we discuss adding a member to that security server and registering applications/services.

   3. If a member has been registered with a central-server , the security-server should provide an API which allows you to add/enable that member on the security-server.

      1. post to /api/members with << WHAT DETAILS >> in order to register a new member with the IM

2. Tõnis' proposed changes/comments for the spec

Next Steps

Old Meeting Notes

• IM Past Meeting Note

• 20.04.2021- Meeting Note

•