forked from w3c-ccg/did-wg-charter
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
622 lines (554 loc) · 25.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
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8" />
<title>[DRAFT] 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/Guide/pubrules-style.css" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css" />
<style type="text/css">
body {
background-image: url('data:image/svg+xml,\
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 150 100" width="100%" height="50%" opacity=".04">\
<g transform="translate(73,45) rotate(-40)">\
<rect fill="none" stroke="black" stroke-width="2" width="120" x="-60" y="3" height="20" rx="10" ry="10"/>\
<text x="0" y="20" font-family="sans-serif" font-size="14" fill="red" text-anchor="middle">Experimental</text>\
</g>\
</svg>\
');
background-position: top center;
background-repeat: repeat;
}
.warning {
box-shadow: 10px 5px 3px 0px gray;
border-top-width: thin;
border-right-width: thin;
border-bottom-width: thin;
border-left-width: thin;
border-top-style: solid;
border-right-style: solid;
border-bottom-style: solid;
border-left-style: solid;
border-radius: 3px;
width: 80%;
padding-top: 0.5em;
padding-right: 0.5em;
padding-bottom: 0.5em;
padding-left: 0.5em;
}
.warning h1 {
font-size: 120%;
font-style: italic;
font-weight: bold;
text-align: center;
}
.warning p {
font-size: 110%;
}
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;
background-color:#FFC !important;
font-style: italic;
}
footer {
font-size: small;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li><a href="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</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>
<div class="warning">
<h1>Draft</h1>
<p>
This is a <em>proposed</em> charter for a Decentralized Identifier Working Group, currently undergoing development by the W3C Credentials Community Group; this is the development version.
It is available on <a href="https://github.com/w3c-ccg/did-wg-charter/">GitHub</a>.
You may raise issues on this document <a href="https://github.com/w3c-ccg/did-wg-charter/issues">issues</a> to help further discussion.
</p>
<p>Items (mostly URL-s), that will need update if and when the charter are accepted, are marked <span class="todo">thusly</span>.
</div>
<h1 id="title">Decentralized Identifier Working Group Charter</h1>
<p>
URL identifiers in use on the Web today (2018) require that the identifier is
leased from an authority such as a Domain Name Registrar. The advent of
Blockchains and Decentralized Ledger Technologies have led to innovations
around a new type of URL, called a Decentralized Identifier (DID). DIDs have
benefits over more traditional URLs:
</p>
<ul>
<li>
DIDs are controlled by individuals, organizations, and machines, not leased from
an authority (e.g. DNS Registrars).
</li>
<li>
The controller of a DID can cryptographically authenticate themselves
(e.g. DID-based website login) .
</li>
<li>
DIDs provide discovery information for bootstrapping into more secure and
privacy preserving communication protocols (e.g. encrypted messaging endpoints).
</li>
<li>
DIDs provide a path to service agnostic data portability
(e.g. switching between Verifiable Credential digital wallet providers).
</li>
</ul>
<p>
W3C Members that would like to lean more about the motivations that led to
this work may find the
<a href="https://w3c-ccg.github.io/did-primer/">Primer for Decentralized Identifiers</a>
useful. There are also a set of
<a href="https://docs.google.com/document/d/1wz8sakevXzO2OSMP341w7M2LjAMZfEQaTQEm_AOs3_Q/edit">Decentralized Identifier Use Cases</a>
that have been curated by the various organizations implementing and deploying
this technology in commercial environments.
</p>
<p class="mission">
The <strong>mission</strong> of the
<a href="https://www.w3.org/2019/did-wg/">Decentralized Identifier Working Group</a>
is to standardize the data model and syntax of Decentralized Identifier
Documents, which contain information related to DIDs that enable the
aforementioned use cases.</p>
<div class="noprint"> <p class="join"><a class="todo" href="https://www.w3.org/2004/01/pp-impl/#####/join">Join the Decentralized Identifier Working Group.</a></p>
</div>
<section id="details">
<table class="summary-table">
<tr id="Duration">
<th>
Start date
</th>
<td>
01 January 2019
</td>
</tr>
<tr id="Duration">
<th>
End date
</th>
<td>
31 December 2020
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
TBD<br/>
TBD
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<a href="mailto:TEAMCONTACT@w3.org">TBD</a> (0.2 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> 1-hour calls will be held 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>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>The Working Group will:</p>
<ol>
<li>
Recommend a data model and syntax(es) for the expression of Decentralized
Identifier Documents, including one or more core vocabularies.
</li>
<li>
Recommend a way of authoring specifications for DID Methods and protocols
that are conformant with the data model and syntax(es).
</li>
<li>
Concentrate their efforts on the identified
<a href="https://docs.google.com/document/d/1wz8sakevXzO2OSMP341w7M2LjAMZfEQaTQEm_AOs3_Q/edit">use cases</a>
with a particular focus on Identity and Access Management. Use cases from
other industries may be included if there is significant industry participation.
</li>
</ol>
<div id="section-out-of-scope">
<h3 id="out-of-scope">Out of Scope</h3>
<p>
The following features and topics are out of scope and will not be
addressed by this Working Group.
</p>
<ul>
<li>Authentication or Authorization Protocols</li>
<li>Browser APIs</li>
<li>Specific Implementations of DID Methods and Protocols</li>
<li>"Solving Identity" on the Web</li>
</ul>
</div>
<div>
<h3>Success Criteria</h3>
<p>
In order to advance to
<a href="https://www.w3.org/Consortium/Process//#RecsPR"
title="Proposed Recommendation">Proposed Recommendation</a>, each specification
is expected to have
</p>
<ul>
<li>
<a href="https://www.w3.org/Consortium/Process/#implementation-experience">At least two independent implementations</a>
of each of feature defined in the specification, and
</li>
<li>
a section detailing any known security or privacy implications for implementers,
Web authors, and end users.
</li>
</ul>
<p>
The group will maintain and advance a <a href="">Test Suite</a> allowing for
testing of implementations.
</p>
</div>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p>More detailed milestones and updated publication schedules are available on the <a href="https://www.w3.org/2018/did-wg/PubStatus">group publication status page</a>.</p>
<div id="normative">
<h3>
Normative Specifications
</h3>
<p>
The Decentralized Identifier Working Group will deliver the following W3C normative specifications:
</p>
<dl>
<dt id="syntax" class="spec">Decentralized Identifiers v1.0</dt>
<dd>
<p>
Decentralized Identifiers (DIDs) are a new type of identifier for verifiable,
"self-sovereign" digital identity. DIDs are fully under the control of the DID
subject, independent from any centralized registry, identity provider, or
certificate authority. DIDs are URLs that relate a DID subject to means for
trustable interactions with that subject. DIDs resolve to DID Documents —
simple documents that describe how to use that specific DID. Each DID Document
contains at least three things: cryptographic material, authentication suites,
and service endpoints. Cryptographic material combined with authentication
suites provide a set of mechanisms to authenticate as the DID subject (e.g.
public keys, pseudonymous biometric protocols, etc.). Service endpoints enable
trusted interactions with the DID subject. This document specifies a common
data model, format, and operations that all DIDs support.
</p>
<p>
The
<a href="https://www.w3.org/community/credentials/">Credentials Community Group</a>
has developed a
<a href="https://w3c-ccg.github.io/did-spec/">Final Community Group Specification for Decentralized Identifiers</a>
that has been shipped in multiple production-grade commercial systems that will
serve as input for this document.
</p>
</dd>
</dl>
<p>
Note that the WG may decide, based on editorial and readability considerations,
to spin off sections into separate Recommendations.
</p>
</div>
<div id="wg-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
Other non-normative documents may be created such as:
</p>
<dl>
<dt id="syntax" class="spec">Decentralized Identifier Use Cases v1.0</dt>
<dd>
<p>
The Working Group will develop a set of use cases and requirements to underpin
its work. Abstract use cases will be supported by real world evidence of
applicability. The
<a href="https://www.w3.org/community/credentials/">Credentials Community Group</a>
has developed a set of
<a href="https://docs.google.com/document/d/1wz8sakevXzO2OSMP341w7M2LjAMZfEQaTQEm_AOs3_Q/edit">use cases and requirements</a>
that will serve as input for this document.</p>
</p>
</dd>
</dl>
</div>
<div id="timeline">
<h3>Timeline</h3>
<table class="roadmap">
<tfoot>
<tr>
<td colspan="5" rowspan="1">Note: The group will document significant changes from this initial schedule
on the group home page.
</td>
</tr>
</tfoot>
<tbody>
<tr>
<th rowspan="1" colspan="1">Specification</th>
<th rowspan="1" colspan="1">
<abbr title="First Working Draft">FPWD</abbr>
</th>
<th rowspan="1" colspan="1">
<abbr title="Candidate Recommendation">CR</abbr>
</th>
<th rowspan="1" colspan="1">
<abbr title="Proposed Recommendation">PR</abbr>
</th>
<th rowspan="1" colspan="1">
<abbr title="Recommendation">Rec</abbr>
</th>
</tr>
<tr>
<th rowspan="1" colspan="1">Decentralized Identifier Use Cases & Requirements (NOTE)</th>
<td class="WD1" rowspan="1" colspan="3">February 2019</td>
<td class="REC" rowspan="1" colspan="3">November 2020</td>
</tr>
<tr>
<th rowspan="1" colspan="1">Decentralized Identifiers Data Model and Syntax(es)</th>
<td class="WD1" rowspan="1" colspan="1">April 2019</td>
<td class="CR" rowspan="1" colspan="1">January 2020</td>
<td class="PR" rowspan="1" colspan="1">July 2020</td>
<td class="REC" rowspan="1" colspan="1">November 2020</td>
</tr>
</tbody>
</table>
</div>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/Charter.html#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> and at least 3 months before <a href="https://www.w3.org/Consortium/Process/#RecsCR" title="Candidate Recommendation">CR</a>, and should be issued when major changes occur in a specification.</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>
<div>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/2017/vc/WG/">Verifiable Claims Working Group</a></dt>
<dd>Coordination on named graph indexing and other concerns regarding support for normalization and digital signatures.</dd>
</dl>
</div>
<!-- <div>
<h3 id="external-coordination">External Groups</h3>
<dl>
<dt>
<a href="https://schema.org">Schema.org</a>
</dt>
<dd>Schema.org should be regularly solicited for reviews and comments on the advancement of the JSON-LD 1.1 Recommendation.</dd>
</dl>
</div> -->
</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>
W3C Members are invited to <a class="todo" href="https://www.w3.org/2004/01/pp-impl/#####/join">join this Working Group</a>.
Individuals who wish to participate as Invited Experts (i.e., they do not represent a W3C Member) should refer to the <a href="https://www.w3.org/2004/08/invexp.html" shape="rect">policy for approval of Invited Experts</a>.
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>
</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 on a public repository, 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/2019/did-wg/">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:public-did-wg@w3.org">public-did-wg@w3.org</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 will publish minutes for each teleconference at <a href="https://github.com/w3c/did-wg/Meeting/Minutes/">https://github.com/w3c/did-wg/Meeting/Minutes/
</a>.
</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 3.3</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, but 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 and/or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue.
If no objections are raised on the mailing list 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/policies#Votes">W3C Process Document (Section 3.4, Votes)</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-20170801/">W3C Patent Policy</a> (Version of 5 February 2004 updated 1 August 2017). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations 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/2004/01/pp-impl/">W3C Patent Policy Implementation</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 5.2</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 class="issue"><b>Note:</b>Display this table and update it when appropriate. Requirements for charter extension history are documented in the <a href="https://www.w3.org/Guide/Charter#extension">Charter Guidebook (section 4)</a>.</p>
<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 5.2.3)</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/2018/03/jsonld-wg-charter.html">Initial Charter</a>
</th>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i class="todo">none</i>
</td>
</tr>
<tr>
<th>
<a class="todo" href="">Charter Extension</a>
</th>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i class="todo">none</i>
</td>
</tr>
<tr>
<th>
<a class="todo" href="">Rechartered</a>
</th>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<p class="todo">[description of change to charter, with link to new deliverable item in charter] <b>Note:</b> use the class <code>new</code> for all new deliverables, for ease of recognition.</p>
</td>
</tr>
</tbody>
</table>
</section -->
</section>
</main>
<hr />
<footer>
<address>
<a href="mailto:msporny@digitalbazaar.com">Manu Sporny</a>
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2018
<a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(
<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://www.keio.ac.jp/">Keio</a>,
<a href="http://ev.buaa.edu.cn/">Beihang</a>
), All Rights Reserved.
<abbr title="World Wide Web Consortium">W3C</abbr> <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 href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
</footer>
</body>
</html>