Supported
OID4VCI: A JSON array containing a list of JSON objects, each of them representing metadata about a separate credential type that the Credential Issuer can issue. The JSON objects in the array MUST conform to the structure of the Section 10.2.3.1.
Constructors
Properties
OID4VCI: ISO mDL: N/A. W3C Verifiable Credentials: OPTIONAL.
OID4VCI: REQUIRED. A JSON string identifying the format of this credential, e.g. jwt_vc_json or ldp_vc. Depending on the format value, the object contains further elements defining the type and (optionally) particular claims the credential MAY contain, and information how to display the credential.
OID4VCI: OPTIONAL. Array of case-sensitive strings that identify how the Credential is bound to the identifier of the End-User who possesses the Credential as defined in Section 7.1. Support for keys in JWK format (RFC7517) is indicated by the value jwk. Support for keys expressed as a COSE Key object (RFC8152) (for example, used in ISO.18013-5) is indicated by the value cose_key. When Cryptographic Binding Method is a DID, valid values MUST be a did: prefix followed by a method-name using a syntax as defined in Section 3.1 of DID-Core, but without a : and method-specific-id. For example, support for the DID method with a method-name "example" would be represented by did:example. Support for all DID methods listed in Section 13 of (DID_Specification_Registries) is indicated by sending a DID without any method-name.
OID4VCI: OPTIONAL. Array of case-sensitive strings that identify the cryptographic suites that are supported for the cryptographic_binding_methods_supported. Cryptosuites for Credentials in jwt_vc format should use algorithm names defined in IANA JOSE Algorithms Registry. Cryptosuites for Credentials in ldp_vc format should use signature suites names defined in Linked Data Cryptographic Suite Registry.