-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathindex.html
679 lines (602 loc) · 23.9 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
678
679
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8">
<title>PROPOSED DID Methods 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">PROPOSED DID Methods Working Group Charter</h1>
<!-- delete PROPOSED after AC review completed -->
<p class="mission">
The <strong>mission</strong> of the DID Methods Working Group is to
standardize DID Methods that use Web technologies.
</p>
<!-- the link to the group is ALWAYS that available from https://www.w3.org/groups/wg or https://www.w3.org/groups/ig because each group page can then point to a different homepage, but not the other way around. -->
<div class="noprint">
<p class="join">
<a href="https://www.w3.org/groups/wg/dm/join/">Join the DID Methods Working
Group</a>
</p>
</div>
<!-- delete the GH link after AC review completed -->
<p style="padding: 0.5ex; border: 1px solid green">
This proposed charter is available on
<a href="https://github.com/msporny/w3c-dmwg">GitHub</a>. Feel free to raise
<a href="https://github.com/msporny/w3c-dmwg/issues">issues</a></i>.
</p>
<div id="details">
<table class="summary-table">
<tr id="Status">
<th>
Charter Status
</th>
<td>
See the <a href="https://www.w3.org/groups/wg/dmwg/charters/">group
status page</A> and <a href="#history">detailed change history</a>.</i>
</td>
</tr>
<tr id="Duration">
<th>
Start date
</th>
<td>
01 June 2025
</td>
</tr>
<tr id="CharterEnd">
<th>
End date
</th>
<td>
01 June 2027
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
<i class="todo">[chair name] (affiliation)</i>
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<span class="todo"><a href="mailto:">[team contact name]</a></span> <i class="todo">(0.1 <abbr title="Full-Time Equivalent">FTE</abbr>)</i>
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> weekly
<br>
<strong>Face-to-face:</strong> we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year.
</td>
</tr>
</table>
</div>
<div id="background" class="background">
<h2>Motivation and Background</h2>
<p>
A <a href="https://www.w3.org/TR/did-core/#methods">DID Method specification</a>
defines the precise operations by which
<a href="https://www.w3.org/TR/did-core/#abstract">Decentralized Identifiers</a>
(DIDs) and
<a href="https://www.w3.org/TR/did-core/#core-properties">DID documents</a> are
created, resolved, updated, and deactivated. Since the publication of the
<a href="https://www.w3.org/TR/2022/REC-did-core-20220719/">DID Core v1.0
specification</a>, many DID Methods have been created and deployed.
As national governments and large corporations continue to adopt this
technology, it is beneficial for those organizations to have standardized,
production-grade DID Methods to deploy. While DID Methods can be standardized
in any standards-development organization, there are a few that utilize the
architecture of the Web, and Web technologies, and would benefit
standardization at W3C.
</p>
</div>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>
The scope of the initial DID Methods Working Group will be to standardize at
least one ephemeral DID Method, one Web-based DID Method, and one fully
decentralized DID Method based on Web technologies.
</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 class="out-of-scope">
<li>
Non-Web-based DID Methods such as Blockchain-based DID Methods.
</li>
</ul>
</section>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p><i class="todo">Updated document status is available on the <a href="https://www.w3.org/groups/wg/dm/publications/">group publication status page</a>.</i></p>
<p>
<i>Draft state</i> indicates the state of the deliverable at the time of the
charter approval. <i>Expected completion</i> indicates when the deliverable is
projected to become a Recommendation, or otherwise reach a stable state.
</span>.
</p>
<section id="normative">
<h3>
Normative Specifications
</h3>
<p>
The Working Group will deliver the following W3C normative specifications:
</p>
<dl>
<dt id="ephemeral-did-method" class="spec">
An Ephemeral DID Method
</dt>
<dd>
<p>
This specification defines a mechanism to create and manage ephemeral DID
Documents, such as those based on public cryptographic key information.
</p>
<p class="draft-status">
<b>Draft specifications:</b>
<a href="https://github.com/decentralized-identity/did-methods/blob/main/method-proposals/PROPOSAL-did-key.md">did:key</a>
</p>
<p class="milestone">
<b>Expected completion:</b> Q3 2026
</p>
</dd>
<dt id="web-did-method" class="spec">
A Web-based DID Method
</dt>
<dd>
<p>
This specification defines a mechanism to create and manage DID Documents using
websites.
</p>
<p class="draft-status">
<b>Draft specifications:</b> Inputs to the Working Group include:
<a href="https://github.com/decentralized-identity/did-methods/blob/main/method-proposals/PROPOSAL-did-web.md">did:web</a>,
<a href="https://github.com/decentralized-identity/did-methods/blob/main/method-proposals/PROPOSAL-did-webplus.md">did:webplus</a>,
<a href="https://github.com/decentralized-identity/did-methods/blob/main/method-proposals/PROPOSAL-did-webs.md">did:webs</a>,
<a href="https://github.com/decentralized-identity/did-methods/blob/main/method-proposals/PROPOSAL-did-webvh.md">did:webvh</a>, and
<a href="https://github.com/decentralized-identity/did-methods/blob/main/method-proposals/PROPOSAL-did-webvh.md">did:scid</a>
</p>
<p class="milestone">
<b>Expected completion:</b> Q3 2026
</p>
</dd>
<dt id="full-did-method" class="spec">
An Fully Decentralized DID Method
</dt>
<dd>
<p>
This specification defines a mechanism to create and manage the full
lifecycle for DID Documents using Web technology but without any sort of
required centralization.
</p>
<p class="draft-status">
<b>Draft specifications:</b> Inputs to the Working Group include:
<a href="https://github.com/decentralized-identity/did-methods/blob/main/method-proposals/PROPOSAL-did-webvh.md">did:webvh</a> (without domain binding),
<a href="https://github.com/decentralized-identity/did-methods/blob/main/method-proposals/PROPOSAL-did-peer.md">did:peer</a>,
<a href="https://github.com/decentralized-identity/did-methods/blob/main/method-proposals/PROPOSAL-did-scid.md">did:scid</a>, or
a DID Method using a <a href="https://docs.google.com/presentation/d/1PKmycxKKww3FoAu-X19Pep--Z_vWZEbyjb19OcW0bSA/edit">cryptographic event log</a> of some kind.
</p>
<p class="milestone">
<b>Expected completion:</b> Q1 2027
</p>
</dd>
</dl>
</section>
<section id="incubation">
<!-- If no incubation or not a Working Group, delete the section. -->
<h3>
Tentative Deliverables
</h3>
<p>
None.
</p>
</section>
<section id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
Other non-normative documents may be created such as:
</p>
<ul>
<li>Use case and requirement documents;</li>
<li>Test suite and implementation report for the specification;</li>
<li>Primer or Best Practice documents to support web developers when designing applications.</li>
</ul>
</section>
<section id="timeline">
<h3>Timeline</h3>
<ul>
<li>Month 1: First teleconference.</li>
<li>Month 3: FPWD for all Normative Deliverables.</li>
<li>Month 9: First face-to-face meeting.</li>
<li>Month 12: Candidate Recommendation for all Normative Deliverables.</li>
<li>Month 15: Proposed Recommendation for all Normative Deliverables.</li>
<li>Month 20: Proposed Recommendation for all Normative Deliverables.</li>
</ul>
</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/policies/process/#RecsPR" title="Proposed
Recommendation">Proposed Recommendation</a>, each normative specification is
expected to have
<a href="https://www.w3.org/policies/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.
</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> through the
Working Group managed test suite.
</p>
<!-- Horizontal review -->
<p>
Each specification should contain sections detailing all known security and
privacy implications for implementers, Web authors, and end users.
</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, privacy, and
security with the relevant Working and Interest Groups, and with the
<a href="https://www.w3.org/groups/other/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/policies/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/policies/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/policies/process/#WGCharter">W3C Process Document</a>:</p>
<section>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt>
<a href="https://www.w3.org/2019/did-wg/">
Decentralized Identifier Working Group</a>
</dt>
<dd>
To ensure alignment with the DID Core, DID Resolution, and other relevant
Working Group specifications.
</dd>
<dt>
<a href="https://www.w3.org/2017/vc/WG/">
Verifiable Credential Working Group</a>
</dt>
<dd>
To ensure alignment with the Verifiable Credential, Data Integrity, and
other relevant Working Group specifications.
</dd>
<dt>
<a href="https://www.w3.org/community/credentials/">
Credentials Community Group</a>
</dt>
<dd>
To ensure alignment with emerging technologies and features being incubated.
</dd>
</dl>
</section>
<section>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt>
<a href="https://identity.foundation/">
Decentralized Identity Foundation</a>
</dt>
<dd>
To ensure alignment with blockchain and DHT-based DID Method standardization.
</dd>
<dt>
<a href="https://trustoverip.org/">
Trust Over IP Foundation</a>
</dt>
<dd>
To ensure alignment with KERI-based DID Method standardization.
</dd>
<dt>
<a href="https://www.1edtech.org/">
1EdTech Consortium</a>
</dt>
<dd>
To ensure alignment with education technology standards utilizing DID Methods.
</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/policies/patent-policy/">W3C Patent Policy</a>.
</p>
<p>
Participants in the group are required (by the
<a href="https://www.w3.org/policies/process/#ParticipationCriteria">
W3C Process</a>) to follow the W3C
<a href="https://www.w3.org/policies/code-of-conduct/">Code of 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/policies/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="https://www.w3.org/groups/wg/dm/">Working Group home page.</a>
</p>
<p>
Most 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="dmwg" href="mailto:[email protected]">[email protected]</a>
(<a href="https://lists.w3.org/Archives/Public/public-dmwg/">archive</a>) or on
each specification's Github repository. 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/policies/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 of one week one
week to 10 working days, 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.
</p>
<p>
This charter is written in accordance with the
<a href="https://www.w3.org/policies/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/policies/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/[shortname]/ipr/">
licensing information</a>.
</p>
<h2>Patent Disclosures </h2>
<p>
The Working Group provides an opportunity to share perspectives on the topic
addressed by this charter. W3C reminds Working Group participants of their
obligation to comply with patent disclosure obligations as set out in <a
href="https://www.w3.org/policies/patent-policy/#sec-Disclosure">Section 6</a>
of the W3C Patent Policy. For more information about disclosure obligations for
this group, please see the
<a href="https://www.w3.org/groups/ig/[shortname]/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/copyright/software-license/">
W3C Software and Document license</a> for all of 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/policies/process/#GAGeneral">section 3.4</a> of the <a href="https://www.w3.org/policies/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/policies/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 class="todo" href="">Initial Charter</a>
</th>
<td>01 June 2025</td>
<td>01 June 2027</td>
<td>None</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>YYYY-MM-DD</dt>
<dd>[changes]]</dd>
</dl>
-->
</section>
</section>
</main>
<hr>
<footer>
<address>
<i class="todo"><a href="mailto:">[team contact name]</a></i>
</address>
<p class="copyright">Copyright © 2024 <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/policies/#disclaimers">liability</a>,
<a href="https://www.w3.org/policies/#trademarks">trademark</a> and
<a rel="license" href="https://www.w3.org/copyright/software-license/" title="W3C Software and Document Notice and License">permissive document license</a> rules apply.</p>
<hr>
<p><span class='todo'><a href="https://github.com/w3c/charter-drafts">Yes, it's on GitHub!</a>.</span></p>
</footer>
</body>
</html>