WebAssembly 2024-10-07 > 2024-10-31 #75
Labels
LC
Working Draft approaching CR.
pending
This issue needs to get a reviewer assigned to it
REVIEW REQUESTED
In the issue title above add the document name followed by the date of this request, then the date of your proposed deadline for comments.
name of spec to be reviewed: WebAssembly Core 2.0, WebAssembly JavaScript Interface 2.0 , WebAssembly Web API 2.0
URL of spec: https://www.w3.org/TR/wasm-core-2/, https://www.w3.org/TR/wasm-js-api-2/, https://www.w3.org/TR/wasm-web-api-2/
Does your document have an in-line Security Considerations section, ideally one separate from the Privacy Considerations? If not, corrrect that before proceeding further. Yes
What and when is your next expected transition? CR for 2.0, to transition as soon as reviews are finished (the date provided is not a hard deadline)
What has changed since any previous review? The specifications contain change history sections summarizing additions to each spec (core, JS, Web)
Please point to the results of your own self-review (see https://w3ctag.github.io/security-questionnaire/) Self-review of security and privacy questionnaire for 2.0 CR transition WebAssembly/spec#1830
Where and how to file issues arising? https://github.com/WebAssembly/spec/issues
Pointer to any explainer for the spec? The spec as a whole does not have an explainer but see below.
Other comments:
This is a request for transition for version 2.0 of all 3 WebAssembly specifications, namely the core spec, which defines the core code format and semantics;
the JS API specification, which provides a JavaScript API for interacting with WebAssembly; and the Web API specification, which describes the integration of WebAssembly with the broader web platform.
For review convenience, here is a list of the explainers for the proposals that have gone into 2.0, compared to 1.0 (currently in REC state). These are informal descriptions of the proposed changes and are not canonical, but describe an overview of the feature and could be useful in determining whether there is anything of interest for horizontal reviewers.
Note also that the specifications contain change history sections summarizing additions to each spec (core, JS, Web)
listing and summarizing additions since version 1.0. The table summarizes the effect on the JS spec. The Web spec is unchanged since 1.0
The text was updated successfully, but these errors were encountered: