2023-07-07 - Weekly Update

Jul 7, 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

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week (fixed)

@Ain Aaviksoo (Deactivated)

 

Jira Kanban update (fixed)

@Ain Aaviksoo (Deactivated)

We will continue with our changelog and will add Jira ticket numbers. Benjamin will tag Rachel.

Comment from Ramkumar about FAQ work: Can we put a link to the FAQ in “Other Resources”?

Models for Authentication Cross-BB

@PSRAMKUMAR

Ramkumar has presented screen flows for authentication and exchange of tokens.

We’ve decided that we are happy to support all 3 models proposed by Ramkumar.

Specification 2.0 presentation and intro

skipped for next week

 

Testing: mock and emulation

@Benjamin Balder Bach

If @PSRAMKUMAR is present, we can discuss this

 

 

 

Future collaboration with a tender

Skipped

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

Updates from TC meeting (fixed)

@Ain Aaviksoo (Deactivated)

Authentication and Cross-BB Authorization
We should give feedback to this document.

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

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