Page Comparison

Action points from last week

Ain Aaviksoo (Deactivated)

Discussed and resolved 🚀

Updates from TC meeting (fixed)

Ain Aaviksoo (Deactivated)(ad-hoc)

•  PSRAMKUMAR to review the GitBook PR https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/oEAfhW9JLP3tJ6mPyxtF/~/changes/18/internal-use-case-definitions/uc-c-pic-a-organisation-administration-use-cases-configuration Ain created

House-keeping

Ain Aaviksoo (Deactivated) and Benjamin Balder Bach

Let’s clean up action Action items and postponed agenda items .cleaned up
☀️

Non-functional security requirements for ID and consent?
(for next meeting)

postponed for next meeting

Should we add inputs to general Non-functional security requirements regarding consent? Training requirements for staff?

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
postponed for next meeting

•  Ain Aaviksoo (Deactivated) will add to

  Jira Legacy
  server System JIRA serverId f5c6bdaf-d23e-347d-a1e8-579e20a81dda key CON-1

House-keeping our action items etc

Completed 💪

Social Cash Transfer

•  Add to

  Jira Legacy
  server System JIRA serverId f5c6bdaf-d23e-347d-a1e8-579e20a81dda key CON-1

  ticket with the links to relevant discussion by other groups Ain Aaviksoo (Deactivated)

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.

•   to write the outcome of discussions with Philippe Page 2w ago Ain Aaviksoo (Deactivated)

Payment Use-Case

Ain Aaviksoo (Deactivated)
postponed for next meeting

What are consent-related aspects of the Payment UC?

•  Add to Spec 2.0 as a ticket Ain Aaviksoo (Deactivated)

Scope and service registry?

sasi Ain Aaviksoo (Deactivated)
postponed for next meeting

What are our next actions on registering required scopes for BB services?

This agenda point seems (today) a bit vague, so that the decision is we will close it for the time being until called again with a specific request for action.

For future reference some keywords discussed:

What is the scope of data from other building blocks even before we can create a consent?

Whether an individual can record a consent?

“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?

Decision: close the agenda point as “resolved”

New issues

sasi

• 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?

•  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)

New issue

Benjamin Balder Bach

We need perhaps more general “BB prerequisites for integrating with Consent BB or something” (in addition to tech spec)

•  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”

Audit use cases test spec and potential update

Philippe Page

Accepted to start working as suggested by Philippe

Toi be agreed over the next week Descriptions within Jira to keep the scope manageable

•  Philippe Page will finish the initial descriptions and commit himself to the ones he feels appropriate

If any task is missing - anyone is free to add one

•  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

Spec 2.0

Everyone

•  Create Jira tickets for the suggested new points under

  Jira Legacy
  server System JIRA serverId f5c6bdaf-d23e-347d-a1e8-579e20a81dda key CON-1

  Ain Aaviksoo (Deactivated)