wasi-sockets
E581953
wasi-sockets is a WebAssembly System Interface (WASI) proposal and API module that defines a capability-based, portable networking interface for using sockets in WebAssembly applications.
All labels observed (2)
| Label | Occurrences |
|---|---|
| wasi-sockets canonical | 2 |
| WASI sockets | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T6247920 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: wasi-sockets Context triple: [wasi-io, relatedTo, wasi-sockets]
-
A.
wasi-http
wasi-http is a WebAssembly System Interface (WASI) proposal that defines standardized APIs for performing HTTP operations from WebAssembly modules in a secure, host-agnostic way.
-
B.
wasi-io
wasi-io is a WebAssembly System Interface (WASI) component that defines standardized I/O APIs for handling streams, files, and related input/output operations in WebAssembly environments.
-
C.
wasi-cli
wasi-cli is a command-line interface component for the WebAssembly System Interface (WASI) that enables running and interacting with WASI-compatible WebAssembly modules from the terminal.
-
D.
WebAssembly System Interface
The WebAssembly System Interface (WASI) is a modular, portable set of system APIs that allows WebAssembly programs to interact safely and consistently with operating system features like files, networking, and clocks across different platforms.
-
E.
WASI
WASI is a modular system interface designed to let WebAssembly programs safely and portably interact with operating system features like files, networking, and clocks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: wasi-sockets Target entity description: wasi-sockets is a WebAssembly System Interface (WASI) proposal and API module that defines a capability-based, portable networking interface for using sockets in WebAssembly applications.
-
A.
wasi-http
wasi-http is a WebAssembly System Interface (WASI) proposal that defines standardized APIs for performing HTTP operations from WebAssembly modules in a secure, host-agnostic way.
-
B.
wasi-io
wasi-io is a WebAssembly System Interface (WASI) component that defines standardized I/O APIs for handling streams, files, and related input/output operations in WebAssembly environments.
-
C.
wasi-cli
wasi-cli is a command-line interface component for the WebAssembly System Interface (WASI) that enables running and interacting with WASI-compatible WebAssembly modules from the terminal.
-
D.
WebAssembly System Interface
The WebAssembly System Interface (WASI) is a modular, portable set of system APIs that allows WebAssembly programs to interact safely and consistently with operating system features like files, networking, and clocks across different platforms.
-
E.
WASI
WASI is a modular system interface designed to let WebAssembly programs safely and portably interact with operating system features like files, networking, and clocks.
- F. None of above. chosen
Statements (43)
| Predicate | Object |
|---|---|
| instanceOf |
WASI proposal
ⓘ
WebAssembly networking API module ⓘ capability-based networking interface ⓘ |
| aimsTo |
abstract platform-specific socket APIs
ⓘ
avoid ambient authority in networking ⓘ provide a consistent networking API for WebAssembly ⓘ |
| compatibleWith |
multiple WebAssembly engines
ⓘ
multiple host operating systems ⓘ |
| constrains | network access via explicit capabilities ⓘ |
| designedFor |
WebAssembly runtimes
ⓘ
portable networking across platforms ⓘ sandboxed execution environments ⓘ |
| documentedAs | WASI sockets proposal ⓘ |
| enables |
creating network connections from WebAssembly modules
ⓘ
listening for incoming connections in WebAssembly ⓘ portable networking across operating systems ⓘ sending and receiving data over sockets in WebAssembly ⓘ |
| followsPrinciple |
capability-based security model
ⓘ
least privilege ⓘ |
| hasProperty |
designed for determinism where possible
ⓘ
host-agnostic design ⓘ language-agnostic API surface ⓘ sandbox-friendly networking ⓘ |
| hasPurpose |
define a portable sockets interface for WebAssembly applications
ⓘ
enable networking in WebAssembly environments ⓘ |
| partOf | WebAssembly System Interface NERFINISHED ⓘ |
| relatedTo |
WASI preview specifications
ⓘ
WebAssembly component model NERFINISHED ⓘ wasi-filesystem NERFINISHED ⓘ wasi-http NERFINISHED ⓘ |
| standardizedBy | WASI community group NERFINISHED ⓘ |
| supportsConcept |
TCP networking
ⓘ
UDP networking ⓘ asynchronous operations ⓘ capability-based security ⓘ non-blocking I/O ⓘ resource handles ⓘ sockets ⓘ |
| targetEnvironment |
WebAssembly modules running outside the browser
ⓘ
server and edge WebAssembly platforms ⓘ |
| usedBy |
WebAssembly applications requiring network access
ⓘ
edge computing WebAssembly runtimes ⓘ server-side WebAssembly workloads ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: wasi-sockets Description of subject: wasi-sockets is a WebAssembly System Interface (WASI) proposal and API module that defines a capability-based, portable networking interface for using sockets in WebAssembly applications.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.