Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify that exchanges are short-lived #441

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Clarify that exchanges are short-lived #441

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a3e9dae
Clarifies that exchanges are short-lived
jrhender Jan 27, 2025
b93e8d0
Clarify relationship between VC API and platforms for long-lived inte…
jrhender Jan 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1122,6 +1122,19 @@ <h3>Workflows and Exchanges</h3>
</p>
<span class="issue">These examples will be added later.</span>
<p>
VC API exchanges are expected to be short-lived but they can be combined with other mechanisms to enable longer interactions.
Examples of other mechanisms include SMS, email, web notifications, or phone calls.
This approach simplifies digital wallet implementation and allows
existing mechanisms to be reused without reinvention within
the VC API. The Web or native platforms are expected to enable
additional interactions via applications (such as Web browsers)
or other platform features.
For example, in asynchronous issuance, a holder requests a credential but must wait for processing.
In such cases, VC API components (such as an issuer coordinator) make
use of mechanisms outside the VC API to notify the holder when their
credential is ready for collection.
</p>
<p>
The following APIs are defined for using workflows and exchanges for credential use cases that require crossing trust boundaries:
</p>

Expand Down