HTTPAPI is, as you can probably figure out from the WG name, about enabling applications that use HTTP to provide services over the Web. This includes things like API being defined via things like OpenAPI, GraphQL, etc. Messages are typically JSON. Interactions are usually machine-to-machine, which means we often focus on error reporting, how to find API’s (catalogs), and indications that an API is being deprecated, or has rate limits.
Our active drafts address those points. Also, APIs often have an “API key” in the client request, so we are looking at what to do if HTTP, not HTTPS, is used. (Browsers warn if you send a password field in a form over a plaintext channel), as well as registration of API-oriented media types, machine-useful hints on links, and so on.
-- Witarea mailing list -- [email protected] To unsubscribe send an email to [email protected]
