HTML5

Quality 0.50 · 2 views · Updated 2 months ago

Fifth and previous version of HyperText Markup Language

title: "HTML5" type: doc version: 1 created: 2026-02-28 author: "Wikipedia contributors" status: active scope: public tags: ["html5", "2014-software", "xml-based-standards"] description: "Fifth and previous version of HyperText Markup Language" topic_path: "technology/web" source: "https://en.wikipedia.org/wiki/HTML5" license: "CC BY-SA 4.0" wikipedia_page_id: 0 wikipedia_revision_id: 0

::summary Fifth and previous version of HyperText Markup Language ::

::data[format=table title="Infobox file format"]

FieldValue
nameHTML5
iconHTML5-logo.svg
icon_size130px
captionHTML5 official logo, introduced on 18 January 2011
extension.html, .htm
mimetext/html
developer
released
latest release version5.2 (Second revision)
latest release date
standardHTML 5.2
extended_fromHTML4, XHTML1, DOM2 HTML
extended_toHTML LS
openYes
type_codeTEXT
uniform_typepublic.html
ownerW3C
genreMarkup language
::

| name = HTML5 | icon = HTML5-logo.svg | icon_size = 130px | caption = HTML5 official logo, introduced on 18 January 2011 | extension = .html, .htm | mime = text/html | developer = | released = | latest release version = 5.2 (Second revision) | latest release date = | standard = HTML 5.2 | extended_from = HTML4, XHTML1, DOM2 HTML | extended_to = HTML LS | open = Yes | type_code = TEXT | uniform_type = public.html | owner = W3C | genre = Markup language HTML5 (Hypertext Markup Language 5) is a markup language used for structuring and presenting hypertext documents on the World Wide Web. It was the fifth and final major HTML version that is now a retired World Wide Web Consortium (W3C) recommendation. The current specification is known as the HTML Living Standard. It is maintained by the Web Hypertext Application Technology Working Group (WHATWG), a consortium of the major browser vendors (Apple, Google, Mozilla, and Microsoft).

HTML5 was first released in a public-facing form on 22 January 2008, with a major update and "W3C Recommendation" status in October 2014. Its goals were to improve the language with support for the latest multimedia and other new features; to keep the language both easily readable by humans and consistently understood by computers and devices such as web browsers, parsers, etc., without XHTML's rigidity; and to remain backward-compatible with older software. HTML5 is intended to subsume not only HTML 4 but also XHTML1 and even the DOM Level 2 HTML itself.

HTML5 includes detailed processing models to encourage more interoperable implementations; it extends, improves, and rationalizes the markup available for documents and introduces markup and application programming interfaces (APIs) for complex web applications. For the same reasons, HTML5 is also a candidate for cross-platform mobile applications because it includes features designed with low-powered devices in mind.

Many new syntactic features are included. To natively include and handle multimedia and graphical content, the new , and elements were added; expandable sections are natively implemented through and rather than depending on CSS or JavaScript; and support for scalable vector graphics (SVG) content and MathML for mathematical formulas was also added. To enrich the semantic content of documents, new page structure elements such as , , , , , , , and are added. New attributes were introduced, some elements and attributes were removed, and others such as , , and were changed, redefined, or standardized. The APIs and Document Object Model (DOM) are now fundamental parts of the HTML5 specification, and HTML5 also better defines the processing for any invalid documents.

History

The Web Hypertext Application Technology Working Group (WHATWG) began work on the new standard in 2004. At that time, HTML 4.01 had not been updated since 2000, and the World Wide Web Consortium (W3C) was focusing future developments on XHTML 2.0. In 2009, the W3C allowed the XHTML 2.0 Working Group's charter to expire and decided not to renew it.

The Mozilla Foundation and Opera Software presented a position paper at a World Wide Web Consortium workshop in June 2004, focusing on developing technologies that are backward-compatible with existing browsers, including an initial draft specification of Web Forms 2.0. The workshop concluded with a vote—8 for, 14 against—for continuing work on HTML. Immediately after the workshop, WHATWG was formed to start work based upon that position paper, and a second draft, Web Applications 1.0, was also announced. The two specifications were later merged to form HTML5. The HTML5 specification was adopted as the starting point of the work of the new HTML working group of the W3C in 2007.

WHATWG's Ian Hickson (Google) and David Hyatt (Apple) produced W3C's first public working draft of the specification on 22 January 2008.

