2023-02-24 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Feb 24, 2023
2 min read

Feb 24, 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

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

  • @sasi

  • @PSRAMKUMAR

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week

@Ain Aaviksoo (Deactivated)

 

Updates from TC meeting (fixed)

@Ain Aaviksoo (Deactivated)

Comments from Ramkumar, 3 priorities from TC:

Update spec for version 1.1 release:

Test APIs with Gherkin without waiting for IM etc.
Unconditional Social Cash Transfer use case has to be gone over.

Gherkin scenario writing discussion

Everyone

Specific questions discussed from Ain’s work on

3 genres of tests:

  1. smoke tests (will be added ASAP)

  2. positive tests (what we are doing now)

  3. negative tests (none yet)

We went over “Individual ID” again, and it becomes evident that we probably need to illustrate the flexibility of the Consent BB “Individual” schema through a complex scenario.

 

 

 

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

@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

Action Items from previous meetings

@Benjamin Balder Bach and @Lal Chandran add latest IMAGE renditions of sequence diagrams. Note from meeting: If not possible, Benjamin will just re-encode the entire diagram whenever the next change occurs. (blocked / reminder) - @Ain Aaviksoo (Deactivated) creates a Jira issue
Presentation of API endpoints, mocks and tests for technical committee meeting Thursday @Ain Aaviksoo (Deactivated) (blocked / reminder)
Compliance concept - @Ain Aaviksoo (Deactivated) (blocked / reminder)
Finish the first full draft of Gherkin scenario service APIs - @Ain Aaviksoo (Deactivated)
We need a meeting around verifying or gathering input from the Working group on the sequence diagram in @Ain Aaviksoo (Deactivated) will call for this.
@Ain Aaviksoo (Deactivated) will prepare an update and digest on Gherkin scenarios for next week’s extra internal meeting.
@Ain Aaviksoo (Deactivated) review the questions that we had
@Benjamin Balder Bach adding “implicit consent” to future considerations since it came up.
@PSRAMKUMAR will forward contacts of Consent BB to the new technical writer for an introduction.
@Benjamin Balder Bach write a more generic Gherkin scenario for Individual creation

Decision

  1. We define Subjects as Proper Nouns in our Gherkin scenarios, properties as lower case.