|
38 | 38 | - ❓ Pay attention to the applicability of the browser-targeted work to non-browser JS environments, in particular Node.js.
|
39 | 39 | - ✔️ Proposal: Extend W3C coordination to TC53 and non-browser projects.
|
40 | 40 |
|
41 |
| -ℹ️ [Targeting WASI-NN and WebNN together #96](https://github.com/w3c/machine-learning-workshop/issues/96) - @mehmetoguzderin @mingqiusun @abrown |
42 |
| -- ❓ Should libraries for browsers and/or Wasm execution environments be able to target WebNN and WASI-NN together? |
43 |
| -- ✔️ Proposal: TBD |
| 41 | +## September 22, 2020, 2pm UTC [🗓️](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200922T14) |
| 42 | + |
| 43 | +>🔎 **Scope:** Web Platform Foundations for Machine Learning |
| 44 | +> |
| 45 | +>✅ **Goal:** Understand how machine learning fits into the Web technology stack |
| 46 | +
|
| 47 | +- [💡 "Web Platform Foundations" discussion topics](https://github.com/w3c/machine-learning-workshop/issues?q=is%3Aissue+is%3Aopen+label%3A%22Web+Platform+Foundations%22+sort%3Acomments-desc) |
44 | 48 |
|
45 | 49 | ## Considerations for creating and deploying models
|
46 | 50 |
|
|
52 | 56 | - ❓ There is no standard format for packaging and shipping ML models, model formats evolve rapidly.
|
53 | 57 | - ✔️ Proposal: Initially focus on defining a Web API for accelerating established reusable ML operations instead of standardizing a model format.
|
54 | 58 |
|
55 |
| -ℹ️ [In-browser training #82](https://github.com/w3c/machine-learning-workshop/issues/82) and [Training across devices #83](https://github.com/w3c/machine-learning-workshop/issues/83) - @irealva @cynthia |
| 59 | +ℹ️ [In-browser training #82](https://github.com/w3c/machine-learning-workshop/issues/82) - @irealva @hapticdata @cynthia |
56 | 60 | - ❓ The current in-browser efforts are focused on inference rather than training.
|
57 | 61 | - ✔️ Proposal: Understand successful real-world usages (e.g. Teachable Machine) and target transfer learning as the initial training use case for related browser API work.
|
58 | 62 |
|
59 |
| -## September 22, 2020, 2pm UTC [🗓️](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200922T14) |
| 63 | + [Training across devices #83](https://github.com/w3c/machine-learning-workshop/issues/83) - @wmaass @Nov1102 @EmmaNingMS @zolkis @jaykishigami |
| 64 | +- ❓ Understand the role of edge computing in training and interactions with the web platform. |
| 65 | +- ✔️ Proposal: Work with Web & Networks IG to understand edge computing use cases and ensure input from ML usages is considered. |
60 | 66 |
|
61 |
| ->🔎 **Scope:** Web Platform Foundations for Machine Learning |
62 |
| -> |
63 |
| ->✅ **Goal:** Understand how machine learning fits into the Web technology stack |
| 67 | +## Extending the web foundations for ML |
64 | 68 |
|
65 |
| -- [💡 "Web Platform Foundations" discussion topics](https://github.com/w3c/machine-learning-workshop/issues?q=is%3Aissue+is%3Aopen+label%3A%22Web+Platform+Foundations%22+sort%3Acomments-desc) |
| 69 | +ℹ️ [Targeting WASI-NN and WebNN together #96](https://github.com/w3c/machine-learning-workshop/issues/96) - @mehmetoguzderin @mingqiusun @abrown |
| 70 | +- ❓ Should libraries for browsers and/or Wasm execution environments be able to target WebNN and WASI-NN together? |
| 71 | +- ✔️ Proposal: TBD |
| 72 | + |
| 73 | +ℹ️ [Heterogeneous parallel computing for the web #92](https://github.com/w3c/machine-learning-workshop/issues/92) - @jeffhammond @Kangz @abrown |
| 74 | +- ❓ How do the heterogeneous parallel computing abstractions fit in with the web platform? |
| 75 | +- ✔️ Proposal: TBD |
66 | 76 |
|
67 | 77 | ## September 23, 2020, 2pm UTC [🗓️](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200923T14)
|
68 | 78 |
|
|
72 | 82 |
|
73 | 83 | - [💡 "Developer's Perspective" discussion topics](https://github.com/w3c/machine-learning-workshop/issues?q=is%3Aissue+is%3Aopen+label%3A%22Developer%27s+Perspective%22+sort%3Acomments-desc)
|
74 | 84 |
|
| 85 | +## Applying web design principles to ML |
| 86 | + |
| 87 | +ℹ️ [Progressive Enhancement / Graceful degradation #68](https://github.com/w3c/machine-learning-workshop/issues/68) - @dontcallmedom @jbingham @wchao1115 @huningxin |
| 88 | +- ❓ How to bring more ML features as optional improvements on more powerful devices and browsers without breaking web compatibility? |
| 89 | +- ✔️ Proposal: TBD |
| 90 | + |
| 91 | +ℹ️ [Conformance testing of ML APIs for the Web #80](https://github.com/w3c/machine-learning-workshop/issues/80) - @wchao1115 @Kangz |
| 92 | +- ❓ Robust conformance testing is a cornerstone of the interoperable web platform, how to scale that to the ML APIs and formats? |
| 93 | +- ✔️ Proposal: TBD |
| 94 | + |
| 95 | +## Improving web developer ergonomics |
| 96 | + |
| 97 | +ℹ️ [JS Operator overloading for Machine Learning #73](https://github.com/w3c/machine-learning-workshop/issues/73) - @TBD |
| 98 | +- ❓ Limitations in ECMAScript expressiveness impose ergonomics limitations for JS APIs on the web platform e.g. in vector matrix or tensor operations. |
| 99 | +- ✔️ Proposal: TBD |
| 100 | + |
| 101 | +ℹ️ [WebGL garbage collection #63](https://github.com/w3c/machine-learning-workshop/issues/63) - @jasonmayes @Kangz @wchao1115 @huningxin |
| 102 | +- ❓ Garbage collection in the WebGL API affects multiple ML libraries. |
| 103 | +- ✔️ Proposal: Identify any improvements in graphics APIs to alleviate the GC issue, ensure purpose-built APIs designed around computational graph abstraction (e.g. WebNN) optimize GC from library usage perspective. |
| 104 | + |
| 105 | +ℹ️ [Neural network-oriented graph database #102](https://github.com/w3c/machine-learning-workshop/issues/102) - @WenheLI |
| 106 | +- ❓ Understand model storage issues on the client, research the feasibility of a neural network-oriented graph database for the web. |
| 107 | +- ✔️ Proposal: TBD |
| 108 | + |
| 109 | +## Developing interactive web experiences with ML |
| 110 | + |
| 111 | +ℹ️ [Action-Response Cycle bottlenecks in interactive music apps #97](https://github.com/w3c/machine-learning-workshop/issues/97) - @teropa |
| 112 | +- ❓ Action-Response Cycle in interactive (music) apps must execute within 20 ms. |
| 113 | +- ✔️ Proposal: Investigate inference in AudioWorklet context and media integration e.g. fast streaming inputs from MediaStream. |
| 114 | + |
| 115 | +ℹ️ Noise suppression with DSP+DNN, WebNN and Web Audio API feature gaps - @TBD |
| 116 | +- ❓ TBD |
| 117 | +- ✔️ Proposal: TBD |
| 118 | + |
75 | 119 | ## September 29, 2020, 2pm UTC [🗓️](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200929T14)
|
76 | 120 |
|
77 | 121 | >🔎 **Scope:** Machine Learning Experiences on the Web: A **User’s** Perspective
|
|
0 commit comments