/
2023-09-29 - Weekly Update

2023-09-29 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Sep 29, 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 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

@Ain Aaviksoo

skipped

General update (5 min)

@Ain Aaviksoo

Review of Consent BB API documentation - needs attention
Review of Consent BB API documentation

Continued discussion of onboarding APIs

@Lal Chandran

  • What to do with Individual API endpoints?

 

 

 

 

 

 

 

 

 

DDX Consent BB implementation open topics/questions:

skipped

  • Solution and adapter, are they separated?

  • Are you aware of the bb-consent/examples/ structure?

  • Are you aware of GovStack UX Guidelines that are published?

  • What to do with APIs that aren't part of GovStack specs - expose them in the same structure?

  • What do we need to accommodate in the Consent BB planning? What "best-practice" guidance is found for building solutions for GovStack?

  • What sort of workflows are great, for instance for building consent. How will engagement with other BBs work? Will you be able to work on this aspect?

Consent delegation

skipped

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

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)
@Philippe Page will finish the initial descriptions and commit himself to the ones he feels appropriate
@Benjamin Balder Bach Prepare fixtures review for Lal

 

Decision