WHATWG
| Abbreviation | WHATWG |
|---|---|
| Formation | 4 June 2004 |
| Purpose | Developing web standards |
| Membership | Apple Inc., Google LLC, Microsoft Corporation, Mozilla Corporation[1] |
Main organ | Steering Group |
| Website | whatwg |
| HTML |
|---|
| HTML and variants |
| HTML elements and attributes |
|
| Editing |
|
| Character encodings and language |
|
| Document and browser models |
|
| Client-side scripting and APIs |
|
| Graphics and Web3D technology |
|
| Comparisons |
|
The Web Hypertext Application Technology Working Group (WHATWG) was founded by representatives from Apple Inc., the Mozilla Foundation and Opera Software, leading web browser vendors in 2004.[2][3] WHATWG is responsible for maintaining multiple web-related technical standards, including the specifications for the HyperText Markup Language (HTML) and the Document Object Model (DOM).[4][5] The central organizational membership and control of WHATWG – its "Steering Group" – consists of Apple, Mozilla, Google, and Microsoft. WHATWG editors of the specifications ensure correct implementation, in consultation with participants, but ultimately in accordance with Steering Group member objectives.[6]
- ^ "Steering Group Agreement – WHATWG". whatwg.org. WHATWG.
- ^ "FAQ – What is the WHATWG?". WHATWG. 12 February 2010. Retrieved 24 February 2010.
- ^ Reid, Jonathan (2015). "1 - Welcome to HTML5". HTML5 Programmer's Reference. Apress. pp. In section "A Brief History of HTML" -- "The Formation of the WHATWG and the Creation of HTML5". ISBN 9781430263678. Retrieved 2 December 2015.
- ^ Cohen, Nancy; Xplore, Tech. "W3C and WHATWG agreement: Single version of HTML, DOM specifications". techxplore.com. Retrieved 19 May 2023.
- ^ "Alliance gives HTML a stronger future after decade-long struggle to control the web's core tech". CNET. Retrieved 19 May 2023.
- ^ "FAQ – How does the WHATWG work?". WHATWG. 22 November 2012. Retrieved 1 January 2013.
If necessary, controversies are resolved by the Steering Group with members appointed from the organizations that develop browser engines, as a backstop to ensure the editor's judgment aligns with what they will implement.