Giuseppe De Marco
Giuseppe De Marco
This PR aims to resolve part of the points contained in the issue: https://github.com/openid/OpenID4VCI/issues/313#issuecomment-2121942187
this PR is merely editorial and aims to resolve the issue https://github.com/openid/OpenID4VCI/issues/311
> Obviously very wrong how it is, so approving. > > Probably we should mention that the Credential Issuer may optionally also be an AS. Can we consolidate the information...
The value_types support string, number, and various image media types such as image/jpeg, as defined in the IANA media type registry for images (https://www.iana.org/assignments/media-types/media-types.xhtml#image). The specification also states that other...
In the current specs the format identifier for mdoc cbor is configured with `mso_cbor`. actually MSO is a Cose Sign1 Document and the digital credential is an entire mdoc cbor...
The response is an encrypted json and not a Netsted JWT, signed and then encrypted. Is there any possibility that implementers look for having a Nested JWT? Probably not. I...
My colleagues and I never really understood the parameters wallet_issuer and user_hint and this PR doesn't solve that either. I think the specification is missing text on this, but unsure...
This issue proposes defining a requirement for setting the value of the aud (audience) claim within the JWT proof sent to the credential endpoint. The proposal suggests that the aud...
In the current text we have the `signed_metadata` ([here](https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html#section-11.2.3-2.9)) As discussed in our call, we need to highlight the scalability problem associated with having a single signed metadata, signed solely...
WDYT about? `wallet_issuer` -> `wallet_provider` it seems more closer to the current language _Originally posted by @peppelinux in https://github.com/openid/OpenID4VCI/pull/98#discussion_r1382582945_