2023-04-17 - Work meeting

Owned by Benjamin Balder Bach
Last updated: Apr 17, 2023
3 min read

Apr 17, 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)

  • This meeting was ad-hoc, it was scheduled last Friday.

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Completing 1.0

@Ain Aaviksoo (Deactivated)

  • Note: First ~20 minutes of last meeting have a good explanation from @PSRAMKUMAR about priorities and changes for the 1.0 release, especially Internal Workflows.

  • We went over questions from Valeria. @Benjamin Balder Bach to send a question to ensure there is no manual changes in the API specs (because of its tooling)

  • Can we build an Internal Workflow that specifies from where events originate? This can specify how the registered parties in AuditTracker are called.

  • Internal Workflows:

    • Event notifications for AuditTracker

    • Revisioning

    • Verification of tampering

    • Logging?

    • APIs: Verification of credentials (configuration / service / auditing)

    • Study current Gherkin Scenarios of registration

  • We anticipate that collaboration with a vendor can happen in a way where we focus on quickly developing and releasing an Internal Workflow

  • We need guidelines for the collaboration between WG and vendor, ensuring independence and integrity of all WG decisions and priorities.

Universal Social Cash Transfer

@Ain Aaviksoo (Deactivated)

We went through the various documents, mockups and diagrams for the new UC.

Diagram: Sandbox Use Case Analysis - USCT 1 (Unconditional Social Cash Transfer)

What to focus on now?

  • We will work towards identifying scenarios relevant to the UC and to the roadmap items of features and issues that the Consent BB 2.0 needs to specify (multi-consent, guardianship etc)

  • Scenarios can be added on Jira already by their title.

  • Sending feedback about the role of Consent in current sandbox team’s analysis?

 

 

 

 

 

 

 

 

 

 

 

 

New Action Items

Open Jira issue: Epic for Internal Workflows, tasks for each internal workflow @Benjamin Balder Bach
Open Jira issue: Epic for Universal Social Cash Transfer @Benjamin Balder Bach See CON-2
@Ain Aaviksoo (Deactivated) identify a process to give feedback and guidance to the use cases analysis lead by the sandbox team

Action Items from previous meetings

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.
@Ain Aaviksoo (Deactivated) add and maintain definitions for subjects of Gherkin scenarios
@Philippe Page sign up to GitBook via GitHub or tell @Ain Aaviksoo (Deactivated) what your existing signup email is.
@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)
Security, Privacy aspects - we need someone to contribute for us (especially if this is not only done by an human) @Ain Aaviksoo (Deactivated) to see if we can find “central” resources to contribute here
@Philippe Page will finish the initial descriptions and commit himself to the ones he feels appropriate
@Benjamin Balder Bach will start revisiting, what’s been written in Consent BB FAQ already in Confluence;
If needed, create another page “to help understand the use of Consent-BB Tech Spec”
@sasi will articulate in Consent BB FAQ these questions to be addressed
(the group can then address them and decide where and how their later proper “place” will be)
@Ain Aaviksoo (Deactivated) will add to CON-1: Consent Specifications v2.0In Progress
Add analysis of UC-USCT to Spec 2.0 as a ticket @Benjamin Balder Bach
@PSRAMKUMAR to review the GitBook PR GitBook Ain created
to write the outcome of discussions with @Philippe Page 2w ago @Ain Aaviksoo (Deactivated)
Open Jira issue about configuration API RBAC @Benjamin Balder Bach edit: we already have CON-74: Revisit RBAC with IDBBDone
Open Jira issue: We need perhaps more general “BB prerequisites for integrating with Consent BB or something” (in addition to tech spec) @Benjamin Balder Bach
@Ain Aaviksoo (Deactivated) @Benjamin Balder Bach follow up on @PSRAMKUMAR 's GitBook review comments

Decision