Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Summary

  • Revocation Requirements – what we need in a Revocation Mechanism
  • Schema Claim Types for Dates
  • Open Discussion

Recording of Call:  

Notices: 

This specification creating group operates under the Linux Foundation Community Specification License v1.0.

Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Meeting Attendees

Stephen Curran (BC Gov / Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>

Tim Bloomfield (OPS) <tim.bloomfield@ontario.ca>


Related Repositories:

Goals of the Working Group:

The goal of AnonCreds v2.0 is to retain and extend the privacy-preserving features of AnonCreds v1.0, while improving capabilities, performance, extensibility, and security.

Meeting Preliminaries:

  • Welcome and Introductions
  • Announcements:
  • Updates to the Agenda?

Agenda

  • Presentation and Discussion – what we need for Revocation.
  • Schema Claim Type:
    • Would it make sense defining encodings for date related schema claim types that are especially useful to use in ZKP predicates?
      • "iso860_date" – encodes to dateint e.g., 2023.06.26 is 20230626
      • "iso860_datetime" - encodes to Unix Time e.g., seconds since Jan 1, 1970

Future Calls

  • Collect some use case specific examples and continue the discussions:
    • Applying the data structures to a real use case or two
      • Take an existing AnonCreds Schema (maybe this) and Credential Definition (maybe this) and define what it would be using Mike's proposed data models.
        • Where would the data models exist, such as on ledger, in the AnonCreds specification?
    • What concrete uses other than link-secret is there for blinded data in a credential?

To Dos:

Action items

Recording


















  • No labels