text:
HTML
From Wikipedia, the free encyclopedia
Jump to: navigation, search
".htm" and ".html" redirect here. For other uses, see HTM.
For the use of HTML on Wikipedia, see Help:HTML in wikitext.
HTML
(Hypertext Markup Language)
Filename extension
.html
.htm
Internet media type
text/html
Type code
TEXT
Developed by
W3C & WHATWG
Initial release
1993; 24 years ago (1993)
Latest release
5.1 2nd Edition[1] / 5.2 (working draft)[2]
(1 November 2016; 11 months ago (2016-11-01))
Type of format
Document file format
Extended from
SGML
Extended to
XHTML
Standards
ISO/IEC 15445
W3C HTML latest recommendation
HTML Living Standard
W3C HTML 5.1
Open format?
Yes
Website
www.w3.org/html/
whatwg.org
HTML
HTML
Dynamic HTML
HTML5
audio
canvas
video
XHTML
Basic
Mobile Profile
C-HTML
HTML element
span and div
HTML attribute
HTML frame
HTML editor
Character encodings
Unicode
Language code
Document Object Model
Browser Object Model
Style sheets
CSS
Font family
Web colors
HTML scripting
JavaScript
WebGL
WebCL
W3C
Validator
WHATWG
Quirks mode
Web storage
Web browser (layout) engine
Comparisons
Document markup languages
Web browsers
HTML
Non-standard HTML
HTML5
canvas
media
XHTML
1.1
v
t
e
Hypertext Markup Language (HTML) is the standard markup language for creating web pages and web applications. With Cascading Style Sheets (CSS) and JavaScript it forms a triad of cornerstone technologies for the World Wide Web.[3] Web browsers receive HTML documents from a web server or from local storage and render them into multimedia web pages. HTML describes the structure of a web page semantically and originally included cues for the appearance of the document.
HTML elements are the building blocks of HTML pages. With HTML constructs, images and other objects, such as interactive forms, may be embedded into the rendered page. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. HTML elements are delineated by tags, written using angle brackets. Tags such as  and <input /> introduce content into the page directly. Others such as
...
 surround and provide information about document text and may include other tags as sub-elements. Browsers do not display the HTML tags, but use them to interpret the content of the page.
HTML can embed programs written in a scripting language such as JavaScript which affect the behavior and content of web pages. Inclusion of CSS defines the look and layout of content. The World Wide Web Consortium (W3C), maintainer of both the HTML and the CSS standards, has encouraged the use of CSS over explicit presentational HTML since 1997.[4]
Contents
[hide]
1 History
1.1 Development
1.2 HTML versions timeline
1.2.1 HTML draft version timeline
1.2.2 XHTML versions
2 Markup
2.1 Elements
2.1.1 Element examples
2.1.2 Attributes
2.2 Character and entity references
2.3 Data types
2.4 Document type declaration
3 Semantic HTML
4 Delivery
4.1 HTTP
4.2 HTML e-mail
4.3 Naming conventions
4.4 HTML Application
5 HTML4 variations
5.1 SGML-based versus XML-based HTML
5.2 Transitional versus strict
5.3 Frameset versus transitional
5.4 Summary of specification versions
6 HTML5 variations
6.1 WHATWG HTML versus HTML5
7 Hypertext features not in HTML
8 WYSIWYG editors
9 See also
10 References
11 External links
History
The historic logo made by the W3C
An example website written in HTML
Development
Tim Berners-Lee
In 1980, physicist Tim Berners-Lee, a contractor at CERN, proposed and prototyped ENQUIRE, a system for CERN researchers to use and share documents. In 1989, Berners-Lee wrote a memo proposing an Internet-based hypertext system.[5] Berners-Lee specified HTML and wrote the browser and server software in late 1990. That year, Berners-Lee and CERN data systems engineer Robert Cailliau collaborated on a joint request for funding, but the project was not formally adopted by CERN. In his personal notes[6] from 1990 he listed[7] "some of the many areas in which hypertext is used" and put an encyclopedia first.
The first publicly available description of HTML was a document called "HTML Tags", first mentioned on the Internet by Tim Berners-Lee in late 1991.[8][9] It describes 18 elements comprising the initial, relatively simple design of HTML. Except for the hyperlink tag, these were strongly influenced by SGMLguid, an in-house Standard Generalized Markup Language (SGML)-based documentation format at CERN. Eleven of these elements still exist in HTML 4.[10]
HTML is a markup language that web browsers use to interpret and compose text, images, and other material into visual or audible web pages. Default characteristics for every item of HTML markup are defined in the browser, and these characteristics can be altered or enhanced by the web page designer's additional use of CSS. Many of the text elements are found in the 1988 ISO technical report TR 9537 Techniques for using SGML, which in turn covers the features of early text formatting languages such as that used by the RUNOFF command developed in the early 1960s for the CTSS (Compatible Time-Sharing System) operating system: these formatting commands were derived from the commands used by typesetters to manually format documents. However, the SGML concept of generalized markup is based on elements (nested annotated ranges with attributes) rather than merely print effects, with also the separation of structure and markup; HTML has been progressively moved in this direction with CSS.
Berners-Lee considered HTML to be an application of SGML. It was formally defined as such by the Internet Engineering Task Force (IETF) with the mid-1993 publication of the first proposal for an HTML specification, the "Hypertext Markup Language (HTML)" Internet Draft by Berners-Lee and Dan Connolly, which included an SGML Document type definition to define the grammar.[11][12] The draft expired after six months, but was notable for its acknowledgment of the NCSA Mosaic browser's custom tag for embedding in-line images, reflecting the IETF's philosophy of basing standards on successful prototypes.[13] Similarly, Dave Raggett's competing Internet-Draft, "HTML+ (Hypertext Markup Format)", from late 1993, suggested standardizing already-implemented features like tables and fill-out forms.[14]
After the HTML and HTML+ drafts expired in early 1994, the IETF created an HTML Working Group, which in 1995 completed "HTML 2.0", the first HTML specification intended to be treated as a standard against which future implementations should be based.[15]
Further development under the auspices of the IETF was stalled by competing interests. Since 1996, the HTML specifications have been maintained, with input from commercial software vendors, by the World Wide Web Consortium (W3C).[16] However, in 2000, HTML also became an international standard (ISO/IEC 15445:2000). HTML 4.01 was published in late 1999, with further errata published through 2001. In 2004, development began on HTML5 in the Web Hypertext Application Technology Working Group (WHATWG), which became a joint deliverable with the W3C in 2008, and completed and standardized on 28 October 2014.[17]
HTML versions timeline
November 24, 1995
HTML 2.0 was published as IETF RFC 1866. Supplemental RFCs added capabilities:
November 25, 1995: RFC 1867 (form-based file upload)
May 1996: RFC 1942 (tables)
August 1996: RFC 1980 (client-side image maps)
January 1997: RFC 2070 (internationalization)
January 14, 1997
HTML 3.2[18] was published as a W3C Recommendation. It was the first version developed and standardized exclusively by the W3C, as the IETF had closed its HTML Working Group on September 12, 1996.[19]
Initially code-named "Wilbur",[20] HTML 3.2 dropped math formulas entirely, reconciled overlap among various proprietary extensions and adopted most of Netscape's visual markup tags. Netscape's blink element and Microsoft's marquee element were omitted due to a mutual agreement between the two companies.[16] A markup for mathematical formulas similar to that in HTML was not standardized until 14 months later in MathML.
December 18, 1997
HTML 4.0[21] was published as a W3C Recommendation. It offers three variations:
Strict, in which deprecated elements are forbidden
Transitional, in which deprecated elements are allowed
Frameset, in which mostly only frame related elements are allowed.
Initially code-named "Cougar",[20] HTML 4.0 adopted many browser-specific element types and attributes, but at the same time sought to phase out Netscape's visual markup features by marking them as deprecated in favor of style sheets. HTML 4 is an SGML application conforming to ISO 8879 – SGML.[22]
April 24, 1998
HTML 4.0[23] was reissued with minor edits without incrementing the version number.
December 24, 1999
HTML 4.01[24] was published as a W3C Recommendation. It offers the same three variations as HTML 4.0 and its last errata were published on May 12, 2001.
May 2000
ISO/IEC 15445:2000[25][26] ("ISO HTML", based on HTML 4.01 Strict) was published as an ISO/IEC international standard. In the ISO this standard falls in the domain of the ISO/IEC JTC1/SC34 (ISO/IEC Joint Technical Committee 1, Subcommittee 34 – Document description and processing languages).[25]
After HTML 4.01, there was no new version of HTML for many years as development of the parallel, XML-based language XHTML occupied the W3C's HTML Working Group through the early and mid-2000s.
October 28, 2014
HTML5[27] was published as a W3C Recommendation.[28]
November 1, 2016
HTML 5.1[29] was published as a W3C Recommendation.[30][31]
HTML draft version timeline
Logo of HTML5
October 1991
HTML Tags,[8] an informal CERN document listing 18 HTML tags, was first mentioned in public.
June 1992
First informal draft of the HTML DTD,[32] with seven[33][34][35] subsequent revisions (July 15, August 6, August 18, November 17, November 19, November 20, November 22)
November 1992
HTML DTD 1.1 (the first with a version number, based on RCS revisions, which start with 1.1 rather than 1.0), an informal draft[35]
June 1993
Hypertext Markup Language[36] was published by the IETF IIIR Working Group as an Internet Draft (a rough proposal for a standard). It was replaced by a second version[37] one month later, followed by six further drafts published by IETF itself[38] that finally led to HTML 2.0 in RFC 1866.
November 1993
HTML+ was published by the IETF as an Internet Draft and was a competing proposal to the Hypertext Markup Language draft. It expired in May 1994.
April 1995 (authored March 1995)
HTML 3.0[39] was proposed as a standard to the IETF, but the proposal expired five months later (28 September 1995)[40] without further action. It included many of the capabilities that were in Raggett's HTML+ proposal, such as support for tables, text flow around figures and the display of complex mathematical formulas.[40]
W3C began development of its own Arena browser as a test bed for HTML 3 and Cascading Style Sheets,[41][42][43] but HTML 3.0 did not succeed for several reasons. The draft was considered very large at 150 pages and the pace of browser development, as well as the number of interested parties, had outstripped the resources of the IETF.[16] Browser vendors, including Microsoft and Netscape at the time, chose to implement different subsets of HTML 3's draft features as well as to introduce their own extensions to it.[16] (see Browser wars). These included extensions to control stylistic aspects of documents, contrary to the "belief [of the academic engineering community] that such things as text color, background texture, font size and font face were definitely outside the scope of a language when their only intent was to specify how a document would be organized."[16] Dave Raggett, who has been a W3C Fellow for many years, has commented for example: "To a certain extent, Microsoft built its business on the Web by extending HTML features."[16]
January 2008
HTML5 was published as a Working Draft by the W3C.[44]
Although its syntax closely resembles that of SGML, HTML5 has abandoned any attempt to be an SGML application and has explicitly defined its own "html" serialization, in addition to an alternative XML-based XHTML5 serialization.[45]
2011 HTML5 – Last Call
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.[46] In January 2011, the WHATWG renamed its "HTML5" living standard to "HTML". The W3C nevertheless continues its project to release HTML5.[47]
2012 HTML5 – Candidate Recommendation
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 as a "snapshot" by WHATWG. The WHATWG organization will continue 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.[48]
In December 2012, W3C designated HTML5 as a Candidate Recommendation.[49] The criterion for advancement to W3C Recommendation is "two 100% complete and fully interoperable implementations".[50]
2014 HTML5 – Proposed Recommendation and Recommendation
In September 2014, W3C moved HTML5 to Proposed Recommendation.[51]
On 28 October 2014, HTML5 was released as a stable W3C Recommendation,[52] meaning the specification process is complete.[53]
XHTML versions
Main article: XHTML
XHTML is a separate language that began as a reformulation of HTML 4.01 using XML 1.0. It is no longer being developed as a separate standard.
XHTML 1.0 was published as a W3C Recommendation on January 26, 2000[54] and was later revised and republished on August 1, 2002. It offers the same three variations as HTML 4.0 and 4.01, reformulated in XML, with minor restrictions.
XHTML 1.1[55] was published as a W3C Recommendation on May 31, 2001. It is based on XHTML 1.0 Strict, but includes minor changes, can be customized, and is reformulated using modules in the W3C recommendation "Modularization of XHTML", which was published on April 10, 2001.[56]
XHTML 2.0 was a working draft, work on it was abandoned in 2009 in favor of work on HTML5 and XHTML5.[57][58][59] XHTML 2.0 was incompatible with XHTML 1.x and, therefore, would be more accurately characterized as an XHTML-inspired new language than an update to XHTML 1.x.
An XHTML syntax, known as "XHTML5.1", is being defined alongside HTML5 in the HTML5 draft.[60]
Markup
HTML markup consists of several key components, including those called tags (and their attributes), character-based data types, character references and entity references. HTML tags most commonly come in pairs like
 and
