HTML5: Difference between revisions
m →New markup: Doctype triggering is not a common term. Doctype sniffing is. |
|||
Line 40: | Line 40: | ||
Some deprecated elements from [[HTML 4.01]] have been dropped for authoring use, including purely presentational elements, such as {{tag|font|open}} and {{tag|center|open}}, whose effects are handled by [[Cascading style sheets|CSS]]. There is also a renewed emphasis on the importance of [[DOM scripting]] in Web behavior. |
Some deprecated elements from [[HTML 4.01]] have been dropped for authoring use, including purely presentational elements, such as {{tag|font|open}} and {{tag|center|open}}, whose effects are handled by [[Cascading style sheets|CSS]]. There is also a renewed emphasis on the importance of [[DOM scripting]] in Web behavior. |
||
The HTML5 syntax is no longer based on [[SGML]] despite its markup being very close. It has, however, been designed to be backward compatible with common parsing of older versions of HTML. It comes with a new introducing line which looks like an SGML [[DOCTYPE|document type declaration]], {{tag|!DOCTYPE html|open}}, and enables standards-compliant rendering in all browsers that use “DOCTYPE |
The HTML5 syntax is no longer based on [[SGML]] despite its markup being very close. It has, however, been designed to be backward compatible with common parsing of older versions of HTML. It comes with a new introducing line which looks like an SGML [[DOCTYPE|document type declaration]], {{tag|!DOCTYPE html|open}}, and enables standards-compliant rendering in all browsers that use “DOCTYPE sniffing”. |
||
==New APIs== |
==New APIs== |
Revision as of 09:16, 25 May 2009
Filename extension |
HTML5: .html, .htm XHTML5: .xhtml, .xht, .xml |
---|---|
Internet media type |
HTML5: text/html XHTML5: application/xhtml+xml, application/xml |
Type code | TEXT |
Uniform Type Identifier (UTI) | public.html |
Developed by | W3C HTML WG, WHATWG |
Type of format | Markup language XHTML |
Standard | http://www.w3.org/html/wg/html5/ |
HTML 5 (HyperText Markup Language Version 5) is the next major revision of the core language of the World Wide Web, HTML. HTML 5 specifies two variants of the same language, a "classic" HTML (text/html) variant known as HTML5 and an XHTML variant known as XHTML5. This is the first time that HTML and XHTML have been developed in parallel.
The ideas behind HTML 5, originally referred to as Web Applications 1.0, were pioneered in 2004 by the Web Hypertext Application Technology Working Group (WHATWG); HTML 5 incorporates Web Forms 2.0, another WHATWG standard. The HTML 5 standard was adopted as the starting point of the work of the new HTML working group of the W3C in 2007. The working group published the First Public Working Draft of the specification on January 22, 2008.[1] The specification is ongoing work, and expected to remain so for many years, although parts of HTML 5 are going to be finished and implemented in browsers before the whole specification reaches final Recommendation status.[2] The editors are Ian Hickson of Google, Inc. and David Hyatt, Apple, Inc.[1]
New markup
HTML |
---|
Comparisons |
HTML 5 provides a number of new elements and attributes that reflect typical usage on modern Web sites. Some of them are semantic replacements for common uses of generic block (<div>
) and inline (<span>
) elements, for example <nav>
(website navigation block) and <footer>
. Other elements provide new functionality through a standardized interface, such as the <audio>
and <video>
elements.[3]
Some deprecated elements from HTML 4.01 have been dropped for authoring use, including purely presentational elements, such as <font>
and <center>
, whose effects are handled by CSS. There is also a renewed emphasis on the importance of DOM scripting in Web behavior.
The HTML5 syntax is no longer based on SGML despite its markup being very close. It has, however, been designed to be backward compatible with common parsing of older versions of HTML. It comes with a new introducing line which looks like an SGML document type declaration, <!DOCTYPE html>
, and enables standards-compliant rendering in all browsers that use “DOCTYPE sniffing”.
New APIs
In addition to specifying markup, HTML 5 specifies scripting application programming interfaces (APIs).[4] Existing Document Object Model (DOM) interfaces are extended and de facto features documented. There are also new APIs, such as:
- The canvas tag for immediate mode 2D drawing
- Timed media playback
- Offline storage database
- Document editing
- Drag-and-drop
- Cross-document messaging
- Browser history management
- MIME type and protocol handler registration
Some of the new features are part of HTML 5 mainly because there are no volunteers to split HTML 5 and maintain separate specifications of these features[5].
Differences from HTML 4/XHTML 1.x
The following is a cursory list of differences and some specific examples.
- New parsing rules oriented towards flexible parsing and compatibility
- New elements –
section
,audio
,video
,progress
,nav
,meter
,time
,aside
,canvas
,datagrid
- New types of form controls – dates and times,
email
,url
,search
- New attributes –
ping
,charset
,async
- Global attributes (that can be applied for every element) –
id
,tabindex
,repeat
- Deprecated elements dropped –
center
,font
,strike
Error handling
An HTML5 (text/html) browser will be flexible in handling incorrect syntax, in contrast to the XHTML variant of HTML 5 (XHTML5), where such errors must not be ignored. HTML5 is designed so that old HTML 4 browsers can safely ignore new HTML 5 constructs. In contrast to HTML 4, the HTML 5 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.[6]
Ogg controversy
HTML 5 introduces new ways of inserting sound and video in webpages with the <audio>
and <video>
elements. Previously, the specification recommended the use of Ogg formats Vorbis and Theora, but this recommendation was later removed[7] after Apple[8] and Nokia[9] had opposed the move. Opera Software and Mozilla have been advocates for including the Ogg formats into the HTML standard[10][11] and have included native decoding for these formats in their browsers.
On December 11, 2007, mention of the HTML 5 specification was updated replacing the reference to concrete formats with a placeholder:[12]
Original | Replacement |
---|---|
User agents should support Ogg Theora video and Ogg Vorbis audio, as well as the Ogg container format | It would be helpful for interoperability if all browsers could support the same codecs. However, there are no known codecs that satisfy all the current players: […] This is an ongoing issue and this section will be updated once more information is available. |
The removal of the Ogg formats from the specification has been criticized by some Web developers.[13][14] In response to such criticism, WHATWG has cited concerns from influential companies including Nokia and Apple over the Ogg formats still being within patent lifetime and thus vulnerable to unexpected future patent challenges.[15] A follow-up discussion also occurred on the W3C questions and answers blog.[16]
Background
On October 17, 2007, the W3C encouraged interested people to take part in a "Video on the Web Workshop", held on December 12, 2007 for two days.[17] A number of global companies were involved, submitting position papers.[18] Among them, Nokia's paper states that "a W3C-led standardization of a 'free' codec, or the active endorsement of proprietary technology such as Ogg … by W3C, is, in our opinion, not helpful."[9] Whether Ogg is proprietary is debatable; while the formats are clearly open, they are designed and maintained by an international organization, Xiph.org. Ogg has followed a path similar to many other formats of the Internet age, such as PNG and GZip. While Xiph.org controls and defines the Ogg format specifications and their reference implementations, it does not own any patents and cannot control use of the formats, and the formats are thus not proprietary to Xiph.org.
See also
- Comparison of layout engines (HTML 5)
- Trident, used by Microsoft in Internet Explorer
- Gecko, used by Mozilla in Mozilla Firefox and other applications
- Presto, used by Opera Software in the Opera browser
- KHTML, used in Konqueror
- WebKit, used by Apple in Safari and by Nokia and Google (derived from KHTML)
References
- ^ a b "HTML 5: A vocabulary and associated APIs for HTML and XHTML". W3C. Retrieved 2009-01-28.
- ^ "When will HTML 5 be finished?". WHATWG. WHATWG Wiki. Retrieved 2008-06-14.
- ^ IBM Developer Works New elements in HTML5: Structure and semantics
- ^ HTML 5 differences from HTML4 - APIs W3C
- ^ Hickson, Ian (2008-10-27). "HTML 5 Specification - List of sections and corresponding work estimates". public-html@w3.org (Mailing list). Retrieved 2008-12-10.
{{cite mailing list}}
: Check date values in:|date=
(help); External link in
(help); Unknown parameter|mailinglist=
|mailinglist=
ignored (|mailing-list=
suggested) (help) - ^ "FAQ – WHATWG Wiki". WHATWG. Retrieved 2008-02-25.
- ^ Hickson, Ian (10 December 2007). "[whatwg] Video codec requirements changed". whatwg mailing list (Mailing list). Retrieved 2008-02-25.
{{cite mailing list}}
: Unknown parameter|mailinglist=
ignored (|mailing-list=
suggested) (help) - ^ Stachowiak, Maciej (21 March 2007). "[whatwg] Codecs (was Re: Apple Proposal for Timed Media Elements)". whatwg mailing list (Mailing list). Retrieved 2008-02-25.
{{cite mailing list}}
: Unknown parameter|mailinglist=
ignored (|mailing-list=
suggested) (help) - ^ a b Wenger, Stephan (28 November 2007). "Web Architecture and Codec Considerations for Audio-Visual Services" (PDF). W3C Workshop on Video on the Web, December 12-13, 2007. Retrieved 2008-02-25.
{{cite conference}}
: Unknown parameter|booktitle=
ignored (|book-title=
suggested) (help) - ^ PC World - Mozilla, Opera Want to Make Video on the Web Easier
- ^ Opera <video> release on Labs - Opera Developer Community
- ^ html5.org
- ^ rudd-o.com
- ^ Abbadingo » Blog » Removal of Ogg Vorbis and Theora from HTML 5: an outrageous disaster
- ^ Hickson, Ian (11 December). "Re: [whatwg] Removal of Ogg is *preposterous*". whatwg mailing list (Mailing list). Retrieved 2008-02-25.
{{cite mailing list}}
: Check date values in:|date=
(help); Unknown parameter|mailinglist=
ignored (|mailing-list=
suggested) (help) - ^ "When will HTML 5 support <video>? Sooner if you help"
- ^ "W3C Video on the Web Workshop". Retrieved 2008-06-14.
- ^ http://www.w3.org/2007/08/video/positions/ position papers