[Openid-specs-ab] Issue #1831: OpenID4VCI: W3C data model based formats and the use of "types" vs "type" (openid/connect)

[Torsten Lodderstedt]

Hi Pedro,

thanks for bringing this up. I created a PR to change the respective claims to "type".
https://bitbucket.org/openid/connect/pull-requests/461
best regards,
Torsten.

On Feb. 23 2023, at 12:16 pm, Pedro Felix via Openid-specs-ab <openid-specs-ab at lists.openid.net> wrote:
> New issue 1831: OpenID4VCI: W3C data model based formats and the use of "types" vs "type"
> https://bitbucket.org/openid/connect/issues/1831/openid4vci-w3c-data-model-based-formats
>
> Pedro Felix:
> 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](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](https://www.w3.org/2018/credentials/v1)
> * However the OpenID4VCI spec is using `types` \(plural\), for `jwt_vc_json`, `jwt_vc_json-ld`, and `ldp_vc` \(e.g. [https://openid.net/specs/openid-4-verifiable-credential-issuance-1\_0.html#section-e.1.3.2](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.
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-ab
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20230223/e657e0c7/attachment-0001.html>