Credential formats
The format is how a credential is encoded and signed. The ARF centres on two, and so does LutraID: it issues and verifies both.
| SD-JWT VC | mdoc | |
|---|---|---|
| Standard | IETF, dc+sd-jwt | ISO/IEC 18013-5, mso_mdoc |
| Encoding | JSON, signed as a JWT | CBOR, signed with COSE |
| Type named by | vct | doctype |
| Comes from | The web and OAuth world | The ISO mobile driving licence work |
Both support selective disclosure and both bind to a holder key. Neither is a subset of the other.
Which one to issue
Whichever your verifiers accept. Mobile driving licences and in-person, proximity-style checks lean mdoc; online presentation and anything close to the OAuth ecosystem leans SD-JWT VC. Issuing the same credential in both is normal, and a verification profile can accept either.
These two are the whole list. There is no jwt_vc_json, no JSON-LD
credential, and no DID-based binding — see Credential
formats for the exact algorithms and
key types.
In the ARF
For the detail, see the Architecture and Reference Framework: