Skip to content

Commit

Permalink
Apply editorial suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: David Chadwick <[email protected]>
  • Loading branch information
Sakurann and David-Chadwick authored Jul 8, 2024
1 parent 9a160de commit 084f112
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions openid-4-verifiable-presentations-1_0.md
Original file line number Diff line number Diff line change
Expand Up @@ -1567,7 +1567,7 @@ Out of the Authorization Request parameters defined in [@!RFC6749] and (#vp_toke

The `client_id` and `client_id_scheme` MUST be omitted in unsigned requests defined in (#unsigned_request). The Wallet determines the Client Identifier from the origin as asserted by the Web Platform and/or app platform. The transport of the request and origin from the Web Platform and/or app platform to the Wallet is platform-specific and is out of scope of this profile.

The value of `response_mode` parameter MUST be `w3c_dc_api` when the response is neither signed nor encrypted and `w3c_dc_api.jwt` when the response is signed and/or encrypted as defined in (#jarm).
The value of the `response_mode` parameter MUST be `w3c_dc_api` when the response is neither signed nor encrypted and `w3c_dc_api.jwt` when the response is signed and/or encrypted as defined in (#jarm).

In addition to the above-mentioned parameters, this profile introduces a new parameter:

Expand All @@ -1579,7 +1579,7 @@ Any OpenID4VP request compliant to this section of this specification can be use

### Unsigned Request {#unsigned_request}

The Verifier MAY send all the OpenID4VP request data as JSON elements in the `request` API parameter and receives the result in the API's `result` parameter. In this case, the Wallet will use the Verifier origin as asserted by the Browser as the Verifer's Client Identifier.
The Verifier MAY send all the OpenID4VP request parameters as members in the `request` member passed to the API. In this case, the Wallet will use the Verifier's origin as asserted by the Browser as the Verifer's Client Identifier.


### Signed Request {#signed_request}
Expand Down Expand Up @@ -1621,7 +1621,6 @@ The following is a non-normative example of an OpenID4VP response that could be
}
```

Note: All mechanisms for cryptographically protecting the OpenID4VP response MAY be utilized with the W3C Digital Credentials API, too.

# Examples with Credentials in Various Formats {#alternative_credential_formats}

Expand Down

0 comments on commit 084f112

Please sign in to comment.