-
Notifications
You must be signed in to change notification settings - Fork 51
Closed
Labels
Description
βΉοΈ The requirements and status have been updated to reflect Q1'24 CR Snapshot target.
This is a meta issue to track Candidate Recommendation (CR) publication readiness for the Web Neural Network API.
About
A Candidate Recommendation is a document that satisfies the technical requirements of the Working Group that produced it and their dependencies, and has already received wide review. W3C publishes a Candidate Recommendation to
- signal to the wider community that it is time to do a final review
- gather implementation experience
Requirements
Legend:
βͺ Not started
π‘ In progress
π’ Completed
To publish a Candidate Recommendation, in addition to meeting the requirements for advancement a Working Group:
- must show that the specification has met all Working Group requirements, or explain why the requirements have changed or been deferred,
- π’ The document meets the requirements set forth in the WG Charter and satisfies the Use Cases updated with transformers
- π’ The document is considered complete and fit for purpose
- π’ Completed Use modern WebIDL and Infra standard conventionsΒ #210
- π’ Other deliverables: ethical considerations documented
- must document changes to dependencies during the development of the specification,
- π’ Diff in normative references since CR1: no changes
- must document how adequate implementation experience will be demonstrated,
- π’ WPT coverage 93.6%:
- web-platform-tests / wpt.fyi
- WIP: gru, gruCell, lstm, lstmCell, resample2d WPT tests tracker / 2 for remaining opsΒ #338
(https://wpt.fyi/results/webnn?label=experimental&label=master&aligned&view=subtest)
- π’ implementation experience:
- Google Chrome and Microsoft Edge: XNNPACK CPU backend, DirectML GPU backend
- ChromeOS: MLService CPU backend
- JavaScript ML Framework Integrations: ONNX Runtime (release), TensorFlow Lite for TF.js (experimental)
- π’ WPT coverage 93.6%:
- must specify the deadline for comments, which must be at least 28 days after publication, and should be longer for complex documents,
- must show that the specification has received wide review, and
- π‘ Delta wide review tracked in Wide review trackerΒ #239, previously completed in Q1'23 for CR1
- Implementation-specific reviews of interest (informational, not a complete list):
- π’ Chromium security review for accelerated backends
- may identify features in the document as at risk. These features may be removed before advancement to Proposed Recommendation without a requirement to publish a new Candidate Recommendation.
- π’ WebGPU interoperability needs more implementation experience, SOTD updated accordingly to note work-in-progress MLBuffer Update Status of this document for CR SnapshotΒ #532