-
Notifications
You must be signed in to change notification settings - Fork 14
/
index.html
461 lines (394 loc) · 12.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
<!DOCTYPE html>
<html>
<head>
<title>Verifiable Credential Extensions</title>
<meta content='text/html; charset=utf-8' http-equiv='Content-Type'><!--
=== 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 class='remove' src='https://www.w3.org/Tools/respec/respec-w3c'></script>
<script class='remove' src='https://w3c.github.io/vc-extensions/common.js'></script>
<script class="remove" type="text/javascript">
var respecConfig = {
wgPublicList: "public-vc-wg",
group: "vc",
// specification status (e.g., WD, LCWD, NOTE, etc.). If in doubt use ED.
specStatus: "NOTE",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "vc-extensions",
edDraftURI: "https://w3c.github.io/vc-extensions/",
// subtitle
subtitle: "A list of extensions for Verifiable Credentials",
// if you wish the publication date to be other than today, set this
publishDate: "2024-09-17",
// 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
github: {
repoURL: "https://github.com/w3c/vc-extensions/",
branch: "main"
},
includePermalinks: false,
// editors, add as many as you like
// only "name" is required
editors: [{
name: "Manu Sporny",
url: "https://www.linkedin.com/in/manusporny/",
company: "Digital Bazaar",
companyURL: "https://www.digitalbazaar.com/",
w3cid: 41758
}],
// 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: "Manu Sporny",
url: "https://www.linkedin.com/in/manusporny/",
company: "Digital Bazaar",
companyURL: "https://www.digitalbazaar.com/",
w3cid: 41758
}],
otherLinks: [{
key: "Related Documents",
data: [{
value: "Verifiable Credentials Data Model",
href: "https://www.w3.org/TR/vc-data-model-2.0/"
}]
}],
postProcess: [window.buildSpecificationTables]
};
</script>
<style>
.label-legend dd{
margin-top: 8px;
}
.label-deprecated {
font-weight: bold;
background: #ef9a9a;
border-radius: 8px;
padding: 4px;
}
.label-no-contact-info {
font-weight: bold;
background: #ffe082;
border-radius: 8px;
padding: 4px;
}
pre .highlight {
font-weight: bold;
color: green;
}
pre .comment {
color: SteelBlue;
-webkit-user-select: none;
-moz-user-select: none;
-ms-user-select: none;
user-select: none;
}
</style>
</head>
<body>
<section id='abstract'>
<p>
This document serves as an unofficial list of all known Verifiable Credential
specifications whether they are released by a global standards setting
organization, a community group, an open source project, or an individual.
</p>
</section>
<section id='sotd'>
<p>
This document is not a formal registry nor is it intended to become a
<a href="https://www.w3.org/2023/Process-20231103/#registries">
Registry Track</a> document per the W3C Process.
</p>
<p>
Comments regarding this document are welcome. Please file issues
directly on
<a href="https://github.com/w3c/vc-extensions/issues/">GitHub</a>,
or send them
to <a href="mailto:public-vc-wg@w3.org">public-vc-wg@w3.org</a> (
<a href="mailto:public-vc-wg-request@w3.org?subject=subscribe">subscribe</a>,
<a href="https://lists.w3.org/Archives/Public/public-vc-wg/">archives</a>).
</p>
</section>
<section class="informative">
<h1>Introduction</h1>
<p>
This document serves as an unofficial directory for all known Verifiable
Credential specifications whether they are released by a global standards
setting organization, a community group, an open source project, or an
individual.
</p>
<section>
<h1>Adding a Specification Entry</h1>
<p>
The Verifiable Credentials Data Model is designed to be extended by 3rd party
specifications to address a variety of real world use cases. Examples of
extensions include, but are not limited to, new types of Verifiable Credentials
and ways of expressing credential status, schema validation, evidence,
refreshing, terms of use, and cryptographic suites for securing credentials.
</p>
<p> In
order to add a new specification to this directory, an implementer submits a
modification request for this directory, as a pull request on the repository
where this directory is hosted.
</p>
Here is an example:
<p>
<pre class="example">
{
"name": "Example VC",
"summary": "Used to demonstrate examples for Verifiable Credentials.",
"specification": "https://example.github.io/example-spec/",
"category": "vc",
"maintainerEmail": "maintainer@community.example",
"maintainerName": "Example Community Group",
"maintainerWebsite": "https://example.github.io/",
"vocabulary": ["https://example.github.io/vocabularies/example.yml"]
}
</pre>
</p>
<p>
The modification request MUST adhere to the following policies:
</p>
<ol>
<li>
Any addition to the directory MUST conform to Section
<a href="#specification-entry-format"></a>.
</li>
<li>
If there are copyright, trademark, or any intellectual property rights
concerns, the addition and use MUST be authorized in writing by the intellectual
property rights holder under a
<a href="https://en.wikipedia.org/wiki/Reasonable_and_non-discriminatory_licensing">F/RAND</a>
license. Examples include specifications that use trademarked brand names,
property names that utilize the titles of copyrighted works, and patented
technology that would cause the use of the extension to require licensing a
patent.
</li>
<li>
Any addition MUST NOT create unreasonable legal, security, moral, or privacy
issues that will result in direct harm to others. Examples of unacceptable
additions include any containing racist language, technologies used to
persecute minority populations, and unconsented pervasive tracking.
</li>
</ol>
<p>
The Editors of this directory MUST consider all of the policies above when
reviewing additions to the directory and MUST reject directory entries if they
violate any of the policies in this section. Entities registering additions can
challenge rejections first with the W3C Verifiable Credentials Working Group and
then, if they are not satisfied with the outcome, with the W3C Staff. W3C Staff
need not be consulted on changes to the directory, but do have the final
authority on directory contents. This is to ensure that W3C can adequately
respond to time sensitive legal, privacy, security, moral, or other pressing
concerns without putting an undue operational burden on W3C Staff.
</p>
<p>
Any submission to the directory that meets all of the criteria listed above will
be accepted for inclusion. The specifications listed in this directory enumerate
all known specifications, without choosing between them.
</p>
<section>
<h1>Specification Entry Format</h1>
<p>
The specification entry format MUST conform to the
<a href="https://w3c.github.io/vc-extensions/tooling/specification-entry.yml">
JSON Schema for a specification entry</a>. Each field is documented below:
</p>
<table class="simple">
<thead>
<th>Field</th>
<th>Description</th>
</thead>
<tbody>
<tr>
<td>name</td>
<td>
A short human readable name for the specification. For example: `Status List
(v2021)`.
</td>
</tr>
<tr>
<td>summary</td>
<td>
A one sentence description for the specification. For example: `A credential
status list with herd privacy characteristics.`
</td>
</tr>
<tr>
<td>specification</td>
<td>
An URL that resolves to a human readable specification. For example:
`https://w3c.github.io/vc-status-list-2021/`.
</td>
</tr>
<tr>
<td>category</td>
<td>
The Verifiable Credential extension category of the specification, which can be
one of the following values: `credentialStatus`, `credentialSchema`, `evidence`,
`media-type`, `multibase`, `multihash`, `multikey`, `securing`,
`refreshService`, `termsOfUse`, or `vc`. For example: `credentialStatus`.
<p class="note">
The extensions might define a `@type`. See [[JSON-LD11]].
</p>
</td>
</tr>
<tr>
<td>maintainerName</td>
<td>
A person or organization which responds to contact requests. For example:
`W3C Verifiable Credentials Working Group`.
</td>
</tr>
<tr>
<td>maintainerEmail</td>
<td>
An email to send contact requests. For example:
`public-vc-wg@w3.org`.
</td>
</tr>
<tr>
<td>maintainerWebsite</td>
<td>
An website to send contact requests. For example:
`https://www.w3.org/groups/wg/vc`.
</td>
</tr>
<tr>
<td>vocabulary</td>
<td>
An array of URLs that contain machine-readable vocabulary information in
yml2vocab or JSON-LD format. For example:
`["https://raw.githubusercontent.com/w3c/vc-status-list-2021/main/contexts/v1.jsonld"]`.
</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="conformance"></section>
</section>
<section>
<h1>Property-based Extensions</h1>
<section>
<h1>Credential Status</h1>
<table class="simple">
<thead>
<th>Specification</th><th>Description</th>
</thead>
<tbody id="credentialStatus-table">
</tbody>
</table>
</section>
<section>
<h1>Credential Schema</h1>
<table class="simple">
<thead>
<th>Specification</th><th>Description</th>
</thead>
<tbody id="credentialSchema-table">
</tbody>
</table>
</section>
<section>
<h1>Evidence</h1>
<table class="simple">
<thead>
<th>Specification</th><th>Description</th>
</thead>
<tbody id="evidence-table">
</tbody>
</table>
</section>
<section>
<h1>Proof</h1>
See Section <a href="#securing-mechanisms"></a>.
</section>
<section>
<h1>Refresh Service</h1>
<table class="simple">
<thead>
<th>Specification</th><th>Description</th>
</thead>
<tbody id="refreshService-table">
</tbody>
</table>
</section>
<section>
<h1>Terms of Use</h1>
<table class="simple">
<thead>
<th>Specification</th><th>Description</th>
</thead>
<tbody id="termsOfUse-table">
</tbody>
</table>
</section>
</section>
<section>
<h1>Type-based Extensions</h1>
<table class="simple">
<thead>
<th>Specification</th><th>Description</th>
</thead>
<tbody id="vc-table">
</tbody>
</table>
</section>
<section>
<h1>Multibase</h1>
<table class="simple">
<thead>
<th>Specification</th><th>Description</th>
</thead>
<tbody id="multibase-table">
</tbody>
</table>
</section>
<section>
<h1>Multihash</h1>
<table class="simple">
<thead>
<th>Specification</th><th>Description</th>
</thead>
<tbody id="multihash-table">
</tbody>
</table>
</section>
<section>
<h1>Multikey</h1>
<table class="simple">
<thead>
<th>Specification</th><th>Description</th>
</thead>
<tbody id="multikey-table">
</tbody>
</table>
</section>
<section>
<h1>Securing Mechanisms</h1>
<table class="simple">
<thead>
<th>Specification</th><th>Description</th>
</thead>
<tbody id="securing-table">
</tbody>
</table>
</section>
<section>
<h1>Media Type Extensions</h1>
<table class="simple">
<thead>
<th>Specification</th><th>Description</th>
</thead>
<tbody id="media-type-table">
</tbody>
</table>
</section>
</body>
</html>