(HyperText Markup Language)
HTML5 logo and wordmark.svg
Filename extension.html, .htm
Internet media typetext/html
Type codeTEXT
Uniform Type Identifier (UTI)public.html[1]
Initial release28 October 2014
(4 years ago)
Extended toXHTML 5 (XML-serialized HTML 5)
StandardHTML 5.2 Recommendation (W3C); HTML Living Standard (WHATWG)
(XHTML Syntax of HTML 5)
Filename extension.xhtml, .html
Internet media typeapplication/xml, application/xhtml+xml
Developed byWorld Wide Web Consortium and WHATWG
Type of formatMarkup language
Extended fromXML, HTML 5
StandardHTML 5.2 Recommendation: "The XHTML Syntax"

HTML 5 (formerly spelled HTML5[a]) is a markup language used for structuring and presenting content on the World Wide Web. It is the fifth and current major version of the HTML standard, and subsumes XHTML. It currently exists in two standardized forms: HTML 5.2 Recommendation[4] by the World Wide Web Consortium (W3C, a broad coalition of organizations), intended primarily for Web content developers; and HTML Living Standard[5] by WHATWG (a small consortium of four browser vendors), intended primarily for browser developers, though it also exists in an abridged Web developer version.[6] There are minor conflicts between the two groups' specifications.

HTML 5 was first released in public-facing form on 22 January 2008,[7] with a major update and "W3C Recommendation" status in October 2014.[2][8] Its goals are 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. HTML 5 is intended to subsume not only HTML 4, but also XHTML 1 and DOM Level 2 HTML;[9] the HTML 4 and XHTML specs were announced as superseded by HTML 5.2 on 27 March 2018.[10]

HTML 5 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.[11] For the same reasons, HTML 5 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, and support for scalable vector graphics (SVG) content and MathML for mathematical formulas. To enrich the semantic content of documents, new page structure elements such as , , , , , , , and are added. New attributes are introduced, some elements and attributes have been removed, and others such as , , and have been changed, redefined, or standardized.

The APIs and Document Object Model (DOM) are now fundamental parts of the HTML 5 specification[11] and HTML 5 also better defines the processing for any invalid documents.[12]


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,[13] 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.[14]

The Mozilla Foundation and Opera Software presented a position paper at a World Wide Web Consortium (W3C) workshop in June 2004,[15] focusing on developing technologies that are backward-compatible with existing browsers,[16] 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.[17] 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.[18] The two specifications were later merged to form HTML 5.[19] The HTML 5 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.[7]

"Thoughts on Flash"

While some features of HTML 5 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 Scalable Vector Graphics. However, HTML 5 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 HTML 5 (see Comparison of HTML5 and Flash). HTML 5's interactive capabilities became a topic of mainstream media attention around April 2010[20][21][22][23] 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".[24] This sparked a debate in web development circles suggesting that, while HTML 5 provides enhanced functionality, developers must consider the varying browser support of the different parts of the standard as well as other functionality differences between HTML 5 and Flash.[25] In early November 2011, Adobe announced that it would discontinue development of Flash for mobile devices and reorient its efforts in developing tools using HTML 5.[26] On July 25, 2017, Adobe announced that both the distribution and support of Flash will cease by the end of 2020.[27]

Last call, candidacy, and recommendation stages

On 14 February 2011, the W3C extended the charter of its HTML Working Group with clear milestones for HTML 5. In May 2011, the working group advanced HTML 5 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.[28] In January 2011, the WHATWG renamed its "HTML5" specification HTML Living Standard". The W3C nevertheless continued its project to release HTML 5.[29]

In July 2012, WHATWG and W3C decided on a degree of separation. W3C will continue the HTML 5 specification work, focusing on a single definitive standard, which is considered as a "snapshot" by WHATWG. The WHATWG organization continues its work with HTML 5 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.[30]

In December 2012, W3C designated HTML 5 as a Candidate Recommendation.[31] The criterion for advancement to W3C Recommendation is "two 100% complete and fully interoperable implementations".[32]

