<div>Hi Pedro,</div><br><div>thanks for bringing this up. I created a PR to change the respective claims to "type". </div><br><div><a href="https://bitbucket.org/openid/connect/pull-requests/461" title="https://bitbucket.org/openid/connect/pull-requests/461">https://bitbucket.org/openid/connect/pull-requests/461</a><br></div><div>best regards,</div><div>Torsten. </div><br><div class="gmail_quote_attribution">On Feb. 23 2023, at 12:16 pm, Pedro Felix via Openid-specs-ab <openid-specs-ab@lists.openid.net> wrote:</div><blockquote><div><div>New issue 1831: OpenID4VCI: W3C data model based formats and the use of "types" vs "type"</div><div>https://bitbucket.org/openid/connect/issues/1831/openid4vci-w3c-data-model-based-formats</div><br><div>Pedro Felix:</div><br><div>Just a minor detail about the use of the "types" field on the W3C VC based formats:</div><br><div>* 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)</div><div>* 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)\).</div><br><div>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.</div><div>_______________________________________________</div><div>Openid-specs-ab mailing list</div><div>Openid-specs-ab@lists.openid.net</div><div>https://lists.openid.net/mailman/listinfo/openid-specs-ab</div></div></blockquote>