...
Agenda | Presenter | Discussion |
|---|---|---|
Action points from last week | ||
Updates from TC meeting (fixed) | (ad-hoc) | |
Spec 1.1 updates in GitBook | ||
Gherkin scenario writing discussion | Everyone | Specific questions discussed from Ain’s work on Gherkin Scenario drafting document |
Additional roadmap item discussion: Configuration for callers of APIs: RBAC for agreements? | Ain Aaviksoo (Deactivated) added as comment Benjamin Balder Bach has an idea for a follow-up | |
Non-functional security requirements for ID and consent? | Should we add inputs to general Non-functional security requirements regarding consent? Training requirements for staff? | |
Social Cash Transfer | ||
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? | postponed for next meeting | 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) | What are consent-related aspects of the Payment UC? |
Scope and service registry? | sasi Ain Aaviksoo (Deactivated) | What are our next actions on registering required scopes for BB services? |
“Consent management” definition | Ain Aaviksoo (Deactivated) | We renamed “Consent Management BB” to “Consent BB”. Is there a useful definition of “consent management” that we can apply? |
...