, although some represent empty elements and so are unpaired, for example . The first tag in such a pair is the start tag, and the second is the end tag (they are also called opening tags and closing tags).
Another important component is the HTML document type declaration, which triggers standards mode rendering.
The following is an example of the classic "Hello, World!" program, a common test employed for comparing programming languages, scripting languages and markup languages. This example is made using 9 source lines of code:
<!DOCTYPE html>   <title>This is a title</title>
Hello world!

(The text between  and  describes the web page, and the text between  and  is the visible page content. The markup text "<title>This is a title</title>" defines the browser page title.)
The Document Type Declaration <!DOCTYPE html> is for HTML5. If a declaration is not included, various browsers will revert to "quirks mode" for rendering.[61]
Elements
Main article: HTML element
HTML documents imply a structure of nested HTML elements. These are indicated in the document by HTML tags, enclosed in angle brackets thus:
[62]
In the simple, general case, the extent of an element is indicated by a pair of tags: a "start tag"
 and "end tag"
. The text content of the element, if any, is placed between these tags.
Tags may also enclose further tag markup between the start and end, including a mixture of tags and text. This indicates further (nested) elements, as children of the parent element.
The start tag may also include attributes within the tag. These indicate other information, such as identifiers for sections within the document, identifiers used to bind style information to the presentation of the document, and for some tags such as the  used to embed images, the reference to the image resource.
Some elements, such as the line break
, do not permit any embedded content, either text or further tags. These require only a single empty tag (akin to a start tag) and do not use an end tag.
Many tags, particularly the closing end tag for the very commonly used paragraph element
, are optional. An HTML browser or other agent can infer the closure for the end of an element from the context and the structural rules defined by the HTML standard. These rules are complex and not widely understood by most HTML coders.
The general form of an HTML element is therefore: <tag attribute1="value1" attribute2="value2">''content''</tag>. Some HTML elements are defined as empty elements and take the form <tag attribute1="value1" attribute2="value2">. Empty elements may enclose no content, for instance, the
 tag or the inline  tag. The name of an HTML element is the name used in the tags. Note that the end tag's name is preceded by a slash character, "/", and that in empty elements the end tag is neither required nor allowed. If attributes are not mentioned, default values are used in each case.
Element examples
Header of the HTML document: .... The title is included in the head, for example:
 <title>The Title</title>
Headings: HTML headings are defined with the
 to
 tags:

Heading level 1

Heading level 2

Heading level 3

Heading level 4

Heading level 5

Heading level 6

Paragraphs:

Paragraph 1

Paragraph 2

Line breaks:
. The difference between
 and
 is that "br" breaks a line without altering the semantic structure of the page, whereas "p" sections the page into paragraphs. Note also that "br" is an empty element in that, although it may have attributes, it can take no content and it may not have an end tag.

This
 is a paragraph
 with
 line breaks

This is a link in HTML. To create a link the  tag is used. The href= attribute holds the URL address of the link.
A link to Wikipedia!
Inputs:
There are many possible ways a user can give input/s like:
1 <input type="text" />  2 <input type="file" />  3 <input type="checkbox" />
Comments:

Comments can help in the understanding of the markup and do not display in the webpage.
There are several types of markup elements used in HTML:
Structural markup indicates the purpose of text
For example,
Golf
 establishes "Golf" as a second-level heading. Structural markup does not denote any specific rendering, but most web browsers have default styles for element formatting. Content may be further styled using Cascading Style Sheets (CSS).[63]
Presentational markup indicates the appearance of the text, regardless of its purpose
For example, boldface indicates that visual output devices should render "boldface" in bold text, but gives little indication what devices that are unable to do this (such as aural devices that read the text aloud) should do. In the case of both bold and italic, there are other elements that may have equivalent visual renderings but that are more semantic in nature, such as strong text and emphasised text respectively. It is easier to see how an aural user agent should interpret the latter two elements. However, they are not equivalent to their presentational counterparts: it would be undesirable for a screen-reader to emphasize the name of a book, for instance, but on a screen such a name would be italicized. Most presentational markup elements have become deprecated under the HTML 4.0 specification in favor of using CSS for styling.
Hypertext markup makes parts of a document into links to other documents
An anchor element creates a hyperlink in the document and its href attribute sets the link's target URL. For example, the HTML markup, Wikipedia, will render the word "Wikipedia" as a hyperlink. To render an image as a hyperlink, an "img" element is inserted as content into the "a" element. Like "br", "img" is an empty element with attributes but no content or closing tag. .
Attributes
Main article: HTML attribute
Most of the attributes of an element are name-value pairs, separated by "=" and written within the start tag of an element after the element's name. The value may be enclosed in single or double quotes, although values consisting of certain characters can be left unquoted in HTML (but not XHTML) .[64][65] Leaving attribute values unquoted is considered unsafe.[66] In contrast with name-value pair attributes, there are some attributes that affect the element simply by their presence in the start tag of the element,[8] like the ismap attribute for the img element.[67]
There are several common attributes that may appear in many elements :
The id attribute provides a document-wide unique identifier for an element. This is used to identify the element so that stylesheets can alter its presentational properties, and scripts may alter, animate or delete its contents or presentation. Appended to the URL of the page, it provides a globally unique identifier for the element, typically a sub-section of the page. For example, the ID "Attributes" in http://en.wikipedia.org/wiki/HTML#Attributes
The class attribute provides a way of classifying similar elements. This can be used for semantic or presentation purposes. For example, an HTML document might semantically use the designation class="notation" to indicate that all elements with this class value are subordinate to the main text of the document. In presentation, such elements might be gathered together and presented as footnotes on a page instead of appearing in the place where they occur in the HTML source. Class attributes are used semantically in microformats. Multiple class values may be specified; for example class="notation important" puts the element into both the "notation" and the "important" classes.
An author may use the style attribute to assign presentational properties to a particular element. It is considered better practice to use an element's id or class attributes to select the element from within a stylesheet, though sometimes this can be too cumbersome for a simple, specific, or ad hoc styling.
The title attribute is used to attach subtextual explanation to an element. In most browsers this attribute is displayed as a tooltip.
The lang attribute identifies the natural language of the element's contents, which may be different from that of the rest of the document. For example, in an English-language document:

Oh well, c'est la vie, as they say in France.

