[Openid-specs-ab] OpenID4VCI: JSON-LD processing of request and metadata fields

[Pedro Felix]

Hi,

The latest OpenID4VCI spec
(https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0-11.html)
requires that certain JSON objects "... MUST be processed using full
JSON-LD processing", namely credentials_supported and
credentials_definition (e.g
https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0-11.html#section-e.1.3.3),
when the format is jwt_vc_json-ld or ldp_vc.

IINM, this requires all the internal fields to be
"fully-contextualized", i.e., they need to be mapped to URIs by a
JSON-LD context. This already happens for credentialSubject, which is
defined on the https://www.w3.org/2018/credentials/v1 context
(credentialSubject maps to
https://www.w3.org/2018/credentials#credentialSubject)
However, there are other fields which are introduced by the OpenID4VCI
spec, such as cryptographic_binding_methods_supported,
cryptographic_suites_supported, used inside credentials_supported and
which aren't mapped to URIs.

So,
1) Doesn't the OpenID4VCI spec need to map those fields to full URIs,
if they are to be used with "full JSON-LD processing"?
2) Should the OpenID4VCI spec define a context with those mappings and
make it available in a openid.net URL, similar to what the W3C does
with https://www.w3.org/2018/credentials/v1?

Thanks.
Regards,
Pedro