Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Differences and relation between component, WASI and WIT #59

Open
brucegainx opened this issue Sep 8, 2023 · 3 comments · May be fixed by #64
Open

Differences and relation between component, WASI and WIT #59

brucegainx opened this issue Sep 8, 2023 · 3 comments · May be fixed by #64

Comments

@brucegainx
Copy link

Maybe clarify how all of these are related and overlap a part of the Component model in the text on the WebAssembly Component Model page.

The concepts listed here are clear on that page, but do they fit together and overlap as part of the Component model? Just a sentence or two would so with diagrams.
--Physically, a component is a specially-formatted WebAssembly file. Internally, the component could include multiple traditional ("core") WebAssembly modules, and sub-components, composed via their imports and exports.
--A package is a set of one or more WIT (Wasm Interface Type) files containing a related set of interfaces and worlds.
--WIT is an IDL (interface definition language) for the Component Model.
--The WebAssembly System Interface (WASI) defines a number of packages, including one named wasi:clocks.
@itowlson itowlson linked a pull request Sep 8, 2023 that will close this issue
Open
@kate-goldenring
Copy link
Collaborator

kate-goldenring commented Mar 15, 2024 •
edited
Loading

closing as resolved by #64. Please reopen if we can further clarify this in the documentation That PR is still in progress

@vados-cosmonic
Copy link
Contributor

Hey @kate-goldenring is this still relevant? Did the clarifications pointed out in #64 ever get merged in any form, or does that PR need to be updated?

@kate-goldenring
Copy link
Collaborator

@vados-cosmonic it didn't get merged. Lets revisit that PR to see where we can add this overview of terms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Clarify more concisely how concepts relate to each other itowlson/component-docs
3 participants
@kate-goldenring @brucegainx @vados-cosmonic