2023-05-26 - Weekly update

Owned by Benjamin Balder Bach
Last updated: Jun 09, 2023 by Ain Aaviksoo (Deactivated)
3 min read

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

  • @Philippe Page

  • @Laurence Berry

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week

@Ain Aaviksoo (Deactivated)

Skipped

 

Consent UI/UX discussion

@Laurence Berry @Ain Aaviksoo (Deactivated) @Benjamin Balder Bach

https://docs.google.com/document/d/1kjLic18ifk_MpcGdHBFBhKA0OlYCLrynF23-9qr7s-U/edit#heading=h.4pzabvifnyg1

  • Lawrence will share scenarios to have consent interactions

  • Joint review of deceptive pattern resources

  • “Acknowledgement” instead of consent

  • Building examples for when to not use consent and when to use consent?

What do we do regarding natural individual identities?

All

Ben: recap of @PSRAMKUMAR 's input from last meeting about BB responsibility of PII. Our “agnostic” approach is falling apart now that we have requirements of doing things in a specific way.

Do we push for a specific approach? Shouldn’t we design against 360 profiling?

Philippe:
Does GovStack have a true position on this matter? There is no common definition of storing identity in BBs.

It’s possible to say that an individual has multiple functional IDs and the individual is responsible for knowing (and proving?) that this is their functional ID?

IDBB questions:

  • Can an application store anonymized IDs in IDBB that are used in the Consent BB? Can it does the mapping?

  • Does IDBB specify how we store individual IDs, i.e. foundational and functional IDs?

  • Is the IDBB a central repository of functional IDs? Can we say that there is a functional ID per BB?

Updates from TC meeting (fixed)

Skipped

 

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

Deceptive pattern review @Benjamin Balder Bach @Laurence Berry
Formulate questions to Payment BB about account mapper @Benjamin Balder Bach

Action Items from previous meetings

@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 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)
Add to CON-1: Consent Specifications v2.0In Progress ticket with the links to relevant discussion by other groups @Ain Aaviksoo (Deactivated)
@Ain Aaviksoo (Deactivated) will add to CON-1: Consent Specifications v2.0In Progress
@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: 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
Review Consent BB FAQ and indicate if an answer is accepted @Ain Aaviksoo (Deactivated) @Philippe Page
Review Call: Experts for GovStack's Consent Working Group @Ain Aaviksoo (Deactivated)
UI/UX draft for consent ideas @Ain Aaviksoo (Deactivated)
Clean up Kanban board to have only active issues in progress @Ain Aaviksoo (Deactivated) @Benjamin Balder Bach
Make Jira board look nice for anyone that wants to contribute @Ain Aaviksoo (Deactivated)
Have someone send out Call: Experts for GovStack's Consent Working Group @Ain Aaviksoo (Deactivated)
Update testing overview with latest figures API Testing - status across BBs @Benjamin Balder Bach

Decision

  1. Onboard new members in 1:1 interviews - if it scales. If there is too much interest, we pick a different model.