Attendees

• Mark Haine
• Nat Sakimura
• Torsten Lodderstedt
• Daniel Fett
• Dima Postnikov
• Durand Stephane
• Joseph Heenan
• Kosuke Koiwai
• Ralph Bragg
• Julian White
• Ben Helps
• Sascha Preibisch
• Taylor Ongaro
• Steinar Noem
• Naohiro Fujie

New attendee

• Ben Helps

Agenda

• Brief review of external Orgs & Events
• Agenda items
• PRs & Issues

Brief review of external Orgs & Event

• Yes.com directed funding
  • Yes.com funded for the conformance test for OIDC4IDA.
• EUeID update
  • Still reviewing
• Any other orgs and events updates?
  • OpenBanking started a new project in UK
    • Creating common technical spec to exchange customer attributes

Agenda Items

• How to get to 3rd implementers draft
  • Abort/omit PR #52
  • Age Verification PR #42
  • Attachments PR #50
  • Alpha-3 vs Alpha-2 Issue #1207
  • Claim types supported Issue #1215
  • id document type Issue #1225
  • requirements for purpose Issue #1195
  • Trust framework element Issue #1224
• Creation of roadmap and FAQ documentation Issues #1123 and #1222
  • Call for volunteers to lead those tasks
  • After this WG, co-chairs will discuss
• Conformance - Joseph
  • The 1st step will focus on data representation, not protocol
  • Daniel and Joseph will work together
  • Joseph will set up a call with certification team
    • Daniel, Mark, Sascha, Taylor
• AB/Connect WG feedback on Santander contribution
  • Alberto joined the meeting
  • Torsten and ant will post the minutes of the meeting to the mailing list.
• Any other discussion points?  

PRs & Issues

• PR #52 – Abort/omit - Daniel
• PR #50 – Attaching evidence documents - Kai
  • Negotiation is required between parties
  • Discuss on the next call
• PR #51 – Authority extension
  • Work together with METI and GLEIF
  • Focus on issues required for 3rd Implementers draft above
• PR #42 Age verification
• Issue #1207 - Jules
  • Breaking change if the spec request Alpha-3
  • Both Alpha2/3 will be accepted
  • Jules will create PR for this
• Issue #1215 claim types supported - Kai
  • Create PR - Torsten
• Issue #1225 - id document / Jules
  • Torsten and Jules have extra discussion
  • Assign this issue to Jules
• Issue #1195 - requirements for purpose
  • Torsten will look the feedback from Jaap on the mailing list

• Issue #1224 - Trust Framework element - Jules

• Review of other issues if we have time

  • Kosuke's issue from OIDF-Japan about business model
    • Yes.com counts whereever the verified data is transferred from OP to RP
    • Not regard on id_token or userinfo
    • Yes.com impmlements using custom hook to provide verified claims to charge, and it able to count the charged transaction easier.
    • Kosuke will close the issue