Page Comparison

Kanban board + Action points from last week

skipped

• Consent BB Spec 2.0 scoping (to be cont’d)

General update (5 min)

skippedHoliday

breaksNext meeting

When do we resume?

Action items

We have been discussion consent definition and alignment with the DDX solution in terms of:

• Current specification’s consent definition

• Data Agreement

• Alignment with UX Guidelines

• What do we need to add in the spec (schemas/endpoints) if the whole UI flow of DDX should be included?

SEASONAL GREETINGS 🌲 🌴 🎆

everyone

Offline consent

postponed to next meeting

We had to postpone this. Note that we’re trying to figure out a terminology here. “On-demand” consent was used to emphasize the risks of this kind of thinking, but “offline consent” will help us capture the broader nature. Everyone is encouraged to think about terminology

UI/UX feature in DDX Spec

Should we add this to Consent BB spec too?

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?