CR Request for WebAssembly Core - wasm-core

[dschuff]

Document title, URLs, estimated publication date

WebAssembly Core Specification, https://www.w3.org/TR/wasm-core-2/
Estimated publication date: ASAP

Abstract

This document describes release 2.0 of the core WebAssembly standard, a safe, portable, low-level code format designed for efficient execution and compact representation.

This is part of a collection of related documents: the Core WebAssembly Specification, the WebAssembly JS Interface, and the WebAssembly Web API.

Status

WD: existing status can be seen in the doc at the link above
Status for all the various states (including what the CR status will be) can be found in our Bikeshed boilerplate
files: https://github.com/speced/bikeshed-boilerplate/tree/main/boilerplate/wasm

Link to group's decision to request transition

https://github.com/WebAssembly/meetings/blob/main/main/2024/WG-06-12.md

Changes

Changes since 1.0 listed at https://www.w3.org/TR/wasm-core-2/#change-history
The following extension proposals have advanced from the CG:
Sign extension instructions; Non-trapping float-to-int conversions; multi-value block types and function results;
reference types, table instructions, and multiple tables; bulk memory and table instructions; SIMD vector instructions.

Requirements satisfied

Dependencies met (or not)

Dependencies are unlikely to change.

Wide Review

Tracking issue for wide review: WebAssembly/spec#1804
Email announcement at https://lists.w3.org/Archives/Public/public-webassembly/2024Jul/0000.html

Issues addressed

Issues are tracked at https://github.com/WebAssembly/spec/issues

Formal Objections

None raised

Implementation

All of these features have been implemented in all 3 major browser engines. A full feature matrix including version
information can be found at https://webassembly.org/features/

Patent disclosures

[TODO: link to IPP]

[dschuff]

/cc @sideshowbarker @lukewagner @rossberg

[plehegar]

It's not clear if horizontal reviews for substantive changes since the previous was done. Were the horizontal groups asked?

[sideshowbarker]

On behalf of the WebAssembly Working Group, I formally request transition of all the WebAssembly specs to CR.

It's not clear if horizontal reviews for substantive changes since the previous was done. Were the horizontal groups asked?

We have now completed all obligations from horizontal review as described at https://www.w3.org/Guide/documentreview/.

I’m not sure how we are expected to document that fact. I’ve looked through all the available guideline docs I could find on how to do transition requests, but I’ve not been able to find anything that describes exactly what we’re supposed to do after we’ve completed all the horizontal-review steps.

Regardless, at this point, I’d like to go ahead here and now formally request transition of all the WebAssembly specs to CR.

[sideshowbarker]

@plehegar friendly ping

On behalf of the WebAssembly Working Group, I formally request transition of all the WebAssembly specs to CR.

[plehegar]

Approved, with the understanding #1843 will be addressed in the next version.

We're assuming the CR exit might come quickly since all features already have implementation.

[sideshowbarker]

@plehegar Thanks much. What’s the next step now? We’re set up to auto-publish/push the CR versions to TR directly ourselves — but I guess in order to do that, this issue needs to be closed first?

I assume I need to work with the comm team to draft the CR announcement? Assuming I can get that done quickly, then I guess we’d be able to publish and announce on Tuesday? (If it’s still the case that we only do publication announcements on Tuesdays and Thursdays)

[plehegar]

Yes, I believe you are correct