Many web browsers released after 2009 support HTML5, including Google Chrome 3.0, Safari 3.1, Firefox 3.5, Opera 10.5, Internet Explorer 9 and later.

"Thoughts on Flash"

Main article: Thoughts on Flash

While some features of HTML5 are often compared to Adobe Flash, the two technologies are very different. Both include features for playing audio and video within web pages, and for using vector graphics. However, HTML5 on its own cannot be used for animation or interactivity – it must be supplemented with CSS3 or JavaScript. There are many Flash capabilities that have no direct counterpart in HTML5 (see Comparison of HTML5 and Flash). HTML5's interactive capabilities became a topic of mainstream media attention around April 2010 after Apple Inc.'s then-CEO Steve Jobs issued a public letter titled "Thoughts on Flash" in which he concluded that "Flash is no longer necessary to watch video or consume any kind of web content" and that "new open standards created in the mobile era, such as HTML5, will win". This sparked a debate in web development circles suggesting that, while HTML5 provides enhanced functionality, developers must consider the varying browser support of the different parts of the standard as well as other functionality differences between HTML5 and Flash. In early November 2011, Adobe announced that it would discontinue the development of Flash for mobile devices and reorient its efforts in developing tools using HTML5. On 25 July 2017, Adobe announced that both the distribution and support of Flash would cease by the end of 2020. Adobe itself officially discontinued Flash on 31 December 2020 and all Flash content was blocked from running in Flash Player as of 12 January 2021.

Last call, candidacy, and recommendation stages

