Initialize a specifications/ directory
#833
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This initializes a basic structure for our previously published specifications, starting with WASI 0.2.0. For the moment all we do is link to the published WIT files, but in the future this will be helpful to clarify which Wasm and/or Wasm Component Model features are required. As well as include additional prose and spec text present that is not necessarily captured by the WIT interfaces.
ricochet
approved these changes
Nov 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This initializes a basic structure for our previously published specifications, starting with WASI 0.2.0. For the moment all we do is link to the published WIT files, but in the future this will be helpful to clarify which Wasm and/or Wasm Component Model features are required. As well as include additional prose and spec text present that is not necessarily captured by the WIT interfaces.
This is the same model followed by the core WebAssembly specification. The main difference being that the core Wasm spec is mainly defined in spectec, while our specification is mainly defined in WIT. We should have further discussion on what exactly specifications should contain and entail, but I'd like to propose doing that as an iterative step after merging the most basic version possible (e.g. this PR).
Thanks!