Page Comparison

Summary

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

...

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.

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

...

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
- Yes – these would be "numbers" by type, but with special encoding handling.

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?

...