From d34174a2804a8bc7bc6c17a0b83966a2bf6a4777 Mon Sep 17 00:00:00 2001 From: Tim Cappalli Date: Thu, 28 Nov 2024 02:03:02 +0900 Subject: [PATCH] s/apps/native apps Co-authored-by: Christian Bormann <8774236+c2bo@users.noreply.github.com> --- openid-4-verifiable-presentations-1_0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openid-4-verifiable-presentations-1_0.md b/openid-4-verifiable-presentations-1_0.md index f459deb..5a74f3e 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -1963,7 +1963,7 @@ This section defines a profile of OpenID4VP for use with the Digital Credentials The name "Digital Credentials API" (DC API) encomposes the W3C Digital Credentials API [@!W3C.Digital_Credentials_API] as well as its native App Platform equivalents in operating systems (such as [Credential Manager on Android](https://developer.android.com/jetpack/androidx/releases/credentials)). -The DC API allows web sites and apps acting as Verifiers to request the presentation of verifiable credentials. +The DC API allows web sites and native apps acting as Verifiers to request the presentation of verifiable credentials. The API itself does not define a Credential exchange protocol but can be used with multiple protocols. The Web Platform, working in conjunction with other layers, such as the app platform/operating system, and based on the permission of the End-User, will send the request data along with the web or app origin of the Verifier to the End-User's chosen Wallet.