Skip to content

Commit b365fef

Browse files
authored
Editorial: Add initial intro text (#193)
1 parent 9b414ea commit b365fef

File tree

1 file changed

+47
-6
lines changed

1 file changed

+47
-6
lines changed

index.html

+47-6
Original file line numberDiff line numberDiff line change
@@ -64,10 +64,48 @@
6464
<h2>
6565
Introduction
6666
</h2>
67+
<p>
68+
This document defines an API enabling a website to request presentation
69+
of a [=digital credential=].
70+
</p>
71+
<p>
72+
The API design is agnostic to both credential presentation [=digital
73+
credential/exchange protocols=] and credential formats. However, to
74+
promote interoperability this document includes a
75+
[[[#protocol-registry]]].
76+
</p>
77+
<p>
78+
The API is designed to support the following goals:
79+
</p>
80+
<ul>
81+
<li>Keep the act of requesting separate from the specific [=digital
82+
credential/protocol=], thereby enabling the extensibility of the
83+
[=digital credential/protocol=] and credential formats.
84+
</li>
85+
<li>Require [=digital credential/requests=] to be unencrypted, enabling
86+
user-agent inspection for risk analysis.
87+
</li>
88+
<li>Assume [=digital credential/presentation response|responses=] opacity
89+
(encrypted responses), enabling verifiers and holders to control where
90+
potentially sensitive personally identifiable information is exposed.
91+
</li>
92+
<li>Require [=transient activation=] to perform [=digital
93+
credential/requests=], ensuring that sites cannot silently query for
94+
digital credentials nor communicate with wallet providers without the
95+
user's active participation and confirmation of each action.
96+
</li>
97+
<li>Enable platform-provided credential selection UX when multiple wallet
98+
applications have credentials that match a [=digital
99+
credential/requests=].
100+
</li>
101+
<li>Enable platforms to potentially provide secure cross-device [=digital
102+
credential/requests=] with proximity checks.
103+
</li>
104+
</ul>
67105
<p id="credential-type-examples">
68-
There are many types of digital credential that can be presented using
69-
this API. <dfn data-lt="credential type examples">Examples of these
70-
types</dfn> include:
106+
[=Digital credentials=] of many types can be presented using this API.
107+
<dfn data-lt="credential type examples">Examples of these types</dfn>
108+
include:
71109
</p>
72110
<ul>
73111
<li>a driving license, passport, or other identity card issued by a
@@ -107,7 +145,8 @@ <h2>
107145
</p>
108146
</dd>
109147
<dt>
110-
<dfn data-dfn-for="digital credential">Presentation request</dfn>
148+
<dfn data-dfn-for="digital credential" data-local-lt=
149+
"requests">Presentation request</dfn>
111150
</dt>
112151
<dd>
113152
A presentation request is a request for a [=digital credential=]
@@ -123,15 +162,17 @@ <h2>
123162
credential=] from a [=holder=].
124163
</dd>
125164
<dt>
126-
<dfn>Presentation response</dfn>
165+
<dfn data-dfn-for="digital credential" data-local-lt=
166+
"response">Presentation response</dfn>
127167
</dt>
128168
<dd>
129169
A format that a [=holder|holder's=] software, such as a digital wallet,
130170
uses, via an [=digital credential/exchange protocol=], to respond to a
131171
[=digital credential/request data=] by a [=verifier=].
132172
</dd>
133173
<dt>
134-
<dfn data-dfn-for="digital credential">Exchange protocol</dfn>
174+
<dfn data-dfn-for="digital credential" data-local-lt=
175+
"protocol">Exchange protocol</dfn>
135176
</dt>
136177
<dd>
137178
A protocol used for exchanging a [=digital credential=] between a

0 commit comments

Comments
 (0)