Overview#

Web Hypertext Application Technology Working Group (WHATWG) is a community of Interest for in evolving the web through standards and tests.Web Hypertext Application Technology Working Group was founded by individuals from Apple, the Mozilla Foundation and Opera Software in 2004. Since then, the editor of the Web Hypertext Application Technology Working Group specifications, Ian Hickson, has moved to Google. Chris Wilson of Microsoft was invited but did not join, citing the lack of a patent policy to ensure all specifications can be implemented on a royalty-free basis.

Web Hypertext Application Technology Working Group has a small, invitation-only oversight committee called "Members", which has the power to impeach the editor of the specifications. Anyone can participate as a Contributor by joining the Web Hypertext Application Technology Working Group mailing list.

Web Hypertext Application Technology Working Group is on GitHub at https://github.com/whatwg

Web Hypertext Application Technology Working Group is working on several web standards: Compatibility The Compatibility Standard describes a collection of non-standard (and often vendor-prefixed) CSS properties and DOM APIs that web browsers need to support for compatibility with the de facto web.

• Console - The Console Standard defines APIs for console debugging facilities.
• DOM - The DOM Standard defines the core infrastructure used to define the web.
• Encoding - The Encoding Standard defines how character encodings work on the web.
• Fetch API - The Fetch Standard defines the networking model for resource retrieval on the web.
• Fullscreen API - The Fullscreen API Standard defines how web pages can take over a user's entire screen (at the user's request), e.g. for gaming or to watch a video.
• HTML - The HTML Standard is a kitchen sink full of technologies for the web. It includes the core markup language for the web, HTML, as well as numerous APIs like Web Sockets, Web Workers, localStorage, etc.
• Infra - The Infra Standard aims to define the fundamental concepts upon which standards are built.
• MIME Sniffing - The MIME Sniffing Standard defines algorithms used to determine the type of resources.
• Notifications API - The Notifications API Standard provides an API to display notifications to alert users outside the context of a web page.
• Quirks Mode - The Quirks Mode Standard describes behaviors in CSS and Selectors that are not yet defined in the relevant specifications but that are nonetheless widely implemented.
• Storage - The Storage Standard defines an API for persistent storage and quota estimates, as well as the platform storage architecture.
• Streams - The Streams Standard provides APIs for creating, composing, and consuming streams of data that map efficiently to low-level I/O primitives.
• URL - The URL Standard defines the infrastructure around URLs on the web.
• XMLHttpRequest - The XMLHttpRequest Standard defines the networking API exposed to scripts on the web.

More Information#

There might be more information for this subject on one of the following:

• Document Object Model
• FETCH
• Fetch API
• HTML Living Standard
• WHATWG

---

• [#1] - WHATWG - based on information obtained 2017-10-11-