I was thinking that all these new releases would have to be backwards compatible with all previous releases to make the Internet stay functional. So, it likely is a lot of time designing new elements so they are backwards compatible and don't just screw up the way the whole internet operates. So, a lot of time would be taken in using them as Betas to test them more fully before releasing them to the general public as a new html release.
Latest release 5.0
HTML5
From Wikipedia, the free encyclopedia
 |
|
| Filename extension | .html |
|---|---|
| Internet media type | text/html |
| Type code | TEXT |
| Uniform Type Identifier (UTI) | index.html[1] |
| Developed by | World Wide Web Consortium and WHATWG |
| Initial release | 28 October 2014[2] |
| Latest release |
HTML 5
HTML 5.1(working draft) |
| Type of format | Markup language |
| Extended to | XHTML5 (XML-serialized HTML5) |
| Standard | W3C HTML5 W3C HTML 5.1 |
| Open format? | Yes |
| Filename extension | .xhtml, .html |
|---|---|
| Internet media type | application/xml, application/xhtml+xml |
| Developed by | World Wide Web Consortium and WHATWG |
| Type of format | Markup language |
| Extended from | XML, HTML5 |
| Open format? | Yes |
| HTML | |||
|---|---|---|---|
| Comparisons | |||
|
|||
Its core aims have been to improve the language with support for the latest multimedia while keeping it easily readable by humans and consistently understood by computers and devices (web browsers, parsers, etc.). HTML5 is intended to subsume not only HTML 4, but also XHTML 1 and DOM Level 2 HTML.[4]
Following its immediate predecessors HTML 4.01 and XHTML 1.1, HTML5 is a response to the fact that the HTML and XHTML in common use on the World Wide Web are a mixture of features introduced by various specifications, along with those introduced by software products such as web browsers, those established by common practice.[5] It is also an attempt to define a single markup language that can be written in either HTML or XHTML. It includes detailed processing models to encourage more interoperable implementations; it extends, improves and rationalises the markup available for documents, and introduces markup and application programming interfaces (APIs) for complex web applications.[6] For the same reasons, HTML5 is also a potential candidate for cross-platform mobile applications. Many features of HTML5 have been built with the consideration of being able to run on low-powered devices such as smartphones and tablets. In December 2011, research firm Strategy Analytics forecast sales of HTML5 compatible phones would top 1 billion in 2013.[7]
In particular, HTML5 adds many new syntactic features. These include the new
,
Contents
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,[9] 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. W3C and WHATWG are currently working together on the development of HTML5.[10]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 Scalable Vector Graphics. 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.
Although HTML5 has been well known among web developers for years, its interactive capabilities became a topic of mainstream media around April 2010[11][12][13][14] after Apple Inc's then-CEO Steve Jobs issued a public letter titled "Thoughts on Flash" where he concludes 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".[15] This sparked a debate in web development circles where some suggested 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.[16] In early November 2011, Adobe announced that it will discontinue development of Flash for mobile devices and reorient its efforts in developing tools using HTML5.[17]
Standardization process
The Mozilla Foundation and Opera Software presented a position paper at a World Wide Web Consortium (W3C) workshop in June 2004,[18] focusing on developing technologies that are backward compatible with existing browsers,[19] 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.[20] Immediately after the workshop, the Web Hypertext Application Technology Working Group (WHATWG) was formed to start work based upon that position paper, and a second draft, Web Applications 1.0, was also announced.[21] The two specifications were later merged to form HTML5.[22] The HTML5 specification was adopted as the starting point of the work of the new HTML working group of the W3C in 2007.- 2008 – First Public Working Draft
- 2011 – Last Call
- 2012 – Candidate Recommendation
In December 2012, W3C designated HTML5 as a Candidate Recommendation.[27] The criterion for advancement to W3C Recommendation is "two 100% complete and fully interoperable implementations".[28][29]
- 2014 – Proposed Recommendation and Recommendation
On 28 October 2014, HTML5 was released as a stable W3C Recommendation,[31] meaning the specification process is complete.[2]
- Future plans
- Core HTML specification
| 2012 | 2013 | 2014 | 2015 | 2016 | |
|---|---|---|---|---|---|
| HTML 5.0 | Candidate Rec | Call for Review | Recommendation | ||
| HTML 5.1 | 1st Working Draft | Last Call | Candidate Rec | Recommendation | |
| HTML 5.2[32] | 1st Working Draft |
- Features and APIs
- HTML Working Group – HTML Canvas 2D Context
- Web Apps WG – Web Messaging, Web Workers, Web Storage, WebSocket API, Server-Sent Events
- IETF HyBi WG – WebSocket Protocol
- WebRTC WG – WebRTC
- W3C Web Media Text Tracks CG – WebVTT
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 (
The HTML5 syntax is no longer based on SGML[39][40] 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,
New APIs
In addition to specifying markup, HTML5 specifies scripting application programming interfaces (APIs) that can be used with JavaScript.[44] Existing document object model (DOM) interfaces are extended and de facto features documented. There are also new APIs, such as:
HTML5 related APIs.[45]
- The canvas element for immediate mode 2D drawing. See Canvas 2D API Specification 1.0 specification[46]
- Timed media playback[47]
- Offline Web Applications[48]
- Document editing[49]
- Drag-and-drop[50]
- Cross-document messaging[51]
- Browser history management[52]
- MIME type and protocol handler registration[53][54]
- Microdata[55]
- Web Storage, a key-value pair storage framework that provides behaviour similar to cookies but with larger storage capacity and improved API.[56]
- Geolocation
- Web SQL Database, a local SQL Database (no longer maintained).[58]
- The Indexed Database API, an indexed hierarchical key-value store (formerly WebSimpleDB).[59]
- HTML5 File API,[60] handles file uploads and file manipulation.[61]
- Directories and System, an API intended to satisfy client-side-storage use cases not well served by databases.[62]
- File Writer, an API for writing to files from web applications.[63]
- Web Audio API,[64] a high-level JavaScript API for processing and synthesizing audio in web applications.
- ClassList API[65]
XHTML5 (XML-serialized HTML5)
XML documents must be served with an XML Internet media type (often called "MIME type") such asapplication/xhtml+xml or application/xml,[67]
and must conform to strict, well-formed syntax of XML. XHTML5 is simply
an XML-serialized HTML5 data (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 termed "polyglot markup".[68]Error handling
HTML5 is designed so that old browsers can safely ignore new HTML5 constructs.[6] In contrast to HTML 4.01, the HTML5 specification gives detailed rules for lexing and parsing, with the intent that different compliant browsers will produce the same result in the case of incorrect syntax.[69] Although HTML5 now defines a consistent behavior for "tag soup" documents, those documents are not regarded as conforming to the HTML5 standard.[69]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.[70] Another report released in August 2013 has shown that 153 of the Fortune 500 U.S. companies implemented HTML5 on their corporate websites.[71]As of 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[72] - New attributes:
charset(onmeta),async(onscript) - 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
Logo
The W3C HTML5 logo
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".[75] Some web standard advocates, including The Web Standards Project, criticised that definition of "HTML5" as an umbrella term, pointing out the blurring of terminology and the potential for miscommunication.[75] Three days later, the W3C responded to community feedback and changed the logo's definition, dropping the enumeration of related technologies.[76] The W3C then said the logo "represents HTML5, the cornerstone for modern Web applications".[74]
Digital rights management
Industrial players including the BBC, Google, Microsoft, and Netflix have been lobbying for the inclusion of Encrypted Media Extensions (EME),[77][78][79][80][81] a form of digital rights management (DRM), into the HTML5 standard. As of the end of 2012 and the beginning of 2013, 27 organisations[82] including the Free Software Foundation[83] have started a campaign against including digital rights management in the HTML5 standard.[84][85] 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.[86][87] WHATWG's "HTML Living Standard" continued to be developed without DRM-enabled proposals.[87]Manu Sporny, a member of the W3C, said that EME will not solve the problem it's supposed to address.[88] Opponents point out that EME itself is just an architecture for a DRM plug-in mechanism.[89]
The initial enablers for DRM in HTML5 were Google[90] and Microsoft.[91] Supporters also include Adobe.[92] On 14 May 2014, Mozilla announced plans to support EME in Firefox, the last major browser to avoid DRM.[93][94] 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.[93] While promising to "work on alternative solutions", Mitchell Baker stated that Mozilla's refusal to implement EME would accomplish little more than convincing many users to switch browsers.[94] This decision was condemned by Cory Doctorow and the Free Software Foundation.[95][96]
See also
References
- "FSF condemns partnership between Mozilla and Adobe to support Digital Rights Management". Free Software Foundation. 2014-05-14. Retrieved 2014-05-20.
External links
 |
Wikimedia Commons has media related to HTML5. |
| Library resources about HTML5 |
- HTML Working Group - HTML5 publications, specifications, and notes
- HTML5 Rocks - A comprehensive HTML5 resource for developers by Google
- Mozilla Demo Studio - Demos of HTML5 implementations
- HTML5 Frontend Comparison - Sheet showing HTML5 vs. other main frontend techniques
- HTML.next Feature requests for future versions of HTML.
|
||
|
||
|
||
Navigation menu
HTML 4 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 a critical mass of deployed 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. HTML5 will replace these documents.
Is this W3C's "official" logo for HTML5? Yes, as of 1 April 2011.
Latest release : I realized the word button "latest release" previous to this describes the release process whereas "5.0 after end quote from actually is the site where html 5 is located.
No comments:
Post a Comment