Do we need a new term for a WASI "module"? about wasi HOT 9 CLOSED

I like the idea of calling them the WASI API.

from wasi.

• WASI support
• WASI environment
• WASI platform
• WASI host

from wasi.

Alternatively we can continue to use WASI module to refer to the system components and come up with a new name for a program that uses WASI?

from wasi.

• interface
• WAD
• WAM
• WAI
• WASAPI

from wasi.

WASI Extensions? The same route as RISC-V and Vulkan?

Something like WASI-64INF => 64-bit WASI with IPC, Network and Floating-point extensions
Or just like OpenGL/Vulkan WASI_IPC, WASI_NETWORK, WASI_FLOATING_POINT

from wasi.

I was asking about the core APIs. Right now we seem to be calling them "modules" but that seems confusing.

from wasi.

I've taken to using the term "API module" when there's a need to disambiguate, and it seems to work well.

from wasi.

I think the original premise of this issue no longer holds: "Since WASI APIs are not provided by WebAssembly modules but by the embedder directly...". These days my understanding is that folks are very excited about virtualization and really want this statement to be false.

So perhaps this whole issue can just be closed?

from wasi.

Good point :-).

from wasi.