Versions Compared

Old Version 2

changes.mady.by.user Benjamin Balder Bach

Saved on

compared with

New Version Current

changes.mady.by.user Benjamin Balder Bach

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Agenda

Presenter

Discussion

API endpoint alignment w/ iGrant team

Outcomes from former discussion are noted as decisions here: 2023-09-22 - Weekly Update
API endpoint table for decisions: https://docs.google.com/spreadsheets/d/1wZ-j_GRGoFJgHxbCG_T0HEX2_JJ0yEsmnDIYcUrN38U/edit#gid=1880599809

Lal Chandran or George J Padayatti will share schemas for webhooks with Benjamin Balder Bach

We want to have a decision on what API endpoints should: Form embedded and/or JSON request body.

Separate discussion with Ain Aaviksoo about renaming ConsentRecord to Record.

Benjamin Balder Bach will share new version of Internal Workflow with Lal and George.

George J Padayatti to observe that /service/individual/.../data-attribute endpoints also can receive a revisionId argument specifying the Agreement’s Revision Id.

Discussion around proposed /onboarding endpoints:

  • Which are mandatory/fundamental and which are optional. Some can go to /config/ and some can stay in /onboard/ (or /setup/)

  • When should the API specification care that an endpoint exists and behaves in a specific way?

  • What should be delegated to functional requirements?

Benjamin Balder Bach check that Individual is part of serialized ConsentRecord

Decision

  • All /config/agreement/data-attribute endpoints will cause Agreement to be revisioned.
  • /config/webhook endpoints will be introduced
  • We will remove Purpose as a 1:many relation, replace it with short and long text on Agreement objects
  • We’ll remove AuditTracking and use webhooks as far as possible. Then, if necessary we’ll re-introduce tracking on basis of use-cases and scenarios.