-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathindex.html
513 lines (367 loc) · 36.4 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
<!DOCTYPE html>
<html>
<head>
<title>Verifiable Credentials for Education, Employment, and Achievement Use Cases</title>
<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
<!--
=== NOTA BENE ===
For the three scripts below, if your spec resides on dev.w3 you can check them
out in the same tree and use relative links so that they'll work offline,
-->
<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script>
<script src="./common.js" class="remove"></script>
<script type="text/javascript" class="remove">
var respecConfig = {
// specification status (e.g., WD, LCWD, NOTE, etc.). If in doubt use ED.
specStatus: "CG-DRAFT",
group: "credentials",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "vc-ed-use-cases",
// subtitle for the spec
subtitle: "Verifiable Credentials use cases specific to formal, informal, and non-formal education and training contexts",
// if you wish the publication date to be other than today, set this
//publishDate: "2019-03-26",
//crEnd: "2019-04-23",
//implementationReportURI: "https://w3c.github.io/sdh-test-suite",
previousMaturity: "UNOFFICIAL",
previousPublishDate: "2021-01-03",
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
// previousPublishDate: "1977-03-15",
// previousMaturity: "WD",
// extend the bibliography entries
//localBiblio: ccg.localBiblio,
//doJsonLd: true,
github: "https://github.com/w3c-ccg/vc-ed-use-cases/",
includePermalinks: false,
// if there a publicly available Editor's Draft, this is the link
edDraftURI: "https://w3c-ccg.github.io/vc-ed-use-cases/",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
// editors, add as many as you like
// only "name" is required
editors: [
{ name: "Simone Ravaioli", url: "https://www.linkedin.com/in/simoneravaioli",company: "Parchment", companyURL: "https://www.parchment.com/"},
{ name: "Deborah Everhart", url: "https://www.linkedin.com/in/deboraheverhart/",company: "Credential Engine", companyURL: "https://credentialengine.org/"},
{ name: "John Kuo", url: "https://www.linkedin.com/in/mjkuo/",company: "Pocket", companyURL: "https://pocket.asu.edu/"},
{ name: "Justin Pozmanter", url: "https://www.linkedin.com/in/justin-pozmanter-4524001/",company: "Velocity Network", companyURL: "https://www.velocitynetwork.foundation/"},
{ name: "Phillip Long", url: "https://www.linkedin.com/in/longpd/",company: "RHz Consulting", companyURL: "https://www.linkedin.com/in/longpd/"},
{ name: "Wesley Teter", url: "https://www.linkedin.com/in/wesleyteter/",company: "UNESCO Bankok", companyURL: "https://bangkok.unesco.org/"}
],
// authors, add as many as you like.
// This is optional, uncomment if you have authors as well as editors.
// only "name" is required. Same format as editors.
authors:
[
{ name: "Kerri Lemoie", url: "https://www.linkedin.com/in/kerrilemoie",company: "MIT Digital Credential Consortium", companyURL: "https://digitalcredentials.mit.edu/"},
{ name: "Kim Hamilton Duffy", url: "https://www.okimsrazor.com/",
company: "Centre", companyURL: "https://www.centre.io/"},
{ name: "Anthony Camilleri", url: "http://www.linkedin.com/in/anthonyfcamilleri",
company: "Knowledge Innovation Centre", companyURL: "https://knowledgeinnovation.eu/"},
{ name: "Dmitri Zagidulin", url: "https://www.linkedin.com/in/dzagidulin/",
company: "MIT Digital Credential Consortium", companyURL: "https://digitalcredentials.mit.edu/"}
],
// name of the WG
wg: "Verifiable Credentials for Education Task Force",
// URI of the public WG page
wgURI: "https://w3c-ccg.github.io/vc-ed/",
// name (with the @w3c.org) of the public mailing to which comments are due
wgPublicList: "public-vc-edu",
// URI of the patent status for this WG, for Rec-track documents
// !!!! IMPORTANT !!!!
// This is important for Rec-track documents, do not copy a patent URI from a random
// document unless you know what you're doing. If in doubt ask your friendly neighborhood
// Team Contact.
//wgPatentURI: "https://www.w3.org/2004/01/pp-impl/98922/status",
maxTocLevel: 3,
inlineCSS: true
};
</script>
<style>
pre .highlight {
font-weight: bold;
color: green;
}
pre .comment {
font-weight: bold;
color: Gray;
}
.color-text {
font-weight: bold;
text-shadow: -1px 0 black, 0 1px black, 1px 0 black, 0 -1px black;
}
ol.algorithm {
counter-reset: numsection;
list-style-type: none;
}
ol.algorithm li {
margin: 0.5em 0;
}
ol.algorithm li:before {
font-weight: bold;
counter-increment: numsection;
content: counters(numsection, ".") ") ";
}
table {
font-family: arial, sans-serif;
border-collapse: collapse;
width: 100%;
}
td, th {
border: 1px solid #dddddd;
text-align: left;
padding: 8px;
}
</style>
</head>
<body>
<section id='abstract'>
<p>
Diplomas, licenses, certifications, certificates, micro-credentials, badges, and other types of achievement recognition and credentials in education and employment are increasingly being issued in digital formats that require different methods of demonstrating integrity than paper documents. These digital credentials when issued as <a Href="https://www.w3.org/TR/vc-data-model">W3C Verifiable Credentials</a> can be asserted as cryptographically secure, privacy-respecting, machine-verifiable, and interoperable <a href="https://www.w3.org/TR/vc-data-model/#dfn-verifiable-credentials">verifiable credentials</a>. This gives individuals access to and control over their achievement data when they need it and throughout their lifetimes. This document outlines user roles in this ecosystem and use cases documented by the <a href="https://w3c-ccg.github.io/vc-ed/">Verifiable Credentials for Education Task Force</a> community that describe user needs, user tasks, and technology needs.</p>
</section>
<section id='sotd'>
<p>
This document represents a collection of education, training, and achievements use cases readers
should review alongside the <a href="https://www.w3.org/TR/vc-data-model/">Verifiable
Credentials Data Model</a>.
</p>
</section>
<section id="introduction">
<h2>Introduction</h2>
<p>
The Verifiable Credentials for Education Task Force (<a href="https://w3c-ccg.github.io/vc-ed/charter/">Charter</a>) is exploring the use of Verifiable Credentials (VC) that represent formal, informal, and non-formal education, employment, and achievement credentials. This effort attempts to bridge the VC ecosystem to the robust work already done in the education and training data standards space. Work in this task force is based on use cases. The use cases below have been provided by participants in the community and across a diverse education and employment credentialing network. Some use cases will exist but others may be theoretical.
</p>
<h3>Importance of this Work</h3>
<p>Learning, employment, and achievement claims come in many forms: formal, informal, and non-formal learning, including degrees, diplomas, certifications, micro-credentials, badges, professional qualifications, recognition of prior learning, etc. Many education data standards and international conventions exist to describe these claims (also called descriptive payloads or achievement descriptions). This includes several that are intended to be used for digital credentialing and have their own methods for verification. </p>
<p>Standardization of digital claim technologies makes it possible for many stakeholders to issue, earn, and trust these essential records about their counterparties, without being locked into proprietary platforms <cite><a href="hhttps://www.w3.org/TR/vc-use-cases/#importance-of-this-work">([Verifiable Credentials Use Cases], section 1.1)</a></cite>. The challenge in learning, employment, and achievements is to standardize verification while providing a structure for the description payloads to be inserted.
</p>
<p>This work provides a way for these claims to be delivered cryptographically verifiably in the control of individuals who are the subjects of the claims giving them immediate access to information about them and the freedom to choose who or what to share this data with.</p>
<h3>Format of this Document</h3>
<p>This document is formatted into four sections to help describe the entities involved, why they could use verifiable credentials, how they could use them, and what is needed by the technologies. User roles describe the types of stakeholders that will be involved with verifiable credentials. The user needs section describes different types of credentials and scenarios of how they could be used. The user tasks section describes the actions of the different stakeholders. The technology needs section describes use cases illustrating what is needed by technologies in this space.</p>
</section>
<section id="user-roles">
<h2>User Roles</h2>
<p>The Verifiable Credentials standard mentions four roles: Subject, Holder, Issuer, and Verifier. Additional roles and details have been added in this document to describe the entities that are participating in education verifiable credentialing ecosystems.</p>
<h3>Subject</h3>
<p>The entity, typically a person such as a student or employee, about whom a claim is issued.</p>
<h3>Holder</h3>
<p>The entity, typically a person such as a student or employee, who may also be the subject of the claim, that can prove control of the verifiable credential containing the claim.</p>
<h3>Issuer</h3>
<p>The entity, which could be an organization such as an educationa institution or employer but also could be an individual including the subject or holder, that creates the claim.</p>
<h4>Employer</h4>
<p>A small company issues verifiable credentials to employees for their achievements at the company. These credentials are evaluated internally to support promotions and reviews. Employees may export them to wallets to be used to prove employment history.</p>
<h4>Formal Institutions</h4>
<p>A university issues a diploma in the form of a verifiable credential.</p>
<h4>Individual/Peer</h4>
<p>An individual endorses the skills of their colleagues.</p>
<h4>Informal Education Organization or Individual</h4>
<p>An app teaching lessons about cooking and cooking safety issues a verifiable credential when quizzes are completed successfully.</p>
<h4>Licensure or Certification Body</h4>
<p>A physical therapist candidate passes an exam and is licensed to practice by a licensure body.</p>
<h4>Non-formal Education Organization</h4>
<p>A community organization teaches residents of a town how to participate in a recycling program. Upon receipt of a verifiable credential, residents are able to register for recycling pick up at their homes.</p>
<h3>Issuer Platform Provider</h3>
<p>The entity that provides the technology. This may be the issuer or it may serve as the agent of trust/proxy on behalf of the issuer. The distinction should be made because decisions about the technology are made by the provider.</p>
<h3>Wallet</h3>
<p>A software system that serves as a data repository used to store, manage, protect, share, and present digital credentials and assets. <cite><a href="https://w3c-ccg.github.io/universal-wallet-interop-spec/">[Universal Wallet 2020]</a></cite></p>
<h3>Verifier</h3>
<p>The entity verifying a claim about a given subject. [] This could be an agent representing an employer or an employer.</p>
<h3>Verifier Services/Platform Provider</h3>
<p>The entity verifying a claim about a given subject. [] These services may be used by a Verifier.</p>
<h3>Reliant Third Party</h3>
<p>The entity expecting the claim to be verified such as an employer or organization evaluating the content of the claim. This entity may also be the verifier.</p>
<h3>Trust Registries</h3>
<p>Trust registries can be a container or set of containers, services, databases, ledgers etc., that verifiers can use to look up information such as issuer identity & profile information, credential descriptions, and rules associated with credentials. The intent of the registries is to provide a source of information for claims to be verified without contacting the issuer and prevent tracking of verification requests. If issuers serve as registries, then the privacy of the verification may be at risk because then the issuer could become aware of any instance when a credential that they issued is being used. </p>
<p>In education, trust registries and governance are often conflated with accreditation bodies. While accreditation bodies may participate in or even host trust registries, the purposes are different in that accreditation bodies evaluate the educational institution and provide information based on that whereas trust registries in the verifiable credentials context are related to verifiability of credential data specifically not the perceived value of the experiences that the data represents.</p>
</section>
<section id="user-needs">
<h2>User Needs</h2>
<h3>Different Types of Credentials</h3>
<h4>Academic Achievements</h4>
<p>A student is issued a verifiable credential for each academic achievement in her post-secondary career including co-curricular activities and her final diploma. She stores the verifiable credentials in a wallet application and presents them to those who request to confirm her experiences.</p>
<h4>Attendance</h4>
<p>Sheila completed a MOOC in Introductory Economics from the University of Göttingen. She chose not to take a 'verified/certified track'. The university issued her a verifiable credential indicating merely that she attended the course and the dates of attendance.</p>
<h4>Corporate Certifications</h4>
<p>A technology company authorizes schools around the world to issue certifications, which indicate that graduates are experts in supporting customers using their products. The certificates must indicate that these certificates were issued with the permission of the parent company, even though the certificates are issued by individual schools.</p>
<h4>Demonstration of Achievement</h4>
<p>Sharon completed her fifth marathon. With each marathon, she was recognized with a verifiable credential. For the fifth marathon, she was awarded a credential that allows her to run future marathons without entering a raffle.</p>
<h4>Endorsement, Performance Review, Professional Assessment, Reference, Recommendation</h4>
<p>Using a verifiable credential, an employer wants to be able to attest to the capabilities of an employee which she describes having obtained while working at her company.</p>
<h4>Enrollment</h4>
<p>Fawaz wishes to present proof of their enrollment at the University of Wisconsin using a verifiable credential that the university issued to him so as to access a student discount to enter a museum.</p>
<h4>Extended Transcript Published by a Registrar</h4>
<p>Joleen is the registrar of Mega University and, by virtue of her office, is responsible for the integrity, accuracy, and security of academic records. Joleen has been a pioneering registrar in advocating an "extended transcript" that includes not only the standard set of course grades but also adds supplementary information on learner competencies. These might include work experiences and non-educational but marketable skills. Joleen upon the request of her students, Joleen issues a verifiable credential that includes an extended transcript.</p>
<h4>Grade Point Average</h4>
<p>A high school wishes to document all the grades that a student has achieved over their high-school lifetime, but also present the summative grade (a GPA) that is based on these grades as a verifiable credential.</p>
<h4>Insurance</h4>
<p>A company that provides software development and support services is required by clients to have liability insurance which can be verified by a verifiable credential.</p>
<h4>Internal Corporate Training and Certification</h4>
<p>A national retailer uses verifiable credentials to track employee training to facilitate employees' moves from department to department and store to store.</p>
<h4>Membership</h4>
<p>Kev is a member of their neighborhood library which participates in an initiative that connects library members to other libraries and participating museums around the world. Their library card is a verifiable credential stored in the wallet app on their mobile phone. The verifiable credential is co-signed by a digital notary service and also serves as an acceptable form of government ID where Kev lives and gives them access to free public transportation.</p>
<h4>Peer Assertion</h4>
<p>Ameilia issues herself a verifiable credential to document her job as a CNA. Amelia’s colleagues issue recommendations in the form of verifiable credentials that support this verifiable credential.</p>
<h4>Professional Certification/Licensure</h4>
<p>A certification or license awarded for completion of a professional program is often needed to meet government regulations. These types of credentials typically have time-to-live licenses with forced expiry without renewal.
</p>
<h4>Recognition of Prior Learning</h4>
<p>Josephina decided to return to college to finish her bachelors degree. The college she attended evaluated her work experience and determined that skills and knowledge that she attained while working qualified to replace several of the courses required for the degree.
</p>
<h4>Self-Assertion</h4>
<p>Louisa improved skills related to her role at the company where she works and issues herself a verifiable credential that contains a description of the skills and video evidence demonstrating her mastery of them.</p>
<h4>Skill Assessment</h4>
<p>Alma has a list of verifiable credentials in her wallet describing the mastery of skills related to her education, employment, and hobbies. She would like to present only the relevant skills when applying for a new role.</p>
<h3>Credential Uses</h3>
<h4>Achievement and Experience History</h4>
<p>A professor wants to use her school-issued credentials to create assignments for students. A student wants to access their assignments and their grades which are viewable only by the students and the professor.</p>
<h4>Access to LMS & Roles</h4>
<p>A professor wants to use her school-issued credentials to create assignments for students. A student wants to access their assignments and their grades which are viewable only by the students and the professor.</p>
<h4>Apply to University/Scholarship</h4>
<p>Geraldine is a high school student and is using their Open Badges as part of an application to attend university.</p>
<h4>Apply for a Job</h4>
<p>Jo has experience working in restaurants and retail. She moves to another state and when she applies for jobs at the restaurants in her new neighborhood, she can provide verifiable proof of previous employment and credentials that describe her mastery of skills.</p>
<h4>Container for Other Credentials</h4>
<p>A teacher uploads certifications, licenses, and test scores in the form of PDFs, Open Badges, and other data formats to a publishing service. On request of the teacher, the service issues a verifiable credential containing the other credentials which the teacher can put in their wallet application.</p>
<h4>Educational & Occupational Health Verification</h4>
<p>University A requires all students to supply proof of vaccinations.</p>
<h4>Promote Access to Higher Education and Lifelong Learning, Including for Refugees and Displaced Persons</h4>
<p>Khaled fled a civil war in his home country and resettled in a new host country. In his old country he earned a bachelors degree in software engineering and would like to pursue a masters in his new country.</p>
<h4>Recognition of Experience</h4>
<p>George is a frequent visitor of the maker lab at his library which has issued him verifiable credentials for his demonstrated experiences in using a soldering iron and the laser printer.</p>
<h4>Qualify for a Promotion or Pay Raise</h4>
<p>As an employee, Gil wants to provide his employer with proof that he is certified in first aid so that he can be given the role of a designated first aid attendant in the workplace and get a raise.</p>
<h4>Student Identity</h4>
<p>Nigel is a student at the technical college. He is issued a verifiable digital identity that is accessible using a QR code on his physical student id or from the wallet app on his mobile phone.</p>
</section>
<section id="user-tasks">
<h2>User Tasks</h2>
The following tasks are performed by the entities as part of the verifiable credentialing processing not specifically to the education and employment domains.
<h3>Issue Claim</h3>
<p>It must be possible for any entity to issue a verifiable credential <cite><a href="https://www.w3.org/TR/vc-use-cases/#issue-claim">([Verifiable Credentials Use Cases], section 4.1)</a></cite>.</p>
<h3>Assert Claim</h3>
<p>It must be possible for the holder of a verifiable credential to restrict the amount of information exposed in a credential they choose to share. It also must be possible for the holder to limit the duration for which that information is shared <cite><a href="https://www.w3.org/TR/vc-use-cases/#assert-claim">([Verifiable Credentials Use Cases], section 4.2)</a></cite>.</p>
<h3>Verify Claim</h3>
<p>It must be possible for a verifier to verify that the credential is an authentic statement of an issuer's claims about the subject. The verifying entity must have the capability to connect the issuer’s identity to its credential identifier and the subject's identity to their identifier as indicated in the credential. The issuer’s verification information, such as its public key, must be discoverable from the credential record and verifiably linked to the issuer. It must be possible to do this in an automated fashion. <cite><a href="https://www.w3.org/TR/vc-use-cases/#verify-claim">([Verifiable Credentials Use Cases], section 4.3)</a></cite></p>
<h3>Check Veracity of Claim</h3>
<p>Additional application-, domain-, or business-specific checks for determining whether the VC fits the intended use. This may have the effect of restricting or relaxing the acceptance of results from previous steps <cite><a href="https://github.com/w3c-ccg/vc-api/blob/main/verification.md#veracity">(Verification, Validation, and Veracity)</a></cite>.</p>
<h3>Store/Move Claim</h3>
<p>It must be possible for the holder of a claim to store that claim in one or more credential repositories. It must also be possible for the holder to move a claim among credential repositories, and to do so without requesting a new claim from the claim issuer. <cite><a href="https://www.w3.org/TR/vc-use-cases/#store-move-claim">([Verifiable Credentials Use Cases], section 4.4)</a></cite></p>
<h3>Retrieve Claim</h3>
<p>It must be possible for a holder to select if and which appropriate credential should be sent to a verifier <cite><a href="https://www.w3.org/TR/vc-use-cases/#retrieve-claim">([Verifiable Credentials Use Cases], section 4.5)</a></cite>.</p>
<h3>Revoke Claim</h3>
<p>It must be possible for the issuer of a claim to revoke it, after which it will no longer satisfy verification procedures <cite><a href="https://www.w3.org/TR/vc-use-cases/#revoke-claim">([Verifiable Credentials Use Cases], section 4.6)</a></cite>.</p>
<h3>Refresh Claim</h3>
<p>Verifiable Credentials can expire. It is useful to provide instructions on refreshing the credential for the times when expiration is imminent or has already occurred. The refresh can be performed manually or, with the prior consent of the credential holder, automatically <cite><a href="https://w3c-ccg.github.io/vc-refresh-2021/">(Verifiable Credential Refresh 2021)</a></cite>.</p>
<h3>Update Claim</h3>
<p>It may be requested that updates be made to a descriptive payload after it has been issued. Edits to the payload such as minor text corrections may not affect meaning but more substantive edits such as changing a description or criteria would affect the meaning. Currently, there is no mechanism to support this except to revoke and reissue when agreed upon by both issuer and subject.</p>
</section>
<section id="tech-needs">
<h2>Technology Needs</h2>
<h3>Identitfier</h3>
<h4>Change Identifier from Email to Decentralized Identifier</h4>
<p>Krystal has been issued several Open Badges to her personal email address. She’d like to put the badges in her VC Wallet and associate those credentials with the DID she creates and controls from that wallet.</p>
<h4>Learner Wishes to Change Decentralized Identifier Associated with the Credential</h4>
<p>Arne was the subject of a VC that described his diploma. He accidentally deleted the private key associated with the DID that is the identity associated with this diploma.</p>
<h3>Display Online</h3>
<h4>Viewable Online</h4>
<p>René’s verifiable digital credential is viewable online by those who do not have access to verifiable credentials verifying services. The online view may or may not display the verification status of René’s credential.</p>
<h3>Guardianship & Delegation</h3>
<h4>Learner is a minor and guardian(s) control their credentials</h4>
<p>Ella is ten years old. Her school issues verifiable records of Ella’s grades and school experiences. Ella’s parents are the holders of Ella’s credentials. When Ella is thirteen the credentials will be transferred to Ella’s wallet.</p>
<h3>Image/file Resources</h3>
<h4>Embedding Image</h4>
<p>Ellis’ verifiable student ID contains a photo of them so that when they present the ID, the verifier can compare the photo to Ellis.</p>
<h4>Linking to Image</h4>
<p>The evidence in Nora’s micro-credential is a URL linking to a photo of her and her classmates demonstrating their final project.</p>
<h4>Credential Image</h4>
<p>Jake is issued an Open Badge and the image representing the verifiable credential is hosted at a URL by the issuing provider.</p>
<h4>Achievement Description Image</h4>
<p>Atul is issued an Open Badge and the image representing the achievement is hosted by the issuing provider.</p>
<h4>Deliver Data Inside an Image/file</h4>
<p>Nick is issued a diploma for completing high school. The diploma is a verifiable credential and is embedded in a PDF that may be printed and framed.</p>
<h4>Include Assets to Support the Claim</h4>
<p>University Y’s digital student IDs contain a photo of the student's faces</p>
<p>Professional license contains a printable certificate</p>
<p>Student’s badge contains a photo documenting their final project</p>
<h3>Resource Linking</h3>
<h4>Credentials Reference to Other Credentials</h4>
<p>Roy’s verifiable digital credential certificate is linked to four other digital credential certificates that were earned in the same training program.</p>
<p>A verifiable credential is issued containing Peter's endorsement and a link to a colleague's verifiable credential containing a self-assertion of their skills.</p>
<h4>Reference Learner Artifacts & Assets</h4>
<p>Jo Jo’s digital badge contains an array of links to files and websites supporting her self-assertion of software development skills.</p>
<h3>Multiple Digital Signatures</h3>
<h4>Signed by More than One University</h4>
<p>A student is issued a transcript of the courses she’s taken at various universities. Each university has signed the transcript.</p>
<h3>Issuing a credential with the achievement described by another entity</h3>
<p>A health organization has authorized many schools to teach a curriculum provided by the organization. Upon completion of a course, every student is issued a credential by the teachers on behalf of the schools. The achievement description of the credential is created by the health organization to correspond with the curriculum that they’ve designed.</p>
<h3>Accessibility</h3>
<h4>WCAG 2.1 AA Compliant</h4>
<p>Make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations <cite><a href="https://www.w3.org/TR/WCAG21/">([Web Content Accessibility Guidelines (WCAG)], 2.1)</a></cite>.
<h4>504/508 Compliance (United States)</h4>
<p>Section 504 states: “No otherwise qualified individual with a disability in the United States . . . shall, solely by reason of her or his disability, be excluded from the participation in, be denied the benefits of, or be subjected to discrimination under any program or activity receiving Federal financial assistance . . . ." <cite><a href="https://www2.ed.gov/about/offices/list/ocr/504faq.html">(Protecting Students With Disabilities)</a></cite></p>
<p>Section 508 requires that Federal agencies' electronic and information technology is accessible to people with disabilities, including employees and members of the public. <cite><a href="https://www.ada.gov/508/">(SECTION 508 SURVEYS and REPORTS)</a></cite></p>
<h4>Limited Technology Access</h4>
Gerardo is attending training that provides certification for heavy equipment use. The training system provides the ceritifcation digitally but Gerardo does not have access to a portable computer or mobile device.
<h3>Privacy</h3>
<h4>PII and Individual Data</h4>
<p>Seondary School questions how much personal information should be containe din a verifiable credential. For example, if they have the parents' permission can they include the student's name, attendance information, address, and grades?</p>
<h4>Selective Disclosure</h4>
<p>Student would like to confirm that she is an active student without revealing what school she attends.</p>
<h3>Security Considerations</h3>
<h4>Outdated or Unsupported Cryptography</h4>
<p>Walter is using a wallet application on his mobile device that is using a cryptography suite that has demonstratrably insecure <cite><a href="https://www.w3.org/TR/vc-data-model/#cryptography-suites-and-libraries">([Verifiable Credentials Use Cases], section 8.1)</a></cite>.</p>
<h4>Content Integrity</h4>
<p>See <a href="#resource-linking">Resource Linking</a> <cite><a href=" https://www.w3.org/TR/vc-data-model/#content-integrity-protection">([Verifiable Credentials Use Cases], section 8.2)</a></cite>.</p>
<h4>Unsigned Claims</h4>
<p>Tracy’s digital credential does not contain a proof and is not digitally signed <cite><a href="https://www.w3.org/TR/vc-data-model/#unsigned-claims">([Verifiable Credentials Use Cases], section 8.3)</a></cite>.</p>
<h4>Preventing a Man-in-the-Middle Attack</h4>
<p>When recieving verifiable credentials for applications to the university, requests for verifiable presentations containing the credentials are tied to the response <cite><a href="https://www.w3.org/TR/vc-data-model/#token-binding">([Verifiable Credentials Use Cases], section 8.4)</a></cite>.</p>
<h4>Prevent Unintended Bundling of Claims</h4>
<p>University Y issues several verifiable credentials to individuals securely with clear description so that when the individual creates custom presentations of a sub-selection of those credentials, the individual doesn’t misrepresentthe achievements <cite><a href="https://www.w3.org/TR/vc-data-model/#bundling-dependent-claims">([Verifiable Credentials Use Cases], section 8.5)</a></cite>.</p>
<h4>Acurate Expiration Dates</h4>
<p>Lisa’s nursing license is set to expire every year so that she must renew and request an updated verifiable credential <cite><a href="https://www.w3.org/TR/vc-data-model/#highly-dynamic-information">([Verifiable Credentials Use Cases], section 8.6)</a></cite>.</p>
<h4>Device Theft and Impersonation</h4>
<p>Charles is advised by the university to enable strong authentication on his mobile device to keep his credentials secure. <cite><a href="https://www.w3.org/TR/vc-data-model/#device-theft-and-impersonation">([Verifiable Credentials Use Cases], section 8.7)</a></cite>.</p>
<h3>Global Considerations</h3>
<h4>Languages</h4>
<p>Hannah has been issued credentials in the language of the country where she attended university and will be sharing these credentials with an institution whose primary language is another country.</p>
<h4>International Interoperability</h4>
<p>Frank’s diploma has been issued as a verifiable credential. Many educational systems worldwide are able to verify and consume this credential because it is aligned with the W3C Verifiable Credentials Specification.</p>
<h4>Privacy</h4>
<p>Because of GDPR, Laura’s training certificate credential continues to be verifiable even though the her account and data has been removed from the training platform.</p>
<h4>Data Models</h4>
<p>Ian’s education credentials issued in the US are verifiable credentials but the descriptions of his achievements vary from his colleagues outside of the US who have the same education background.</p>
<h4>Governance</h4>
<p>Lucille’s credentials are issued by organizations participating in a trust registry hosted by the government where the institutions are located. Jason’s credentials are issued by organizations participating in a trust registry hosted by an accreditation body.</p>
</section>
<section id="acknowledgements"class="appendix">
<h2>Acknowledgements</h2>
<p>The use cases in this document have been submitted by members VC-EDU Task Force community and participants at the T3 Innovation Network.</p>
</section>
<section id="references" class="appendix">
<h2>References</h2>
<dl>
<dt>[Universal Wallet 2020]</dt>
<dd><cite><a href="https://w3c-ccg.github.io/universal-wallet-interop-spec/">Universal Wallet 2020</a></cite>,
O. Steele, M. Johnson, G. Dardelet, M. Prorock, S. Shetty, K. Hamilton Duffy. W3C Editor's Draft 30 August 2022. URL: https://w3c-ccg.github.io/universal-wallet-interop-spec/
</dd>
<dt>[Verifiable Credentials]</dt>
<dd><cite><a href="https://www.w3.org/TR/vc-data-model/">Verifiable Credentials Data Model v1.1</a></cite>,
M.Sporny, G.Noble, D. Longley, D.C. Burnett, B. Zundel, K. Den Hartog. W3C Verifiable Credentials Working Group. W3C Recommendation 09 November 2021. URL: https://www.w3.org/TR/vc-data-model/
</dd>
<dt>[Verifiable Credential Refresh 2021]</dt>
<dd><cite><a href="https://w3c-ccg.github.io/vc-refresh-2021/">Verifiable Credential Refresh 2021</a></cite>,
M. Sporny, D. Zagidulin. W3C Draft Community Group Report 14 February 2022. URL: https://w3c-ccg.github.io/vc-refresh-2021/
</dd>
<dt>[Verifiable Credentials Use Cases]</dt>
<dd><cite><a href="https://www.w3.org/TR/vc-use-cases/">Verifiable Credentials Use Cases</a></cite>,
S.McCarron; J. Andrieu; M. Stone; T. Siegman; G. Kellogg; T. Thibodeau, Jr. W3C Working Group Note 24 September 2019. URL: https://www.w3.org/TR/vc-use-cases/
</dd>
<dt>[Web Content Accessibility Guidelines]</dt>
<dd><cite><a href="https://www.w3.org/TR/WCAG21/">Web Content Accessibility Guidelines (WCAG)</a></cite>,
A. Kirkpatrick; J. O'Connor; A. Campbell; M. Cooper. Web Content Accessibility Guidelines (WCAG) 2.1. 5 June 2018. W3C Recommendation. URL: https://www.w3.org/TR/WCAG21/ ED: https://w3c.github.io/wcag/21/guidelines/
</dd>
</dl>
</section>
</body>
</html>