On 16 September 2014, W3C moved HTML 5 to Proposed Recommendation.[33] On 28 October 2014, HTML 5 was released as a W3C Recommendation,[34] bringing the specification process to completion.[2] On 1 November 2016, HTML 5.1 was released as a W3C Recommendation.[35] On 14 December 2017, HTML 5.2 was released as a W3C Recommendation.[36]


The combined timelines for HTML 5.0, HTML 5.1 and HTML 5.2:

Version First draft Candidate recommendation Recommendation
HTML 5.0 2007[37] 2012 2014
HTML 5.1 2012 2015 2016
HTML 5.2[38] 2015 2017 2017
HTML 5.3[39] 2017 N/A N/A

W3C and WHATWG conflict

W3C and WHATWG have been characterized as both working together on the development of HTML 5,[14] and yet also at cross purposes[30][2] ever since the July 2012 split of the W3C work into milestone-based static standards and WHATWG's into a continually updated "living standard". The relationship has been described as "fragile", even a "rift",[40] and characterized by "squabbling".[2]

In at least one case, namely the permissible content of the element, the two specifications directly contradict each other (as of July 2018), with the W3C definition being permissive and reflecting traditional use of the element since its introduction,[41] but WHATWG limiting it to a single defined type of content (the title of the work cited).[42] This is actually at odds with WHATWG's stated goals of ensuring backward compatibility[43] and not losing prior functionality.[30]

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 HTML 5 plans, then jumping on the bandwagon belatedly (though Hickson was in control of the W3C HTML 5 spec, too). Regardless, it indicates a major philosophical divide between the organizations:[44]

For a number of years, both groups then worked together. In 2011, however, the groups came to the conclusion that they had different goals: the W3C wanted to publish a "finished" version of "HTML5", while the WHATWG wanted to continue working on a Living Standard for HTML, continuously maintaining the specification rather than freezing it in a state with known problems, and adding new features as needed to evolve the platform.

Since then, the WHATWG has been working on this specification (amongst others), and the W3C has been copying fixes made by the WHATWG into their fork of the document (which also has other changes).

The "markets" for the two specifications are largely different. The W3C spec is the one that Web developers most often refer to,[] while the WHATWG version is used by the software development teams of the browser makers (though a version exists for Web content authors, trimmed of the material only of interest to browser coders[6]). New features are added to HTML and, often experimentally, to browsers long before they appear in a W3C spec, because they arise in the WHATWG one.[40] The technology journal Ars Technica observed that "both groups are likely to continue to exist, and both groups will continue to have broad-based industry backing".[2]

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, as of September 2018:

Content or Features Unique to W3C or WHATWG Standard
W3C[45] WHATWG[46]
Site pagination Single page version[47] (allows global search of contents)
Chapters §5 Microdata[48]

§9 Communication[49]

§10 Web workers[50]

§11 Web storage[51]

Global attributes [52]: class, id [53]: autocapitalize, enterkeyhint, inputmode, is, itemid, itemprop, itemref, itemscope, itemtype, nonce
Chapter Elements of HTML §4.13 Custom elements[54]
Elements <rb>[55], <rtc>[56] (See compatibility notes below.)

<address>[57] is in section Grouping content.

<hgroup>[58], <menu>[59], <slot>[60] (See compatibility notes below.)

<address>[61] is in section Sections.

§ <meta> § Other pragma directives[62], based on deprecated WHATWG procedure[63].
§ Sections § Sample outlines[64]

§ Exposing outlines to users[65]

Structured data Recommends RDFa (code examples[66][57][67], separate specs[68][69], no special attributes[52]). Recommends Microdata (code examples[70][71][72][73], spec chapter[48], special attributes[53]).

The following table provides data from the Mozilla Development Network on compatibility with major browsers, as of September 2018, of HTML elements unique to one of the standards:

Element Standard Compatibility Note
<rb>[74] W3C All browsers, except Edge
<rtc>[75] W3C None, except Firefox
<hgroup>[76] WHATWG All browsers "[Since] the HTML outline algorithm is not implemented in any browsers ... the <hgroup> semantics are in practice only theoretical."
<menu>[77] WHATWG Full support only in Edge and Firefox desktop.

Partial support in Firefox mobile.

Supported in Opera with user opt-in.

Not supported in other browsers.

