2023-10-13 - Weekly Update

Owned by Benjamin Balder Bach
Last updated: Oct 13, 2023
2 min read

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 ordinary starting time at 07:45 UTC / 09:45 CET / 13:15 IST

Attendees

  • @Ain Aaviksoo (meeting facilitator)

  • @Benjamin Balder Bach (note keeper)

  • @Lal Chandran

  • @PSRAMKUMAR

  • @Philippe Page

  • @George J Padayatti

Meeting Notes

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Kanban board + Action points from last week

@Ain Aaviksoo

skipped

General update (5 min)

@Ain Aaviksoo

Review of Consent BB API documentation - needs attention

Notes from this weeks meetings

 

See:

Discussion around final version

 

  • 2 weeks needed to implement a lot of feedback regarding API. Feedback is from SolDevelo review and iGrant implementation work.

  • All APIs are so far mandatory.

  • Discussion with the Sandbox team is very important. @Ain Aaviksoo understands that the technical part, API descriptions etc, is the first priority. The explanatory part should be correct, but additional improvements will happen in the coming months.

  • George is invited to help improve descriptions of API schemas, schema fields and endpoints – via the Google Spreadsheet.

  • iGrant has a much more developed OpenAPI infrastructure, we can use this as a goal for GovStack OpenAPI specs: Making them copy-paste friendly..

  • Note that we are also adding changes from (but these are minor, see new Action Item)

  • November 15th is a big deadline, there are 4 major deliverables for iGrant and Red Pill -

 

 

 

 

 

 

DDX Consent BB implementation open topics/questions:

skipped

  • Solution and adapter, are they separated?

  • Are you aware of the bb-consent/examples/ structure?

  • Are you aware of GovStack UX Guidelines that are published?

  • What to do with APIs that aren't part of GovStack specs - expose them in the same structure?

  • What do we need to accommodate in the Consent BB planning? What "best-practice" guidance is found for building solutions for GovStack?

  • What sort of workflows are great, for instance for building consent. How will engagement with other BBs work? Will you be able to work on this aspect?

Consent delegation

skipped

  • 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

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

@Ain Aaviksoo will coordinate with Sandbox team - note that Lal is requesting and end2end use case.

Action Items from previous meetings

@Ain Aaviksoo (Deactivated) consider if the decision to have “external ID” and “external ID type” referencing Individuals is relevant for the Key Desicion Log (if it’s not already there)
@Philippe Page will finish the initial descriptions and commit himself to the ones he feels appropriate
@Benjamin Balder Bach Prepare fixtures review for Lal
@Benjamin Balder Bach Finish translating SolDevelo’s review into issues (added after-the-fact)

 

Decision