Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

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 ordinary starting time at 07:45 UTC / 09:45 CET / 13:15 IST

Attendees

Meeting Notes

Agenda

Presenter

Discussion

Kanban board + Action points from last week

Ain Aaviksoo

skipped

General update (5 min)

Ain Aaviksoo

skipped

iGrant demo (Tuesday)

https://www.youtube.com/watch?v=UAiFvciYM34

Discussion on consent on-demand

There is a lot of UX, technical and ethical implications that makes it challenging.

Should the Consent BB have responsibility for on-demand consent? Our previous position has been to delegate this to the application on its own terms.

Lal proposes to do further research on this. Will call for a meeting dedicated to the topic.

This is inspired from the USCT (Universal Cash Transfer) use case.

Potential outputs: Our own specification recommendations/guidelines/Workflow BB pattern.

Workflows are not just digital, but workflows can happen offline.

Delegation

Delegation is prioritized highly.

There are two other items in the roadmap that we keep separate: Multi-party consent. Relationships between multiple agreements.

We need a separate meeting. Future Considerations (Consent)

Consent delegation

skipped

  • CON-52 - Getting issue details... STATUS

  • Where is the relationship between individuals stored?

    • The application is aware of it?

    • Another BB is aware of it?

    • Auditing should be able to verify it

Review necessary Gherkin scenarios to implement

Benjamin Balder Bach Skipped

CON-15 - Getting issue details... STATUS

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

  • Organize a coordinating meeting with Testing team Ain Aaviksoo
  • Open a PR with Dockerized setup in consent-bb repository George J Padayatti
  • Call for a discussion meeting regarding “on-demand” OR multi-party consent workflows (need to choose which topic?) Ain Aaviksoo

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)
  • Benjamin Balder Bach Prepare fixtures review for Lal
  • Ain Aaviksoo will coordinate with Sandbox team - note that Lal is requesting and end2end use case.
  • Benjamin Balder Bach solve a million Jira issues and do not let Ain have all action items alone (smile)

Decision

  • No labels