...
- Eliminating having a special `@context` for AnonCreds
- Issue: https://github.com/hyperledger/anoncreds-spec/issues/192
- HackMD: https://hackmd.io/@BYJVN-mpSCe5H3eaIw7-7g/ryk4dvIIp
- Presentation
- Discuss the updates needed to implement the changes
- Idea: Having a commit-time "config" setting for 1.0 vs. 2.0 (or can we do better?)
- Results documented in issue 192 (linked above)
- Aries Issue Credential / Present Proof Attachments
- Current: Indy, JSON-LD - which do we use, or should we define another that (also) handles JWTs?
- HackMD: https://hackmd.io/JEIOxf_ETnaX33kTIu7YJw?view
- Outcome still to be defined. Leading proposals:
- Issue either:
- With RFC 0592/0771 and add handling for an extra an proof type, or
- With the new attachment format being proposed by Timo
- Present either:
- With RFC 0592/0771 for AnonCreds presentations and RFC 0510 (DIF Presentation Exchange) for JSON-LD presentations, or
- With RFC 0510 for both AnonCreds and JSON-LD presentations
- Extending the 0510 handling for generating/verifying AnonCreds presentations by automating the finding of AnonCreds source VCs for a presentation from DIF PE data, and creating a DIF PE Submission.
- Challenge: I think (to be confirmed), an AnonCreds presentation requires including an AnonCreds-format presentation request. Can that be produced? Should it be, since the verifier already has it...
- Extending the 0510 handling for generating/verifying AnonCreds presentations by automating the finding of AnonCreds source VCs for a presentation from DIF PE data, and creating a DIF PE Submission.
- Issue either:
- Open discussion
Future Calls
...