wasi-http
E138282
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.
All labels observed (3)
| Label | Occurrences |
|---|---|
| wasi-http canonical | 2 |
| WebAssembly System Interface HTTP | 1 |
| WebAssembly System Interface HTTP proposal | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1210075 — 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-http Context triple: [WebAssembly System Interface, hasComponent, wasi-http]
-
A.
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.
-
B.
WebAssembly JavaScript Interface
The WebAssembly JavaScript Interface is the standard API that defines how JavaScript code interacts with and controls WebAssembly modules within web browsers and other host environments.
-
C.
Deno
Deno is a modern, secure JavaScript and TypeScript runtime created by Ryan Dahl as a successor to Node.js, featuring built-in TypeScript support and a permission-based security model.
-
D.
WebAssembly specification
The WebAssembly specification is a standardized, low-level binary instruction format designed to enable high-performance, portable code execution on the web and other platforms.
-
E.
actix-web
actix-web is a powerful, asynchronous web framework for the Rust programming language, known for its high performance and strong type safety.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: wasi-http Target entity description: 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.
-
A.
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.
-
B.
WebAssembly JavaScript Interface
The WebAssembly JavaScript Interface is the standard API that defines how JavaScript code interacts with and controls WebAssembly modules within web browsers and other host environments.
-
C.
Deno
Deno is a modern, secure JavaScript and TypeScript runtime created by Ryan Dahl as a successor to Node.js, featuring built-in TypeScript support and a permission-based security model.
-
D.
WebAssembly specification
The WebAssembly specification is a standardized, low-level binary instruction format designed to enable high-performance, portable code execution on the web and other platforms.
-
E.
actix-web
actix-web is a powerful, asynchronous web framework for the Rust programming language, known for its high performance and strong type safety.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
WASI proposal
ⓘ
WebAssembly API specification ⓘ |
| abbreviationOf |
wasi-http
self-linksurface differs
ⓘ
surface form:
WebAssembly System Interface HTTP
|
| allows |
implementing HTTP clients in WebAssembly
ⓘ
implementing HTTP servers or handlers in WebAssembly ⓘ |
| category |
WebAssembly networking interface
ⓘ
systems programming interface for WebAssembly ⓘ |
| compatibleWith |
WASI component model
ⓘ
surface form:
WASI Preview 2 component model
|
| defines | standardized HTTP APIs for WebAssembly modules ⓘ |
| designedFor |
WebAssembly modules
ⓘ
edge computing environments ⓘ server-side WebAssembly ⓘ |
| documentationURL | https://github.com/WebAssembly/wasi-http ⓘ |
| ensures | no direct access to host networking without explicit capabilities ⓘ |
| focusesOn | interoperability between WebAssembly components and host HTTP stacks ⓘ |
| fullName |
wasi-http
self-linksurface differs
ⓘ
surface form:
WebAssembly System Interface HTTP proposal
|
| goal |
enable HTTP networking from WebAssembly without host-specific APIs
ⓘ
improve security isolation for HTTP operations in WebAssembly ⓘ provide a portable HTTP interface across different runtimes ⓘ |
| hostLanguageAgnostic | true ⓘ |
| intendedEnvironment |
cloud platforms
ⓘ
edge platforms ⓘ embedded runtimes supporting WebAssembly ⓘ serverless platforms ⓘ |
| name | wasi-http self-link ⓘ |
| partOf | WebAssembly System Interface ⓘ |
| property |
capability-based
ⓘ
host-agnostic ⓘ sandbox-friendly ⓘ secure-by-design ⓘ |
| providesAbstractionOver |
HTTP client implementation details
ⓘ
host networking stack ⓘ |
| relatedTo |
wasi-io
ⓘ
surface form:
WASI I/O
wasi-sockets ⓘ
surface form:
WASI sockets
WASI component model ⓘ
surface form:
WebAssembly component model
WebAssembly runtime environments ⓘ |
| securityProperty |
enforces explicit capability grants for outbound HTTP
ⓘ
prevents arbitrary socket access by default ⓘ |
| standardizedBy |
WASI community group
ⓘ
WebAssembly Community Group ⓘ |
| status | proposal ⓘ |
| supportsOperation |
HTTP headers handling
ⓘ
HTTP request ⓘ HTTP response ⓘ HTTP status codes handling ⓘ streaming HTTP bodies ⓘ |
| supportsProtocol |
HTTP
ⓘ
HTTPS ⓘ |
| usesModel | WASI capability-based security model ⓘ |
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-http Description of subject: 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.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.