Wiki

Clone wiki

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

Attendees

  • Nat Sakimura
  • Domingos Creado
  • Mike Leszcz
  • Tatsuo Kudo
  • Joseph Heenan
  • Bertrand
  • Andrew Hughes
  • Mark Haine
  • Daniel Fett
  • Takasaki Kawasaki

Brief review of external Orgs & Events

  • Series of identity related events.
    • Authenticate in October in Seattle
    • IIW in November, also OIDF workshop prior to the IIW
    • IETF 114
    • FDX Meeting
    • Money 2020 in Las Vegas
    • Identity Week Singapore
    • ISO/TC 68 - natural person identifier standardization

PRs & Issues

  • Review PRs

    • PR #114 – ISO references – Taka – 8601:2014 (withdrawn) or 8601-1:2019
      • We should refer to most recent one, 8601-2019.
      • Mark will write summary of discussion in the PR.
    • PR #116 – fix document structure – Daniel
      • No concern from attendees
      • merged
    • PR #117 – Clarifications in section 5.3 – Mark
      • No updates
    • PR #118 – Clarification of key retrieval - Daniel
      • To fix the word "claim source" in another PR.
    • PR #119 - Daniel
      • Raised during this meeting
      • Addressing on the issue #1254
  • Review Issues

    • Currently tagged for ID4:
      • Issue #1309 – Is JSON Schema normative? - Mark
        • The easiest way to solve this one is to say it's not normative. But it make the conformance test difficult. - Mark
        • Do not recommend to make schema normative for long term. - Daniel
          • We can not distinguish between should and must in the schema
          • Most people will be working with the text, not the schema.
        • The draft is the prime definition. And the schema is also normative but if there's a discrepancy between schema and drafts, then the draft is the master and for a number of specified parts of the schema, they're not normative and effectively implementations of stuff that's not typically referenced in other specs. - Mark
      • Issue #1261 – JSON ‘null’ – Joseph
        • Mark, Torsten, Joseph, Brian had a conversation around this topic.
        • Not reached to conclusion and continue discussing in the ticket.
        • This issue is problematic for some of library implementations.
        • At least for there is no problem on Daniel's implementation.
      • Issue #1308 – essential claims handling – Joseph
        • Assigned to Daniel.
        • Daniel will create PR for this issue.
      • Issue #1287 – Broken reference in JSON Schema – Torsten?
      • Issue #1300 – Document History & Acknowledgements - Jules
      • Issue #1256 – Clarification about retrieving keys - Daniel
      • Issue #1306 – Identifier for UK DIATF - Adrian
      • Issue #1254 – clarification about optional sub-elements - Daniel

Updated