[Openid-specs-ab] Issue #1872: credentialSubject consistency and meaning (openid/connect)

[Pedro Felix]

New issue 1872: credentialSubject consistency and meaning
https://bitbucket.org/openid/connect/issues/1872/credentialsubject-consistency-and-meaning

Pedro Felix:

Regarding the `credentialSubject` property that appears inside `authorization_details` \([https://openid.net/specs/openid-4-verifiable-credential-issuance-1\_0.html#section-e.1.1.4](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-e.1.1.4)\) and on a credential request \([https://openid.net/specs/openid-4-verifiable-credential-issuance-1\_0.html#section-e.1.1.5](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-e.1.1.5)\) for format `jwt_vc_json`:

1. This property does not appear on the equivalent sections for `jwt_vc_json-ld` and `ldp_vc` \([https://openid.net/specs/openid-4-verifiable-credential-issuance-1\_0.html#section-e.1.1.5](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-e.1.1.5) and [https://openid.net/specs/openid-4-verifiable-credential-issuance-1\_0.html#section-e.1.1.5](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-e.1.1.5), however it does appear in the non-normative examples. Is this absence on purpose? If so, what is the rationale for this distinction between formats? Also, if so, the non-normative examples should probably be updated to remove its usage.
2. How should an issuer process the `credentialSubject` in RAR and in the credential request? The spec states `determines the optional claims to be added to the credential to be issued` . Are these extra claims that can be optionally added to the VC, in addition to the ones inferred from the requested types? Also, how should the value \(empty object in the non-normative examples\) be interpreted by the issuer?

‌