HTML5

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.…

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. ==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. 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, <!DOCTYPE html> , 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=== 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: Canvas; Timed Media Playback; Offline; Editable content; Drag and drop; History; MIME type and protocol handler registration; Microdata; Web Messaging; Web Storage – a key-value pair storage framework that provides behavior similar to cookies but with larger storage capacity and improved API. 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 HTML5 the 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 , 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", which provides a complete outline of additions, removals and changes between HTML5 and HTML4. ==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), a form of digital rights management (DRM), into the HTML5 standard. As of the end of 2012 and the beginning of 2013, 27 organizations including the Free Software Foundation have started a campaign against including digital rights management in the HTML5 standard. 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. WHATWG's "HTML Living Standard" continued to be developed without DRM-enabled proposals. Manu Sporny, a member of the W3C, said that EME would not solve the problem it was supposed to address. Opponents point out that EME itself is just an architecture for a DRM plug-in mechanism. The initial enablers for DRM in HTML5 were Google and Microsoft. Supporters also include Adobe. On 14 May 2014, Mozilla announced plans to support EME in Firefox, the last major browser to avoid DRM. 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, later it was replaced with Widevine module from Google which is much more widely adopted by content providers. 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. This decision was condemned by Cory Doctorow and the Free Software Foundation. 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". ==See also== Cache manifest in HTML5 Canvas element Dave Hyatt, Apple's editor of HTML5 specs Ian Hickson, Google's main editor of HTML5 specs Polyglot markup ==References== ==External links== HTML Living standard from WHATWG, GitHub repo The W3C Markup Validation Service, including Nu Html Checker HTML 5.2, the last HTML recommendation from W3C, superseded Memorandum of Understanding Between W3C and WHATWG HTML Media Extensions Working Group HTML.next, Feature requests for future versions of HTML

Text derived from https://en.wikipedia.org/w/index.php?oldid=1377171002 under CC BY-SA 4.0; modifications have been made.