2023-06-23 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Jul 03, 2023 by Ain Aaviksoo (Deactivated)
2 min read

Jun 23, 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)

 

Specification 2.0 presentation and intro

skipped for next week

 

Misc

 

Philippe will be at an ITU event https://aiforgood.itu.int/summit23/

Sandbox team syncup (2 min)

@Benjamin Balder Bach

/api/status/ is discussed and organized with Sandbox team. @PSRAMKUMAR encourages to pull together Sandbox and Testing efforts, both to align these APIs and to ensure that Emulation of BBs (in the Sandbox) and Mock applications (in testing) aren’t duplicating efforts.

Testing updates

@Benjamin Balder Bach and @Ain Aaviksoo (Deactivated)

We went through current Gherkin scenarios. We discussed the approach and will:

  • Continue to develop more tests in a good pace

  • Develop examples systematically. We are adding a new examples section to our API specification work to align these efforts.

  • New roles and terms are identified in the tests: Configuration Administrator was identified.

  • We start with simple Happy Path tests.

  • We won’t have a lot of time to discuss each scenario, so let’s keep them simple for now. Assumptions can be written as notes for the Happy Path tests.

  • @Philippe Page is participating in this work

  • @PSRAMKUMAR

Future collaboration with a tender

Skipped

Note-keeper: @Ain Aaviksoo (Deactivated) you fell out of the meeting, but I talked to Ramkumar about the task that we have ahead of us: Understanding how we want to govern specification work as a WG once that a tender starts to actively work on a candidate application. I’ll put it here for the next meeting, and it sounds like @PSRAMKUMAR already knows how WGs should function in this setting.

Updates from TC meeting (fixed)

@Ain Aaviksoo (Deactivated)


We should give feedback to this document.

Gherkin scenario writing discussion (ongoing)

Skipped

Review necessary Gherkin scenarios to implement

@Benjamin Balder Bach Skipped

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 @Ain Aaviksoo (Deactivated)
Formulate questions to Payment BB about account mapper @Benjamin Balder Bach
Give feedback to @Ain Aaviksoo (Deactivated)

 

Decision

  1. We will develop examples in our OpenAPI schema