-
Notifications
You must be signed in to change notification settings - Fork 6
/
Copy pathindex.html
677 lines (597 loc) · 30.8 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
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8">
<title>Decentralized Identifier Working Group Charter</title>
<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/OldGuide/pubrules-style.css">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css">
<style>
main {
max-width: 60em;
margin: 0 auto;
}
ul#navbar {
font-size: small;
}
dt.spec {
font-weight: bold;
}
dt.spec new {
background: yellow;
}
ul.out-of-scope > li {
font-weight: bold;
}
ul.out-of-scope > li > ul > li{
font-weight: normal;
}
.issue {
background: cornsilk;
font-style: italic;
}
.todo {
color: #900;
}
footer {
font-size: small;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li><a href="#background">Background</a></li>
<li><a href="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</a></li>
<li><a href="#success-criteria">Success Criteria</a></li>
<li><a href="#coordination">Coordination</a></li>
<li><a href="#participation">Participation</a></li>
<li><a href="#communication">Communication</a></li>
<li><a href="#decisions">Decision Policy</a></li>
<li><a href="#patentpolicy">Patent Policy</a></li>
<li><a href="#licensing">Licensing</a></li>
<li><a href="#about">About this Charter</a></li>
</ul>
</aside>
<p>
<a href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72"></a>
</p>
</header>
<main>
<h1 id="title">Decentralized Identifier Working Group Charter</h1>
<p class="mission">
The <strong>mission</strong> of the
<a href="https://www.w3.org/groups/wg/did/">Decentralized Identifier Working Group</a>
is two-fold. First, it will maintain the <a href="https://www.w3.org/TR/did-core/">Decentralized Identifiers (DIDs)</a>
specification and related Working Group Notes.
Second, it will seek consensus around the best way to achieve effective interoperability through common requirements, algorithms, architectural options, and various considerations for the DID resolution and DID URL dereferencing processes.
</p>
<div class="noprint">
<p class="join"><a href="https://www.w3.org/groups/wg/did/join">Join the Decentralized Identifier Working Group.</a></p>
</div>
<!--
<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
on <a href="https://github.com/w3c/charter-drafts/">GitHub</a>.
Feel free to raise <a href="https://github.com/w3c/charter-drafts/issues">issues</a>.
</p>
-->
<section id="details">
<table class="summary-table">
<tr id="Duration">
<th>
Start date
</th>
<td>
25 April 2024
</td>
</tr>
<tr id="CharterEnd">
<th>
End date
</th>
<td>
28 April 2026
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
Will Abramson (Digital Contract Design), Daniel Burnett (Invited Expert), Gabe Cohen (Block, Inc)
</td>
</tr>
<tr>
<th>
Team Contact
</th>
<td>
Pierre-Antoine Champin (0.1 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> On an as-needed basis, up to once every week.
<br>
<strong>Face-to-face:</strong> We may meet during TPAC.
</td>
</tr>
</table>
</section>
<section id="background" class="background">
<h2>Motivation and Background</h2>
<p>
The Working Group will maintain the <a href="https://www.w3.org/TR/did-core/">DID</a>
specification, which defines a new type of identifier that enables verifiable,
decentralized digital identity. This includes possible
<a href="https://www.w3.org/Consortium/Process/#correction-classes">class 1, 2, or 3 </a>
level changes on the Recommendation.
</p>
<p>
The Working Group will also take over the work started by the Credentials Community Group around <a href="https://w3c-ccg.github.io/did-resolution/">DID Resolution</a>, to define common requirements, algorithms including their inputs and results, architectural options, and various considerations for the DID resolution and DID URL dereferencing processes.
</p>
<p>
It is expected that these two goals will be taken by distinct task forces in the WG.
</p>
<p>
The Working Group must pursue consensus in any task pursued under the name of the working group--whether by Chairs, Editors, or other contributors--including any Notes for publication by the WG and any Charters for a future DID WG.
</p>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>Beyond the maintenance of the <a href="https://www.w3.org/TR/did-core/">Decentralized Identifiers (DIDs) v1.0</a> specification, the following, non-normative Working Group Notes will also be maintained by the Working Group:</p>
<ul>
<li>
<a href="https://www.w3.org/TR/did-spec-registries/">DID Specification Registries</a>, including transitioning it from a WG Note to a <a href="https://www.w3.org/Consortium/Process/#registries">W3C Registry</a>.
</li>
<li>
<a href="https://www.w3.org/TR/did-rubric/">DID Method Rubric</a>, including transitioning it from a WG Note to a <a href="https://www.w3.org/Consortium/Process/#registries">W3C Registry</a>.
</li>
<li>
<a href="https://www.w3.org/TR/did-cbor-representation/">The Plain CBOR representation</a>.
</li>
<li>
<a href="https://www.w3.org/TR/did-imp-guide/">DID Implementation Guide v1.0</a>.
</li>
</ul>
<p>
The Working Group may also publish new Working Group Notes.
Any additional notes beyond those explicitly listed in the deliverable section will not include DID Method specifications and will not address issues regarding any particular DID Methods. The WG welcomes DID Method standardization outside the WG (whether in the W3C or in other standards bodies).
</p>
<section id="section-out-of-scope">
<h3 id="out-of-scope">Out of Scope</h3>
<p>The following features are out of scope, and will not be addressed by this Working group.</p>
<ul>
<li>
<a href="https://www.w3.org/Consortium/Process/#correction-classes">Class 4</a> level changes on the <a href="https://www.w3.org/TR/did-core/">DID</a> specification.
</li>
<li>
Authentication or Authorization Protocols
</li>
<li>
Browser APIs
</li>
<li>
"Solving Identity" on the Web
</li>
</ul>
</section>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p>Updated document status is available on the <a href="https://www.w3.org/groups/wg/did/publications">group publication status page</a>.</p>
<section id="normative">
<h3>
Normative Specifications
</h3>
<p>
The Working Group will maintain the following W3C normative specification:
</p>
<dl id="deliverable-did-core">
<dt class="spec"><a href="https://www.w3.org/TR/did-core/">Decentralized Identifiers (DIDs) v1.0</a></dt>
<dd>
<p>This specification defines new type of identifier that enables verifiable, decentralized digital identity.
</p><p class="draft-status">
<b>Draft State</b>: Recommendation
</p><p class="milestone">
<b>Expected completion</b>: not applicable (maintenance)
</p><p>
<b>Adpoted Draft</b>: Decentralized Identifiers (DIDs) v1.0, <a href="https://www.w3.org/TR/2022/REC-did-core-20220719/">https://www.w3.org/TR/2022/REC-did-core-20220719/</a>, published 2022-07-19
</p><p>
<b>Exclusion Draft</b>: Decentralized Identifiers (DIDs) v1.0, <a href="https://www.w3.org/TR/2021/CR-did-core-20210615/">https://www.w3.org/TR/2021/CR-did-core-20210615/</a>, published 2021-06-15. Exclusion period <b>began</b> 2021-06-15, <b>ended</b> 2021-08-14.
</p><p>
<b>Exclusion Draft Charter</b>: <a href="https://www.w3.org/2020/12/did-wg-charter.html">https://www.w3.org/2020/12/did-wg-charter.html</a>.
</p>
</dd>
</dl>
<dl id="deliverable-did-resolution">
<dt class="spec">Decentralized Identifier (DID) Resolution and DID URL Dereferencing v1.0</dt>
<dd>
<p>
This document specifies the algorithms and guidelines for resolving DIDs and dereferencing DID URLs.
</p>
<p class="draft-status">
<b>Draft State:</b> Draft Community Group Report
</p>
<p class="milestone"><b>Expected completion:</b>
28 April 2026
</p>
<p><b>Adopted Draft:</b>
DID Resolution v0.3, <a href="https://w3c-ccg.github.io/did-resolution/">https://w3c-ccg.github.io/did-resolution/</a>, published 2023-01-18, may serve as a starting point.
</p>
</dd>
</dl>
</section>
<section id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<dl>
<dt class="spec"><a href="https://www.w3.org/TR/did-spec-registries/">DID Specification Registries</a></dt>
<dd>
<p>
Status: Group Note
<br>
Last update: 2021-11-02
</p>
<p>
The Working Group Note will be transitioned to a <a href="https://www.w3.org/Consortium/Process/#registries">W3C Registry</a>.
</p>
</dd>
<dt class="spec"><a href="https://www.w3.org/TR/did-rubric/">DID Method Rubric</a></dt>
<dd>
<p>
Status: Group Note
<br>
Last update: 2021-11-19
</p>
<p>
The Working Group Note will be transitioned to a <a href="https://www.w3.org/Consortium/Process/#registries">W3C Registry</a>.
</p>
</dd>
<dt class="spec"><a href="https://www.w3.org/TR/did-cbor-representation/">The Plain CBOR representation</a></dt>
<dd>
<p>
Status: Group Note
<br>
Last update: 2021-06-26
</p>
</dd>
<dt class="spec"><a href="https://www.w3.org/TR/did-imp-guide/">DID Implementation Guide v1.0</a></dt>
<dd>
<p>
Status: Group Note
<br>
Last update: 2021-10-12
</p>
</dd>
</dl>
</section>
</section>
<section id="success-criteria">
<h2>Success Criteria</h2>
<!-- Testing and interop -->
<p>In order to advance to
<a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a> or to <a href="https://www.w3.org/Consortium/Process/#change-review">incorporate candidate amendments</a>, each normative specification is expected to have
<a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent interoperable
implementations</a> of every feature defined in the specification, where
interoperability can be verified by passing open test suites, and two or
more implementations interoperating with each other. In order to advance to
Proposed Recommendation, each normative specification must have an open
test suite of every feature defined in the specification.</p>
<p>In order for <a href="#deliverable-did-resolution">DID Resolution</a> to advance to <a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, it is expected that each of the independent implementations mentioned above support at least two DID methods which 1) have an open specifications
(freely available specification, freely implementable),
and 2) are implemented interoperably by more than one
of the independent implementations mentioned above.
This means that there will exist at least two openly-specified DID methods that are each implemented by at least two independent implementations.
</p>
<p>There should be testing plans for each specification, starting from the earliest drafts.</p>
<p>To promote interoperability, all changes made to specifications
in Candidate Recommendation
or to features that have deployed implementations
should have <a href='https://www.w3.org/2019/02/testing-policy.html'>tests</a>.
</p>
<!-- Horizontal review -->
<p>Each specification should contain sections detailing
security and privacy implications for implementers,
Web authors, and end users,
as well as recommendations for mitigations.
There should be a clear description of the residual risk
to the user or operator of that protocol
after threat mitigation has been deployed.</p>
<!-- Design principles -->
<p>This Working Group expects to follow the
TAG <a href="https://www.w3.org/TR/design-principles/">Web Platform Design Principles</a>.
</p>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">horizontal review</a> for
accessibility, internationalization, performance, privacy, and security with the relevant Working and
Interest Groups, and with the <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>.
Invitation for review must be issued during each major standards-track document transition, including
<a href="https://www.w3.org/Consortium/Process/#RecsWD" title="First Public Working Draft">FPWD</a>. The
Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of
each specification. The Working Group is advised to seek a review at least 3 months before first entering
<a href="https://www.w3.org/Consortium/Process/#RecsCR" title="Candidate Recommendation">CR</a> and is encouraged
to proactively notify the horizontal review groups when major changes occur in a specification following a review.</p>
<p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/Consortium/Process/#WGCharter">W3C Process Document</a>:</p>
<section>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt>
<a href="https://www.w3.org/2017/vc/WG/">Verifiable Credentials Working Group</a>
</dt>
<dd>
Coordination on the use of Decentralized Identifiers in Verifiable Credential ecosystems.
</dd>
<dt>
<a href="https://www.w3.org/blog/webauthn/">Web Authentication Working Group</a>
</dt>
<dd>
Coordination to ensure that Web Authentication primitives, such as public keys, can be expressed in DID Documents.
</dd>
<dt>
<a href="https://w3c-ccg.github.io/">Credentials Community Group</a>
</dt>
<dd>
Coordination on the use of Decentralized Identifiers in various ecosystems including Linked Data Integrity and Encrypted Data Vaults.
</dd>
<dt>
<a href="https://www.w3.org/groups/wg/apa">Accessible Platform Architectures Working Group</a>
</dt>
<dd>
Coordination on the use of Decentralized Identifiers in helping to enable greater accessibility on the web.
</dd>
</dl>
</section>
<section>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt>
<a href="https://datatracker.ietf.org/group/secdir/about/">IETF Security Area Directorate</a>
</dt>
<dd>
Coordination with IETF regarding the management of security reviews on the DID specification.
</dd>
<dt>
<a href="https://irtf.org/cfrg">IRTF Crypto Forum Research Group</a>
</dt>
<dd>
Discussion, analysis, and review of the cryptographic aspects of the DID specification.
</dd>
<dt>
<a href="https://github.com/decentralized-identity/identifiers-discovery/">DIF Identifiers & Discovery Working Group</a>
</dt>
<dd>
Coordination with DIF regarding various open-source implementations of DIDs as well as additional specification work.
</dd>
</dl>
</section>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
To be successful, this Working Group is expected to have 6 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a working day per week towards the Working Group. There is no minimum requirement for other Participants.
</p>
<p>
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href='#communication'>Communication</a>.
</p>
<p>
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a>.
</p>
<p>Participants in the group are required (by the <a href="https://www.w3.org/Consortium/Process/#ParticipationCriteria">W3C Process</a>) to follow the
W3C <a href="https://www.w3.org/Consortium/cepc/">Code of Ethics and Professional Conduct</a>.</p>
</section>
<section id="communication">
<h2>
Communication
</h2>
<p id="public">
Technical discussions for this Working Group are conducted in <a href="https://www.w3.org/Consortium/Process/#confidentiality-levels">public</a>: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests.
The meetings themselves are not open to public participation, however.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="">Decentralized Identifier Working Group home page.</a>
</p>
<p>
Most Decentralized Identifier Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
</p>
<p>
This group primarily conducts its technical work on the public mailing list <a id="public-name" href="mailto:[email protected]">[email protected]</a> ( <a href="https://lists.w3.org/Archives/Public/public-did-wg/">archive</a>) or on <a id="public-github" href="https://github.com/w3c/did-wg/">GitHub issues</a> (and specification-specific GitHub repositories and issue trackers). The public is invited to review, discuss and contribute to this work.
</p>
<p>
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
</p>
</section>
<section id="decisions">
<h2>
Decision Policy
</h2>
<p>
This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/Consortium/Process/#Consensus"> W3C Process Document (section 5.2.1, Consensus</a>). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.</p>
<p>
However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections.
</p>
<p>
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional.
A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from <span id='cfc'>one week to 10 working days</span>, depending on the chair's evaluation of the group consensus on the issue.
If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.
</p>
<p>
All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs or the Director.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/#Votes">W3C Process Document (Section 5.2.3, Deciding by Vote)</a> and includes no voting procedures beyond what the Process Document requires.
</p>
</section>
<section id="patentpolicy">
<h2>
Patent Policy
</h2>
<p>
This Working Group operates under the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a> (Version of 15 September 2020). To promote the widest adoption of Web standards, W3C seeks to issue Web specifications that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the <a href="https://www.w3.org/groups/wg/did/ipr">licensing information</a>.
</p>
</section>
<section id="licensing">
<h2>Licensing</h2>
<p>This Working Group will use the <a href="https://www.w3.org/Consortium/Legal/copyright-software">W3C Software and Document license</a> for all its deliverables.</p>
</section>
<section id="about">
<h2>
About this Charter
</h2>
<p>
This charter has been created according to <a href="https://www.w3.org/Consortium/Process/#GAGeneral">section 3.4</a> of the <a href="https://www.w3.org/Consortium/Process/">Process Document</a>. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
</p>
<section id="history">
<h3>
Charter History
</h3>
<p>The following table lists details of all changes from the initial charter, per the <a href="https://www.w3.org/Consortium/Process/#CharterReview">W3C Process Document (section 4.3, Advisory Committee Review of a Charter)</a>:</p>
<table class="history">
<tbody>
<tr>
<th> Charter Period </th>
<th> Start Date </th>
<th> End Date </th>
<th> Changes </th>
</tr>
<tr>
<th> <a href="https://www.w3.org/2019/08/did-wg-charter.html">Initial Charter</a> </th>
<td> <i>September 2019</i> </td>
<td> <i>September 2021</i> </td>
<td> <i>none</i> </td>
</tr>
<tr>
<th> <a href="https://www.w3.org/2019/08/did-wg-charter.html">Update</a> </th>
<td></td>
<td></td>
<td> <i>Changed an erroneous link to the <a href="https://www.w3.org/2019/did-wg/PublStatus">publication status page</a> (Ivan Herman, 2020-01-24)</i> </td>
</tr>
<tr>
<th> <a href="https://www.w3.org/2019/08/did-wg-charter.html">Update</a></th>
<td> </td>
<td></td>
<td> <i><a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2020JulSep/0013.html">Daniel Burnett re-appointed as group co-Chair</a> (Xueyuan Jia, 2020-07-24)</i> </td>
</tr>
<tr>
<th><a href="https://www.w3.org/2020/12/did-wg-charter.html">Rechartered</a></th>
<td>15 December 2020</td>
<td>September 2021</td>
<td>New Patent Policy</td>
</tr>
<tr>
<th> <a href="https://www.w3.org/2020/12/did-wg-charter.html">Update</a> </th>
<td></td>
<td></td>
<td> FTE value update for staff contact: 0.2 reduced to 0.15 (2021-06)</td>
</tr>
<tr>
<th> <a href="https://www.w3.org/2020/12/did-wg-charter.html">Extension</a> </th>
<td>1 October 2021</td>
<td>31 December 2021</td>
<td>none</td>
</tr>
<tr>
<th> <a href="https://www.w3.org/2020/12/did-wg-charter.html">Extension</a> </th>
<td>31 December 2021</td>
<td>30 June 2022</td>
<td>none</td>
</tr>
<tr>
<th> <a href="https://www.w3.org/2020/12/did-wg-charter.html">Update</a> </th>
<td></td>
<td></td>
<td>Added Pierre-Antoine Champin as staff contact <em>(Ivan Herman, 2022-01-12)</em></td>
</tr>
<tr>
<th> <a href="https://www.w3.org/2020/12/did-wg-charter.html">Extension</a> </th>
<td>30 June 2022</td>
<td>31 December 2022</td>
<td>none</td>
</tr>
<tr>
<th> <a href="https://www.w3.org/2020/12/did-wg-charter.html">Update</a> </th>
<td></td>
<td></td>
<td>(1) Brent Zundel's affiliation changed to Avast; (2) Ivan Herman is no longer staff contact <em>(Ivan Herman, 2022-07-19)</em></td>
</tr>
<tr>
<th><a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2022OctDec/0040.html">Extension</a></th>
<td>15 December 2022</td>
<td>31 March 2023</td>
<td>none</td>
</tr>
<tr>
<th><a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2023JanMar/0048.html">Extension</a></th>
<td>30 March 2023</td>
<td>31 May 2023</td>
<td>none</td>
</tr>
<tr>
<th><a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2023JulSep/0016.html">Extension</a></th>
<td>31 May 2023</td>
<td>30 September 2023</td>
<td>none</td>
</tr>
<tr>
<th><a href="https://www.w3.org/2024/04/did-wg-charter.html">Rechartered</a></th>
<td>25 April 2024</td>
<td>28 April 2026</td>
<td>Adopt DID Resolution as a new REC track deliverable.</td>
</tr>
<tr>
<th> <a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2024AprJun/0051.html">Update</a> </th>
<td></td>
<td></td>
<td>New co-chair Will Abramson <em>(Pierre-Antoine Champin, 2024-06-21)</em></td>
</tr>
<tr>
<th>Update</th>
<td></td>
<td></td>
<td>The group's homepage now lives at <a href="https://www.w3.org/groups/wg/did/">https://www.w3.org/groups/wg/did/</a>. Relevant links updated. <em>(Pierre-Antoine Champin, 2024-09-09)</em></td>
</tr>
</tbody>
</table>
</section>
<!--
<section id="changelog">
<h3>Change log</h3>
--><!-- Use this section for changes _after_ the charter was approved by the Director. --><!--
<p>Changes to this document are documented in this section.</p>
<dl id='changes'>
<dt>2023-08-17</dt>
<dd>The GitHub repository to receive comments was updated, reflecting <a href="https://github.com/w3c/strategy/issues/421">#421</a></dd>
</dl>
</section>
-->
</section>
</main>
<hr>
<footer>
<address>
<a href="mailto:[email protected]">Pierre-Antoine Champin</a>
</address>
<p class="copyright">Copyright © 2023 <a href="https://www.w3.org/">World Wide Web Consortium</a>.<br>
<abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup>
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
<a rel="license" href="https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document" title="W3C Software and Document Notice and License">permissive document license</a> rules apply.</p> <hr>
<!--
<p><a href="https://github.com/w3c/did-wg-charter">Yes, it's on GitHub!</a>.</p>
-->
</footer>
</body>
</html>