Kanban board + Action points from last week

Ain Aaviksoo

skipped

Should we store text content of Policy and DataAgreements?

Benjamin Balder Bach

Our fixtures example data doesn’t contain any legal text or any user-facing texts. This will confuse anyone reading the spec about what these data models are for.

Should we add a simple text field that has no requirements or assumptions about formatting?

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

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

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