On 14 February 2011, the W3C extended the charter of its HTML Working Group with clear milestones for HTML5. In May 2011, the working group advanced HTML5 to "Last Call", an invitation to communities inside and outside W3C to confirm the technical soundness of the specification. The W3C developed a comprehensive test suite to achieve broad interoperability for the full specification by 2014, which was the target date for recommendation.{{cite web |url=https://www.w3.org/2011/02/htmlwg-pr.html |title=W3C Confirms May 2011 for HTML5 Last Call, Targets 2014 for HTML5 Standard |publisher= World Wide Web Consortium |access-date=18 February 2011 |date=14 February 2011}} In January 2011, the WHATWG renamed its "HTML5" specification HTML Living Standard. The W3C nevertheless continued its project to release HTML5.

In July 2012, WHATWG and W3C decided on a degree of separation. W3C will continue the HTML5 specification work, focusing on a single definitive standard, which is considered a "snapshot" by WHATWG. The WHATWG organization continues its work with HTML5 as a "living standard". The concept of a living standard is that it is never complete and is always being updated and improved. New features can be added but functionality will not be removed.

In December 2012, W3C designated HTML5 as a Candidate Recommendation. The criterion for advancement to W3C Recommendation is "two 100% complete and fully interoperable implementations".{{cite web |url=http://wiki.whatwg.org/wiki/FAQ#What.27s_this_I_hear_about_2022.3F |title= When Will HTML5 Be Finished? |work=FAQ |publisher=WHAT Working Group |access-date=29 November 2009}}

On 16 September 2014, W3C moved HTML5 to Proposed Recommendation. On 28 October 2014, HTML5 was released as a W3C Recommendation, bringing the specification process to completion. On 14 December 2017, HTML 5.2 was released as a W3C Recommendation.

Retirement

The W3C retired HTML5 on 27 March 2018. Additionally, the retirement included HTML 4.0, HTML 4.01, XHTML 1.0, and XHTML 1.1. HTML 5.1, HTML 5.2 and HTML 5.3 were all retired on 28 January 2021, in favour of the HTML living standard.

Timeline

The combined timelines for the W3C recommendations of HTML5, HTML 5.1, HTML 5.2 and HTML 5.3:

::data[format=table] | Version | First draft | Candidate recommendation | Recommendation | Retired | |---|---|---|---|---| | HTML5 | 1 May 2007 | 17 December 2012 | 28 October 2014 | 27 March 2018 | | HTML 5.1 | 17 December 2012 | 21 June 2016 | 1 November 2016 | 28 January 2021 | | HTML 5.1 2nd Edition | | 20 June 2017 | 3 October 2017 | | | HTML 5.2 | 18 August 2016 | 8 August 2017 | 14 December 2017 | 28 January 2021 | | HTML 5.3 | url=https://www.w3.org/TR/2017/WD-html53-20171214/|title=HTML 5.3|date=14 December 2017|id=W3C First Public Working Draft|publisher=World Wide Web Consortium}} | | | 28 January 2021 | ::

W3C and WHATWG conflict

The W3C ceded authority over the HTML and DOM standards to WHATWG on 28 May 2019, as it considered that having two standards is harmful. The HTML Living Standard is now authoritative. However, W3C will still participate in the development process of HTML.

Before the ceding of authority, W3C and WHATWG had been characterized as both working together on the development of HTML5, and yet also at cross purposes ever since the July 2012 split. The W3C "HTML5" standard was snapshot-based (HTML5, HTML 5.1, etc.) and static, while the WHATWG "HTML living standard" is continually updated. The relationship had been described as "fragile", even a "rift", and characterized by "squabbling".

In at least one case, namely the permissible content of the element, the two specifications directly contradicted each other ( with the W3C definition allowing a broader range of uses than the WHATWG definition.

The "Introduction" section in the WHATWG spec (edited by Ian "Hixie" Hickson) is critical of W3C, e.g. "Note: Although we have asked them to stop doing so, the W3C also republishes some parts of this specification as separate documents." In its "History" subsection it portrays W3C as resistant to Hickson's and WHATWG's original HTML5 plans, then jumping on the bandwagon belatedly (though Hickson was in control of the W3C HTML5 spec, too). Regardless, it indicates a major philosophical divide between the organizations:

The two entities signed an agreement to work together on a single version of HTML on 28 May 2019.

Differences between the two standards

In addition to the contradiction in the element mentioned above, other differences between the two standards include at least the following, : ::data[format=table title=""]

FeatureW3CWHATWG
Site paginationSingle page version (allows global search of contents)
Chaptersurl=https://html.spec.whatwg.org/#microdata
Global attributesurl=https://www.w3.org/TR/html/dom.html#global-attributestitle=HTML 5.2, § 3.2.5. Global attributes
Chapter Elements of HTML§4.13 Custom elements
Elements, (See compatibility notes below.), , `` (See compatibility notes below.)
§ ``§4.2.5.4. Other pragma directives, based on deprecated WHATWG procedure.
§ Sections§ 4.3.11.2 Sample outlines
Structured dataRecommends RDFa (code examples, separate specs, no special attributes).Recommends Microdata (code examples, spec chapter, special attributes).
::

The following table provides data from the Mozilla Development Network on compatibility with major browsers, , of HTML elements unique to one of the standards: ::data[format=table]

ElementStandardCompatibilityNote
``W3CAll browsers, except Edge
``W3CAll browsers, except IE
``WHATWGAll browsers"[Since] the HTML outline algorithm is not implemented in any browsers ... the `` semantics are in practice only theoretical."
``WHATWGAll browsers
``WHATWGAll browsers
::

Features and APIs

The W3C proposed a greater reliance on modularity as a key part of the plan to make faster progress, meaning identifying specific features, either proposed or already existing in the spec, and advancing them as separate specifications. Some technologies that were originally defined in HTML5 itself are now defined in separate specifications:

  • HTML Working Group — HTML Canvas 2D Context;
  • Immersive Web Working Group — WebXR Device API, WebXR Gamepads Module, WebXR Augmented Reality Module, and others;
  • Web Apps Working Group — Web Messaging, Web workers, Web storage, WebSocket, Server-sent events, Web Components (this was not part of HTML5, though); the Web Applications Working Group was closed in October 2015 and its deliverables transferred to the Web Platform Working Group (WPWG).
  • IETF HyBi Working Group — WebSocket Protocol;
  • WebRTC Working Group — WebRTC;
  • Web Media Text Tracks Community Group — WebVTT.

Some features that were removed from the original HTML5 specification have been standardized separately as modules, such as Microdata and Canvas. Technical specifications introduced as HTML5 extensions such as Polyglot markup have also been standardized as modules. Some W3C specifications that were originally separate specifications have been adapted as HTML5 extensions or features, such as SVG. Some features that might have slowed down the standardization of HTML5 were or will be standardized as upcoming specifications, instead.

Features

Markup

HTML5 introduces elements and attributes that reflect typical usage on modern websites. Some of them are semantic replacements for common uses of generic block () and inline () elements, for example (website navigation block), (usually referring to bottom of web page or to last lines of HTML code), or and instead of . Some deprecated elements from HTML 4.01 have been dropped, including purely presentational elements such as and , whose effects have long been superseded by the more capable Cascading Style Sheets. | url = https://www.w3.org/TR/html5/obsolete.html | title = 11 Obsolete features – HTML5 | publisher = W3C | access-date = 11 March 2014}} There is also a renewed emphasis on the importance of client-side JavaScript used to create dynamic web pages.

The HTML5 syntax is no longer based on SGML despite the similarity of its markup. It has, however, been designed to be backward-compatible with common parsing of older versions of HTML. It comes with a new introductory line that looks like an SGML document type declaration, `, which triggers the standards-compliant rendering mode. Since 5 January 2009, HTML5 also includes Web Forms 2.0, a previously separate WHATWG specification.

New APIs

::figure[src="https://upload.wikimedia.org/wikipedia/commons/7/7f/HTML5_APIs_and_related_technologies_taxonomy_and_status.svg" caption="978-0-9833867-2-8}}"] ::

In addition to specifying markup, HTML5 specifies scripting application programming interfaces (APIs) that can be used with JavaScript. Existing Document Object Model (DOM) interfaces are extended and de facto features documented. There are also new APIs, such as:

Not all of the above technologies are included in the W3C HTML5 specification, though they are in the WHATWG HTML specification. Some related technologies, which are not part of either the W3C HTML5 or the WHATWG HTML specification, are as follows. The W3C publishes specifications for these separately:

  • Geolocation;
  • IndexedDB – an indexed hierarchical key-value store (formerly WebSimpleDB);
  • File – an API intended to handle file uploads and file manipulation;
  • Directories and System – an API intended to satisfy client-side-storage use cases not well served by databases;
  • File Writer – an API for writing to files from web applications;
  • Web Audio – a high-level JavaScript API for processing and synthesizing audio in web applications;
  • ClassList.
  • Web cryptography API
  • WebRTC
  • Web SQL Database – a local SQL Database (no longer maintained);

HTML5 cannot provide animation within web pages. Additional JavaScript or CSS3 is necessary for animating HTML elements. Animation is also possible using JavaScript and HTML 4, and within SVG elements through SMIL, although browser support of the latter remains uneven .

XHTML5 (XML-serialized HTML5)

XML documents must be served with an XML Internet media type (often called "MIME type") such as application/xhtml+xml or application/xml, and must conform to strict, well-formed syntax of XML. XHTML5 is simply XML-serialized HTML5 data (that is, HTML5 constrained to XHTML's strict requirements, e.g., not having any unclosed tags), sent with one of XML media types. HTML that has been written to conform to both the HTML and XHTML specifications and therefore produces the same DOM tree whether parsed as HTML or XML is known as polyglot markup.

There is no DTD for XHTML5.

Error handling

HTML5 is designed so that old browsers can safely ignore new HTML5 constructs. In contrast to HTML 4.01, the HTML5 specification gives detailed rules for lexing and parsing, with the intent that compliant browsers will produce the same results when parsing incorrect syntax. Although HTML5 now defines a consistent behavior for "tag soup" documents, those documents do not conform to the HTML5 standard.

Popularity

According to a report released on 30 September 2011, 34 of the world's top 100 Web sites were using HTML5the adoption led by search engines and social networks. Another report released in August 2013 has shown that 153 of the Fortune 500 U.S. companies implemented HTML5 on their corporate websites.

Since 2014, HTML5 is at least partially supported by most popular layout engines.

Differences from HTML 4.01 and XHTML 1.x

The following is a cursory list of differences and some specific examples.

  • New parsing rules: oriented towards flexible parsing and compatibility; not based on SGML
  • Ability to use inline SVG and MathML in text/html
  • New elements: article, aside, audio, bdi, canvas, command, data, datalist, details, embed, figcaption, figure, footer, header, keygen, mark, meter, nav, output, progress, rp, rt, [ruby](ruby-character-html), section, source, summary, time, track, video, wbr
  • New types of form controls: dates and times, email, url, search, number, range, tel, color
  • New attributes: charset (on meta), async (on script)
  • Global attributes (that can be applied for every element): id, tabindex, hidden, data-* (custom data attributes)
  • Deprecated elements will be dropped altogether: acronym, applet, basefont, big, center, dir, font, frame, frameset, isindex, noframes, strike, tt

W3C Working Group publishes "HTML5 differences from HTML 4",{{cite web |url=https://www.w3.org/TR/html5-diff/ |title=HTML5 Differences from HTML4 |work=FAQ |publisher= World Wide Web Consortium |date=9 December 2014 |access-date=2 March 2018}} which provides a complete outline of additions, removals and changes between HTML5 and HTML4.

Logo

::figure[src="https://upload.wikimedia.org/wikipedia/commons/6/6e/HTML5-logo.svg" caption="The W3C HTML5 logo"] ::

On 18 January 2011, the W3C introduced a logo to represent the use of or interest in HTML5. Unlike other badges previously issued by the W3C, it does not imply validity or conformance to a certain standard. As of 1 April 2011, this logo is official.

When initially presenting it to the public, the W3C announced the HTML5 logo as a "general-purpose visual identity for a broad set of open web technologies, including HTML5, CSS, SVG, WOFF, and others". Some web standard advocates, including The Web Standards Project, criticized that definition of "HTML5" as an umbrella term, pointing out the blurring of terminology and the potential for miscommunication. Three days later, the W3C responded to community feedback and changed the logo's definition, dropping the enumeration of related technologies. The W3C then said the logo "represents HTML5, the cornerstone for modern Web applications".

Digital rights management

Industry players including the BBC, Google, Microsoft, and Apple Inc. have been lobbying for the inclusion of Encrypted Media Extensions (EME),{{cite web |title=Netflix coming to HTML5 just as soon as the DRM ducks are in a row |url=https://arstechnica.com/information-technology/2013/04/netflix-coming-to-html5-just-as-soon-as-the-drm-ducks-are-in-a-row/ |publisher=Ars Technica |date=16 April 2013 |first=Peter |last=Bright |title=DRM in HTML5 |url=http://manu.sporny.org/2013/drm-in-html5/ |date=26 January 2013 |first=Manu |last=Sporny |access-date=5 June 2013 |archive-date=2 June 2017 |archive-url=https://web.archive.org/web/20170602181658/http://manu.sporny.org/2013/drm-in-html5/ |url-status=dead |title=Tell W3C: We don't want the Hollyweb |url=https://www.defectivebydesign.org/no-drm-in-html5 |publisher=Free Software Foundation |date=May 2013 |title=HTML5 webpage locks 'would stifle innovation' |url=https://www.bbc.co.uk/news/technology-22714209 |publisher=BBC News |date=30 May 2013 | url = https://www.eff.org/deeplinks/2013/10/lowering-your-standards | title = Lowering Your Standards: DRM and the Future of the W3C | first = Danny | last = O'Brien | publisher = Electronic Frontier Foundation | date = 2 October 2013 | access-date = 3 October 2013

Manu Sporny, a member of the W3C, said that EME would not solve the problem it was supposed to address.{{cite web | url = http://manu.sporny.org/2013/drm-in-html5/ | title = DRM in HTML5 | first = Manu | last = Sporny | work = The Beautiful, Tormented Machine | publisher = Manu Sporny | date = 26 January 2013 | access-date = 16 May 2014 | archive-url = https://web.archive.org/web/20140425044032/http://manu.sporny.org/2013/drm-in-html5/ | archive-date=25 April 2014 Opponents point out that EME itself is just an architecture for a DRM plug-in mechanism.{{cite web |url = http://www.webmonkey.com/2013/02/drm-for-the-web-say-it-aint-so/ |title = DRM for the Web? Say It Ain't So |first = Scott |last = Gilbertson |work = Webmonkey |date = 12 February 2013 |access-date = 21 March 2013 |archive-url = https://web.archive.org/web/20130324134750/http://www.webmonkey.com/2013/02/drm-for-the-web-say-it-aint-so |archive-date = 24 March 2013 |url-status = dead

The initial enablers for DRM in HTML5 were Google{{cite web | url = http://googlechromereleases.blogspot.be/2013/02/stable-channel-update-for-chrome-os_21.html | title = Release notes for Google Chrome 25.0.1364.87 | url = http://techblog.netflix.com/2013/06/html5-video-in-ie-11-on-windows-81.html | title = HTML5 Video in IE 11 on Windows 8.1 | date = 18 April 2017

As of December 2023, the W3C defended their formation of the EME standard, stating: "Encrypted Media Extensions (EME) brings greater interoperability, better privacy, security, accessibility and user experience in viewing movies and TV on the Web".

References

References

  1. (17 November 2009). "Mac Developer Library: System-Declared Uniform Type Identifiers". [[Apple Inc..
  2. (28 October 2014). "HTML5 is a W3C recommendation". [[World Wide Web Consortium]].
  3. "HTML5 Differences from HTML4". [[W3C]].
  4. (19 October 2010). "HTML5 Differences from HTML4". [[W3C]].
  5. (14 December 2017). "HTML 5.2 W3C Recommendation". [[W3C]].
  6. "HTML 4 Errata". [[World Wide Web Consortium]].
  7. "Position Paper for the W3C Workshop on Web Applications and Compound Documents". [[W3C]].
  8. (1 June 2004). "W3C Workshop on Web Applications and Compound Documents (Day 1)". [[W3C]].
  9. (2 June 2004). "W3C Workshop on Web Applications and Compound Documents (Day 2)". [[W3C]].
  10. Hickson, -Ian. (5 June 2004). "[whatwg] WHAT open mailing list announcement". [[W3C]].
  11. Pilgrim, Mark. (15 September 2008). "This Week in HTML 5 – Episode 5". [[WHATWG]].
  12. (22 January 2008). "HTML5: A vocabulary and associated APIs for HTML and XHTML". [[W3C]].
  13. (29 April 2010). "FOX News: No Flash on the iPhone? Apple's Steve Jobs Finally Explains Why". Fox News Channel.
  14. (29 April 2010). "TIME: Steve Jobs: 'Flash is No Longer Necessary' and Other Musings".
  15. "Steve Jobs: Why Apple Banned Flash". [[CBS News]].
  16. (29 April 2010). "FastCompany: Steve Jobs: Adobe's Flash Is Old PC History, Open Web Is the Future".
  17. Jobs, Steve. "Thoughts on Flash".
  18. "Is HTML5 Replacing Flash?". Lyquix.com.
  19. "Flash to Focus on PC Browsing and Mobile Apps; Adobe to More Aggressively Contribute to HTML5".
  20. (25 July 2017). "Adobe will finally kill Flash in 2020".
  21. (1 January 2021). "Adobe Flash reaches end of life with nostalgia from users".
  22. Hickson, Ian. "HTML Is the New HTML5".
  23. "HTML5 gets the splits". NetMagazine.com.
  24. (17 December 2012). "HTML5". W3.org.
  25. (16 September 2014). "Call for Review: HTML5 Proposed Recommendation Published W3C News". [[W3C]].
  26. (28 October 2014). "Open Web Platform Milestone Achieved with HTML5 Recommendation". [[W3C]].
  27. "HTML 5.1 W3C Recommendation". [[W3C]].
  28. "HTML 5.2 W3C Recommendation". [[W3C]].
  29. "HTML5 Publication History - W3C".
  30. "HTML 4.0 Publication History - W3C".
  31. "HTML 4.01 Publication History - W3C".
  32. "XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition) Publication History - W3C".
  33. "XHTML™ 1.1 - Module-based XHTML - Second Edition Publication History - W3C".
  34. "HTML 5.2 Publication History - W3C".
  35. "HTML 5.3 Publication History - W3C".
  36. (3 May 2007). "Web Applications 1.0".
  37. "HTML5 Publication History - W3C".
  38. "HTML 5.1 2nd Edition Publication History - W3C".
  39. (14 December 2017). "HTML 5.3". [[World Wide Web Consortium]].
  40. (28 May 2019). "W3C and WHATWG to Work Together to Advance the Open Web Platform".
  41. (28 May 2019). "W3C and the WHATWG Signed an Agreement to Collaborate on a Single Version of HTML and DOM".
  42. (28 May 2019). "Memorandum of Understanding Between W3C and WHATWG".
  43. (29 May 2019). "Browser vendors Win War with W3C over HTML and DOM standards". ZDNet.
  44. (14 December 2017). "HTML 5.2 W3C Recommendation". [[W3C]].
  45. Hoffmann, Jay. (2017). "A Tale of Two Standards". The History of the Web.
  46. (29 October 2014). "HTML5 specification finalized, squabbling over specs continues". Ars Technica.
  47. (14 December 2017). "HTML 5.2 W3C Recommendation". [[W3C]].
  48. (25 July 2018). "HTML Living Standard". [[WHATWG]].
  49. (25 July 2018). "HTML Living Standard". [[WHATWG]].
  50. (28 May 2019). "W3C and the WHATWG Signed an Agreement to Collaborate on a Single Version of HTML and DOM". [[W3C]].
  51. "HTML 5.2".
  52. "HTML Standard".
  53. "HTML Standard, One-Page Version".
  54. "HTML Standard, Chapter 5: Microdata".
  55. "HTML Standard, Chapter 9: Communication".
  56. "HTML Standard, Chapter 10: Web workers".
  57. "HTML Standard, Chapter 11: Web storage".
  58. "HTML 5.2, § 3.2.5. Global attributes".
  59. "HTML Standard, § 3.2.6 Global attributes".
  60. "HTML Standard, § 4.13 Custom elements".
  61. "HTML 5.2: § 4.5.11. The rb element".
  62. "HTML 5.2: § 4.5.13. The rtc element".
  63. "HTML 5.2: § 4.4.2. The address element".
  64. "HTML Standard, § 4.3.7 The hgroup element".
  65. "HTML Standard, § 4.4.7 The menu element".
  66. "HTML Standard, § 4.12.4 The slot element".
  67. "HTML Standard, § 4.3.10 The address element".
  68. "HTML 5.2: § 4.2.5.4. Other pragma directives".
  69. "PragmaExtensions – WHATWG Wiki".
  70. "HTML Standard, § 4.3.11.2 Sample outlines".
  71. "HTML Standard, § 4.3.11.3 Exposing outlines to users".
  72. "HTML 5.2: § 4.3.2. The article element".
  73. "HTML 5.2: § 4.5.16. The time element".
  74. "HTML+RDFa 1.1 – Second Edition".
  75. "RDFa Lite 1.1 – Second Edition".
  76. "HTML Standard, § 4.3.2 The article element".
  77. "HTML Standard, § 4.3.4 The nav element".
  78. "HTML Standard, § 4.4.9 The dl element".
  79. "HTML Standard, § 4.5.14 The time element".
  80. "<rb>: The Ruby Base element".
  81. "HTML element: rtc {{!}} Can I use... Support tables for HTML5, CSS3, etc".
  82. "<rtc>: The Ruby Text Container element".
  83. "
    ".
  84. "".
  85. "".
  86. "The Immersive Web Working Group/Community Group". [[W3C]].
  87. "PubStatus – WEBAPPS". [[W3C]].
  88. Introduction to HTML 5 [http://dev.opera.com/articles/view/introduction-html5-video/ video] {{Webarchive. link. (24 January 2011)
  89. link. (5 January 2011)
  90. ICAMD.org [https://www.amazon.com/dp/B003H05Q18 Finalcut Silverlight Films that Videographers share Quicktime in a Flash: Video on the Web using HTML5 and other Codecs] {{Webarchive. link. (26 November 2022)
  91. [https://jkorpela.fi/html5-dtd.html HTML5 DTD] {{Webarchive. link. (26 November 2022 : "HTML5 is not SGML-based, and there will be no official DTD for it.")
  92. [https://dev.w3.org/html5/html-author/ HTML 5 Reference] {{Webarchive. link. (26 November 2022 : "Although it is inspired by its SGML origins, in practice, it really only shares minor syntactic similarities. ... As HTML5 is no longer formally based upon SGML, the DOCTYPE no longer serves this purpose, and thus no longer needs to refer to a DTD.")
  93. Suetos, Shannon. (26 April 2010). "HTML5: Worth the Hype?". instantshift.com.
  94. (5 January 2009). "Web Forms 2.0".
  95. "HTML". whatwg.org.
  96. Sergey Mavrody, ''Sergey's HTML5 & CSS3 Quick Reference'', 2nd ed. Belisso Corp., 2012. {{ISBN. 978-0-9833867-2-8
  97. "Get Started with HTM Canvas".
  98. "HTML". whatwg.org.
  99. [https://www.w3.org/TR/offline-webapps/ "Offline Web Applications"] {{Webarchive. link. (26 November 2022 . [[World Wide Web Consortium]].)
  100. "HTML". whatwg.org.
  101. "HTML". whatwg.org.
  102. "The History interface". w3.org.
  103. "HTML". whatwg.org.
  104. "HTML". whatwg.org.
  105. "HTML". whatwg.org.
  106. "Web Messaging specification". whatwg.org.
  107. "Web Storage specification". whatwg.org.
  108. "1 Introduction – HTML Standard". Whatwg.org.
  109. [https://www.w3.org/TR/IndexedDB/ "Indexed Database"] {{Webarchive. link. (2 March 2018 . [[World Wide Web Consortium]].)
  110. "File API". W3.org.
  111. [https://www.w3.org/TR/FileAPI/ "File API"] {{Webarchive. link. (26 November 2022 . [[World Wide Web Consortium]].)
  112. [https://www.w3.org/TR/file-system-api/ "Filesystem API"] {{Webarchive. link. (26 November 2022 . [[World Wide Web Consortium]].)
  113. [https://www.w3.org/TR/file-writer-api/ "File API: Writer"] {{Webarchive. link. (26 November 2022 . [[World Wide Web Consortium]].)
  114. "Web Audio API". [[World Wide Web Consortium]].
  115. MDN. "element.classList".
  116. "Web Cryptography API".
  117. "WebRTC 1.0: Real-time Communication Between Browsers".
  118. [https://www.w3.org/TR/webdatabase/ "Web SQL Database"] {{Webarchive. link. (3 February 2019 . [[World Wide Web Consortium]].)
  119. Williamson, James. (2010). "What HTML5 is (and what it isn't)".
  120. "HTML5 differences from HTML4". [[World Wide Web Consortium]].
  121. Graff, Eliot. "Polyglot Markup: HTML-Compatible XHTML Documents". W3C.
  122. "14 The XML syntax". WHATWG.
  123. "FAQ – WHATWG Wiki". WHATWG.
  124. (30 September 2011). "Percentage of Web sites Using HTML5". binvisions.
  125. "[http://www.incore.com/Fortune500HTML5/#infographic HTML5 Popularity Among Fortune 500 Companies] {{Webarchive. link. (14 June 2017 ". INCORE. Retrieved 5 March 2013.)
  126. "HTML5 form additions". [[World Wide Web Consortium]].
  127. "W3C HTML5 Logo FAQ". [[World Wide Web Consortium]].
  128. "HTML5 Logo: Be Proud, But Don't Muddy the Waters!". [[The Web Standards Project]].
  129. "The HTML5 Logo Conversation". World Wide Web Consortium.
  130. [https://w3c.github.io/encrypted-media/ Encrypted Media Extensions] {{Webarchive. link. (20 January 2021 draft specification of the W3C)
  131. (24 April 2013). "Une coalition de vingt-sept organisations demande au W3C de garder les menottes numériques (DRM) hors des standards du Web".
  132. "Tell W3C: We don't want the Hollyweb – Free Software Foundation".
  133. Stallman, Richard. (2 May 2013). "The W3C's Soul at Stake". The Free Software Foundation.
  134. Lord, Timothy. (16 April 2013). "Netflix Wants to Go HTML5, but Not Without DRM".
  135. (30 September 2013). "New Charter for the HTML Working Group from Philippe Le Hegaret on 2013-09-30 (public-html-admin@w3.org from September 2013)". Lists.w3.org.
  136. [https://blogs.adobe.com/standards/2013/06/19/adobe-support-for-encrypted-media-extensions/ Adobe Support for Encrypted Media Extensions] {{Webarchive. link. (9 November 2016 Adobe.com. 19 June 2013.)
  137. Gal, Andreas. (14 May 2014). "Reconciling Mozilla's Mission and W3C EME". Mozilla.
  138. Baker, Mitchell. (14 May 2014). "DRM and the Challenge of Serving Users". Mozilla.
  139. Doctorow, Cory. (14 May 2014). "Firefox's adoption of closed-source DRM breaks my heart". The Guardian.
  140. (14 May 2014). "FSF condemns partnership between Mozilla and Adobe to support Digital Rights Management". Free Software Foundation.
  141. (2017-09-18). "W3C Publishes Encrypted Media Extensions (EME) as a W3C Recommendation".

::callout[type=info title="Wikipedia Source"] This article was imported from Wikipedia and is available under the Creative Commons Attribution-ShareAlike 4.0 License. Content has been adapted to SurfDoc format. Original contributors can be found on the article history page. ::

html52014-softwarexml-based-standards