The abbreviation element, abbr, can be used to demonstrate some of these attributes :
HTML
This example displays as HTML; in most browsers, pointing the cursor at the abbreviation should display the title text "Hypertext Markup Language."
Most elements take the language-related attribute dir to specify text direction, such as with "rtl" for right-to-left text in, for example, Arabic, Persian or Hebrew.[68]
Character and entity references
See also: List of XML and HTML character entity references and Unicode and HTML
As of version 4.0, HTML defines a set of 252 character entity references and a set of 1,114,050 numeric character references, both of which allow individual characters to be written via simple markup, rather than literally. A literal character and its markup counterpart are considered equivalent and are rendered identically.
The ability to "escape" characters in this way allows for the characters < and & (when written as < and &, respectively) to be interpreted as character data, rather than markup. For example, a literal < normally indicates the start of a tag, and & normally indicates the start of a character entity reference or numeric character reference; writing it as & or & or & allows & to be included in the content of an element or in the value of an attribute. The double-quote character ("), when not used to quote an attribute value, must also be escaped as " or " or " when it appears within the attribute value itself. Equivalently, the single-quote character ('), when not used to quote an attribute value, must also be escaped as ' or ' (or as ' in HTML5 or XHTML documents[69][70]) when it appears within the attribute value itself. If document authors overlook the need to escape such characters, some browsers can be very forgiving and try to use context to guess their intent. The result is still invalid markup, which makes the document less accessible to other browsers and to other user agents that may try to parse the document for search and indexing purposes for example.
Escaping also allows for characters that are not easily typed, or that are not available in the document's character encoding, to be represented within element and attribute content. For example, the acute-accented e (é), a character typically found only on Western European and South American keyboards, can be written in any HTML document as the entity reference é or as the numeric references é or é, using characters that are available on all keyboards and are supported in all character encodings. Unicode character encodings such as UTF-8 are compatible with all modern browsers and allow direct access to almost all the characters of the world's writing systems.[71]
Data types
HTML defines several data types for element content, such as script data and stylesheet data, and a plethora of types for attribute values, including IDs, names, URIs, numbers, units of length, languages, media descriptors, colors, character encodings, dates and times, and so on. All of these data types are specializations of character data.
Document type declaration
HTML documents are required to start with a Document Type Declaration (informally, a "doctype"). In browsers, the doctype helps to define the rendering mode—particularly whether to use quirks mode.
The original purpose of the doctype was to enable parsing and validation of HTML documents by SGML tools based on the Document Type Definition (DTD). The DTD to which the DOCTYPE refers contains a machine-readable grammar specifying the permitted and prohibited content for a document conforming to such a DTD. Browsers, on the other hand, do not implement HTML as an application of SGML and by consequence do not read the DTD.
HTML5 does not define a DTD; therefore, in HTML5 the doctype declaration is simpler and shorter:[72]
<!DOCTYPE html>
An example of an HTML 4 doctype
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
This declaration references the DTD for the "strict" version of HTML 4.01. SGML-based validators read the DTD in order to properly parse the document and to perform validation. In modern browsers, a valid doctype activates standards mode as opposed to quirks mode.
In addition, HTML 4.01 provides Transitional and Frameset DTDs, as explained below. Transitional type is the most inclusive, incorporating current tags as well as older or "deprecated" tags, with the Strict DTD excluding deprecated tags. Frameset has all tags necessary to make frames on a page along with the tags included in transitional type[citation needed].
Semantic HTML
Main article: Semantic HTML
Semantic HTML is a way of writing HTML that emphasizes the meaning of the encoded information over its presentation (look). HTML has included semantic markup from its inception,[73] but has also included presentational markup, such as ,  and  tags. There are also the semantically neutral span and div tags. Since the late 1990s when Cascading Style Sheets were beginning to work in most browsers, web authors have been encouraged to avoid the use of presentational HTML markup with a view to the separation of presentation and content.[74]
In a 2001 discussion of the Semantic Web, Tim Berners-Lee and others gave examples of ways in which intelligent software "agents" may one day automatically crawl the web and find, filter and correlate previously unrelated, published facts for the benefit of human users.[75] Such agents are not commonplace even now, but some of the ideas of Web 2.0, mashups and price comparison websites may be coming close. The main difference between these web application hybrids and Berners-Lee's semantic agents lies in the fact that the current aggregation and hybridization of information is usually designed in by web developers, who already know the web locations and the API semantics of the specific data they wish to mash, compare and combine.
An important type of web agent that does crawl and read web pages automatically, without prior knowledge of what it might find, is the web crawler or search-engine spider. These software agents are dependent on the semantic clarity of web pages they find as they use various techniques and algorithms to read and index millions of web pages a day and provide web users with search facilities without which the World Wide Web's usefulness would be greatly reduced.
In order for search-engine spiders to be able to rate the significance of pieces of text they find in HTML documents, and also for those creating mashups and other hybrids as well as for more automated agents as they are developed, the semantic structures that exist in HTML need to be widely and uniformly applied to bring out the meaning of published text.[76]
Presentational markup tags are deprecated in current HTML and XHTML recommendations and are illegal in HTML5[citation needed].
Good semantic HTML also improves the accessibility of web documents (see also Web Content Accessibility Guidelines). For example, when a screen reader or audio browser can correctly ascertain the structure of a document, it will not waste the visually impaired user's time by reading out repeated or irrelevant information when it has been marked up correctly.
Delivery
HTML documents can be delivered by the same means as any other computer file. However, they are most often delivered either by HTTP from a web server or by email.
HTTP
Main article: Hypertext Transfer Protocol
The World Wide Web is composed primarily of HTML documents transmitted from web servers to web browsers using the Hypertext Transfer Protocol (HTTP). However, HTTP is used to serve images, sound, and other content, in addition to HTML. To allow the web browser to know how to handle each document it receives, other information is transmitted along with the document. This meta data usually includes the MIME type (e.g. text/html or application/xhtml+xml) and the character encoding (see Character encoding in HTML).
In modern browsers, the MIME type that is sent with the HTML document may affect how the document is initially interpreted. A document sent with the XHTML MIME type is expected to be well-formed XML; syntax errors may cause the browser to fail to render it. The same document sent with the HTML MIME type might be displayed successfully, since some browsers are more lenient with HTML.
The W3C recommendations state that XHTML 1.0 documents that follow guidelines set forth in the recommendation's Appendix C may be labeled with either MIME Type.[77] XHTML 1.1 also states that XHTML 1.1 documents should[78] be labeled with either MIME type.[79]
HTML e-mail
Main article: HTML email
Most graphical email clients allow the use of a subset of HTML (often ill-defined) to provide formatting and semantic markup not available with plain text. This may include typographic information like coloured headings, emphasized and quoted text, inline images and diagrams. Many such clients include both a GUI editor for composing HTML e-mail messages and a rendering engine for displaying them. Use of HTML in e-mail is criticized by some because of compatibility issues, because it can help disguise phishing attacks, because of accessibility issues for blind or visually impaired people, because it can confuse spam filters and because the message size is larger than plain text.
Naming conventions
The most common filename extension for files containing HTML is .html. A common abbreviation of this is .htm, which originated because some early operating systems and file systems, such as DOS and the limitations imposed by FAT data structure, limited file extensions to three letters.[80]
HTML Application
Main article: HTML Application
An HTML Application (HTA; file extension ".hta") is a Microsoft Windows application that uses HTML and Dynamic HTML in a browser to provide the application's graphical interface. A regular HTML file is confined to the security model of the web browser's security, communicating only to web servers and manipulating only webpage objects and site cookies. An HTA runs as a fully trusted application and therefore has more privileges, like creation/editing/removal of files and Windows Registry entries. Because they operate outside the browser's security model, HTAs cannot be executed via HTTP, but must be downloaded (just like an EXE file) and executed from local file system.
HTML4 variations
Since its inception, HTML and its associated protocols gained acceptance relatively quickly.[by whom?] However, no clear standards existed in the early years of the language. Though its creators originally conceived of HTML as a semantic language devoid of presentation details,[81] practical uses pushed many presentational elements and attributes into the language, driven largely by the various browser vendors. The latest standards surrounding HTML reflect efforts to overcome the sometimes chaotic development of the language[82] and to create a rational foundation for building both meaningful and well-presented documents. To return HTML to its role as a semantic language, the W3C has developed style languages such as CSS and XSL to shoulder the burden of presentation. In conjunction, the HTML specification has slowly reined in the presentational elements.
There are two axes differentiating various variations of HTML as currently specified: SGML-based HTML versus XML-based HTML (referred to as XHTML) on one axis, and strict versus transitional (loose) versus frameset on the other axis.
SGML-based versus XML-based HTML
One difference in the latest HTML specifications lies in the distinction between the SGML-based specification and the XML-based specification. The XML-based specification is usually called XHTML to distinguish it clearly from the more traditional definition. However, the root element name continues to be "html" even in the XHTML-specified HTML. The W3C intended XHTML 1.0 to be identical to HTML 4.01 except where limitations of XML over the more complex SGML require workarounds. Because XHTML and HTML are closely related, they are sometimes documented in parallel. In such circumstances, some authors conflate the two names as (X)HTML or X(HTML).
Like HTML 4.01, XHTML 1.0 has three sub-specifications: strict, transitional and frameset.
Aside from the different opening declarations for a document, the differences between an HTML 4.01 and XHTML 1.0 document—in each of the corresponding DTDs—are largely syntactic. The underlying syntax of HTML allows many shortcuts that XHTML does not, such as elements with optional opening or closing tags, and even empty elements which must not have an end tag. By contrast, XHTML requires all elements to have an opening tag and a closing tag. XHTML, however, also introduces a new shortcut: an XHTML tag may be opened and closed within the same tag, by including a slash before the end of the tag like this:
. The introduction of this shorthand, which is not used in the SGML declaration for HTML 4.01, may confuse earlier software unfamiliar with this new convention. A fix for this is to include a space before closing the tag, as such:
.[83]
To understand the subtle differences between HTML and XHTML, consider the transformation of a valid and well-formed XHTML 1.0 document that adheres to Appendix C (see below) into a valid HTML 4.01 document. To make this translation requires the following steps:
The language for an element should be specified with a lang attribute rather than the XHTML xml:lang attribute. XHTML uses XML's built in language-defining functionality attribute.
Remove the XML namespace (xmlns=URI). HTML has no facilities for namespaces.
Change the document type declaration from XHTML 1.0 to HTML 4.01. (see DTD section for further explanation).
If present, remove the XML declaration. (Typically this is: <?xml version="1.0" encoding="utf-8"?>).
Ensure that the document's MIME type is set to text/html. For both HTML and XHTML, this comes from the HTTP Content-Type header sent by the server.
Change the XML empty-element syntax to an HTML style empty element (
 to
).
Those are the main changes necessary to translate a document from XHTML 1.0 to HTML 4.01. To translate from HTML to XHTML would also require the addition of any omitted opening or closing tags. Whether coding in HTML or XHTML it may just be best to always include the optional tags within an HTML document rather than remembering which tags can be omitted.
A well-formed XHTML document adheres to all the syntax requirements of XML. A valid document adheres to the content specification for XHTML, which describes the document structure.
The W3C recommends several conventions to ensure an easy migration between HTML and XHTML (see HTML Compatibility Guidelines). The following steps can be applied to XHTML 1.0 documents only:
Include both xml:lang and lang attributes on any elements assigning language.
Use the empty-element syntax only for elements specified as empty in HTML.
Include an extra space in empty-element tags: for example
 instead of
.
Include explicit close tags for elements that permit content but are left empty (for example,

, not
).
Omit the XML declaration.
By carefully following the W3C's compatibility guidelines, a user agent should be able to interpret the document equally as HTML or XHTML. For documents that are XHTML 1.0 and have been made compatible in this way, the W3C permits them to be served either as HTML (with a text/html MIME type), or as XHTML (with an application/xhtml+xml or application/xml MIME type). When delivered as XHTML, browsers should use an XML parser, which adheres strictly to the XML specifications for parsing the document's contents.
Transitional versus strict
HTML 4 defined three different versions of the language: Strict, Transitional (once called Loose) and Frameset. The Strict version is intended for new documents and is considered best practice, while the Transitional and Frameset versions were developed to make it easier to transition documents that conformed to older HTML specification or didn't conform to any specification to a version of HTML 4. The Transitional and Frameset versions allow for presentational markup, which is omitted in the Strict version. Instead, cascading style sheets are encouraged to improve the presentation of HTML documents. Because XHTML 1 only defines an XML syntax for the language defined by HTML 4, the same differences apply to XHTML 1 as well.
The Transitional version allows the following parts of the vocabulary, which are not included in the Strict version:
A looser content model
Inline elements and plain text are allowed directly in: body, blockquote, form, noscript and noframes
Presentation related elements
underline (u)(Deprecated. can confuse a visitor with a hyperlink.)
strike-through (s)
center (Deprecated. use CSS instead.)
font (Deprecated. use CSS instead.)
basefont (Deprecated. use CSS instead.)
Presentation related attributes
background (Deprecated. use CSS instead.) and bgcolor (Deprecated. use CSS instead.) attributes for body (required element according to the W3C.) element.
align (Deprecated. use CSS instead.) attribute on div, form, paragraph (p) and heading (h1...h6) elements
align (Deprecated. use CSS instead.), noshade (Deprecated. use CSS instead.), size (Deprecated. use CSS instead.) and width (Deprecated. use CSS instead.) attributes on hr element
align (Deprecated. use CSS instead.), border, vspace and hspace attributes on img and object (caution: the object element is only supported in Internet Explorer (from the major browsers)) elements
align (Deprecated. use CSS instead.) attribute on legend and caption elements
align (Deprecated. use CSS instead.) and bgcolor (Deprecated. use CSS instead.) on table element
nowrap (Obsolete), bgcolor (Deprecated. use CSS instead.), width, height on td and th elements
bgcolor (Deprecated. use CSS instead.) attribute on tr element
clear (Obsolete) attribute on br element
compact attribute on dl, dir and menu elements
type (Deprecated. use CSS instead.), compact (Deprecated. use CSS instead.) and start (Deprecated. use CSS instead.) attributes on ol and ul elements
type and value attributes on li element
width attribute on pre element
Additional elements in Transitional specification
menu (Deprecated. use CSS instead.) list (no substitute, though unordered list is recommended)
dir (Deprecated. use CSS instead.) list (no substitute, though unordered list is recommended)
isindex (Deprecated.) (element requires server-side support and is typically added to documents server-side, form and input elements can be used as a substitute)
applet (Deprecated. use the object element instead.)
The language (Obsolete) attribute on script element (redundant with the type attribute).
Frame related entities
iframe
noframes
target (Deprecated in the map, link and form elements.) attribute on a, client-side image-map (map), link, form and base elements
The Frameset version includes everything in the Transitional version, as well as the frameset element (used instead of body) and the frame element.
Frameset versus transitional
In addition to the above transitional differences, the frameset specifications (whether XHTML 1.0 or HTML 4.01) specify a different content model, with frameset replacing body, that contains either frame elements, or optionally noframes with a body.
Summary of specification versions
As this list demonstrates, the loose versions of the specification are maintained for legacy support. However, contrary to popular misconceptions, the move to XHTML does not imply a removal of this legacy support. Rather the X in XML stands for extensible and the W3C is modularizing the entire specification and opening it up to independent extensions. The primary achievement in the move from XHTML 1.0 to XHTML 1.1 is the modularization of the entire specification. The strict version of HTML is deployed in XHTML 1.1 through a set of modular extensions to the base XHTML 1.1 specification. Likewise, someone looking for the loose (transitional) or frameset specifications will find similar extended XHTML 1.1 support (much of it is contained in the legacy or frame modules). The modularization also allows for separate features to develop on their own timetable. So for example, XHTML 1.1 will allow quicker migration to emerging XML standards such as MathML (a presentational and semantic math language based on XML) and XForms—a new highly advanced web-form technology to replace the existing HTML forms.
In summary, the HTML 4 specification primarily reined in all the various HTML implementations into a single clearly written specification based on SGML. XHTML 1.0, ported this specification, as is, to the new XML defined specification. Next, XHTML 1.1 takes advantage of the extensible nature of XML and modularizes the whole specification. XHTML 2.0 was intended to be the first step in adding new features to the specification in a standards-body-based approach.
HTML5 variations
WHATWG HTML versus HTML5
Main article: HTML5
The WHATWG considers their work as living standard HTML for what constitutes the state of the art in major browser implementations by Apple (Safari), Google (Chrome), Mozilla (Firefox), Opera (Opera), and others. HTML5 is specified by the HTML Working Group of the W3C following the W3C process. As of 2013[update] both specifications are similar and mostly derived from each other, i.e., the work on HTML5 started with an older WHATWG draft, and later the WHATWG living standard was based on HTML5 drafts in 2011.[84][85]
Hypertext features not in HTML
HTML lacks some of the features found in earlier hypertext systems, such as source tracking, fat links and others.[86] Even some hypertext features that were in early versions of HTML have been ignored by most popular web browsers until recently[when?], such as the link element and in-browser Web page editing.
Sometimes Web services or browser manufacturers remedy these shortcomings. For instance, wikis and content management systems allow surfers to edit the Web pages they visit.
WYSIWYG editors
There are some WYSIWYG editors (What You See Is What You Get), in which the user lays out everything as it is to appear in the HTML document using a graphical user interface (GUI), often similar to word processors. The editor renders the document rather than show the code, so authors do not require extensive knowledge of HTML.
The WYSIWYG editing model has been criticized,[87][88] primarily because of the low quality of the generated code; there are voices advocating a change to the WYSIWYM model (What You See Is What You Mean).
WYSIWYG editors remain a controversial topic because of their perceived flaws such as:
Relying mainly on layout as opposed to meaning, often using markup that does not convey the intended meaning but simply copies the layout.[89]
Often producing extremely verbose and redundant code that fails to make use of the cascading nature of HTML and CSS.
Often producing ungrammatical markup, called tag soup or semantically incorrect markup (such as  for italics).
As a great deal of the information in HTML documents is not in the layout, the model has been criticized for its "what you see is all you get"-nature.[90]
See also
Breadcrumb (navigation)
Comparison of HTML parsers
Dynamic web page
HTML decimal character rendering
List of document markup languages
List of XML and HTML character entity references
Microdata (HTML)
Microformat
Polyglot markup
Semantic HTML
W3C (X)HTML Validator
References
Jump up ^ "HTML 5.1 2nd Edition". W3C. 2017-10-03. Retrieved 2017-10-03.
Jump up ^ "HTML 5.2 Editor’s Draft". W3C. 2017-10-13. Retrieved 2017-10-17.
Jump up ^ Flanagan, David. JavaScript - The definitive guide (6 ed.). p. 1. JavaScript is part of the triad of technologies that all Web developers must learn: HTML to specify the content of web pages, CSS to specify the presentation of web pages, and JavaScript to specify the behaviour of web pages.
Jump up ^ "HTML 4.0 Specification — W3C Recommendation — Conformance: requirements and recommendations". World Wide Web Consortium. December 18, 1997. Retrieved July 6, 2015.
Jump up ^ Tim Berners-Lee, "Information Management: A Proposal." CERN (March 1989, May 1990). W3.org
Jump up ^ Tim Berners-Lee, "Design Issues"
Jump up ^ Tim Berners-Lee, "Design Issues"
^ Jump up to: a b c "Tags used in HTML". World Wide Web Consortium. November 3, 1992. Retrieved November 16, 2008.
Jump up ^ "First mention of HTML Tags on the www-talk mailing list". World Wide Web Consortium. October 29, 1991. Retrieved April 8, 2007.
Jump up ^ "Index of elements in HTML 4". World Wide Web Consortium. December 24, 1999. Retrieved April 8, 2007.
Jump up ^ Tim Berners-Lee (December 9, 1991). "Re: SGML/HTML docs, X Browser (archived www-talk mailing list post)". Retrieved June 16, 2007. SGML is very general. HTML is a specific application of the SGML basic syntax applied to hypertext documents with simple structure.
Jump up ^ Berners-Lee, Tim; Connolly, Daniel (June 1993). "Hypertext Markup Language (HTML): A Representation of Textual Information and MetaInformation for Retrieval and Interchange". w3.org. Retrieved 2017-01-04.
Jump up ^ Raymond, Eric. "IETF and the RFC Standards Process". The Art of Unix Programming. Archived from the original on 2005-03-17. In IETF tradition, standards have to arise from experience with a working prototype implementation — but once they become standards, code that does not conform to them is considered broken and mercilessly scrapped. ...Internet-Drafts are not specifications; software implementers and vendors are specifically barred from claiming compliance with them as if they were specifications. Internet-Drafts are focal points for discussion, usually in a working group... Once an Internet-Draft has been published with an RFC number, it is a specification to which implementers may claim conformance. It is expected that the authors of the RFC and the community at large will begin correcting the specification with field experience.
Jump up ^ Raggett, Dave. "A Review of the HTML+ Document Format". Archived from the original on 2000-02-29. The hypertext markup language HTML was developed as a simple non-proprietary delivery format for global hypertext. HTML+ is a set of modular extensions to HTML and has been developed in response to a growing understanding of the needs of information providers. These extensions include text flow around floating figures, fill-out forms, tables and mathematical equations.
Jump up ^ Berners-Lee, Tim; Connelly, Daniel (November 1995). "RFC 1866 – Hypertext Markup Language – 2.0". Internet Engineering Task Force. Retrieved 1 December 2010. This document thus defines an HTML 2.0 (to distinguish it from the previous informal specifications). Future (generally upwardly compatible) versions of HTML with new features will be released with higher version numbers.
^ Jump up to: a b c d e f Raggett, Dave (1998). Raggett on HTML 4. Retrieved July 9, 2007.
Jump up ^ "HTML5 – Hypertext Markup Language – 5.0". Internet Engineering Task Force. 28 October 2014. Retrieved 25 November 2014. This document recommends HTML 5.0 after completion.
Jump up ^ "HTML 3.2 Reference Specification". World Wide Web Consortium. January 14, 1997. Retrieved November 16, 2008.
Jump up ^ "IETF HTML WG". Retrieved June 16, 2007. Note: This working group is closed
^ Jump up to: a b Arnoud Engelfriet. "Introduction to Wilbur". Web Design Group. Retrieved June 16, 2007.
Jump up ^ "HTML 4.0 Specification". World Wide Web Consortium. December 18, 1997. Retrieved November 16, 2008.
Jump up ^ "HTML 4 – 4 Conformance: requirements and recommendations". Retrieved December 30, 2009.
Jump up ^ "HTML 4.0 Specification". World Wide Web Consortium. April 24, 1998. Retrieved November 16, 2008.
Jump up ^ "HTML 4.01 Specification". World Wide Web Consortium. December 24, 1999. Retrieved November 16, 2008.
^ Jump up to: a b ISO (2000). "ISO/IEC 15445:2000 – Information technology – Document description and processing languages – HyperText Markup Language (HTML)". Retrieved December 26, 2009.
Jump up ^ Cs.Tcd.Ie. Cs.Tcd.Ie (2000-05-15). Retrieved on 2012-02-16.
Jump up ^ "HTML5: A vocabulary and associated APIs for HTML and XHTML". World Wide Web Consortium. 28 October 2014. Retrieved 31 October 2014.
Jump up ^ "Open Web Platform Milestone Achieved with HTML5 Recommendation" (Press release). World Wide Web Consortium. 28 October 2014. Retrieved 31 October 2014.
Jump up ^ "HTML 5.1". World Wide Web Consortium. 1 November 2016. Retrieved 6 January 2017.
Jump up ^ "HTML 5.1 is a W3C Recommendation". World Wide Web Consortium. 1 November 2016. Retrieved 6 January 2017.
Jump up ^ Philippe le Hegaret (17 November 2016). "HTML 5.1 is the gold standard". World Wide Web Consortium. Retrieved 6 January 2017.
Jump up ^ Connolly, Daniel (6 June 1992). "MIME as a hypertext architecture". CERN. Retrieved 24 October 2010.
Jump up ^ Connolly, Daniel (15 July 1992). "HTML DTD enclosed". CERN. Retrieved 24 October 2010.
Jump up ^ Connolly, Daniel (18 August 1992). "document type declaration subset for Hyper Text Markup Language as defined by the World Wide Web project". CERN. Retrieved 24 October 2010.
^ Jump up to: a b Connolly, Daniel (24 November 1992). "Document Type Definition for the Hyper Text Markup Language as used by the World Wide Web application". CERN. Retrieved 24 October 2010. See section "Revision History"
Jump up ^ Berners-Lee, Tim; Connolly, Daniel (June 1993). "Hyper Text Markup Language (HTML) Internet Draft version 1.1". IETF IIIR Working Group. Retrieved 18 September 2010.
Jump up ^ Berners-Lee, Tim; Connolly, Daniel (June 1993). "Hypertext Markup Language (HTML) Internet Draft version 1.2". IETF IIIR Working Group. Retrieved 18 September 2010.
Jump up ^ Berners-Lee, Tim; Connolly, Daniel (28 November 1994). "HyperText Markup Language Specification – 2.0 INTERNET DRAFT". IETF. Retrieved 24 October 2010.
Jump up ^ "HTML 3.0 Draft (Expired!) Materials". World Wide Web Consortium. December 21, 1995. Retrieved November 16, 2008.
^ Jump up to: a b "HyperText Markup Language Specification Version 3.0". Retrieved June 16, 2007.
Jump up ^ Raggett, Dave (28 March 1995). "HyperText Markup Language Specification Version 3.0". HTML 3.0 Internet Draft Expires in six months. World Wide Web Consortium. Retrieved 17 June 2010.
Jump up ^ Bowers, Neil. "Weblint: Just Another Perl Hack".
Jump up ^ Lie, Håkon Wium; Bos, Bert (April 1997). Cascading style sheets: designing for the Web. Addison Wesley Longman. p. 263. Retrieved 9 June 2010.
Jump up ^ "HTML5". World Wide Web Consortium. June 10, 2008. Retrieved November 16, 2008.
Jump up ^ "HTML5, one vocabulary, two serializations". Retrieved February 25, 2009.
Jump up ^ "W3C Confirms May 2011 for HTML5 Last Call, Targets 2014 for HTML5 Standard". World Wide Web Consortium. 14 February 2011. Retrieved 18 February 2011.
Jump up ^ Hickson, Ian. "HTML Is the New HTML5". Retrieved 21 January 2011.
Jump up ^ "HTML5 gets the splits.". netmagazine.com. Retrieved 23 July 2012.
Jump up ^ "HTML5". W3.org. 2012-12-17. Retrieved 2013-06-15.
Jump up ^ "When Will HTML5 Be Finished?". FAQ. WHAT Working Group. Retrieved 29 November 2009.
Jump up ^ "Call for Review: HTML5 Proposed Recommendation Published W3C News". W3.org. 2014-09-16. Retrieved 2014-09-27.
Jump up ^ "Open Web Platform Milestone Achieved with HTML5 Recommendation". W3C. 28 October 2014. Retrieved 29 October 2014.
Jump up ^ "HTML5 specification finalized, squabbling over specs continues". Ars Technica. 2014-10-29. Retrieved 2014-10-29.
Jump up ^ "XHTML 1.0: The Extensible HyperText Markup Language (Second Edition)". World Wide Web Consortium. January 26, 2000. Retrieved November 16, 2008.
Jump up ^ "XHTML 1.1 – Module-based XHTML — Second Edition". World Wide Web Consortium. February 16, 2007. Retrieved November 16, 2008.
Jump up ^ "Modularization of XHTML". www.w3.org. Retrieved 2017-01-04.
Jump up ^ "XHTM 2.0". World Wide Web Consortium. July 26, 2006. Retrieved November 16, 2008.
Jump up ^ "XHTML 2 Working Group Expected to Stop Work End of 2009, W3C to Increase Resources on HTML5". World Wide Web Consortium. July 17, 2009. Retrieved November 16, 2008.
Jump up ^ "W3C XHTML FAQ".
Jump up ^ "HTML5". W3C. 19 October 2013.
Jump up ^ Activating Browser Modes with Doctype. Hsivonen.iki.fi. Retrieved on 2012-02-16.
Jump up ^ "HTML Elements". w3schools. Retrieved 16 March 2015.
Jump up ^ "CSS Introduction". W3schools. Retrieved 16 March 2015.
Jump up ^ "On SGML and HTML". World Wide Web Consortium. Retrieved November 16, 2008.
Jump up ^ "XHTML 1.0 – Differences with HTML 4". World Wide Web Consortium. Retrieved November 16, 2008.
Jump up ^ Korpela, Jukka (July 6, 1998). "Why attribute values should always be quoted in HTML". Cs.tut.fi. Retrieved November 16, 2008.
Jump up ^ "Objects, Images, and Applets in HTML documents". World Wide Web Consortium. December 24, 1999. Retrieved November 16, 2008.
Jump up ^ "H56: Using the dir attribute on an inline element to resolve problems with nested directional runs". Techniques for WCAG 2.0. W3C. Retrieved 18 September 2010.
Jump up ^ "Character Entity Reference Chart". World Wide Web Consortium. October 24, 2012.
Jump up ^ "The Named Character Reference '". World Wide Web Consortium. January 26, 2000.
Jump up ^ "The Unicode Standard: A Technical Introduction". Retrieved 2010-03-16.
Jump up ^ "HTML: The Markup Language (an HTML language reference)". Retrieved 2013-08-19.
Jump up ^ Berners-Lee, Tim; Fischetti, Mark (2000). Weaving the Web: The Original Design and Ultimate Destiny of the World Wide Web by Its Inventor. San Francisco: Harper. ISBN 978-0-06-251587-2.
Jump up ^ Raggett, Dave (2002). "Adding a touch of style". W3C. Retrieved October 2, 2009. This article notes that presentational HTML markup may be useful when targeting browsers "before Netscape 4.0 and Internet Explorer 4.0". See the list of web browsers to confirm that these were both released in 1997.
Jump up ^ Tim Berners-Lee, James Hendler and Ora Lassila (2001). "The Semantic Web". Scientific American. Retrieved October 2, 2009.
Jump up ^ Nigel Shadbolt, Wendy Hall and Tim Berners-Lee (2006). "The Semantic Web Revisited" (PDF). IEEE Intelligent Systems. Retrieved October 2, 2009.
Jump up ^ "XHTML 1.0 The Extensible HyperText Markup Language (Second Edition)". World Wide Web Consortium. 2002 [2000]. Retrieved December 7, 2008. XHTML Documents which follow the guidelines set forth in Appendix C, "HTML Compatibility Guidelines" may be labeled with the Internet Media Type "text/html" [RFC2854], as they are compatible with most HTML browsers. Those documents, and any other document conforming to this specification, may also be labeled with the Internet Media Type "application/xhtml+xml" as defined in [RFC3236].
Jump up ^ "RFC 2119: Key words for use in RFCs to Indicate Requirement Levels". Harvard University. 1997. Retrieved December 7, 2008. 3. SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
Jump up ^ "XHTML 1.1 – Module-based XHTML — Second Edition". World Wide Web Consortium. 2007. Retrieved December 7, 2008. XHTML 1.1 documents SHOULD be labeled with the Internet Media Type text/html as defined in [RFC2854] or application/xhtml+xml as defined in [RFC3236].
Jump up ^ "Naming Files, Paths, and Namespaces". Microsoft. Retrieved 16 March 2015.
Jump up ^ HTML Design Constraints, W3C Archives
Jump up ^ WWW:BTB – HTML, Pris Sears
Jump up ^ Freeman, E (2005). Head First HTML. O'Reilly.
Jump up ^ Hickson, Ian (2011-01-19). "HTML is the new HTML5". The WHATWG blog. Retrieved 2013-01-14.
Jump up ^ "HTML5 — Smile, it's a Snapshot!". W3C Blog. 2012-12-17. Retrieved 2013-01-14.
Jump up ^ Jakob Nielsen (January 3, 2005). "Reviving Advanced Hypertext". Retrieved June 16, 2007.
Jump up ^ Sauer, C.: WYSIWIKI – Questioning WYSIWYG in the Internet Age. In: Wikimania (2006)
Jump up ^ Spiesser, J., Kitchen, L.: Optimization of HTML automatically generated by WYSIWYG programs. In: 13th International Conference on World Wide Web, pp. 355—364. WWW '04. ACM, New York, NY (New York, NY, U.S., May 17–20, 2004)
Jump up ^ XHTML Reference: blockquote. Xhtml.com. Retrieved on 2012-02-16.
Jump up ^ Doug Engelbart's INVISIBLE REVOLUTION . Invisiblerevolution.net. Retrieved on 2012-02-16.
External links
Find more aboutHTMLat Wikipedia's sister projects
Definitions from Wiktionary
Media from Commons
Textbooks from Wikibooks
Learning resources from Wikiversity
Data from Wikidata
Discussion from Meta-Wiki
Documentation from MediaWiki
HTML at DMOZ
WHATWG's HTML Living Standard
W3C's HTML 5.2, the upcoming version of HTML
W3C's HTML 5.1, the most recent finished specification (1 November 2016)
Dave Raggett's Introduction to HTML
Tim Berners-Lee Gives the Web a New Definition
[hide]
v
t
e
World Wide Web Consortium (W3C)
Products and
standards
Recommendations
ARIA
Canonical XML
CDF
CSS
DOM
Geolocation API
HTML (HTML5)
ITS
JSON-LD
Linked Data Notifications
MathML
Micropub
OWL
P3P
PLS
RDF
RDF Schema
SISR
SKOS
SMIL
SOAP
SRGS
SRI
SSML
SVG
SCXML
SPARQL
Timed text
VoiceXML
Web storage
WSDL
Webmention
XForms
XHTML
XHTML+RDFa
XInclude
XLink
XML
XML Base
XML Encryption
XML Events
XML Information Set
XML namespace
XML Schema
XML Signature
XOP
XPath
XPath 2.0
XPointer
XProc
XQuery
XSL
XSL-FO
XSLT (elements)
Notes
XAdES
XHTML+SMIL
XUP
Working drafts
CCXML
CURIE
EME
InkML
MSE
RIF
SMIL Timesheets
sXBL
WICD
XFDL
XFrames
XBL
XMLHttpRequest
Guidelines
Web Content Accessibility Guidelines
Initiative
Multimodal Interaction Activity (MMI)
Markup Validation Service
Web Accessibility Initiative
WebPlatform
Deprecated
C-HTML
HDML
JSSS
PGML
VML
XHTML+MathML+SVG
Organizations
Advisory Committee (AC)
World Wide Web Foundation
Elected groups
Advisory Board (AB)
Technical Architecture Group (TAG)
Working groups
CSS
HTML
Geolocation
Social Web
SVG
Web Hypertext Application Technology (WHATWG)
Web Platform
Closed groups
Device Description (DDWG)
WebOnt (Semantic Web Activity)
Software
CERN httpd
Libwww
Browsers
Line Mode (1990–)
Arena (1993–98)
Agora (1994–97)
Argo (1994–97)
Amaya (browser/editor, 1996–2012)
Conferences
International World Wide Web Conference (IW3C)
Steering Committee (IW3C2)
First conference ("WWW1", 1994)
[show]
v
t
e
Document markup languages
Office suite
Compound Document Format
OOXML
SpreadsheetML
PresentationML
WordprocessingML
ODF
UOF
Well-known
HTML
XHTML
MathML
RTF
TeX
LaTeX
Markdown
Lesser-known
AmigaGuide
AsciiDoc
CML
C-HTML
ConTeXt
Crossmark
DITA
DocBook
eLML
EAD
Enriched text
FHTML
GML
GuideML
HDML
HyTime
HyperTeX
IPF
LilyPond
LinuxDoc
Lout
MIF
MAML
MEI
MusicXML
OMDoc
OpenMath
POD
RTML
RTML
RFT
S1000D
TEI
Texinfo
troff
Wikitext
WML
WapTV
XAML
YAML
List of document markup languages
[show]
v
t
e
ISO standards by standard number
List of ISO standards / ISO romanizations / IEC standards
1–9999
1
2
3
4
5
6
7
9
16
31
-0
-1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
128
216
217
226
228
233
259
269
302
306
428
518
519
639
-1
-2
-3
-5
-6
646
690
732
764
843
898
965
1000
1004
1007
1073-1
1413
1538
1745
1989
2014
2015
2022
2047
2108
2145
2146
2240
2281
2709
2711
2788
2848
2852
3029
3103
3166
-1
-2
-3
3297
3307
3602
3864
3901
3977
4031
4157
4217
4909
5218
5428
5775
5776
5800
5964
6166
6344
6346
6385
6425
6429
6438
6523
6709
7001
7002
7098
7185
7200
7498
7736
7810
7811
7812
7813
7816
8000
8178
8217
8571
8583
8601
8632
8652
8691
8807
8820-5
8859
-1
-2
-3
-4
-5
-6
-7
-8
-8-I
-9
-10
-11
-12
-13
-14
-15
-16
8879
9000/9001
9075
9126
9293
9241
9362
9407
9506
9529
9564
9594
9660
9897
9899
9945
9984
9985
9995
10000–19999
10005
10006
10007
10116
10118-3
10160
10161
10165
10179
10206
10218
10303
-11
-21
-22
-28
-238
10383
10487
10585
10589
10646
10664
10746
10861
10957
10962
10967
11073
11170
11179
11404
11544
11783
11784
11785
11801
11898
11940 (-2)
11941
11941 (TR)
11992
12006
12182
12207
12234-2
13211
-1
-2
13216
13250
13399
13406-2
13450
13485
13490
13567
13568
13584
13616
14000
14031
14224
14289
14396
14443
14496
-2
-3
-6
-10
-11
-12
-14
-17
-20
14644
14649
14651
14698
14750
14764
14882
14971
15022
15189
15288
15291
15292
15398
15408
15444
-3
15445
15438
15504
15511
15686
15693
15706
-2
15707
15897
15919
15924
15926
15926 WIP
15930
16023
16262
16612-2
16750
16949 (TS)
17024
17025
17100
17203
17369
17442
17799
18000
18004
18014
18245
18629
18916
19005
19011
19092 (-1
-2)
19114
19115
19125
19136
19439
19500
19501
19502
19503
19505
19506
19507
19508
19509
19510
19600:2014
19752
19757
19770
19775-1
19794-5
19831
20000+
20000
20022
20121
20400
21000
21047
21500
21827:2002
22000
23270
23271
23360
24517
24613
24617
24707
25178
25964
26000
26300
26324
27000 series
27000
27001:2005
27001:2013
27002
27006
27729
28000
29110
29148
29199-2
29500
30170
31000
32000
38500
40500
42010
55000
80000
-1
-2
-3
Category
[show]
v
t
e
Web browsers
Comparison
lightweight
History
List
for Unix
Timeline
Usage share
Features
Ad filtering
Augmented browsing
Bookmarks
Bookmarklet
Live bookmark
Smart Bookmarks
Browser extension
Browser security
Browser synchronizer
comparison
Cookies
Download manager
Favicon
Incremental search
Plug-in
Privacy mode
Tabs
Universal Edit Button
Web standards
Acid tests
Cascading Style Sheets
HTML
HTML5
JavaScript
MathML
OCSP
SVG
WebGL
XHTML
Related topics
BrowserChoice.eu
CRL
HTTP
HTTPS
iLoo
Internet suite
Man-in-the-browser
Mobile Web
Offline reader
PAC
Pwn2Own
Rich Internet application
Site-specific browser
SPDY
SSL/TLS
WebSocket
Widget
World Wide Web
WPAD
XML
[show]
Desktop
Blink-based
Chromium
Brave
Chrome
Dragon
Opera
QupZilla
Sleipnir
Slimjet
SRWare Iron
UC Browser
Vivaldi
Yandex Browser
Sputnik
SafeZone
Gecko-based
AT&T Pogo
Avant
Camino
Firefox
Conkeror
GNU IceCat
IceDragon
Swiftfox
Swiftweasel
TenFourFox
Timberwolf
Tor Browser
Waterfox
xB Browser
Galeon
Ghostzilla
K-Meleon
Kazehakase
Kirix Strata
Lotus Symphony
Lunascape
Mozilla
Beonex Communicator
Classilla
Netscape
SeaMonkey
Trident-based
AOL Explorer
Avant
Deepnet Explorer
GreenBrowser
Internet Explorer
Lunascape
Maxthon
MediaBrowser
MenuBox
NeoPlanet
NetCaptor
SlimBrowser
SpaceTime
UltraBrowser
WebbIE
ZAC Browser
WebKit-based
Arora
Avant
Dooble
Epic
Flock
Fluid
iCab
Konqueror
Lunascape
Maxthon
Midori
OmniWeb
Origyn Web Browser
Otter Browser
QtWeb
rekonq
Safari
Shiira
SlimBoat
surf
Torch
Uzbl
Epiphany
WebPositive
xombrero
Text-based
ELinks
Emacs/W3
Line Mode Browser
Links
Lynx
w3m
Other
abaco
Amaya
Arachne
Arena
Charon
Dillo
eww
Gazelle
HotJava
IBM Home Page Reader
IBrowse
KidZui
Microsoft Edge
Mosaic
Mothra
NetPositive
NetSurf
Pale Moon
Qihoo 360 Secure Browser
[show]
Mobile
Blink-based
Android Browser
Chromium
Brave
Chrome for Android
Opera Mobile
Silk
Gecko-based
Firefox for Android
MicroB
Minimo
Presto-based
Opera Mini
Trident-based
Maxthon
WebKit-based
BOLT
Dolphin Browser
Chrome for iOS
Firefox for iOS
Maxthon
Mercury Browser
Nokia Browser for Symbian
Rockmelt
Safari
Steel
Other
Blazer
CM Browser
Deepfish
ibisBrowser
Internet Explorer Mobile
Iris Browser
Konqueror Embedded
Microsoft Edge
NetFront
Nokia Xpress
Skweezer
Skyfire
Teashark
ThunderHawk
UC Browser
Vision
WinWAP
[show]
Television and video game console
Gecko-based
Kylo
Presto-based
Internet Channel
WebKit-based
Google TV
Nintendo 3DS Internet Browser
Nintendo DS & DSi Browser
NetFront
Steam Overlay
Wii U Internet Browser
Other
MSN TV
Software no longer in development shown in italics
Category
Commons
Internet portal
Software portal
[show]
v
t
e
List of International Electrotechnical Commission standards
IEC standards
IEC 60027
IEC 60034
IEC 60038
IEC 60062
IEC 60063
IEC 60068
IEC 60112
IEC 60228
IEC 60269
IEC 60297
IEC 60309
IEC 60320
IEC 60364
IEC 60446
IEC 60559
IEC 60601
IEC 60870
IEC 60870-5
IEC 60870-6
IEC 60906-1
IEC 60908
IEC 60929
IEC 60958
AES3
S/PDIF
IEC 61030
IEC 61131
IEC 61131-3
IEC 61158
IEC 61162
IEC 61334
IEC 61346
IEC 61355
IEC 61400
IEC 61499
IEC 61508
IEC 61511
IEC 61850
IEC 61883
IEC 61960
IEC 61968
IEC 61970
IEC 62014-4
IEC 62056
IEC 62061
IEC 62196
IEC 62262
IEC 62264
IEC 62304
IEC 62325
IEC 62351
IEC 62365
IEC 62366
IEC 62379
IEC 62386
IEC 62455
IEC 62680
IEC 62682
IEC 62700
ISO/IEC standards
ISO/IEC 646
ISO/IEC 2022
ISO/IEC 4909
ISO/IEC 5218
ISO/IEC 6429
ISO/IEC 6523
ISO/IEC 7810
ISO/IEC 7811
ISO/IEC 7812
ISO/IEC 7813
ISO/IEC 7816
ISO/IEC 7942
ISO/IEC 8613
ISO/IEC 8632
ISO/IEC 8652
ISO/IEC 8859
ISO/IEC 9126
ISO/IEC 9293
ISO/IEC 9592
ISO/IEC 9593
ISO/IEC 9899
ISO/IEC 9945
ISO/IEC 9995
ISO/IEC 10021
ISO/IEC 10116
ISO/IEC 10165
ISO/IEC 10179
ISO/IEC 10646
ISO/IEC 10967
ISO/IEC 11172
ISO/IEC 11179
ISO/IEC 11404
ISO/IEC 11544
ISO/IEC 11801
ISO/IEC 12207
ISO/IEC 13250
ISO/IEC 13346
ISO/IEC 13522-5
ISO/IEC 13568
ISO/IEC 13818
ISO/IEC 14443
ISO/IEC 14496
ISO/IEC 14882
ISO/IEC 15288
ISO/IEC 15291
ISO/IEC 15408
ISO/IEC 15444
ISO/IEC 15445
ISO/IEC 15504
ISO/IEC 15511
ISO/IEC 15693
ISO/IEC 15897
ISO/IEC 16262
ISO/IEC 17024
ISO/IEC 17025
ISO/IEC 18000
ISO/IEC 18004
ISO/IEC 18014
ISO/IEC 19752
ISO/IEC 19757
ISO/IEC 19770
ISO/IEC 19788
ISO/IEC 20000
ISO/IEC 21000
ISO/IEC 21827
ISO/IEC 23003
ISO/IEC 23270
ISO/IEC 23360
ISO/IEC 24707
ISO/IEC 24727
ISO/IEC 24744
ISO/IEC 24752
ISO/IEC 26300
ISO/IEC 27000
ISO/IEC 27000-series
ISO/IEC 27002
ISO/IEC 27040
ISO/IEC 29119
ISO/IEC 33001
ISO/IEC 38500
ISO/IEC 42010
ISO/IEC 80000
Related
International Electrotechnical Commission
Authority control
LCCN: sh95002791
GND: 4373477-7
BNF: cb12493600c (data)
BNE: XX539726
Retrieved from "https://en.wikipedia.org/w/index.php?title=HTML&oldid=805841444"
Categories:
HTML
Computer-related introductions in 1990
Markup languages
Open formats
Technical communication
World Wide Web Consortium standards
Hidden categories:
Wikipedia pages semi-protected against vandalism
Pages using deprecated image syntax
All articles with unsourced statements
Articles with unsourced statements from March 2016
Articles with unsourced statements from June 2017
Articles with specifically marked weasel-worded phrases from March 2017
Articles containing potentially dated statements from 2013
All articles containing potentially dated statements
All articles with vague or ambiguous time
Vague or ambiguous time from August 2015
Articles with DMOZ links
Wikipedia articles with LCCN identifiers
Wikipedia articles with GND identifiers
Wikipedia articles with BNF identifiers
Articles with example code
Pages using RFC magic links
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
View source
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
In other projects
Wikimedia Commons
Wikibooks
Wikiversity
Languages
Afrikaans
Alemannisch
العربية
Aragonés
Azərbaycanca
বাংলা
Bân-lâm-gú
Башҡортса
Беларуская
Беларуская (тарашкевіца)
Български
Boarisch
Bosanski
Brezhoneg
Català
Чӑвашла
Čeština
Corsu
Cymraeg
Dansk
Deutsch
Dolnoserbski
Eesti
Ελληνικά
Español
Esperanto
Euskara
فارسی
Fiji Hindi
Føroyskt
Français
Frysk
Furlan
Gaeilge
Gàidhlig
Galego
گیلکی
한국어
Հայերեն
हिन्दी
Hornjoserbsce
Hrvatski
Bahasa Indonesia
Interlingua
Íslenska
Italiano
עברית
Basa Jawa
ქართული
Қазақша
Kiswahili
Kurdî
Кыргызча
Latgaļu
Latviešu
Lëtzebuergesch
Lietuvių
Lumbaart
Magyar
Македонски
Malagasy
മലയാളം
मराठी
Bahasa Melayu
Mìng-dĕ̤ng-ngṳ̄
Монгол
မြန်မာဘာသာ
Nederlands
नेपाली
नेपाल भाषा
日本語
Нохчийн
Norsk
Norsk nynorsk
Олык марий
Oʻzbekcha/ўзбекча
ਪੰਜਾਬੀ
ភាសាខ្មែរ
Polski
Português
Qaraqalpaqsha
Română
Русиньскый
Русский
Davvisámegiella
Scots
Shqip
සිංහල
Simple English
Slovenčina
Slovenščina
Soomaaliga
کوردی
Српски / srpski
Srpskohrvatski / српскохрватски
Suomi
Svenska
Tagalog
தமிழ்
తెలుగు
ไทย
Тоҷикӣ
Türkçe
Türkmençe
Українська
اردو
Tiếng Việt
Wolof
ייִדיש
Yorùbá
粵語
Žemaitėška
中文
Edit links
This page was last edited on 17 October 2017, at 23:57.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

values: mw-page-base noprint

values: mw-head-base noprint

values: This article is semi-protected due to vandalism

attrs: class id

values: firstHeading firstHeading en

values: siteSub noprint

values: jump-to-nav mw-jump

values:
/wiki/HTM_(disambiguation)
mw-redirect mw-disambig
HTM (disambiguation)

attrs: role class

values:
note
hatnote navigation-not-searchable

value: small

values:
nofollow
https://www.w3.org/TR/html/
external text

values:
nofollow
https://html.spec.whatwg.org/multipage/
external text

values:
nofollow
https://www.w3.org/TR/html51/
external text

values:
nofollow
https://www.w3.org/html/
external text

values:
nofollow
https://whatwg.org/
external text

values: Comparison of layout engines (non-standard HTML)

values: Comparison of layout engines (HTML5 canvas)

values: Comparison of layout engines (HTML5 media)

values: Comparison of layout engines (XHTML 1.1)

values: float:right;clear:right;width:22.0em;margin:0 0 1.0em 1.0em;background:#f9f9f9;border:1px solid #aaa;padding:0.2em;border-spacing:0.4em 0;text-align:center;line-height:1.4em;font-size:88%

values: International Organization for Standardization

values: Web Hypertext Application Technology Working Group

values:
external mw-magiclink-rfc
nofollow
//tools.ietf.org/html/rfc1866

values:
external mw-magiclink-rfc
nofollow
//tools.ietf.org/html/rfc1867

values:
external mw-magiclink-rfc
nofollow
//tools.ietf.org/html/rfc1942

values:
external mw-magiclink-rfc
nofollow
//tools.ietf.org/html/rfc1980

values:
external mw-magiclink-rfc
nofollow
//tools.ietf.org/html/rfc2070

values:
/wiki/W3C_Recommendation
mw-redirect
W3C Recommendation

values:
/wiki/ISO/IEC_JTC1/SC34
mw-redirect
ISO/IEC JTC1/SC34

values:
/wiki/Standards_mode
mw-redirect
Standards mode

values:
/wiki/Line_breaking_character
mw-redirect
Line breaking character

values:
/wiki/Uniform_Resource_Locator
mw-redirect
Uniform Resource Locator

values:
nofollow
https://www.google.com/
external text

values:
/wiki/Attribute-value_pair
mw-redirect
Attribute-value pair

values:
anId
jargon
color:purple;
Hypertext Markup Language

values:
/wiki/Arabic_language
mw-redirect
Arabic language

values: List of XML and HTML character entity references

values:
/wiki/Character_entity_reference
mw-redirect
Character entity reference

values:
/wiki/Document_Type_Declaration
mw-redirect
Document Type Declaration

values:
/wiki/Document_Type_Definition
mw-redirect
Document Type Definition

values: This claim needs references to reliable sources. (March 2016)

values:
noprint Inline-Template Template-Fact
white-space:nowrap;

values:
/wiki/Price_comparison_service
mw-redirect
Price comparison service

values:
/wiki/Feed_aggregator
mw-redirect
Feed aggregator

values: padding-left:0.1em; padding-right:0.1em; color:#595959; border:1px solid #DDD;

values: If this means the i, b, u, etc. tags, they're still present in §4.5 of HTML5. (June 2017)

values:
noprint Inline-Template Template-Fact
margin-left:0.1em; white-space:nowrap;

values:
/wiki/Character_encoding_in_HTML
mw-redirect
Character encoding in HTML

values:
/wiki/Semantic_web
mw-redirect
Semantic web

values: The material near this tag may use weasel words or too-vague attribution. (March 2017)

values: Wikipedia:Manual of Style/Words to watch

values:
nofollow
external text
http://www.w3.org/TR/xhtml1/#guidelines

values:
/wiki/Cascading_style_sheets
mw-redirect
Cascading style sheets

values:
plainlinks noprint asof-tag update
display:none;

values: The time period mentioned near this tag is ambiguous. (August 2015)

values: Wikipedia:Manual of Style/Dates and numbers

values:
/wiki/HTML_decimal_character_rendering
mw-redirect
HTML decimal character rendering

values:
nofollow
https://w3c.github.io/html/
external text

values:
nofollow
http://www.w3.org/DesignIssues/
external text

values:
nofollow
http://www.faqs.org/docs/artu/
external text

values:
nofollow
external text
http://tools.ietf.org/html/rfc1866

values:
nofollow
external text
http://www.w3.org/TR/REC-html32

values:
nofollow
http://www.w3.org/MarkUp/HTML-WG/
external text

values:
nofollow
http://www.w3.org/TR/REC-html40-971218/
external text

values:
nofollow
http://www.w3.org/TR/html401/
external text

values:
nofollow
external text
https://www.cs.tcd.ie/15445/15445.HTML

values:
nofollow
http://www.w3.org/MarkUp/html3/
external text

values:
nofollow
http://www.w3.org/TR/html5/
external text

values:
nofollow
http://www.w3.org/TR/xhtml1/
external text

values:
nofollow
http://www.w3.org/TR/xhtml11/
external text

values:
nofollow
http://www.w3.org/TR/xhtml2/
external text

values:
nofollow
external text
http://www.w3.org/News/2009#item119

values:
nofollow
http://hsivonen.iki.fi/doctype/
external text

values:
nofollow
external text
http://www.w3.org/TR/xhtml1/#C_16

values:
nofollow
external text
http://www.w3.org/TR/xhtml1/#media

values:
nofollow
external text
http://www.ietf.org/rfc/rfc2119.txt

values:
nofollow
http://www.invisiblerevolution.net/
external text

values: -moz-column-width: 30em; -webkit-column-width: 30em; column-width: 30em; list-style-type: decimal;

values: padding-bottom: 0.75em; text-align: center;

attrs: alt src width height style srcset data-file-width data-file-height

values: display: inline-block; width: 31px; line-height: 31px; vertical-align: middle; text-align: center;

values: display: inline-block; margin-left: 4px; width: 182px; vertical-align: middle;

values: border-top:1px solid #aaa; padding-top: 0.75em;

values: metadata plainlinks plainlist mbox-small

values: border:1px solid #aaa; padding:0.75em; background:#f9f9f9;

values:
nofollow
external text
http://whatwg.org/html

values:
nofollow
http://www.w3.org/MarkUp/Guide/
external text

values: Semantic Interpretation for Speech Recognition

values: Synchronized Multimedia Integration Language

values: Speech Recognition Grammar Specification

values: Advisory Committee (W3C) (page does not exist)

values: Advisory Board (W3C) (page does not exist)

values: Technical Architecture Group (page does not exist)

values: Geolocation Working Group (page does not exist)

values: Social Web Working Group (page does not exist)

values: Web Platform Working Group (page does not exist)

values: International World Wide Web Conferences Steering Committee

values: First International Conference on the World-Wide Web

values: nowraplinks collapsible uncollapsed navbox-inner

values:
/wiki/Office_suite
mw-redirect
Office suite

values: nowraplinks collapsible autocollapse navbox-inner

values: List of International Organization for Standardization standards

values:
/wiki/List_of_IEC_standards
mw-redirect
List of IEC standards

values:
/wiki/British_standard_pipe_thread
mw-redirect
British standard pipe thread

values: Language Of Temporal Ordering Specification

values: Guidelines for the Definition of Managed Objects

values: Document Style Semantics and Specification Language

values: Tag Image File Format / Electronic Photography

values: Delivery Multimedia Integration Framework

values:
/wiki/MPEG-4_Part_12
mw-redirect
MPEG-4 Part 12

values: International Standard Identifier for Libraries and Related Organizations

values: International Standard Audiovisual Number

values: International Standard Musical Work Code

values:
/wiki/Simple_feature_access
mw-redirect
Simple feature access

values: Common Object Request Broker Architecture

values: Cloud Infrastructure Management Interface

values: nowraplinks hlist collapsible autocollapse navbox-inner

values: List of web browsers for Unix and Unix-like operating systems

values:
/wiki/Ad_filtering
mw-redirect
Ad filtering

values:
/wiki/Revocation_list
mw-redirect
Revocation list

values:
/wiki/Graphical_control_element
mw-redirect
Graphical control element

values:
/wiki/Web_Proxy_Autodiscovery_Protocol
mw-redirect
Web Proxy Autodiscovery Protocol

values:
/wiki/Blink_(layout_engine)
mw-redirect
Blink (layout engine)

values:
/wiki/Epiphany_(GNOME)
mw-redirect
Epiphany (GNOME)

values:
/wiki/Mothra_(web_browser)
mw-redirect
Mothra (web browser)

values: nowraplinks collapsible collapsed navbox-subgroup

values:
/wiki/Android_Browser
mw-redirect
Android Browser

values: Template:List of International Electrotechnical Commission standards

values: Template talk:List of International Electrotechnical Commission standards

values: List of International Electrotechnical Commission standards

values:
/wiki/IEEE_floating_point
mw-redirect
IEEE floating point

values:
nofollow
external text
http://d-nb.info/gnd/4373477-7

values: Category:Computer-related introductions in 1990

values: Category:World Wide Web Consortium standards

values: Category:Wikipedia pages semi-protected against vandalism

values: Category:Pages using deprecated image syntax

values: Category:All articles with unsourced statements

values: Category:Articles with unsourced statements from March 2016

values: Category:Articles with unsourced statements from June 2017

values: Category:Articles with specifically marked weasel-worded phrases from March 2017

values: Category:Articles containing potentially dated statements from 2013

values: Category:All articles containing potentially dated statements

values: Category:All articles with vague or ambiguous time

values: Category:Vague or ambiguous time from August 2015

values: Category:Wikipedia articles with LCCN identifiers

values: Category:Wikipedia articles with GND identifiers

values: Category:Wikipedia articles with BNF identifiers

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/HTML
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values:
This page is protected.
You can view its source [ctrl-alt-e]

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values: Find background information on current events

values:
/wiki/Special:Random
Load a random article [ctrl-alt-x]
x

values: portal navigation p-wikibase-otherprojects p-wikibase-otherprojects-label

values:
https://af.wikipedia.org/wiki/HTML
HTML – Afrikaans
af
af
interlanguage-link-target

values:
https://als.wikipedia.org/wiki/HTML
HTML – Alemannisch
als
als
interlanguage-link-target

values: لغة ترميز النص الفائق – Arabic

values:
https://an.wikipedia.org/wiki/HTML
HTML – Aragonese
an
an
interlanguage-link-target

values:
https://az.wikipedia.org/wiki/HTML
HTML – Azerbaijani
az
az
interlanguage-link-target

values: এইচটিএমএল – Bangla

values:
https://ba.wikipedia.org/wiki/HTML
HTML – Bashkir
ba
ba
interlanguage-link-target

values:
https://be.wikipedia.org/wiki/HTML
HTML – Belarusian
be
be
interlanguage-link-target

values: HTML – Belarusian (Taraškievica orthography)

values:
https://bg.wikipedia.org/wiki/HTML
HTML – Bulgarian
bg
bg
interlanguage-link-target

values:
https://bar.wikipedia.org/wiki/HTML
HTML – Bavarian
bar
bar
interlanguage-link-target

values:
https://bs.wikipedia.org/wiki/HTML
HTML – Bosnian
bs
bs
interlanguage-link-target

values:
https://br.wikipedia.org/wiki/HTML
HTML – Breton
br
br
interlanguage-link-target

values:
https://cv.wikipedia.org/wiki/HTML
HTML – Chuvash
cv
cv
interlanguage-link-target

values:
https://co.wikipedia.org/wiki/HTML
HTML – Corsican
co
co
interlanguage-link-target

values:
https://cy.wikipedia.org/wiki/HTML
HTML – Welsh
cy
cy
interlanguage-link-target

values:
https://da.wikipedia.org/wiki/HTML
HTML – Danish
da
da
interlanguage-link-target

values:
https://dsb.wikipedia.org/wiki/HTML
HTML – Lower Sorbian
dsb
dsb
interlanguage-link-target

values:
https://et.wikipedia.org/wiki/HTML
HTML – Estonian
et
et
interlanguage-link-target

values:
https://el.wikipedia.org/wiki/HTML
HTML – Greek
el
el
interlanguage-link-target

values:
https://es.wikipedia.org/wiki/HTML
HTML – Spanish
es
es
interlanguage-link-target

values:
https://eo.wikipedia.org/wiki/HTML
HTML – Esperanto
eo
eo
interlanguage-link-target

values:
https://eu.wikipedia.org/wiki/HTML
HTML – Basque
eu
eu
interlanguage-link-target

values: اچ‌تی‌ام‌ال – Persian

values:
https://hif.wikipedia.org/wiki/HTML
HTML – Fiji Hindi
hif
hif
interlanguage-link-target

values:
https://fo.wikipedia.org/wiki/HTML
HTML – Faroese
fo
fo
interlanguage-link-target

values:
https://fy.wikipedia.org/wiki/HTML
HTML – Western Frisian
fy
fy
interlanguage-link-target

values:
https://fur.wikipedia.org/wiki/HTML
HTML – Friulian
fur
fur
interlanguage-link-target

values:
https://ga.wikipedia.org/wiki/HTML
HTML – Irish
ga
ga
interlanguage-link-target

values:
https://gd.wikipedia.org/wiki/HTML
HTML – Scottish Gaelic
gd
gd
interlanguage-link-target

values:
https://gl.wikipedia.org/wiki/HTML
HTML – Galician
gl
gl
interlanguage-link-target

values: ئچ.تي.ئم.ئل – Gilaki

values:
https://ko.wikipedia.org/wiki/HTML
HTML – Korean
ko
ko
interlanguage-link-target

values:
https://hy.wikipedia.org/wiki/HTML
HTML – Armenian
hy
hy
interlanguage-link-target

values: ऍचटीऍमऍल – Hindi

values:
https://hsb.wikipedia.org/wiki/HTML
HTML – Upper Sorbian
hsb
hsb
interlanguage-link-target

values:
https://hr.wikipedia.org/wiki/HTML
HTML – Croatian
hr
hr
interlanguage-link-target

values:
https://id.wikipedia.org/wiki/HTML
HTML – Indonesian
id
id
interlanguage-link-target

values:
https://ia.wikipedia.org/wiki/HTML
HTML – Interlingua
ia
ia
interlanguage-link-target

values:
https://is.wikipedia.org/wiki/HTML
HTML – Icelandic
is
is
interlanguage-link-target

values:
https://it.wikipedia.org/wiki/HTML
HTML – Italian
it
it
interlanguage-link-target

values:
https://he.wikipedia.org/wiki/HTML
HTML – Hebrew
he
he
interlanguage-link-target

values: ჰიპერტექსტური მარკირების ენა – Georgian

values:
https://kk.wikipedia.org/wiki/HTML
HTML – Kazakh
kk
kk
interlanguage-link-target

values:
https://sw.wikipedia.org/wiki/HTML
HTML – Swahili
sw
sw
interlanguage-link-target

values:
https://ku.wikipedia.org/wiki/HTML
HTML – Kurdish
ku
ku
interlanguage-link-target

values:
https://ky.wikipedia.org/wiki/HTML
HTML – Kyrgyz
ky
ky
interlanguage-link-target

values:
https://ltg.wikipedia.org/wiki/HTML
HTML – Latgalian
ltg
ltg
interlanguage-link-target

values:
https://lv.wikipedia.org/wiki/HTML
HTML – Latvian
lv
lv
interlanguage-link-target

values: Hypertext Markup Language – Luxembourgish

values:
https://lt.wikipedia.org/wiki/HTML
HTML – Lithuanian
lt
lt
interlanguage-link-target

values:
https://lmo.wikipedia.org/wiki/HTML
HTML – Lombard
lmo
lmo
interlanguage-link-target

values:
https://hu.wikipedia.org/wiki/HTML
HTML – Hungarian
hu
hu
interlanguage-link-target

values:
https://mk.wikipedia.org/wiki/HTML
HTML – Macedonian
mk
mk
interlanguage-link-target

values:
https://ms.wikipedia.org/wiki/HTML
HTML – Malay
ms
ms
interlanguage-link-target

values:
https://cdo.wikipedia.org/wiki/HTML
HTML – Min Dong Chinese
cdo
cdo
interlanguage-link-target

values:
https://mn.wikipedia.org/wiki/HTML
HTML – Mongolian
mn
mn
interlanguage-link-target

values:
https://my.wikipedia.org/wiki/HTML
HTML – Burmese
my
my
interlanguage-link-target

values: एच टी एम् एल् – Newari

values:
https://ce.wikipedia.org/wiki/HTML
HTML – Chechen
ce
ce
interlanguage-link-target

values:
https://no.wikipedia.org/wiki/HTML
HTML – Norwegian
no
no
interlanguage-link-target

values:
https://nn.wikipedia.org/wiki/HTML
HTML – Norwegian Nynorsk
nn
nn
interlanguage-link-target

values:
https://mhr.wikipedia.org/wiki/HTML
HTML – Eastern Mari
mhr
mhr
interlanguage-link-target

values:
https://uz.wikipedia.org/wiki/HTML
HTML – Uzbek
uz
uz
interlanguage-link-target

values:
https://km.wikipedia.org/wiki/HTML
HTML – Khmer
km
km
interlanguage-link-target

values:
https://pl.wikipedia.org/wiki/HTML
HTML – Polish
pl
pl
interlanguage-link-target

values:
https://pt.wikipedia.org/wiki/HTML
HTML – Portuguese
pt
pt
interlanguage-link-target

values:
https://kaa.wikipedia.org/wiki/HTML
HTML – Kara-Kalpak
kaa
kaa
interlanguage-link-target

values:
https://rue.wikipedia.org/wiki/HTML
HTML – Rusyn
rue
rue
interlanguage-link-target

values:
https://ru.wikipedia.org/wiki/HTML
HTML – Russian
ru
ru
interlanguage-link-target

values:
https://se.wikipedia.org/wiki/HTML
HTML – Northern Sami
se
se
interlanguage-link-target

values:
https://sco.wikipedia.org/wiki/HTML
HTML – Scots
sco
sco
interlanguage-link-target

values:
https://sq.wikipedia.org/wiki/HTML
HTML – Albanian
sq
sq
interlanguage-link-target

values: එච්ටීඑම්එල් – Sinhala

values:
https://simple.wikipedia.org/wiki/HTML
HTML – Simple English
simple
simple
interlanguage-link-target

values:
https://sl.wikipedia.org/wiki/HTML
HTML – Slovenian
sl
sl
interlanguage-link-target

values:
https://so.wikipedia.org/wiki/HTML
HTML – Somali
so
so
interlanguage-link-target

values:
https://sr.wikipedia.org/wiki/HTML
HTML – Serbian
sr
sr
interlanguage-link-target

values:
https://sh.wikipedia.org/wiki/HTML
HTML – Serbo-Croatian
sh
sh
interlanguage-link-target

values:
https://fi.wikipedia.org/wiki/HTML
HTML – Finnish
fi
fi
interlanguage-link-target

values:
https://sv.wikipedia.org/wiki/HTML
HTML – Swedish
sv
sv
interlanguage-link-target

values:
https://tl.wikipedia.org/wiki/HTML
HTML – Tagalog
tl
tl
interlanguage-link-target

values: மீயுரைக் குறியிடு மொழி – Tamil

values: హెచ్‌టిఎమ్ఎల్(HTML) – Telugu

values: เอชทีเอ็มแอล – Thai

values:
https://tg.wikipedia.org/wiki/HTML
HTML – Tajik
tg
tg
interlanguage-link-target

values:
https://tr.wikipedia.org/wiki/HTML
HTML – Turkish
tr
tr
interlanguage-link-target

values:
https://tk.wikipedia.org/wiki/HTML
HTML – Turkmen
tk
tk
interlanguage-link-target

values:
https://uk.wikipedia.org/wiki/HTML
HTML – Ukrainian
uk
uk
interlanguage-link-target

values: interlanguage-link interwiki-uk badge-Q17437798 badge-goodarticle

values: ایچ ٹی ایم ایل – Urdu

values:
https://vi.wikipedia.org/wiki/HTML
HTML – Vietnamese
vi
vi
interlanguage-link-target

values:
https://wo.wikipedia.org/wiki/HTML
HTML – Wolof
wo
wo
interlanguage-link-target

values:
https://yi.wikipedia.org/wiki/HTML
HTML – Yiddish
yi
yi
interlanguage-link-target

values:
https://yo.wikipedia.org/wiki/HTML
HTML – Yoruba
yo
yo
interlanguage-link-target

values:
https://zh-yue.wikipedia.org/wiki/HTML
HTML – Cantonese
zh-yue
zh-yue
interlanguage-link-target

values:
https://bat-smg.wikipedia.org/wiki/HTML
HTML – Samogitian
bat-smg
bat-smg
interlanguage-link-target

values:
https://zh.wikipedia.org/wiki/HTML
HTML – Chinese
zh
zh
interlanguage-link-target

values:
suggestions
display: none; font-size: 13px;

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-HTML rootpage-HTML vector-experimental-print-styles vector-nav-directionality skin-vector action-view