Wiki

Clone wiki

ekyc-ida / Minutes / eKYC-IDA_Meeting_Notes_2022-06-01

Attendees

  • Bjorn Hjelm
  • Dave Tonge
  • Mark Haine
  • Mike Leszcz
  • Nat Sakimura
  • Brian Campbell
  • Dima Postnikov
  • Don Thibeau
  • Gail Hodges
  • Joseph Heenan
  • Kosuke Koiwai
  • Naohiro Fujie
  • Takahiko Koiwai
  • Torsten Lodderstedt

Brief review of external Orgs & Events

  • Identiverse
    • Mike organizing in person meeting at Identiverse

Main Agenda Items

  • Proposal to get to Final this year: ida.png

Naohiro expressed concern about too short gap between the implementers draft 4 and the final.

  • NOT DO in Implementer’s Draft 4
    • Anything in other drafts – ASC, Authority
    • Anything that could or should be done as an extra draft or profile
      • New end-user claims
      • Further enrichment to metadata
      • Richer error handling
      • Pending Verification
      • Pre-defined claims sets
    • Most of the JSON Schema issues (except Issue #1287)
    • Mapping to eIDAS
    • Issue #1283 – birth_date definition -> do in ASC
    • Issue #1292 - unique person identifiers -> other draft or profile
  • DO in Implementer’s Draft 4
    • PR #112 - External attachment audience
    • PR #114 - ISO references
    • Issue #1300 – Document History & Acknowledgements
    • Issue #1256 – Clarification about retrieving keys
    • Issue #1255 – Section 5.3 clarifications
    • Issue #1306 – Identifier for UK DIATF
    • Issue #1254 –clarification about optional sub-elements
    • Issue #1247 – value/values
    • Issue #1287 – Broken reference in JSON Schema
  • Decide whether to include in Implementer’s Draft 4
    • Issue #1261 – JSON ‘null’
      • Joseph proposed make essentially mandatory
      • Torsten's concern is backward compatibility
    • Statement that JSON Schema is normative or not
      • Mark raised this as #1309
      • Kosuke : Will there be any barriers to use JSON schema when we are sending the spec to other organization such as ISO?
      • Nat: If we want to finish the 1.0 quickly, it may be better to keep JSON Schema non-normative and wait for ver 1.1 or something to get it normative.

PRs & Issues

  • Review PRs

    • PR #112 – External attachment token audience – Taka
      • Joseph has reviewed the PR
    • PR #114 – ISO references – Taka
      • Mark and Jules will review offline and no one expressed objection to merge this PR after their approval was made.
    • PR #115 – fix value/values – Daniel
      • Joseph and Taka approved the PR
    • PR #116 – fix document structure – Daniel
      • Joseph already approved this
  • Review Issues

    • New
      • Issue #1307 – Section 7.6 html render – Mark
      • Issue #1308 – essential claims handling - Joseph

Updated