-
Notifications
You must be signed in to change notification settings - Fork 24
WG 2022 06 13
Stephen Curran edited this page Jun 13, 2022
·
2 revisions
Time: 7:00 Pacific (fixed), 16:00 CET
Zoom Link: https://us02web.zoom.us/j/85188125213?pwd=UHRUVlgweFJ0T0g4SVdDUytYSkxJUT09
Recording: 2022.06.13 AnonCreds Specification Working Group Meeting Recording
- Start Recording
- Reminder: Community License v1.0 and Working Group Code of Conduct
- Welcome and Introductions
- Announcements:
-
Open PRs Review
- What can we merge?
- Well...we managed to merge 2 of 5, with actions on the others.
- Action Items
- What's left?
- Question: Do we need an explicit data model section? My vote is no -- better to have that inline.
- Suggestion from Jason that we wrap the data models in
[[def: ]]
markings so that we can[[ref: ]]
them later.
- Suggestion from Jason that we wrap the data models in
- Question: Do we need an explicit algorithm section (set of definitions to be referenced), or leave in line?
- Same as above -- define them inline, but as a
def
that can theref
'd in other parts of the document.
- Same as above -- define them inline, but as a
- Question: Do we need to talk about DID creation? My vote is no, since not necessary for AnonCreds when it is ledger agnostic.
- Suggestion is to not define the process, but to help understanding by talking about how DIDs really don't play into AnonCreds cryptography, but may have a role in both publishing objects, and in messaging amongst the participants.
- Question: Do we keep schema as a necessary object? Will be an interesting question in v2.0 -- BBS+.
- While agreed that technically a schema is not crucial to anoncreds, it is extremely useful in enabling the trust of the credentials.
- To Dos:
- Cred Def Generation + PRIVATE_CRED_DEF -- non revocation, and plus revocation
- Revocation data elements -- definition
- Revocation: Revoke, Presentation elements.
- Security and Privacy
- Normative/Non-normative references
- Collect from documents mentioned below (under action items) and from previous meetings
- Question: Do we need an explicit data model section? My vote is no -- better to have that inline.
- Review of the first cryptography PR (PR #46)
- @swcurran to complete updates needed to the link secret section based on comments (PR #45)
- Review and approval/requests for updates for the Setup Rev Reg Def section (PR #47)
- @ArPhil to complete and make ready for review the issuance flow (PR #39)
- Links to be referenced in the spec and used where needed:
- From Will Abramson : https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.186.5994&rep=rep1&type=pdf
- From Will Abramson : https://github.com/hyperledger/indy-hipe/blob/c761c583b1e01c1e9d3ceda2b03b35336fdc8cc1/text/anoncreds-protocol/README.md
- From Artur Philipp : Issue about raw/encoded values used in AnonCreds https://jira.hyperledger.org/browse/IS-786