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

« Previous Version 2 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 at 07:30 UTC / 09:30 CET / 13:00 IST

Attendees

Meeting Note

Agenda

Presenter

Discussion

Action points from last week (fixed)

Ain Aaviksoo (Deactivated)

Jira Kanban update (fixed)

Ain Aaviksoo (Deactivated)

We will continue with our changelog and will add Jira ticket numbers. Benjamin will tag Rachel.

Comment from Ramkumar about FAQ work: Can we put a link to the FAQ in “Other Resources”?

Models for Authentication Cross-BB

PSRAMKUMAR

Ramkumar has presented screen flows for authentication and exchange of tokens.

We’ve decided that we are happy to support all 3 models proposed by Ramkumar.

Specification 2.0 presentation and intro

skipped for next week

Testing: mock and emulation

Benjamin Balder Bach

If PSRAMKUMAR is present, we can discuss this

Future collaboration with a tender

Skipped

Based on experiences from other WGs, what modality of collaboration should we have with a future tenderer?

Updates from TC meeting (fixed)

Ain Aaviksoo (Deactivated)

Authentication and Cross-BB Authorization
We should give feedback to this document.

Gherkin scenario writing discussion (ongoing)

Skipped

Gherkin Scenario drafting document

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

  • Create Jira epic to track individual Gherkin scenarios being drafted and implemented Benjamin Balder Bach
  • Add cases that we want to cover for Internal Workflows section in CON-109 - Getting issue details... STATUS Benjamin Balder Bach
  • Create an issue for MVP APIs and how to treat them (GitBook specification? OpenAPI spec?) Ain Aaviksoo (Deactivated) - identify APIs and functional requirements + separately: what does the MVP subset of APIs and functional requirements look like? Do we mark the requirements that are not strictly necessary? Should we mark what is “required for cross-bb integration”?
  •  

Action Items from previous meetings

Decision

  • No labels