3
3
layout: subpage
4
4
base: ../
5
5
parent: proceeding.html
6
+ hasPDF: true
7
+ nextlink: 20200922.html
8
+ nexttitle: "Minutes of 2nd Live Session (September 22, 2020)"
9
+ uplink: ../proceeding.html
10
+ uptitle: List of minutes
6
11
---
7
12
< h2 > Minutes of 1st Live Session (September 16 2020)</ h2 >
8
13
< address > Scribe: François Daoust</ address >
14
+ < p > < strong > < a href ="https://github.com/w3c/machine-learning-workshop/tree/master/agenda "> Agenda</ a > </ strong > - < strong > < a href ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf#page=1 "> Slides</ a > </ strong > < p >
9
15
< p > < cite > Present:</ cite > Dominique Hazael-Massieux, Anssi
10
16
Kostiainen, Bernard Aboba, Deng Yuguang, Gabriel Vigliensoni, Jason
11
17
Mayes, Jeff Hammond, Jun Weifu, Qiang Chen, Sangwhan Moon, Wendy
@@ -26,25 +32,30 @@ <h2>Minutes of 1st Live Session (September 16 2020)</h2>
26
32
Rachel Yager, Mark Crawford, Piotr Migdal, Chenzelun, Marie-Claire
27
33
Forgue, John Rochford, Virginie Galindo,</ p >
28
34
< h2 > Introduction to the workshop</ h2 >
35
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-2 "> </ div >
29
36
< p > < cite > Anssi:</ cite > Welcome. I work with Intel, chair of the
30
37
workshop. Background in Web standards and Web technologies. The
31
38
purpose of this workshop, in a nutshell, is to bring together
32
39
machine learning and web people to make sure that the Web platform
33
40
has better foundations for machine learning. We want to understand
34
41
how in-browser machine learning fits into the machine learning
35
42
ecosystem, and explore things both ways. Many pieces of the
36
- platform could be improved.</ p >
43
+ platform could be improved.</ p >
44
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-3 "> </ div >
37
45
< p > < cite > Anssi:</ cite > Why are we here? The reality is that people
38
46
from diverse backgrounds need to gather together to complement each
39
- other, and better evolve the Web platform.</ p >
47
+ other, and better evolve the Web platform.</ p >
48
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-4 "> </ div >
40
49
< p > < cite > Anssi:</ cite > On behalf of the program committee, I would
41
50
like to thank the speakers for the incredible work you've produced.
42
51
Special thanks to our sponsor Futurice for making this workshop
43
- possible.</ p >
52
+ possible.</ p >
53
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-5 "> </ div >
44
54
< p > < cite > Anssi:</ cite > Today's session is on opportunities and
45
55
challenges of browser based ML. We have divided the rest in 3 other
46
56
slots. 4 sessions in total. Sep 22, 23, 29, same time as today for
47
- remaining sessions.</ p >
57
+ remaining sessions.</ p >
58
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-7 "> </ div >
48
59
< p > < cite > Dom:</ cite > What is W3C? I'm Dominique Hazaël-Massieux,
49
60
part of the technical staff at W3C. You may have received emails
50
61
from me… W3C stands for the World Wide Web Consortium. We are
@@ -63,15 +74,17 @@ <h2>Introduction to the workshop</h2>
63
74
are new for our scope. A big motivation for this workshop is that,
64
75
as we see communities working with ML, we understand opportunities
65
76
that ML creates for the Web, as well as opportunities that the Web
66
- creates for ML. Welcome all to this W3C event!</ p >
77
+ creates for ML. Welcome all to this W3C event!</ p >
78
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-8 "> </ div >
67
79
< p > < cite > Anssi:</ cite > Here is an illustration of how we work
68
80
together. Coming here, we received an array of talks. We have had
69
81
very productive discussions on GitHub on some of the issues raised
70
82
by the talk. As an outcome of this workshop, we will have a list of
71
83
proposals, some of which may be ready for standardization
72
84
(agreement and scope). We'll probably identify areas that are good
73
85
target for incubation. We may also identify areas that would be
74
- better served in other organizations, not W3C.</ p >
86
+ better served in other organizations, not W3C.</ p >
87
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-9 "> </ div >
75
88
< p > < cite > Anssi:</ cite > Please do not hesitate to comment using
76
89
whatever mechanism you are comfortable with. Practically speaking,
77
90
you are muted by default in Zoom to avoid background noise. Please
@@ -80,12 +93,14 @@ <h2>Introduction to the workshop</h2>
80
93
to Zoom, we have a Slack channel, you may want to follow that as
81
94
well. We take live notes through a scribe (Francois does it today).
82
95
Lastly, we are operating under the Code of Ethics and Professional
83
- Conduct (CEPC).</ p >
96
+ Conduct (CEPC).</ p >
97
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-10 "> </ div >
84
98
< p > < cite > Anssi:</ cite > Let's get to the meat of the meeting and
85
99
look at the opportunities and challenges. Plenty of discussion
86
100
topics for today in 3 buckets.</ p >
87
101
< h2 > Improving existing web platform capabilities</ h2 >
88
102
< h3 > WebGPU fitness for ML frameworks</ h3 >
103
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-13 "> </ div >
89
104
< p > < a href ="https://github.com/w3c/machine-learning-workshop/issues/66 "> Related Discussions on Github</ a > </ p >
90
105
< p > < cite > Anssi:</ cite > First topic is WebGPU fitness for ML
91
106
frameworks. Extensively discussed on GitHub. Does the WebGPU API
@@ -165,6 +180,7 @@ <h3>WebGPU fitness for ML frameworks</h3>
165
180
progress. "Try different things and see what sticks". I would like
166
181
to move to next topic now. Thank you for the great discussion.</ p >
167
182
< h3 > Support for Float16 in JS & WebAssembly environments</ h3 >
183
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-14 "> </ div >
168
184
< p > < a href ="https://github.com/w3c/machine-learning-workshop/issues/64 "> Related Discussions on Github</ a > </ p >
169
185
< p > < cite > Anssi:</ cite > Lack of support in these environments is an
170
186
issue for quantized models. There has been discussion a couple of
@@ -228,6 +244,7 @@ <h3>Comments on chat</h3>
228
244
doesn't exist on ARM / GPU?</ p >
229
245
</ div >
230
246
< h3 > Memory Copies</ h3 >
247
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-15 "> </ div >
231
248
< p > < a href ="https://github.com/w3c/machine-learning-workshop/issues/93 "> Related Discussions on Github</ a > </ p >
232
249
< p > < cite > Anssi:</ cite > The issue is that ML apps within the browser
233
250
may trigger too many memory copies compared to native apps. This
@@ -317,6 +334,7 @@ <h3>Comments on chat</h3>
317
334
doesn't solve it all)</ p >
318
335
</ div >
319
336
< h3 > Permission model for Machine Learning APIs</ h3 >
337
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-16 "> </ div >
320
338
< p > < a href ="https://github.com/w3c/machine-learning-workshop/issues/72 "> Related Discussions on Github</ a > </ p >
321
339
< p > < cite > Anssi:</ cite > How to design a forward-looking permission
322
340
model for ML APIs? This is a large problem, and not restricted to
@@ -408,6 +426,7 @@ <h3>Comments on chat</h3>
408
426
</ div >
409
427
< h2 > Extending beyond the browser</ h2 >
410
428
< h3 > Applicability to non-browser JS environments</ h3 >
429
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-18 "> </ div >
411
430
< p > < cite > Anssi:</ cite > Pay attention to the application of the
412
431
browser-targeted work to non-browser JS runtimes, such as
413
432
Node.js.</ p >
@@ -446,6 +465,7 @@ <h3>Applicability to non-browser JS environments</h3>
446
465
< p > < cite > Anssi:</ cite > I believe we have a separate topic for this
447
466
discussion. So get in touch with TC53.</ p >
448
467
< p > [Time check, oh no, too late!]</ p >
468
+ < div role ="region " data-fmt =pdf data-src ="http://www.w3.org/2020/Talks/mlws/live-sessions.pdf " id ="slide-19 "> </ div >
449
469
< p > < cite > Anssi:</ cite > This was the first time we tried this,
450
470
thanks for the discussion. We'll reschedule pending topics to the
451
471
other 3 sessions. Virtual applause to everyone! I hope to see you
0 commit comments