OpenID4VCI: W3C data model based formats and the use of "types" vs "type"
Issue #1831
resolved
Just a minor detail about the use of the "types" field on the W3C VC based formats:
- The W3C data model uses
type
(singular) - https://www.w3.org/TR/vc-data-model/#types. This field is defined in the standard JSON-LD context present at https://www.w3.org/2018/credentials/v1 - However the OpenID4VCI spec is using
types
(plural), forjwt_vc_json
,jwt_vc_json-ld
, andldp_vc
(e.g. https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-e.1.3.2).
Is this difference intentional? Note that when using JSON-LD processing, type
will be well-defined (it is defined on https://www.w3.org/2018/credentials/v1
as an alias for @type
) but types
isn't.
Comments (3)
-
-
OID4VCI uses
types
in places that will not be handled using JSON-LD processing (as clarified in separate thread/PR), having said that, I think it will be easier to implement if the parameter names in credential offer, issuer metadata, etc. are consistent with what is in the issued JSON-LD credential. -
- changed status to resolved
PR merged.
- Log in to comment
PR #461