2023-07-14 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Jul 14, 2023
3 min read

Jul 14, 2023

About this document: Agenda and notes are kept in the same document, a separate copy of the document is maintained for each meeting. Please add agenda points before the meeting. Action items created in previous meeting and all other unresolved action items are kept in the document. Please tick off any completed items.

Meeting link: https://meet.google.com/rsf-cqaq-eyq at 07:30 UTC / 09:30 CET / 13:00 IST

Attendees

  • @Ain Aaviksoo (Deactivated) (meeting facilitator; meeting note keeper as Benjamin was in the train today)

  • @Benjamin Balder Bach (weekly note keeper and time keeper)

  • @PSRAMKUMAR

  • @Philippe Page

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week (fixed)

@Ain Aaviksoo (Deactivated)

 

Jira Kanban update (fixed)

@Ain Aaviksoo (Deactivated)

Readying our Kanban board for 2-week break. New column: “Review” added.

Numerous issues updated and assigned. We have plentiful of actionable items.

Updates from Technical Committee meeting (fixed)

@Ain Aaviksoo (Deactivated)

(added after meeting by note-keeper) We co-sponsored a decision to align Sandbox and Testing needs for emulating building blocks, and the Consent BB can be a POC that it’s possible by continuing to implement a simulation of our own endpoints.

Consent delegation

@PSRAMKUMAR

Next meeting

 

August 4th: Next weekly meeting
24th of July: Meeting regarding consent tendor

Specification 2.0 presentation and intro

skipped for next week

 

Future collaboration with a tender

Skipped

Based on experiences from other WGs, what modality of collaboration should we have with a future tenderer?

Gherkin scenario writing discussion (ongoing)

Skipped

Gherkin Scenario drafting document

Review necessary Gherkin scenarios to implement

@Benjamin Balder Bach Skipped

CON-15: Create test configuration for Consent Configuration APIsIn Progress

Spec 2.0: Unfolding new roadmap items

Skipped

 

New issues

@sasi

parked for future meeting

  • What do we expect other BBs that call Consent-BB to store?

  • When do we like to use Consent-BB and when do we not expect this? (This should also be know to the auditor.)

Discussion: How shall we address such matters, which do not fit into specification format?

New Action Items

Create Jira epic to track individual Gherkin scenarios being drafted and implemented @Benjamin Balder Bach
Create an issue for MVP APIs and how to treat them (GitBook specification? OpenAPI spec?) @Ain Aaviksoo (Deactivated) - identify APIs and functional requirements + separately: what does the MVP subset of APIs and functional requirements look like? Do we mark the requirements that are not strictly necessary? Should we mark what is “required for cross-bb integration”?

Action Items from previous meetings

@Ain Aaviksoo (Deactivated) consider if the decision to have “external ID” and “external ID type” referencing Individuals is relevant for the Key Desicion Log (if it’s not already there)
@Philippe Page will finish the initial descriptions and commit himself to the ones he feels appropriate
Have someone send out Call: Experts for GovStack's Consent Working Group @Ain Aaviksoo (Deactivated) (converted to Jira task)
Formulate questions to Payment BB about account mapper @Benjamin Balder Bach
Give feedback to Authentication and Cross-BB Authorization @Ain Aaviksoo (Deactivated)

 

Decision