2023-12-01 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Dec 08, 2023 by Ain Aaviksoo
2 min read

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 ordinary starting time at 07:45 UTC / 09:45 CET / 13:15 IST

Attendees

  • @Ain Aaviksoo (meeting facilitator)

  • @Benjamin Balder Bach (note keeper)

  • @Lal Chandran

  • @PSRAMKUMAR

  • @Philippe Page (out)

  • @George J Padayatti

Meeting Notes

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Kanban board + Action points from last week

@Ain Aaviksoo

skipped

General update (5 min)

@Ain Aaviksoo

skipped

iGrant demo (Tuesday)

 

Watch the demo to implement the [GovStack] consent-building blocks | visit www.iGrant.io

Discussion on consent on-demand

 

There is a lot of UX, technical and ethical implications that makes it challenging.

Should the Consent BB have responsibility for on-demand consent? Our previous position has been to delegate this to the application on its own terms.

Lal proposes to do further research on this. Will call for a meeting dedicated to the topic.

This is inspired from the USCT (Universal Cash Transfer) use case.

Potential outputs: Our own specification recommendations/guidelines/Workflow BB pattern.

Workflows are not just digital, but workflows can happen offline.

Delegation

 

Delegation is prioritized highly.

There are two other items in the roadmap that we keep separate: Multi-party consent. Relationships between multiple agreements.

We need a separate meeting. Future Considerations (Consent)

Consent delegation

skipped

Review necessary Gherkin scenarios to implement

@Benjamin Balder Bach Skipped

https://govstack-global.atlassian.net/browse/CON-15

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

Organize a coordinating meeting with Testing team @Ain Aaviksoo
Open a PR with Dockerized setup in consent-bb repository @George J Padayatti
Call for a discussion meeting regarding “on-demand” OR multi-party consent workflows (need to choose which topic?) @Ain Aaviksoo

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)
@Benjamin Balder Bach Prepare fixtures review for Lal
@Ain Aaviksoo will coordinate with Sandbox team - note that Lal is requesting and end2end use case.
@Benjamin Balder Bach solve a million Jira issues and do not let Ain have all action items alone

 

Decision