Experimental technology
<slot>[78] WHATWG All browsers, except Edge and IE Experimental technology

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 HTML 5 itself are now defined in separate specifications:

  • HTML Working Group - HTML Canvas 2D Context;
  • Web Apps Working Group - Web Messaging, Web workers, Web storage, WebSocket, Server-sent events, Web Components[79] (this was not part of HTML 5, 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.

After the standardization of the HTML 5 specification in October 2014,[80] the core vocabulary and features are being extended in four ways.[81] Likewise, some features that were removed from the original HTML 5 specification have been standardized separately as modules, such as Microdata and Canvas. Technical specifications introduced as HTML 5 extensions such as Polyglot Markup have also been standardized as modules. Some W3C specifications that were originally separate specifications have been adapted as HTML 5 extensions or features, such as SVG. Some features that might have slowed down the standardization of HTML 5 will be standardized as upcoming specifications, instead. HTML 5.1 is expected to be finalized in 2016, and it is currently on the standardization track at the W3C.



HTML 5 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 .[82][83][84] 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.[85] There is also a renewed emphasis on the importance of DOM scripting in Web behavior.

The HTML 5 syntax is no longer based on SGML[86][87] 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, <!DOCTYPE html>, which triggers the standards-compliant rendering mode.[88] Since 5 January 2009, HTML 5 also includes Web Forms 2.0, a previously separate WHATWG specification.[89][90]

New APIs

HTML5 related APIs[91]

In addition to specifying markup, HTML 5 specifies scripting application programming interfaces (APIs) that can be used with JavaScript.[92] 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 HTML 5 specification, though they are in the WHATWG HTML specification.[104] Some related technologies, which are not part of either the W3C HTML 5 or the WHATWG HTML specification, are as follows. The W3C publishes specifications for these separately:

HTML 5 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[115][not in citation given], and within SVG elements through SMIL, although browser support of the latter remains uneven as of 2011.

XHTML 5 (XML-serialized HTML 5)

XML documents must be served with an XML Internet media type (often called "MIME type") such as application/xhtml+xml or application/xml,[92] and must conform to strict, well-formed syntax of XML. XHTML 5 is simply XML-serialized HTML 5 data (that is, HTML 5 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 which will therefore produce the same DOM tree whether parsed as HTML or XML is known as Polyglot markup[116]

Error handling

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


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

Since 2014, HTML 5 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, section, source, summary, time, track, video, wbr
  • New types of form controls: dates and times, email, url, search, number, range, tel, color[120]
  • 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",[121] which provides a complete outline of additions, removals and changes between HTML 5 and HTML 4.

The W3C HTML5 logo

On 18 January 2011, the W3C introduced a logo to represent the use of or interest in HTML 5. 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.[122]

When initially presenting it to the public, the W3C announced the HTML 5 logo as a "general-purpose visual identity for a broad set of open web technologies, including HTML 5, CSS, SVG, WOFF, and others".[123] 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.[123] Three days later, the W3C responded to community feedback and changed the logo's definition, dropping the enumeration of related technologies.[124] The W3C then said the logo "represents HTML5, the cornerstone for modern Web applications".[122]

Digital rights management

Industry players including the BBC, Google, Microsoft, Apple Inc. have been lobbying for the inclusion of Encrypted Media Extensions (EME),[125][126][127][128][129] a form of digital rights management (DRM), into the HTML 5 standard. As of the end of 2012 and the beginning of 2013, 27 organisations[130] including the Free Software Foundation[131] have started a campaign against including digital rights management in the HTML 5 standard.[132][133] However, in late September 2013, the W3C HTML Working Group decided that Encrypted Media Extensions, a form of DRM, was "in scope" and will potentially be included in the HTML 5.1 standard.[134][135] WHATWG's "HTML Living Standard" continued to be developed without DRM-enabled proposals.[135]

Manu Sporny, a member of the W3C, said that EME will not solve the problem it's supposed to address.[136] Opponents point out that EME itself is just an architecture for a DRM plug-in mechanism.[137]

The initial enablers for DRM in HTML 5 were Google[138] and Microsoft.[139] Supporters also include Adobe.[140] On 14 May 2014, Mozilla announced plans to support EME in Firefox, the last major browser to avoid DRM.[141][142] Calling it "a difficult and uncomfortable step", Andreas Gal of Mozilla explained that future versions of Firefox would remain open source but ship with a sandbox designed to run a content decryption module developed by Adobe.[141] While promising to "work on alternative solutions", Mozilla's Executive Chair Mitchell Baker stated that a refusal to implement EME would have accomplished little more than convincing many users to switch browsers.[142] This decision was condemned by Cory Doctorow and the Free Software Foundation.[143][144]

See also


  1. ^ In early W3C recommendations, there was no space between "HTML" and "5" in the name.[3] This has not been the case since HTML 5.1; the current specification is named HTML 5.2 W3C Recommendation, and "HTML5" does not appear in it.[4] WHATWG had also used the "HTML5" spelling, but their specification is now named HTML Living Standard, and they have abandoned version numbering.[5]


  1. ^ "Mac Developer Library: System-Declared Uniform Type Identifiers". Apple. 17 November 2009.
  2. ^ a b c d e f "HTML5 specification finalized, squabbling over specs continues". Ars Technica. 29 October 2014. Retrieved 2014.
  3. ^ "A vocabulary and associated APIs for HTML and XHTML". World Wide Web Consortium (W3C). 28 October 2014. Retrieved 2018.
  4. ^ a b Faulkner, Steve; Eicholz, Arron; Leithead, Travis; Danilo, Alex; Moon, Sangwhan; Doyle Navara, Erika; O'Connor, Theresa; Berjon, Robin, eds. (14 December 2017) [2016]. "HTML 5.2 W3C Recommendation". Revised version. World Wide Web Consortium (W3C). Retrieved 2018.
  5. ^ a b Hickson, Ian, ed. (25 July 2018). "HTML Living Standard". Multipage Version. WHATWG. Retrieved 2018.
  6. ^ a b Hickson, Ian, ed. (25 July 2018). "HTML Living Standard". Developer's Edition. WHATWG. Retrieved 2018.
  7. ^ a b "HTML5: A vocabulary and associated APIs for HTML and XHTML". W3C. 22 January 2008. Retrieved 2009.
  8. ^ "HTML5 is a W3C recommendation". W3C Blog. World Wide Web Consortium (W3C). 28 October 2014. Retrieved 2014.
  9. ^ "HTML5 Differences from HTML4". W3C. "Introduction". Retrieved 2018. HTML4 became a W3C Recommendation in 1997. While it continues to serve as a rough guide to many of the core features of HTML, it does not provide enough information to build implementations that interoperate with each other and, more importantly, with Web content. The same goes for XHTML1, which defines an XML serialization for HTML4, and DOM Level 2 HTML, which defines JavaScript APIs for both HTML and XHTML. HTML replaces these documents.
  10. ^ The 27 March 2018 superseded date appears on the legacy specification pages of HTML 4.1, XHTML 1.1, and earlier versions; the DOM 4 spec is not marked as superseded, nor is even the DOM 2 spec, as of July 2018.
  11. ^ a b c "HTML5 Differences from HTML4". W3C. 19 October 2010. Retrieved 2010.
  12. ^ "HTML 5.2 W3C Recommendation". W3C. 14 December 2017. § 1.10.2 Syntax Errors. Retrieved 2017.
  13. ^ "HTML 4 Errata". World Wide Web Consortium. Retrieved 2010.
  14. ^ a b "HTML 5.2 W3C Recommendation". W3C. 14 December 2017. § 1.4 History. Retrieved 2017.
  15. ^ "Position Paper for the W3C Workshop on Web Applications and Compound Documents". W3C. Retrieved 2011.
  16. ^ "W3C Workshop on Web Applications and Compound Documents (Day 1)". W3C. 1 June 2004. Retrieved 2011.
  17. ^ "W3C Workshop on Web Applications and Compound Documents (Day 2)". W3C. 2 June 2004. Retrieved 2011.
  18. ^ Hickson, -Ian (5 June 2004). "&#91whatwg] WHAT open mailing list announcement". W3C. Retrieved 2015.
  19. ^ Pilgrim, Mark (15 September 2008). "This Week in HTML 5 - Episode 5". WHATWG Blog. WHATWG. Retrieved 2011.
  20. ^ "FOX News: No Flash on the iPhone? Apple's Steve Jobs Finally Explains Why". Fox News. 29 April 2010.
  21. ^ "TIME: Steve Jobs: 'Flash is No Longer Necessary' and Other Musings". Time. 29 April 2010.
  22. ^ "Steve Jobs: Why Apple Banned Flash". CBS News.
  23. ^ "FastCompany: Steve Jobs: Adobe's Flash Is Old PC History, Open Web Is the Future".
  24. ^ "'Thoughts on Flash', by Steve Jobs, CEO of Apple, Inc". Retrieved .
  25. ^ "Is HTML5 Replacing Flash?". Retrieved .
  26. ^ "Flash to Focus on PC Browsing and Mobile Apps; Adobe to More Aggressively Contribute to HTML5". Retrieved 2012.
  27. ^ Warren, Tom (25 July 2017). "Adobe will finally kill Flash in 2020". The Verge. Vox Media.
  28. ^ "W3C Confirms May 2011 for HTML5 Last Call, Targets 2014 for HTML5 Standard". World Wide Web Consortium. 14 February 2011. Retrieved 2011.
  29. ^ Hickson, Ian. "HTML Is the New HTML5". Retrieved 2011.
  30. ^ a b c "HTML5 gets the splits". Retrieved 2012.
  31. ^ "HTML5". 2012-12-17. Retrieved .
  32. ^ "When Will HTML5 Be Finished?". FAQ. WHAT Working Group. Retrieved 2009.
  33. ^ "Call for Review: HTML5 Proposed Recommendation Published W3C News". W3C. 16 September 2014. Retrieved .
  34. ^ "Open Web Platform Milestone Achieved with HTML5 Recommendation". W3C. 28 October 2014. Retrieved 2014.
  35. ^ "HTML 5.1 W3C Recommendation". W3C. Retrieved 2017.
  36. ^ "HTML 5.2 W3C Recommendation". W3C. Retrieved 2017.
  37. ^ "Web Applications 1.0". 2007-05-03. Retrieved .
  38. ^ "Plan 2014". World Wide Web Consortium. Retrieved 2012.
  39. ^ "Editor's Draft". World Wide Web Consortium. Retrieved 2017.
  40. ^ a b Hoffmann, Jay (2017). "A Tale of Two Standards". The History of the Web. Archived from the original on 1 September 2017. Retrieved 2018. (Original title: "When Standards Divide".)
  41. ^ "HTML 5.2 W3C Recommendation". W3C. 14 December 2017. § 4.5.6. The cite element. Retrieved 2018.
  42. ^ "HTML Living Standard". WHATWG. 25 July 2018. § 4.5.6 The cite element. Retrieved 2018.
  43. ^ "HTML Living Standard". WHATWG. 25 July 2018. § 1.6 History. Retrieved 2018.
  44. ^ "HTML Living Standard". WHATWG. 25 July 2018. § 1 Introduction; §1.6 History. Retrieved 2018.
  45. ^ "HTML 5.2". Retrieved .
  46. ^ "HTML Standard". Retrieved .
  47. ^ "HTML Standard, One-Page Version". Retrieved .
  48. ^ a b "HTML Standard, Chapter 5: Microdata". Retrieved .
  49. ^ "HTML Standard, Chapter 9: Communication". Retrieved .
  50. ^ "HTML Standard, Chapter 10: Web workers". Retrieved .
  51. ^ "HTML Standard, Chapter 11: Web storage". Retrieved .
  52. ^ a b "HTML 5.2, § 3.2.5. Global attributes". Retrieved .
  53. ^ a b "HTML Standard, § 3.2.6 Global attributes". Retrieved .
  54. ^ "HTML Standard, § 4.13 Custom elements". Retrieved .
  55. ^ "HTML 5.2: § 4.5.11. The rb element". Retrieved .
  56. ^ "HTML 5.2: § 4.5.13. The rtc element". Retrieved .
  57. ^ a b "HTML 5.2: § 4.4.2. The address element". Retrieved .
  58. ^ "HTML Standard, § 4.3.7 The hgroup element". Retrieved .
  59. ^ "HTML Standard, § 4.4.7 The menu element". Retrieved .
  60. ^ "HTML Standard, § 4.12.4 The slot element". Retrieved .
  61. ^ "HTML Standard, § 4.3.10 The address element". Retrieved .
  62. ^ "HTML 5.2: § Other pragma directives". Retrieved .
  63. ^ "PragmaExtensions - WHATWG Wiki". Retrieved . This document is obsolete.
  64. ^ "HTML Standard, § Sample outlines". Retrieved .
  65. ^ "HTML Standard, § Exposing outlines to users". Retrieved .
  66. ^ "HTML 5.2: § 4.3.2. The article element". Retrieved .
  67. ^ "HTML 5.2: § 4.5.16. The time element". Retrieved .
  68. ^ "HTML+RDFa 1.1 - Second Edition". Retrieved .
  69. ^ "RDFa Lite 1.1 - Second Edition". Retrieved .
  70. ^ "HTML Standard, § 4.3.2 The article element". Retrieved .
  71. ^ "HTML Standard, § 4.3.4 The nav element". Retrieved .
  72. ^ "HTML Standard, § 4.4.9 The dl element". Retrieved .
  73. ^ "HTML Standard, § 4.5.14 The time element". Retrieved .
  74. ^ ": The Ruby Base element". MDN Web Docs. Retrieved .
  75. ^ ": The Ruby Text Container element". MDN Web Docs. Retrieved .
  76. ^ "<hgroup>". MDN Web Docs. Retrieved .
  77. ^ "<menu>". MDN Web Docs. Retrieved .
  78. ^ "<slot>". MDN Web Docs. Retrieved .
  79. ^ "PubStatus - WEBAPPS". W3C.
  80. ^ "HTML5: A Vocabulary and Associated APIs for HTML and XHTML". Retrieved 2015.
  81. ^ Leslie Sikos. "HTML5 Became a Standard, HTML 5.1 and HTML 5.2 on the Way". Retrieved 2015.
  82. ^ Introduction to HTML 5 video
  83. ^ IBM Developer Works New elements in HTML5: Structure and semantics
  84. ^ Finalcut Silverlight Films that Videographers share Quicktime in a Flash: Video on the Web using HTML5 and other Codecs
  85. ^ "11 Obsolete features -- HTML5". W3C. Retrieved .
  86. ^ HTML5 DTD: "HTML5 is not SGML-based, and there will be no official DTD for it."
  87. ^ HTML 5 Reference: "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."
  88. ^ Shannon Suetos (26 April 2010). "HTML5: Worth the Hype?". Retrieved 2012.
  89. ^ "Web Forms 2.0". 2009-01-05. Retrieved . obsolescence notice
  90. ^ "HTML".
  91. ^ Sergey Mavrody, Sergey's HTML5 & CSS3 Quick Reference, 2nd ed. Belisso Corp., 2012. ISBN 978-0-9833867-2-8[javascript:]
  92. ^ a b van Kesteren, Anne; Pieters, Simon. "HTML5 differences from HTML4". World Wide Web Consortium. Retrieved 2017.
  93. ^ "Get Started with HTM Canvas".
  94. ^ "HTML".
  95. ^ "Offline Web Applications". World Wide Web Consortium.
  96. ^ "HTML".
  97. ^ "HTML".
  98. ^ "The History interface".
  99. ^ "HTML".
  100. ^ "HTML".
  101. ^ "HTML".
  102. ^ "Web Messaging specification".
  103. ^ "Web Storage specification".
  104. ^ href. "1 Introduction -- HTML Standard". Retrieved .
  105. ^ "Indexed Database". World Wide Web Consortium.
  106. ^ "File API". Retrieved .
  107. ^ "File API". World Wide Web Consortium.
  108. ^ "Filesystem API". World Wide Web Consortium.
  109. ^ "File API: Writer". World Wide Web Consortium.
  110. ^ "Web Audio API". World Wide Web Consortium. Retrieved .
  111. ^ MDN. "element.classList".
  112. ^ "Web Cryptography API".
  113. ^ "WebRTC 1.0: Real-time Communication Between Browsers".
  114. ^ "Web SQL Database". World Wide Web Consortium.
  115. ^ Williamson, James (2010). "What HTML5 is (and what it isn't)". Retrieved .
  116. ^ Graff, Eliot. "Polyglot Markup: HTML-Compatible XHTML Documents". W3C. Retrieved 2013.
  117. ^ a b "FAQ - WHATWG Wiki". WHATWG. Retrieved 2011.
  118. ^ "Percentage of Web sites Using HTML5". binvisions. Retrieved 2011.
  119. ^ "HTML5 Popularity Among Fortune 500 Companies". INCORE. Retrieved 5 March 2013.
  120. ^ "HTML5 form additions". World Wide Web Consortium. Retrieved 2014.
  121. ^ "HTML5 Differences from HTML4". FAQ. World Wide Web Consortium. 9 December 2014. Retrieved 2018.
  122. ^ a b "W3C HTML5 Logo FAQ". World Wide Web Consortium. Retrieved 2011. Is this W3C's "official" logo for HTML5? Yes, as of 1 April 2011.
  123. ^ a b "HTML5 Logo: Be Proud, But Don't Muddy the Waters!". The Web Standards Project. Retrieved 2011.
  124. ^ "The HTML5 Logo Conversation". World Wide Web Consortium. Retrieved 2011.
  125. ^ Encrypted Media Extensions draft specification of the W3C
  126. ^ Peter Bright (16 April 2013). "Netflix coming to HTML5 just as soon as the DRM ducks are in a row". Ars Technica.
  127. ^ Manu Sporny (26 January 2013). "DRM in HTML5".
  128. ^ "Tell W3C: We don't want the Hollyweb". Free Software Foundation. May 2013.
  129. ^ "HTML5 webpage locks 'would stifle innovation'". BBC News Online. 30 May 2013.
  130. ^ "Une coalition de vingt-sept organisations demande au W3C de garder les menottes numériques (DRM) hors des standards du Web". 2013-04-24. Retrieved .
  131. ^ "Tell W3C: We don't want the Hollyweb - Free Software Foundation".
  132. ^ Stallman, Richard (2013-05-02). "The W3C's Soul at Stake". The Free Software Foundation. Retrieved .
  133. ^ Lord, Timothy (2013-04-16). "Netflix Wants to Go HTML5, but Not Without DRM". Retrieved .
  134. ^ "New Charter for the HTML Working Group from Philippe Le Hegaret on 2013-09-30 ( from September 2013)". 2013-09-30. Retrieved .
  135. ^ a b Danny O'Brien (2013-10-02). "Lowering Your Standards: DRM and the Future of the W3C". Electronic Frontier Foundation. Retrieved .
  136. ^ Manu Sporny (2013-01-26). "DRM in HTML5". The Beautiful, Tormented Machine. Manu Sporny. Archived from the original on 2014-04-25. Retrieved .
  137. ^ Scott Gilbertson (2013-02-12). "DRM for the Web? Say It Ain't So". Webmonkey. Condé Nast. Archived from the original on 2013-04-06. Retrieved .
  138. ^ "Releasenotes for Google Chrome 25.0.1364.87".
  139. ^ "HTML5 Video in IE 11 on Windows 8.1".
  140. ^ Adobe Support for Encrypted Media Extensions 19 June 2013.
  141. ^ a b Gal, Andreas (2014-05-14). "Reconciling Mozilla's Mission and W3C EME". Mozilla. Retrieved .
  142. ^ a b Baker, Mitchell (2014-05-14). "DRM and the Challenge of Serving Users". Mozilla. Retrieved .
  143. ^ Doctorow, Cory (2014-05-14). "Firefox's adoption of closed-source DRM breaks my heart". The Guardian. Retrieved .
  144. ^ "FSF condemns partnership between Mozilla and Adobe to support Digital Rights Management". Free Software Foundation. 2014-05-14. Retrieved .

External links

  This article uses material from the Wikipedia page available here. It is released under the Creative Commons Attribution-Share-Alike License 3.0.


Manage research, learning and skills at IT1me. Create an account using LinkedIn to manage and organize your IT knowledge. IT1me works like a shopping cart for information -- helping you to save, discuss and share.

  Contact Us  |  About |  IT Training & References |  IT Careers |  IT Hardware |  IT Software |  IT Books