2023-01-17 ACDC Meeting Notes

Owned by Kevin Griffin
May 09, 2023
1 min read

Philip Feairheller 

Sam Smith 

Kent Bull 

Henk van Cann 

Rodolfo Miranda 

Steven Milstein 

Nuttawut Kongsuwan 

Mark Scott 

Joseph Lee Hunsaker 

OLD ACCOUNT (Peter McCormick) 

Arshdeep Singh 

Scott Whitmire 


Agenda

  • Announcements
    • Trust Over IP Calendar needs to be updated, again.  Calendar invite needs updated Zoom link.
    • Jason Colburne: QuiIdentity blog post incoming about why they are choosing KERI.
    • vLEI is in Production and Provenant is the first ever Qualified vLEI Issuer.

Reports implementation of ACDCs

  • vLEI
    • Working on production roadmap for Q1
      • Will include QVI SDK
      • Will include Watcher Network
  • ViRA
    • XBRL signatures group join meeting
  • GS1
  • HCF

Items

  • Review "Future topics"
    • Clean up
      • Discovery Web-of-trust ecosystem trust anchors - comparison to did:peer: Discussed in KERI meeting, brief summary here.
      • Root of Trust / Trust Anchor also serves as a Discovery mechanism for pre-discovering KELs for the AIDs in a given ecosystem.
    • add summary of expectations for the discussion
    • do we need a third party (LF Open Wallet for example)
  • ACDC Validation Bundling - From validating signature, chains and schema all the way up the business logic stack
    • Structural validation:  Schema, signatures, chains, content (as constrained by the schema)
    • Business Logic Validation:  Does this credential meet the requirements and needs of given business logic
    • GLEIF Reporting API Verifcation Service:
    • Is there a place for interleaving the structural validation with business logic validation?
      • Could we have call-outs from the structural validation at various stages in the process to perform step-wise business logic
    • How does caching of ACDC/KEL/TEL information affect forensic investigations of data
      • For example, "Did this driver have a valid license at the time (in the past) of an accident.
      • Having to constantly check for revocation status introduces possible network latency.
        • Polling or pushing can mitigate these problems