Summary
| Excerpt |
|---|
|
...
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>
...
- IIW Update
- Session on Hyperledger AnonCreds
- Discussions about JSON-LD usage
- Lots of discussions of supporting AnonCreds in "other formats" – e.g. OWF, OID4VCs
- BBS+ Predicates work that is happening - Dan Yamamoto
- Aside: Mike Lodder presentation
- Backwards Compatibility
- PRs in (#82, #105) that seem to change public data structures – ones that are handled outside of AnonCreds and/or by two or more participants (issuer, holder, verifier)
- We want to retain compatibility with existing data – credentials that have been issued and the published AnonCreds objects on which they rely.
- That extends to business logic – e.g. the handling of the objects not just by AnonCreds, AnonCreds Methods and Aries Frameworks, but also by business applications built on Aries.
- Suggestion:
- Include in the specification a statement about backward compatibility
- Formalize what data structures will be expected by AnonCreds
- As needed support sending and receiving data in "old" and "new" formats, but (for now) always sending "old" formats.
- Creating/sharing AnonCreds verifiable credential and presentation objects in W3C VC Data Model format
- Repository with code: andrewwhitehead/anoncreds-w3c-mapping
- Signing an AnonCreds VC with an LDSignature based on a static context
- Open PRs Review, Open Issues Review
- Open Discussion
...