Kanban board + Action points from last week

@Ain Aaviksoo

skipped

General update (5 min)

@Ain Aaviksoo

skipped

iGrant demo (Tuesday)

Watch the demo to implement the [GovStack] consent-building blocks | visit www.iGrant.io

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: Consent delegationIn Progress

• 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: Create test configuration for Consent Configuration APIsIn Progress

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?