2023-03-31 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Mar 31, 2023
2 min read

Mar 31, 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

@Ain Aaviksoo (Deactivated)

 

Updates from TC meeting (fixed)

@Ain Aaviksoo (Deactivated) (skipped)

 

Gherkin scenario writing discussion

Everyone (skipped)

Gherkin Scenario drafting document

 

Social Cash Transfer

 

UC-E-USCT-001: Eligibility Determination and Benefit Package(s) Design - Unconditional Social Cash Transfer

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?

Spec 2.0

Everyone

parked for future meeting

 

New Action Items

@Ain Aaviksoo (Deactivated) @Benjamin Balder Bach follow up on @PSRAMKUMAR 's GitBook review comments

Action Items from previous meetings

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) schedule to review Social Cash Transfer Use Case.
@Ain Aaviksoo (Deactivated) add and maintain definitions for subjects of Gherkin scenarios
@Philippe Page sign up to GitBook via GitHub or tell @Ain Aaviksoo (Deactivated) what your existing signup email is.
@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)
Security, Privacy aspects - we need someone to contribute for us (especially if this is not only done by an human) @Ain Aaviksoo (Deactivated) to see if we can find “central” resources to contribute here
@Philippe Page will finish the initial descriptions and commit himself to the ones he feels appropriate
@Benjamin Balder Bach will start revisiting, what’s been written in Consent BB FAQ already in Confluence;
If needed, create another page “to help understand the use of Consent-BB Tech Spec”
@sasi will articulate in Consent BB FAQ these questions to be addressed
(the group can then address them and decide where and how their later proper “place” will be)
@Ain Aaviksoo (Deactivated) will add to CON-1: Consent Specifications v2.0In Progress
Add analysis of UC-USCT to Spec 2.0 as a ticket @Benjamin Balder Bach
@PSRAMKUMAR to review the GitBook PR GitBook Ain created
to write the outcome of discussions with @Philippe Page 2w ago @Ain Aaviksoo (Deactivated)
Open Jira issue about configuration API RBAC @Benjamin Balder Bach edit: we already have CON-74: Revisit RBAC with IDBBDone
Open Jira issue: We need perhaps more general “BB prerequisites for integrating with Consent BB or something” (in addition to tech spec) @Benjamin Balder Bach

Decision