[PROPOSED] Web Machine Learning Working Group Charter #19
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -96,7 +96,12 @@ | |
| <h1 id="title"> | ||
| [DRAFT] Web Machine Learning Working Group Charter | ||
| </h1><!-- delete PROPOSED after AC review completed --> | ||
| <p style="padding: 0.5ex; border: 1px solid green"> | ||
| This draft charter is available on <a href= | ||
| "https://github.com/w3c/machine-learning-charter">GitHub</a>. Feel free | ||
| to raise <a href= | ||
| "https://github.com/w3c/machine-learning-charter/issues">issues</a>. | ||
| </p> | ||
| <p class="mission"> | ||
| The <strong>mission</strong> of the <a href="">Web Machine Learning | ||
| Working Group</a> is to develop APIs for enabling efficient machine | ||
|
|
@@ -108,12 +113,6 @@ <h1 id="title"> | |
| Machine Learning Working Group.</a> | ||
| </p> | ||
| </div> | ||
| <section id="details"> | ||
| <table class="summary-table"> | ||
| <tr id="Duration"> | ||
|
|
@@ -175,6 +174,15 @@ <h1 id="title"> | |
| </section> | ||
| <section id=bg> | ||
| <h2>Motivation and Background</h2> | ||
| <p> | ||
| Computer Vision enables computers to gain understanding from images | ||
| or videos, Natural Language Processing enables interaction between | ||
| computers and human languages, and Speech Recognition enables | ||
| computers to recognize and translate spoken language into text. | ||
| Bringing these experiences to the web in a privacy-preserving manner | ||
| requires efficient machine learning inference capabilities built into | ||
| the browser. | ||
| </p> | ||
| <p>Enabling Machine Learning inference in | ||
| the browser (as opposed e.g. to in the cloud) enhances privacy, since input | ||
| data such as locally sourced images or video streams stay within the | ||
|
|
@@ -214,13 +222,23 @@ <h2> | |
| and retrieve the output when hardware execution completes. | ||
| </li> | ||
| </ul> | ||
| <p> | ||
| This Working Group puts priority on building blocks required by | ||
| well-known model architectures in the fields of Computer Vision, | ||
| Natural Language Processing and Speech Recognition. | ||
| </p> | ||
| <p> | ||
| The APIs in scope of this group will not be tied to any particular | ||
| platform and will be implementable on top of existing major platform | ||
| APIs, such as Android Neural Networks API, Windows DirectML, and | ||
| macOS/iOS Metal Performance Shaders and Basic Neural Network | ||
| Subroutines. | ||
| </p> | ||
| <p> | ||
| For each high-level building block that decomposes into well-known | ||
| lower-level operations, the APIs will informatively define a generic | ||
| emulation path to allow for future extensibility. | ||
| </p> | ||
| <p>It may also work on a higher-level API to load a custom pre-trained Machine Learning model for inference in the browser.</p> | ||
| <section id="section-out-of-scope"> | ||
| <h3 id="out-of-scope"> | ||
|
|
@@ -237,11 +255,11 @@ <h3 id="out-of-scope"> | |
| algorithms. | ||
| </p> | ||
| <p> | ||
| To avoid overlap with existing work, alignment with the Basic | ||
| Linear Algebra Subprograms (BLAS) interface is out of scope. The | ||
| WebGL and WebGPU shaders and WebAssembly SIMD are expected to | ||
|
There was a problem hiding this comment. Since we already removed WebGL interop from the spec, should we also remove it here from the charter? Preferably noted as out of scope. There was a problem hiding this comment. Thanks for the suggestions. I pushed 33e2eb5 that should address your comments. Namely: I removed the WebGL reference from this BLAS compatibility context and added the following text following this paragraph:
With this change, the only other reference to WebGL in addition to the above out of scope statement remains in the Motivation and Background section as follows:
I think this is appropriate for context setting and to give a historical perspective. With WebNN API becoming more broadly available, the need to use WebGL API for ML workloads is expected to diminish over time. |
||
| address the BLAS compatibility requirement, see the Coordination | ||
| section for details. | ||
| </p> | ||
| <ul class="out-of-scope"></ul> | ||
| </section> | ||
|
|
@@ -253,14 +271,7 @@ <h2> | |
| <p> | ||
| More detailed milestones and updated publication schedules are | ||
| available on the <a href= | ||
| "https://www.w3.org/groups/wg/webmachinelearning">group home page</a>. | ||
| </p> | ||
| <section id="normative"> | ||
| <h3> | ||
|
|
@@ -272,21 +283,31 @@ <h3> | |
| </p> | ||
| <dl> | ||
| <dt id="webnn" class="spec"> | ||
| <a href="https://www.w3.org/TR/webnn/">Web Neural Network API</a> | ||
| </dt> | ||
| <dd> | ||
| <p> | ||
| This specification defines an API to enable neural network | ||
| inference that can take advantage of hardware acceleration. | ||
| </p> | ||
| <p class="draft-status"> | ||
| <b>Draft state:</b> Working Draft | ||
| </p> | ||
| <p> | ||
| <b>Adopted Draft:</b> The <span class="todo">title, stable URL, | ||
| and publication date of the <a href= | ||
| "https://www.w3.org/Consortium/Process/#adopted-draft"> | ||
| Adopted Draft</a></span> which will serve as the basis for | ||
| work on the deliverable. | ||
| </p> | ||
| <p> | ||
| <b>Exclusion Draft:</b> The <span class="todo">title, stable | ||
| URL, and publication date of the most recent <a href= | ||
| "https://www.w3.org/Consortium/Process/#exclusion-draft"> | ||
| Exclusion Draft</a></span>. | ||
| </p> | ||
| <p class="milestone"> | ||
| <b>Expected completion:</b> Q1 2025 | ||
| </p> | ||
| </dd> | ||
| </dl> | ||
|
|
@@ -315,7 +336,8 @@ <h3> | |
| </p> | ||
| <p class="draft-status"> | ||
| <b>Draft state:</b> <a href= | ||
| "https://webmachinelearning.github.io/model-loader/">Adopted from Web | ||
| Machine Learning Community Group</a> | ||
| </p> | ||
| <p class="milestone"> | ||
| <b>Expected completion:</b> [N/A] | ||
|
|
@@ -330,7 +352,14 @@ <h3> | |
| <h3> | ||
| Other Deliverables | ||
| </h3> | ||
| <p> | ||
| The Working Group develops <a href= | ||
| "https://www.w3.org/TR/webmachinelearning-ethics/">Ethical | ||
| Principles for Web Machine Learning</a> Working Group Note | ||
| documenting ethical issues associated with using Machine Learning | ||
| on the Web, to help identify what mitigations its normative | ||
| specifications should take into account. | ||
| </p> | ||
| <p> | ||
| Other non-normative documents may be created such as: | ||
| </p> | ||
|
|
@@ -344,19 +373,6 @@ <h3> | |
| </li> | ||
| </ul> | ||
| </section> | ||
| </section> | ||
| <section id="success-criteria"> | ||
| <h2> | ||
|
|
@@ -453,7 +469,8 @@ <h3 id="w3c-coordination"> | |
| The GPU for the Web Working Group defines a WebGPU Shading | ||
| Language that may be used to implement traditional machine | ||
| learning algorithms efficiently. The Web Machine Learning Working | ||
| Group should coordinate with this group to avoid overlap and | ||
| to enable interoperability between the WebNN and WebGPU APIs. | ||
| </dd> | ||
| </dl> | ||
| <dl> | ||
|
|
@@ -469,7 +486,11 @@ <h3 id="w3c-coordination"> | |
| to avoid overlap. | ||
| </dd> | ||
| <dt><a href="https://www.w3.org/groups/wg/webrtc">WebRTC Working Group</a></dt> | ||
| <dd> | ||
| The WebRTC Working Group defines the <code>MediaStream</code> | ||
| interface and related media processing APIs that enable integration | ||
| with Machine Learning capabilities afforded by the WebNN API. | ||
| </dd> | ||
| <dt><a href="https://www.w3.org/2001/tag/">Technical Architecture Group</a></dt> | ||
| <dd>Given the well-known ethical risks of bias in the use of Machine Learning, the Web Machine Learning Working Group will work with the Technical Architecture Group to ensure its work align with the <a href="https://w3ctag.github.io/ethical-web-principles/">W3C TAG Ethical Web Principles</a>.</dd> | ||
| </dl> | ||
|
|
@@ -479,21 +500,21 @@ <h3 id="external-coordination"> | |
| External Organizations | ||
| </h3> | ||
| <dl> | ||
| <dt><a href="https://tc39.es/">ECMA TC39</a></dt> | ||
| <dd>TC39 defines the JavaScript language whose primitives are key in how WebNN access data (e.g. <code>ArrayBuffer</code>). Possible work on <a href="https://github.com/tc39/proposal-operator-overloading#matrixvector-computations">operator overloading</a> would also impact possible evolutions of the WebNN API.</dd> | ||
| </dl> | ||
| <dl> | ||
| <dt><a href="https://github.com/openxla">OpenXLA Project</a></dt> | ||
| <dd> | ||
| OpenXLA Project develops StableHLO, a portable ML compute | ||
| operation set that makes frameworks easier to deploy across | ||
| different hardware. WebNN API targets diverse hardware platforms | ||
| and defines an operation set whose high-level operations can be | ||
| decomposed to low level primitives that can map to StableHLO | ||
| operations. Coordination and alignment between these two | ||
| operation sets is beneficial to the open ML ecosystem. | ||
| </dd> | ||
| </dl> | ||
| </section> | ||
| </section> | ||
| <section class="participation"> | ||
|
|
@@ -672,16 +693,16 @@ <h3> | |
| </tr> | ||
| <tr> | ||
| <th> | ||
| <a href="https://www.w3.org/2021/04/web-machine-learning-charter.html">Initial Charter</a> | ||
| </th> | ||
| <td> | ||
| 2021-04-20 | ||
| </td> | ||
| <td> | ||
| 2023-04-30 | ||
| </td> | ||
| <td> | ||
| Initial charter | ||
| </td> | ||
| </tr> | ||
| </tbody> | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We excluded training capability from the original charter. Do we want to rediscuss that aspect of the spec for webnn v2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for raising this. I have opened #27 to solicit input on training capability. Please provide your feedback in that issue to feed into a broader WG discussion. We still have time to in-scope this if there is adequate interest.