2023-01-27 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Jan 27, 2023
2 min read

Jan 27, 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 09:30am CET

Attendees

  • @Ain Aaviksoo (Deactivated) (meeting facilitator)

  • @Philippe Page (on mobile in beginning, fully joined in the end)

  • @Lal Chandran (out)

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

  • @sasi

  • @PSRAMKUMAR

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week

@Ain Aaviksoo (Deactivated)

 

Updates from TC meeting

@Ain Aaviksoo (Deactivated)

TC awareness created around IDBB, scopes.

When is the information mediator needed?
Does GovStack need a service registry?
See: BB Interaction Flow

Comment from @PSRAMKUMAR about workflow and scope: A BB will be responsible for specifying the workflow of a “step”. A service can “origin” or start and end somewhere, this is important to identify responsibility. It’s necessary to break down into Building Blocks.
Notekeeper’s note: It’s difficult to capture the details in the discussion around BB workflows and scopes. It seems to be an unresolved area.

IDBB Followup

@Ain Aaviksoo (Deactivated) @sasi

Follow-up from Wednesdays meeting

  • Scopes?

  • Bundled APIs?

  • Individual schema: Would we want to add more fields?

Declare the “many APIs”. Let improvements happen “evolutionary”. Deprecations etc. can happen later. We can improve slowly. Another BB has over 40 APIs

Gherkin scenario

@Benjamin Balder Bach @Ain Aaviksoo (Deactivated)
postponed for next meeting

Status update based on scenario drafting document: Gherkin Scenario drafting document

Payment Use-Case

@Ain Aaviksoo (Deactivated)
postponed for next meeting

What are consent-related aspects of the Payment UC?

Scope and service registry?

@sasi @Ain Aaviksoo (Deactivated)
postponed for next meeting

What are our next actions on registering required scopes for BB services?

“Consent management” definition

@Ain Aaviksoo (Deactivated)
postponed for next meeting

We renamed “Consent Management BB” to “Consent BB”. Is there a useful definition of “consent management” that we can apply?

AOB

all hands

Feedback on API test reporting UX?

New Action Items

Action Items from previous meetings

@Benjamin Balder Bach and @Lal Chandran add latest IMAGE renditions of sequence diagrams. Note from meeting: If not possible, Benjamin will just re-encode the entire diagram whenever the next change occurs. (blocked / reminder)
Presentation of API endpoints, mocks and tests for technical committee meeting Thursday @Ain Aaviksoo (Deactivated) (blocked / reminder)
Everyone: Read email forwarded from Jaume about new IMBB
Next meeting: Feedback on API test reporting UX
Compliance concept - @Ain Aaviksoo (Deactivated) (blocked / reminder)
Finish the first full draft of Gherkin scenario service APIs - @Ain Aaviksoo (Deactivated)
@Ain Aaviksoo (Deactivated) to reschedule the weekly meeting for 9:30 AM and call for a meeting on ID BB and a Spec 2.0 planning meeting.
We need a meeting around verifying or gathering input from the Working group on the sequence diagram in BB Interaction Flow @Ain Aaviksoo (Deactivated) will call for this.
@Ain Aaviksoo (Deactivated) will prepare an update and digest on Gherkin scenarios for next week’s extra internal meeting.

Decision

  1. Consent BB decides to restrain from redesigning API endpoints in order to “bundle” or “optimize” sequences of calls. Unless the TC eventually comes up with a stance of this.