-
Notifications
You must be signed in to change notification settings - Fork 12
/
Copy pathwg-charter.html
519 lines (451 loc) · 27.1 KB
/
wg-charter.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
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8" />
<title>GPU for the Web 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">
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"><i class="todo">PROPOSED</i> GPU for the Web Working Group Charter</h1>
<p class="todo"><strong>Warning:</strong> This document has no official status. It is a draft charter for discussion within the GPU for the Web groups and the W3C Advisory Committee.</p>
<p class="mission">The <strong>mission</strong> of the <a
href="https://www.w3.org/2020/gpu/">GPU for the Web Working Group</a> is to
provide an interface between the Web Platform and modern 3D graphics and
computation capabilities present on native system platforms.</p>
<div class="noprint">
<p class="join"><a href="https://www.w3.org/2004/01/pp-impl/125519/join">Join the GPU for the Web Working Group</a>.</p>
</div>
<section id="details">
<table class="summary-table">
<tr id="Status">
<th>
Charter Status
</th>
<td>
See the <a href="https://www.w3.org/groups/wg/gpu/charters/">group status page</a> and <a href="#history">detailed change history</a>.
</td>
</tr>
<tr id="Duration">
<th>
Start date
</th>
<td>
<i class="todo">[dd monthname yyyy] (date of the "Call for Participation", when the charter is approved)</i>
</td>
</tr>
<tr id="Duration">
<th>
End date
</th>
<td>
<i class="todo">[dd monthname yyyy]</i> (Start date + 2 years)
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
Kelsey Gilbert (Mozilla)<br/>
Corentin Wallez (Google)
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<a href="mailto:[email protected]">François Daoust</a> (0.05 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> weekly or bi-weekly calls, as necessary.
<br />
<strong>Face-to-face:</strong> 3 times per year as necessary,
including during W3C's annual Technical Plenary week.
</td>
</tr>
</table>
</section>
<section id="background" class="background">
<h2>Motivation and Background</h2>
<p>
In this document, the term <dfn>GPU</dfn> stands for Graphics Processing Unit, typically a piece of hardware dedicated to efficiently processing graphics and related features.
</p>
<p>
GPUs have become essential for drawing complex images efficiently, including for rendering virtual reality and augmented reality scenes in real-time as needed by the <a href="https://www.w3.org/TR/webxr/">WebXR Device API</a>. GPUs are also at the heart of computations that leverage parallelism, such as machine learning inference.
</p>
<p>
Web applications may leverage GPUs through the <a href="https://www.khronos.org/webgl/">WebGL</a> family of APIs, but WebGL does not enable access to more advanced features of GPUs, focuses on drawing images and does not provide first-class support for performing general computations, and is not agnostic of the GPU system API exposed by the underlying operating system.
</p>
<p>
The overall goal of the GPU for the Web Working Group is to provide a foundation that can be implemented on top of modern GPU system APIs to expose modern GPU functionality on the Web, both for computation and for image rendering.
</p>
<p>
See also the <a href="https://gpuweb.github.io/gpuweb/explainer/">WebGPU Explainer</a>, maintained by the GPU for the Web Community Group, for additional background, use cases, and design considerations.
</p>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>
This Working Group will recommend a Web programming interface for
graphics and computation that:
</p>
<ol>
<li>enables rendering of modern graphics to both onscreen and offscreen drawing surfaces</li>
<li>enables computation tasks to be performed, and the results of such tasks to be retrieved</li>
<li>This group will also recommend a companion Shading Language that describes the graphics and computation tasks in a format
that can be translated or compiled into platform-specific instructions</li>
</ol>
<p>
The API will not be restricted to any particular platform technology. Instead, it will
be generic enough to be implemented on top of modern GPU system APIs, such as
Microsoft's Direct3D 12, Apple's Metal, and Khronos's Vulkan.
</p>
<p>
This Working Group will investigate and document threat mitigation
strategies for the API, notably to address fingerprinting issues
and to prevent unauthorized use of computational resources.
</p>
<h2>Out of Scope</h2>
<p>
The scope of work is restricted to the development of a programming
interface between the Web Platform and modern 3D graphics and
computation capabilities present on native system platforms. The work
will not define hardware features or algorithms, and the interface it
defines is not intended to be directly exposed by a GPU driver.
</p>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p>Updated document status is available on the <a href="https://www.w3.org/groups/wg/gpu/publications">group publication status page</a>.</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 reach a stable state. The Working Group intends to publish the latest state of their work as Candidate Recommendation (with Snapshots) and does not intend to advance their documents to Recommendation.</p>
<div id="normative">
<h3>
Normative Specifications
</h3>
<dl>
<dt><a href="https://www.w3.org/TR/webgpu/">WebGPU API</a></dt>
<dd>
An API for performing operations, such as rendering and
computation, on a Graphics Processing Unit (GPU).
<p class="draft-status"><b>Draft state:</b> Working Draft</p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2022/WD-webgpu-20220831/">31 August 2022</a></p>
<p><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2021/WD-webgpu-20210518/">WebGPU 18 May 2021</a>;
<br/>associated <a href="https://www.w3.org/mid/[email protected]">Call for Exclusion</a> on 2021-05-18 ended on 2021-10-15;
<br/>produced under Working Group charter: <a href="https://www.w3.org/2020/12/gpu-wg-charter.html">https://www.w3.org/2020/12/gpu-wg-charter.html</a></p>
<p class="milestone"><b>Expected completion:</b> Q2 2025</p>
</dd>
<dt><a href="https://www.w3.org/TR/WGSL/">WebGPU Shading Language</a></dt>
<dd>
A Shading Language specification that defines the programmable
interface to the GPU for the Web graphics and computation
pipeline, and that can be translated into the shading languages
of the system APIs WebGPU is implemented upon.
<p class="draft-status"><b>Draft State:</b> Working Draft</p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2022/WD-WGSL-20220831/">31 August 2022</a></p>
<p><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2021/WD-WGSL-20210518/">WebGPU Shading Language 18 May 2021</a>;
<br/>associated <a href="https://www.w3.org/mid/[email protected]">Call for Exclusion</a> on 2021-05-18 ended on 2021-10-15;
<br/>produced under Working Group charter: <a href="https://www.w3.org/2020/12/gpu-wg-charter.html">https://www.w3.org/2020/12/gpu-wg-charter.html</a></p>
<p class="milestone"><b>Expected completion:</b> Q2 2025</p>
</dd>
</dl>
</div>
<div id="wg-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
This Working Group will produce <a href="https://github.com/gpuweb/cts">conformance test suites</a> and
implementation reports for its normative deliverables.
</p>
<p>
Other non-normative documents may be created, including:
</p>
<ul>
<li>Reference implementations of the group's deliverables</li>
<li>Use case and requirement documents</li>
<li>Explainers, primers and best-practice documents</li>
</ul>
</div>
</section>
<section id="success-criteria">
<h2>Success Criteria</h2>
<p>There should be testing plans for each specification, starting from the earliest drafts. Normative specification changes are generally expected to have a corresponding set of tests, either in the form of new tests or modifications to existing tests, or must include the rationale for why test updates are not required for the proposed update.</p>
<p>Each specification should contain sections detailing all known security and privacy —including fingerprinting— implications, and suggested mitigation strategies for implementers, web authors, and end users. The group should not publish a specification if acceptable mitigation strategies cannot be found.</p>
<p>Each specification should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and recommendations for maximising accessibility in implementations.</p>
<p>This Working Group expects to follow the TAG <a href="https://www.w3.org/TR/design-principles/">Web Platform Design Principles</a>.</p>
<p>All new features should have expressions of interest from at least two potential implementors before being incorporated in the specification.</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>
<div>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/community/gpu/">GPU for the Web Community Group</a></dt>
<dd>The GPU for the Web Community Group developed the specifications adopted by this Working Group. It is expected that the Community Group will continue to work on test suites, tools, white papers and other non normative reports associated with the deliverables of this Working Group.</dd>
<dt><a href="https://www.w3.org/immersive-web/">Immersive Web Working Group</a></dt>
<dd>The Immersive Web Working Group produces specifications to interact with Virtual Reality (VR) and Augmented Reality (AR) devices and sensors, and may add a 3D rendering layer based on the WebGPU API.</dd>
<dt><a href="https://www.w3.org/groups/wg/webapps/">Web Applications Working Group</a></dt>
<dd>The Web Applications Working Group (WebApps WG) produces specifications that facilitate the development of client-side web applications.</dd>
<dt><a href="https://www.w3.org/groups/wg/webappsec/">Web Application Security Working Group</a></dt>
<dd>This Working Group develops security and policy mechanisms to improve the security of Web Applications, and enable secure cross-site communication.</dd>
<dt><a href="https://www.w3.org/groups/wg/wasm/">Web Assembly Working Group</a></dt>
<dd>This Working Group develops a size- and load-time-efficient format and execution environment, allowing compilation to the web with consistent behavior across a variety of implementations.</dd>
<dt><a href="https://www.w3.org/groups/wg/webmachinelearning/">Web Machine Learning Working Group</a></dt>
<dd>This Working Group develops a dedicated low-level Web API for enabling efficient machine learning inference in the browser.</dd>
</dl>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a title="WHATWG" href="https://whatwg.org/" id="whatwg">Web Hypertext Application Technology Working Group (WHATWG)</a></dt>
<dd>The Web Hypertext Application Technology Working Group (WHATWG) is a community of people interested in evolving the web through standards and tests.</dd>
<dt><a title="Khronos" href="https://khronos.org/" id="khronos">Khronos</a></dt>
<dd>The Khronos Organization is a standards body that develops many graphics-related technologies, including OpenGL, Vulkan and SPIR-V.</dd>
<dt><a title="UTC" href="https://www.unicode.org/consortium/utc.html" id="utc">Unicode Technical Committee (UTC)</a></dt>
<dd>The Unicode Technical Committee is responsible for the development and maintenance of the Unicode Standard, including the Unicode Character Database. This Working Group will coordinate with the UTC where appropriate, notably with regards to supporting Unicode identifiers in the WebGPU Shading Language specification.</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>
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 on 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/2020/gpu/">GPU for the Web Working Group home page.</a>
</p>
<p>
Most GPU for the Web 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 in its <a href="https://github.com/gpuweb">public repositories</a>. There is also a public mailing list <a id="public-name" href="mailto:[email protected]">[email protected]</a> (<a href="https://lists.w3.org/Archives/Public/public-gpu/">archive</a>). The public is invited to contribute to the github repositories and post messages to the list. Regular activity summaries around the github repositories will be provided.
</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 from <span id='cfc'>10 working days</i></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.
</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/gpu/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 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 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/2020/08/gpuweb-charter.html">Initial Charter</a>
</th>
<td>
20 August 2020
</td>
<td>
31 August 2022
</td>
<td>
Initial charter
</td>
</tr>
<tr>
<th><a href="https://www.w3.org/2020/12/gpu-wg-charter.html">Rechartered</a></th>
<td>15 December 2020</td>
<td>31 August 2022</td>
<td>New Patent Policy</td>
</tr>
<tr>
<th><a href="https://www.w3.org/2020/12/gpu-wg-charter.html">New co-chair</a></th>
<td>07 April 2021</td>
<td>31 August 2022</td>
<td>Jeff Gilbert replaces Dean Jackson as co-chair</td>
</tr>
<tr>
<th><a href="https://www.w3.org/2020/12/gpu-wg-charter.html">Co-chair update</a></th>
<td>17 February 2022</td>
<td>31 August 2022</td>
<td>Reflect change of firstname for Kelsey Gilbert</td>
</tr>
<tr>
<th><a href="https://www.w3.org/2020/12/gpu-wg-charter.html">Charter Extension</a></th>
<td>07 September 2022</td>
<td>30 November 2022</td>
<td>None</td>
</tr>
<tr>
<th><a href="https://www.w3.org/2022/11/gpuweb-charter.html">Rechartered</a></th>
<td>6 December 2022</td>
<td>30 November 2024</td>
<td><ul>
<li>Align text with charter template</li>
<li>Refresh deliverables drafts info</li>
<li>Replace Web Machine Learning Community Group with Working Group in coordination section</li>
<li>Add Unicode Technical Committee to coordination section</li>
</ul></td>
</tr>
<tr>
<th><a href="#">Rechartered</a></th>
<td><i class="todo">When approved</i></td>
<td>30 November 2026</td>
<td><ul>
<li>Align text with charter template, refresh links</li>
<li>Add link to Conformance Test Suite</li>
<li>Switch to CR with Snapshots (no intent to advance to Recommendation) mode</li>
<li>Clarify that technical discussions on the deliverables are now driven by this Working Group</li>
<li>Add a Motivation and Background section</li>
</ul></td>
</tr>
</tbody>
</table>
</section>
</section>
</main>
<hr />
<footer>
<address>
<a href="mailto:[email protected]">François Daoust</a>
</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>
</footer>
</body>
</html>