...
- JWT for Selective Disclosure. https://www.ietf.org/archive/id/draft-fett-oauth-selective-disclosure-jwt-02.html
- Flow:
- Issuer passes two objects to the holder:
- SD-JWT (signed JWT, contains CLAIMs, HASHES OF VALUES, and a signature)
- SD-JWT-SVC (Salt Value Container, contains CLAIMs, SALTS, and JSON-Encoded VALUES)
- Holder
- creates SD-JWT-R (unsigned subset of the SD-JWT-SVC) i.e. holder can see the values of the claims that are released.
- passes SD-JWT and SD-JWT-R to the verifier
- Verifier
- Uses salts to verify hashes
- Can then trust the SD-JWT
- Issuer passes two objects to the holder:
- Extensions allow for "holder binding" to eliminate replay attacks.
- Pros:
- User sees values that are passed on
- User is in charge of the selection of claims
- Cons:
- Breaks existing JWT flows
JSON-LD
- JSON for Linked Data https://json-ld.org/
- Extension of JSON with "@-Claims" that point to external resources
- Most prominent: "@context" which links to a schema that describes the JSON at hand
- Why is this relevant?: (I think) it provides a way to pass around arbitrary JSONs from Issuer via Holder to Verifier.
- The wallet software does not need to understand the JSON a-priori (e.g. at development time)
ELM-V3
- European Learning Model https://htmlpreview.github.io/?https://github.com/european-commission-empl/European-Learning-Model/blob/master/rdf/ap/edc/documentation/EDC-generic-no-cv.html#evidence
- Extensive (
extremely overly complicated) model to define all kinds of learning: over 480 properties to capture and validate all types of learning - Based on
- JSON-LD
- Verifiable Credentials: https://www.w3.org/2018/credentials/
...