2023-12-22 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Dec 15, 2023
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

  • @George J Padayatti

Meeting Notes

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Kanban board + Action points from last week

skipped

  • Consent BB Spec 2.0 scoping (to be cont’d)

  •  

General update (5 min)

skipped

 

Next meeting

 

When do we resume?

Action items

 

We have been discussion consent definition and alignment with the DDX solution in terms of:

  • Current specification’s consent definition

  • Data Agreement

  • Alignment with UX Guidelines

  • What do we need to add in the spec (schemas/endpoints) if the whole UI flow of DDX should be included?

 

 

 

SEASONAL GREETINGS

everyone

 

 

 

 

 

 

 

Offline consent

postponed to next meeting

We had to postpone this. Note that we’re trying to figure out a terminology here. “On-demand” consent was used to emphasize the risks of this kind of thinking, but “offline consent” will help us capture the broader nature. Everyone is encouraged to think about terminology

UI/UX feature in DDX Spec

 

Should we add this to Consent BB spec too?

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

Action Items from previous meetings

@Ain Aaviksoo 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.
@Ain Aaviksoo Call for a discussion meeting regarding “on-demand” OR multi-party consent workflows (need to choose which topic?)

 

Decision