2023-08-04 - Weekly Update (agenda)

Owned by Benjamin Balder Bach
Last updated: Aug 04, 2023 by Ain Aaviksoo (Deactivated)
2 min read

Aug 4, 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)

  • @PSRAMKUMAR

  • @Philippe Page

  • @sasi

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week (fixed)

@Ain Aaviksoo (Deactivated)

 

Updates from Technical Committee meeting (fixed)

@Ain Aaviksoo (Deactivated)

@Benjamin Balder Bach

  • has passsed over our input to Sandbox team

  • will continue writing Gherkin scenarios and send over to testing teams

  • add test data in addition to APIs

 

Benjamin had a contact with a Danish Gov architec; potential link for

Finalising v1 spec

@Ain Aaviksoo (Deactivated)

Need to comply with the spec release plan - https://govstack-global.atlassian.net/jira/plans/reports/6EFAz

For this

  • Consent MVP

Planning for Egypt meeting (Sept)

@PSRAMKUMAR , @Ain Aaviksoo (Deactivated)

 

Consent agreement lifecycle

@Benjamin Balder Bach

We have a stub model AgreementLifecycle. Let’s discuss and decide what to do from here.

Consent delegation

@PSRAMKUMAR

Review necessary Gherkin scenarios to implement

@Benjamin Balder Bach Skipped

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
Create Jira epic to track individual Gherkin scenarios being drafted and implemented @Benjamin Balder Bach
Add cases that we want to cover for Internal Workflows section in @Benjamin Balder Bach
Create an issue for MVP APIs and how to treat them (GitBook specification? OpenAPI spec?) @Ain Aaviksoo (Deactivated) - identify APIs and functional requirements + separately: what does the MVP subset of APIs and functional requirements look like? Do we mark the requirements that are not strictly necessary? Should we mark what is “required for cross-bb integration”?

 

Decision