You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Web Neural Network API (or WebNN API in short) is a specification for constructing and executing computational graphs of neural networks. It provides web applications with the ability to create, compile, and run machine learning networks on the web browsers. The WebNN API may be implemented in web browsers using the available native operating system machine learning APIs for the best performance and reliability of results.
The group where standardization of this work is intended to be done:
Major unresolved issues with or opposition to this specification: N/A
This work is being funded by: N/A
For the full review template, please unfold the above section ⤴️
The initial TAG review completed Oct 2021. This delta request focuses your attention on the following architectural changes and issues since the previous review:
Naming of the sync and async methods: createContext, build and compute. The WG has considered two API naming conventions (x() + xSync() or xAsync() + x()) but was unable to reach consensus and resolved to seek TAG recommendation. See Support asynchronous context creation webmachinelearning/webnn#272
Related to the naming issue, the WG decided to restrict the sync API to worker context only. This API complements the async API. The key use case for the sync API is to support Wasm code generators. The async API is the recommended path for mainstream use cases. We would like to hear the TAG perspective on this API split. We are aware that the worker-only sync API design is a rare exception on the web platform.
Hi TAG!
I'm requesting a delta TAG review of the Web Neural Network API.
The Web Neural Network API (or WebNN API in short) is a specification for constructing and executing computational graphs of neural networks. It provides web applications with the ability to create, compile, and run machine learning networks on the web browsers. The WebNN API may be implemented in web browsers using the available native operating system machine learning APIs for the best performance and reliability of results.More details about this review request
Further details:
The initial TAG review completed Oct 2021. This delta request focuses your attention on the following architectural changes and issues since the previous review:
Naming of the sync and async methods:
createContext,buildandcompute. The WG has considered two API naming conventions (x() + xSync()orxAsync() + x()) but was unable to reach consensus and resolved to seek TAG recommendation. See Support asynchronous context creation webmachinelearning/webnn#272Related to the naming issue, the WG decided to restrict the sync API to worker context only. This API complements the async API. The key use case for the sync API is to support Wasm code generators. The async API is the recommended path for mainstream use cases. We would like to hear the TAG perspective on this API split. We are aware that the worker-only sync API design is a rare exception on the web platform.
The WG resolved to drop support for WebGL and focused on WebGPU interoperability.
The CR publication is slated for Q4 2022 so your feedback is the most impactful if it arrives by the end Oct 2022 latest.
We'd prefer the TAG provide feedback as:
💬 leave review feedback as a comment in this issue and @-notify @anssiko
For context, these are the related issues in the WebNN GH repo: