Page Comparison

Summary

Excerpt
Revocation Scheme Proposal ALLOSAUR - Presentation - Mike Lodder Request: Support for Arrays and Nested data in AnonCreds Open Discussion

Mike Lodder Presentation on ALLOSAUR Revocation: dummyfile.txt

Mike Lodder Q&A on ALLOSAUR Revocation: dummyfile.txt

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>

...

Mike Lodder will continue the discussion of his proposal for AnonCreds v2.0, this time talking about the proposed ALLOSAUR accumulator/ZKP revocation scheme.
Request: Support for Arrays and Nested data in AnonCreds – Kyle Robinson - Presentation: BC Digital Trust AnonCreds April 3 2023.pptx
- Supported needed for arrays and nested data.
- Suggestion is to use Data URLs (e.g., "data: application/json,...") – Aries RFC being posted Real Soon Now:
  - Holder, verifier would at least know that the Attribute contained a string that was (in this case) JSON data, and could process it accordingly.
  - However – would lose ability to selectively disclose (all or nothing) or use predicates on such data.
  - Same approach is going to be used for images in attributes – "data: image/png,...")
Plans for IIW?
Next Meeting (two weeks):
- ALLOSAUR Revocation
- Suspension vs./as well as revocation?Cancelled for IIW

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?

...