Attendees
Apologies
Agenda | Presenter | Duration | Discussion | ||||||||
Technical Reviews of BB specs | 10 minutes | Update on review process:
Wes to review Wave 3 BBs to ensure that they are aligned to the template. Ramkumar to work with Wave 3 teams to get complete list of contributors. Steve Conrad - Set up meeting with eMarketplace so that we can articulate the current and future scope, as well as what procurement functionality should be included (either current or future) Specific question for Architecture team:
| |||||||||
PAERA Update | 15 minutes | Update on changes to PAERA document and progress/next steps Working draft: Ready for review and comment (Sections 1-3). Steve and Wes to review. Need to decide where this lives for the upcoming release (GitBook, linked, PDF)?
| |||||||||
Capabilities/Service Blocks | 15 minutes | Review service block (capabilities) template Need clear definition of distinction between building block and service block. | |||||||||
Future Topic - September | Go through key learnings from Egypt deep dive and Kenya roadshow and map out how to address them in the architecture documents
| ||||||||||
Future Topic - October | Identify experts that can do reviews of all Wave 1, 2, 3 BBs and map out process for external reviews | ||||||||||
Future Topic | How to articulate the different levels/scopes of building blocks - foundational/DPI, functional, and possibly application (things like eMarketplace). This should be clearly articulated in GovStack documentation. Also articulate how service blocks fit in to this paradigm. Identify BBs that are missing/needed and develop plan to address those new BBs - get feedback from Egypt and Kenya meetings Provide clear examples of complete solutions that address a use case that show how they are composed of various BBs. Next release can focus more on service blocks and how to use GovStack to create solutions. | ||||||||||
Future topic - Fall 2023 Manage Access Authorization to BB APIs | 30 minutes |
From Technical Committee Meeting: BBs should not own RBAC - the calling applications are responsible for it. Are we using token based authorization within the request to BB? How to get candidates bypass its own RBAC?
|
...