2023-05-12 - Weekly update

Owned by Benjamin Balder Bach
Last updated: Jun 29, 2023 by PSRAMKUMAR
3 min read

May 12, 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)

  •  

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week

@Ain Aaviksoo (Deactivated)

 

Updates from TC meeting (fixed)

@Ain Aaviksoo (Deactivated)

  • There are no new actions for Consent BB. There has been an outreach from the UI/UX BB who will present their proposal for consent UI soon.

  • We need to resolve what the Identity BB’s resource model means when it mentions consent. Ain will continue dialogue with the IDBB such that the Consent BB is used in their resource model.

Gherkin scenario writing discussion

 

Updates from Tuesday meeting

 

We have tried to make use of a Gherkin Scenario to understand the depth of delegation for consent.

Benjamin will follow up with some notes on Ain’s Gherkin scenario mock-up.

Spec 2.0: Unfolding new roadmap items

 

 

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?

Next meeting

 

  • Scheduled an meeting on Wednesday May 3

  • Weekly meeting on May 5 moved to May 9

 

 

 

 

 

 

 

 

 

 

 

 

New Action Items

Review and indicate if an answer is accepted @Ain Aaviksoo (Deactivated) @Philippe Page
Review @Ain Aaviksoo (Deactivated)

Action Items from previous meetings

We need a meeting around verifying or gathering input from the Working group on the sequence diagram in @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)
@Philippe Page will finish the initial descriptions and commit himself to the ones he feels appropriate
@sasi will articulate in these questions to be addressed
(the group can then address them and decide where and how their later proper “place” will be)
Add to ticket with the links to relevant discussion by other groups @Ain Aaviksoo (Deactivated)
@Ain Aaviksoo (Deactivated) will add to
@PSRAMKUMAR to review the GitBook PR Ain created
to write the outcome of discussions with @Philippe Page 2w ago @Ain Aaviksoo (Deactivated)
Open Jira issue: Epic for Internal Workflows, tasks for each internal workflow @Benjamin Balder Bach
Open Jira issue: Epic for Universal Social Cash Transfer @Benjamin Balder Bach See CON-2 + Cross-reference TECH Jira tickets about the same.
@Ain Aaviksoo (Deactivated) identify a process to give feedback and guidance to the use cases analysis lead by the sandbox team
Draft a sharable call for new WG members @Benjamin Balder Bach (intention is to have it approved and made official so we can share it for targeted recruitment of new WG members).

Decision