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>
...
- Welcome and Introductions
- Announcements:
- IIW – April 18-20 – Let's plan some presentations.
- New v2.0 Specification Repository created.
- Updates to the Agenda
Agenda
- Mike Lodder will continue a discussion of the Data Models he is proposing for AnonCreds v2.0, this time talking about Presentations
- Data Models HackMD document: https://hackmd.io/ZlsnLoclSveePJOZljgMfA
- Notes from Meeting:
- Contents of the Issued Credential – easily mapped into other formats, such as the W3C VC Data Model.
- Open question on where encoding occurs – within AnonCreds (better interoperability, less data to store, more computation) or by the Issuer.
- PresentationSchema
- A possibly published data structure used by the Verifier to ask for data from the Holder.
- Atomic – when requested, a Proof based on a PresentationSchema is either proven or not.
- Can use something like DIF Presentation exchange to AND/OR a set of PresentationSchemas in to a Presentation Request – plus adding an ID and a nonce.
- Different types of proofs were covered – from plain signatures to range-proofs.
- Different crypto can be used.
- Contents of the Issued Credential – easily mapped into other formats, such as the W3C VC Data Model.
- Plans for IIW?
- Next Meeting (two weeks):
- Suspension vs./as well as revocation?
- Collect some use case specific examples and continue this discussionthe discussions:
- Applying the data structures to a real use case or two
- What concrete uses other than link-secret is there for blinded data in a credential?
- ALLOSAUR Revocation
Future Calls
To Dos:
- Create a repository for the specificationPlan session for IIW on AnonCreds.