Attendees
PSRAMKUMAR
Wes Brown
Jukka Aaltonen (Deactivated)
Steve Conrad
Aare Laponin
Uwe Wahser
Aleksander Reitsakas
Paweł Gesek
Ingmar Vali
Apologies
Satyajit Suri
Agenda | Presenter | Duration | Discussion |
Review Mandate and Voting | Steve Conrad | 10 minutes | Architecture Team |
Update on review tasks | Steve Conrad | 10 minutes | Status of BB spec review, non-functional requirements review Ramkumar: Started to work on ID BB spec, will start with other groups next week Suggest to divide specs between team to ensure we can do both a deep technical dive as well as across BBs to ensure consistency
Jukka Next steps, assigning review tasks Ramkumar, Aare, Steve, Aleksander to divide BB specs (ID, Payments, IM, Workflow, Registration, Registries, Messaging, Scheduling, Consent) Aleksander - Registration/Registries Uwe - Registration/Registries (has done a previous review) Ramkumar - ID, IM, Messaging Aare - Scheduler, Payments Steve - Consent, Workflow
Jukka and Aare to review non-functional and security specs Comments can go in Confluence: 1.0 Publication. Each BB should have a separate page - all reviewers to use the same page. Wes and Steve to develop a template/format.
Goal: Initial reviews done by March 31 |
Adaptors | PSRAMKUMAR | 30 minutes | Current approach for onboarding existing tools: https://govstack.gitbook.io/specification/architecture-and-nonfunctional-requirements/6-onboarding Discussion on adaptors and phased approach Is the current approach correct? What is missing? Updating the current documentation How can we create examples of this process? Identifying first products to work with and build adaptors for
|
Information Mediator | PSRAMKUMAR | 15 minutes | Testing with IM: https://github.com/GovStackWorkingGroup/bb-information-mediator/tree/main/examples/bb-openapi |
Next steps/AOB | | 5 minutes | What should we prioritize? Can we spin off small groups to work through specific tasks? |