2023-03-03 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Mar 03, 2023
3 min read

Mar 3, 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 9:30am CET

Attendees

  • @Ain Aaviksoo (Deactivated) (meeting facilitator)

  • @Philippe Page

  • @Lal Chandran (out)

  • @Benjamin Balder Bach (weekly note keeper and time keeper)

  • @sasi (out)

  • @PSRAMKUMAR (out)

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week

@Ain Aaviksoo (Deactivated)

 

Updates from TC meeting (fixed)

@Ain Aaviksoo (Deactivated)

(ad-hoc)

Spec 1.1 updates in GitBook

 

Merging on GitBook and maintaining Jira issues.

We have almost gone through all specification updates, pending some merges and Jira issue maintenance.

A larger outstanding item remains around data models, which Benjamin suggests will be auto-generated by our API spec tooling.

Gherkin scenario writing discussion

Everyone

Specific questions discussed from Ain’s work on Gherkin Scenario drafting document

Comment from Philippe: The usage of functional IDs for consent can be full of problems.
Ain: The approaches can be illustrated, as well as issues with using functional IDs.

Example can be worked out for how for instance Consent IDs can be used (notekeeper: this ID already may already exist, so the issue is around how we can illustrate the usage and reference of Consent BB’s Individual IDs and Consent Record IDs).

Added as an action item for Philippe and Ain to expand in a Jira issue.

 

 

 

Non-functional security requirements for ID and consent?
(for next meeting)

Noted for next meeting.

Should we add inputs to general Non-functional security requirements regarding consent? Training requirements for staff?

Social Cash Transfer

(noted for next week’s agenda)

 

Question from Sasi: is there any way to that multiple parties can interact with each other based on a broader agreement rather than a one to one agreement?

 

Note keepers notes: We’ll probably have to take this one up at a later meeting because we didn’t get to an action item on this one.

Payment Use-Case

@Ain Aaviksoo (Deactivated)
postponed for next meeting

What are consent-related aspects of the Payment UC?

Scope and service registry?

@sasi @Ain Aaviksoo (Deactivated)
postponed for next meeting

What are our next actions on registering required scopes for BB services?

“Consent management” definition

@Ain Aaviksoo (Deactivated)
postponed for next meeting

We renamed “Consent Management BB” to “Consent BB”. Is there a useful definition of “consent management” that we can apply?

New Action Items

Get GitBook invite for @Philippe Page
@Philippe Page sign up to GitBook via GitHub or tell @Ain Aaviksoo (Deactivated) what your existing signup email is.
@Ain Aaviksoo (Deactivated) forward a question about
@Benjamin Balder Bach create a variety of simple Gherkin scenarios for registering an individual so it’s clear that the Consent BB doesn’t care about the type of ID and how it stores external references.
@Philippe Page Create a Jira issue discussing to create a confluence page that has new scenarios which can illustrate why a modular system like GovStack benefits from using Consent IDs that aren’t directly mapped to functional IDs. Ultimately to mature into specification, maybe Gherkin scenarios.
@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)

Action Items from previous meetings

Presentation of API endpoints, mocks and tests for technical committee meeting Thursday @Ain Aaviksoo (Deactivated) (blocked / reminder)
Compliance concept - @Ain Aaviksoo (Deactivated) (blocked / reminder)
We need a meeting around verifying or gathering input from the Working group on the sequence diagram in BB Interaction Flow @Ain Aaviksoo (Deactivated) will call for this.
@Ain Aaviksoo (Deactivated) schedule to review Social Cash Transfer Use Case.
@Benjamin Balder Bach look at previous notes to embed OpenAPI in GitBook and send a note to Ramkumar
@Ain Aaviksoo (Deactivated) sync up with @Benjamin Balder Bach on Tuesday about reporting back to TC on Spec 1.1 updates
@Benjamin Balder Bach add the next Gherkin scenario for Draft Consent Records based on Ain’s work
@Ain Aaviksoo (Deactivated) add and maintain definitions for subjects of Gherkin scenarios

Decision