- From: <sysbot+notifier@w3.org>
- Date: Wed, 20 Nov 2024 17:04:51 +0000
- To: public-transition-announce@w3.org
This is a transition request for a Candidate Recommendation CR Request for WebGPU and WebGPU Shading Language - webgpu / WGSL from https://github.com/w3c/transitions/issues/676 # Document title, URLs, estimated publication date Two specs to transition: - WebGPU: https://www.w3.org/TR/webgpu/ - WebGPU Shading Language: https://www.w3.org/TR/WGSL/ Note: The source of the specifications to publish as CR is maintained in a dedicated [`milestone-0` branch](https://github.com/gpuweb/gpuweb/tree/milestone-0) in the repository. The `main` branch contains further updates that will not be part of this snapshot. No specific deadline for the publication date. Whenever transition is approved. # Abstract - WebGPU: "WebGPU exposes an API for performing operations, such as rendering and computation, on a Graphics Processing Unit." - WGSL: "Shading language for WebGPU." # Status - WebGPU: https://www.w3.org/TR/webgpu/#sotd - WGSL: https://www.w3.org/TR/WGSL/#sotd The group intends to switch to the "Living Recommendations" mode for both specifications once the [proposed charter](https://www.w3.org/2024/11/gpuweb-charter-review.html) has been reviewed by the AC and approved. If the specifications get published under the current charter and exit criteria need to be specified, the idea would be to use regular exit criteria, like: - The API/shading language is implementable on top of modern GPU system APIs, such as Microsoft's Direct3D 12, Apple's Metal, and Khronos's Vulkan. - The API/shading language has at least two independent, interoperable implementations of every feature defined in the specification, where interoperability can be verified by passing open test suites, and two or more implementations interoperating with each other. - The API/shading language has an open test suite of every feature defined in the specification. Minimal CR duration: 2 months. # Link to the group's decision to request transition See [resolution during last F2F](https://docs.google.com/document/d/1FlVeiqRzx5t-9z03Ocx7_gw-lPpysUaw_83xofJyxQQ/edit?tab=t.0#bookmark=id.v9yzbqjs47az). The group has resolved pending "milestone 0" since the F2F, also see the [CR tracking issue](https://github.com/gpuweb/gpuweb/issues/3107) # Changes First CR # Requirements satisfied # Dependencies met (or not) Normative dependencies are established standards with one exception: WebGPU specifies the integration with WebCodecs to process media frames, and WebCodecs is still a Working Draft at this stage. The `VideoFrame` interface at the core of this integration is stable and implemented across browsers already. # Wide Review - For horizontal reviews, see https://github.com/gpuweb/gpuweb/issues/2531 - For messages sent to relevant groups, see https://github.com/gpuweb/gpuweb/issues/3107#issuecomment-1192723179 An issue was raised during PING review on the fingerprinting surface of the API (https://github.com/gpuweb/gpuweb/issues/3101). The group reduced the fingerprinting surface to 5 bits and documented the mitigations that were put in place and the rationale in the issue. This issue is still under discussion in PING. # Issues addressed All [issues at milestone 0](https://github.com/gpuweb/gpuweb/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Milestone+0%22) have been addressed. # Formal Objections None # Implementation Implementations of WebGPU and WGSL are shipping or are about to ship in major browser codebases: - shipped in Chromium (behind a flag on Linux) - behind flags in Firefox and WebKit The group maintains a [conformance test suite](https://github.com/gpuweb/cts) (no implementation report available today) # Patent disclosures https://www.w3.org/groups/wg/gpu/ipr/ -- This email was generated automatically using https://github.com/w3c/transition-issues-bot
Received on Wednesday, 20 November 2024 17:04:56 UTC