From c81fa61495584c53e9640968f5b877522b59e1ce Mon Sep 17 00:00:00 2001 From: Matthew Miller Date: Wed, 28 May 2025 14:44:52 -0700 Subject: [PATCH 1/6] Add some basic guidance --- index.html | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/index.html b/index.html index 6e8a43fc..ff04b128 100644 --- a/index.html +++ b/index.html @@ -482,6 +482,28 @@

Details of how to actually get the [=digital credential=] are forthcoming. + +
    +
  1. + + When multiple [=digital credential/presentation requests=] are present + in {{DigitalCredentialRequestOptions/requests}}, + [=user agents=] MUST only return one + [=digital credential/presentation responses | presentation response=] for one + of these requests. + Multiple credentials MAY be present in this one response depending on the capabilities + of the corresponding [=digital credential/exchange protocol=]. + +
    2. +
  • Return a {{DigitalCredential}}.
    • From f28d35f17a9f2ed63046cb872c3c3bff43d07edc Mon Sep 17 00:00:00 2001 From: Matthew Miller Date: Wed, 28 May 2025 15:02:36 -0700 Subject: [PATCH 2/6] Remove note to self --- index.html | 1 - 1 file changed, 1 deletion(-) diff --git a/index.html b/index.html index ff04b128..4ce901b2 100644 --- a/index.html +++ b/index.html @@ -482,7 +482,6 @@

    Details of how to actually get the [=digital credential=] are forthcoming. -
    From 28cb8d4a4ec5f00756fb58ede3aa0af909c29600 Mon Sep 17 00:00:00 2001 From: Matthew Miller Date: Wed, 27 Aug 2025 11:48:52 -0700 Subject: [PATCH 5/6] Add text about semantic equivalency of requests --- index.html | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/index.html b/index.html index 383249c6..3abc1b63 100644 --- a/index.html +++ b/index.html @@ -1983,6 +1983,14 @@

    We need to describe concerns, tradeoffs and possible mitigations of handling multiple requests and responses for credential presentation.

    +

    + Verifiers may wish to define a single credential request + using multiple [=digital credential/exchange protocols=], + for example to achieve maximum compatibility across [=user agent | user agents=] + or when migrating to a newer version of a protocol. When doing so, + verifiers SHOULD ensure that all requests are semantically equivalent to avoid confusing + the user, the user agent, and the wallet during processing of the request. +

    Integrating Multiple User Agents

    From 2d3c3c50cafb73af7e4f175b95e840e9dc023797 Mon Sep 17 00:00:00 2001 From: Matthew Miller Date: Thu, 28 Aug 2025 11:29:08 -0700 Subject: [PATCH 6/6] Incorporate PR feedback --- index.html | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/index.html b/index.html index 3abc1b63..1b2ac377 100644 --- a/index.html +++ b/index.html @@ -777,11 +777,12 @@

    The following guidance on handling multiple requests will need to be relocated once this entire section of the algorithm is defined. - When multiple [=digital credential/presentation requests=] are present - in {{DigitalCredentialRequestOptions/requests}}, - [=user agents=] MUST NOT return more than one - [=digital credential/presentation responses | presentation response=]. - Multiple credentials MAY be present in this one response depending on the capabilities + When multiple [=digital credential/presentation request | presentation requests=] + are present in |requests|, + a [=user agent=] MUST NOT return more than one + [=digital credential/presentation response=]. + However, multiple credentials MAY be included in this single response + depending on the capabilities of the corresponding [=digital credential/exchange protocol=].