forked from w3c-ccg/vc-ed-use-cases
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
326 lines (276 loc) · 9.93 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
<!DOCTYPE html>
<html>
<head>
<title>Verifiable Credentials for Education 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-common' 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",
// 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 educational 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: "Anthony Camilleri", url: "http://www.linkedin.com/in/anthonyfcamilleri",
company: "Knowledge Innovation Centre", companyURL: "https://knowledgeinnovation.eu/"},
{ name: "Kim Hamilton Duffy", url: "https://www.okimsrazor.com/",
company: "Massachusetts Institute of Technology", companyURL: "https://openlearning.mit.edu/"}
],
// 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: "Anthony Camilleri", url: "http://www.linkedin.com/in/anthonyfcamilleri",
company: "Knowledge Innovation Centre", companyURL: "https://knowledgeinnovation.eu/"},
{ name: "Kim Hamilton Duffy", url: "https://www.okimsrazor.com/",
company: "Massachusetts Institute of Technology", companyURL: "https://openlearning.mit.edu/" }
],
// name of the WG
wg: "Credentials Community Group",
// URI of the public WG page
wgURI: "https://www.w3.org/community/credentials/",
// name (with the @w3c.org) of the public mailing to which comments are due
wgPublicList: "public-credentials",
// 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: 2,
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, ".") ") ";
}
</style>
</head>
<body>
<section id='abstract'>
<p>
TODO: Abstract goes here.
</p>
</section>
<section id='sotd'>
<p>
TODO: This document represents a concise but limited collection of use cases readers
should review alongside the <a href="https://www.w3.org/TR/vc-data-model/">Verifiable
Credentials Data Model</a>.
</p>
<p>
This document is experimental and is undergoing development.
</p>
</section>
<section class="informative">
<h2>Introduction</h2>
<p>
TODO: introduction
</p>
</section>
<section id="conformance" class="normative">
</section>
<section class="informative">
<h2>Terminology</h2>
<div
data-include="./terms.html" data-oninclude="restrictReferences"></div>
</section>
<section class="informative">
<h2>Core Concepts</h2>
<p>
TODO: may not need this
</p>
</section>
<section class="informative">
<h2>User Roles</h2>
<p>
TODO: just point roles in VC use cases
</p>
</section>
<section>
<h2>User Needs</h2>
<p>TODO: included this from vc use cases as a template.</p>
<section>
<h3>Need 1</h3>
<p>
Details... Note that our table formatting results are different, but the following can be filled out to yield the desired grouping, and we can tweak the display later if we like.
</p>
<dl class="left dl-horizontal">
<dt>
<udef>E.1 Digital transcript (for example) </udef>
</dt>
<dd>
TODO: e.g. 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. Upon the request of her students, Joleen issues a digital credential that includes an extended transcript.
</dd>
</dl>
</section>
</section>
<section>
<h2>Focal Use Cases</h2>
<p>
Focal Use Cases are meant to provide examples where a blend of features from
<a>verifiable credentials</a> standard may be used together to solve complex
or challenging marketplace needs.
</p>
<section>
<h3>Focal Use Case 1</h3>
<h4>Background</h4>
<p>
Background of focal use case 1
</p>
<h4>Distinction</h4>
<p>
Distinction...
</p>
<h4>Scenario</h4>
<p>
Scenario...
</p>
<h4>Verifiable Credentials</h4>
<dl class="dl-horizontal">
<dt>
Credential type...
</dt>
<dd>
What it does...
</dd>
</dl>
<h4>Verifiable Presentation</h4>
<p>
A <a>verifiable presentation</a> which includes ...along with the assertions that —
</p>
<ul>
<li>
assertion 1
</li>
<li>
assertion 2
</li>
</ul>
<h4>Trust Hierarchy</h4>
<p>
TODO: trust hierarchty
</p>
<h4>Threat model</h4>
<ul>
<li>
<strong>Threat: the threat</strong> description of the threat
<ul>
<li>
<strong>Response:</strong> response 1
</li>
</ul>
</li>
</ul>
</section>
</section>
<section class="informative">
<h2>Security Considerations</h2>
<p>
There are a number of security considerations that implementers should be
aware of when processing data described by this specification. Ignoring or
not understanding the implications of this section can result in
security vulnerabilities.
</p>
<p>
While this section attempts to highlight a broad set of security
considerations, it is not a complete list. Implementers are urged to seek the
advice of security and cryptography professionals when implementing mission
critical systems using the technology outlined in this specification.
</p>
<p class="issue">
Write security considerations.
</p>
</section>
<section class="informative">
<h2>Accessibility Considerations</h2>
<p>
There are a number of accessibility considerations implementers should be
aware of when processing data described in this specification. As with any web
standards or protocols implementation, ignoring accessibility issues makes
this information unusable to a large subset of the population. It is important
to follow accessibility guidelines and standards, such as [[WCAG21]], to ensure
all people, regardless of ability, can make use of this data. This is
especially important when establishing systems utilizing cryptography, which
have historically created problems for assistive technologies.
</p>
<p>
This section details the general accessibility considerations to take into
account when utilizing this data model.
</p>
<p class="issue">
Write accessibility considerations.
</p>
</section>
<section class="informative">
<h2>Internationalization Considerations</h2>
<p>
There are a number of internationalization considerations implementers should be
aware of when publishing data described in this specification. As with any web
standards or protocols implementation, ignoring internationalization makes it
difficult for data to be produced and consumed across a disparate set of
languages and societies, which would limit the applicability of the
specification and significantly diminish its value as a standard.
</p>
<p>
This section outlines general internationalization considerations to take into
account when utilizing this data model.
</p>
<p class="issue">
Write i18n considerations.
</p>
</section>
</body>
</html>