Wikipedia preview

出典(authority):フリー百科事典『ウィキペディア（Wikipedia）』「2013/08/19 19:32:15」(JST)

wiki ja

ウィキペディアにおけるHTMLの扱いについては、Help:ウィキテキストにおけるHTMLをご覧ください。

HyperText Markup Language（ハイパーテキストマークアップランゲージ）、略記・略称：HTML（エイチティーエムエル）とは、ウェブ上の文書を記述するためのマークアップ言語である。文章の中に記述することでさまざまな機能を記述設定することができる。

ウェブの基幹的役割を持つ技術の一つでHTMLでマークアップされたドキュメントはほかのドキュメントへのハイパーリンクを設定できるハイパーテキストであり、画像・リスト・表などの高度な表現力を持つ。

W3Cは、XMLベースの規格であるXHTMLの勧告も行っている。また2012年12月現在、HTML5も策定中である。

特徴[編集]

HTMLの特徴はハイパーテキストを利用した、相互間文書参照のフレームワークである。マークアップはプレーンテキストの文書を要素で括って意味付けすることで行い、文書の特定要素にURIを用いた他文書へのリンクを記載しておけばユーザエージェントはそれを解釈して指定された他文書を表示させることが可能となる。またマークアップを施す際に引用や画像の埋め込み、文書のタイトルの指定などを定める要素を記載すればユーザエージェントがそれらを解釈し形態に見合った表示を行う。HTMLはそうしたマークアップの規則を定めている。

マークアップ規則はDTDとして公開され要素ごとに記載することの出来る属性、内容に含むことの出来る要素などが定められている。2007年4月現在の最新バージョンである HTML 4.01 では厳密なもの^[1]、HTML 3.2 からの移行過渡期のためのもの^[2]、フレームを用いた文書のためのもの^[3]といった3つのDTDが定義されている。

文書の内容の一部分に「段落」や「章題」や「強調したい箇所」など、文章中での意味を付加する要素の多くは開始タグ、意味を付加したい部分、終了タグの形で構成される。開始タグ・終了タグはそれぞれ「<要素名>」、「</要素名>」のように表現される。また、META 要素や IMG 要素や BR 要素のように一つのタグだけからなる要素もある。これらは単体で文書そのものについてのメタ情報を宣言したり、画像や改行など文字では表現できない文書要素を記述するためのものである。

要素には必要に応じて、要素に付加する特性を現す属性を記述する。基本的に、属性と属性名はセットに指定する。要素名と属性名については大文字と小文字を区別しない。属性値については、属性によって大文字と小文字を区別するかどうかが個別に定められる。文脈上一意に特定できる場合は開始タグや終了タグを省略できる。また内容を持たず開始タグのみで構成される空要素も存在する^[4]。さらに一部の属性についても属性名の省略が可能となっている^[5]。

HTML 3.2 では見た目を左右する要素や属性が追加されたがHTMLは本来文書構造を示すためだけにその存在意義があり、それらの要素は目的に反するものとされた。そのため視覚的・感覚的効果を定義する手段としてスタイルシート（一般にはその中のCSS）が考案された。見た目を左右する要素や属性の一部は HTML 4 以降では非推奨とされており、HTML 4.01 Strict では定義されていないので使用できない。ただし HTML 4.01 Strict で定義され、非推奨とされない要素や属性の一部にも見た目を左右するものがある。装飾的な視覚表現のためにそれらの要素や属性を用いているのであればその内容に適する要素を用いた上で、スタイルシートで表現を指定するのが望ましい。

HTML文書[編集]

HTML で書かれた文書をHTML文書と言い、DTD によって定義される書式に沿って記述しなければならない。DTD は文書型宣言（DOCTYPE 宣言）で宣言したバージョンのものが選択される。以下に DTD は HTML 4.01 Strict の文書の例を示す。

HTML では、まず文書型宣言を書く。文書型宣言が無いものは、HTML の規格に従っているとはいえない。HTML 4.01 Strict の文書型宣言は以下のようなものである。

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

このとき、HTML 4.01 Strict の使用およびそのDTDの場所が明示されている。

次にHTML文書の例を挙げる。

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<HTML lang="ja">
 <HEAD>
  <META http-equiv="content-type" content="text/html; charset=UTF-8">
  <LINK rev="made" href="mailto:mail@example.com">
  <TITLE lang="en">HyperText Markup Language - Wikipedia</TITLE>
 </HEAD>
 <BODY>
  <DIV>
   <H1 lang="en">HyperText Markup Language</H1>
   <P>HTMLは、<A href="http://ja.wikipedia.org/wiki/SGML">SGML</A>
      アプリケーションの一つで、ハイパーテキストを利用してワールド
      ワイドウェブ上で情報を発信するために作られ、
      ワールドワイドウェブの<STRONG>基幹的役割</STRONG>をなしている。
      情報を発信するための文書構造を定義するために使われ、
      ある程度機械が理解可能な言語で、
      写真の埋め込みや、フォームの作成、
      ハイパーテキストによるHTML間の連携が可能である。</P>
  </DIV>
 </BODY>
</HTML>

このHTML文書は次のような構造を示している。

文書型宣言
HTML 要素（ルート要素。また、言語コード ja の言語が使われていることの明示）
- HEAD 要素（この文書のヘッダ情報の明示）
  - META 要素（文書のメタ情報。この場合、HTTPヘッダの代用）
  - LINK 要素（他のリソースとの関連を明示。この場合、作者の明示）
  - TITLE 要素（この文書のタイトルの明示、この部分は en の言語が使われていることの明示）
- BODY 要素（この文書の内容の明示）
- DIV 要素（ブロックを明示）
  - H1 要素（第一レベルの見出しを明示、この部分は en の言語が使われていることの明示）
  - P 要素（段落の明示）
    - A 要素（他のリソースへのアンカーであることの明示）
    - STRONG 要素（強い強調であることの明示）

タグによって文字列を括ることによりその文字列の意味付けがなされる。ユーザエージェントはそれを解釈して、例えば GUI によるウェブブラウザであれば STRONG 要素で括られたテキストを太字として表示するなどする。また、スタイルシートを用いることで見た目などを指定することができるようになっている。尚、テキストエディターで改行をしても、ウェブブラウザ上では BR 要素がなければ改行はされない。

HTMLタグ[編集]

タグとは本来、文字「<」で始まり、文字「>」で終わる要素を記述するための符号を示す意味で用いられる言葉であるが、HTMLの要素を示す意味でタグと言う言葉が用いられることがある。W3C勧告の HTML4.01 仕様書には、「要素はタグではない^[6]」としてこの用法を明確に否定する文言が見られる^[7]。

歴史[編集]

1989年、CERNのティム・バーナーズ=リーは、オリジナルのHTML（および多くの関連したプロトコル、HTTPなど）のメモを提案し、1990年5月にコード化した^[8]。NEXTSTEPの動作するNeXTcubeワークステーション上で開発された。当時のHTMLは仕様ではなく、直面していた問題を解決するためのツール群であった。直面していた問題とは、バーナーズ=リーやその同僚たちがどのように情報や進行中の研究を共有するかということである。彼の成果は後に国際的かつ公開のネットワークの出現として結実し、世界的な注目を集めることになった。

HTML の初期のバージョンはゆるい文法規則によって定義されており、ウェブ技術になじみのない層に受け入れられる助けとなった。ウェブブラウザはウェブページの意図を推測し、レンダリングを実行するのが一般的であった。やがて公式規格においては厳格な言語構文をつくることを志向するようになっていったが、お節介な解釈をするブラウザは今でも存在する。

HTML が公式な仕様として定義されたのは1990年代からである。それは従来のマークアップ言語であるSGMLに、インターネットのためのハイパーテキストの機能を取り入れるというバーナーズ=リーの提案に大きく影響を受けたものだった。

1993年にはIETFからHTML仕様書バージョン 1.0が公開され、SGMLからの拡張として文法定義のDTDを持つようになった。また1994年にIETFのHTMLワーキンググループが発足した。しかし、2.0以降のIETFの元での開発は他の開発との競合から停滞した。1996年からはW3Cによって商用ソフトウェア・ベンダーからの支援も受け、HTMLの仕様が標準化されている^[9]。また2000年からは国際標準ともなった（ISO/IEC 15445:2000）。W3Cから公開された最新のHTML仕様はHTML 4.01である。

HTML 1.0[編集]

1993年6月に、IETFのIIIR Workingグループより提出されたインターネット・ドラフトを通常HTML 1.0と呼ぶ。このドラフトはバーナーズ=リーおよびダニエル・コノリーによって、ティムの出したHTML Design Constraintsに極力従うように書かれた。

HTML仕様書

HTML+[編集]

HTML+仕様書

HTML 2.0[編集]

1995年11月に、IETFのHTMLワーキンググループによってRFC 1866として仕様が発表された。HTML 2.0はRFC 2854によって破棄された。

RFC 1866 （日本語訳）

HTML 2.x[編集]

1997年1月、RFC 2070として発表された。「HTML i18n」とも呼ばれるが、現在はRFC 2854によって破棄された。

日本語を扱えるHTMLのバージョンとしては、最も古い。

RFC 2070（非公式な日本語訳）

HTML 3.0[編集]

策定作業が行われたが、ドラフトの段階で策定途中に破棄された。

HTML 3.0仕様書

HTML 3.2[編集]

1997年1月14日に、W3C勧告として仕様が発表された。

HTML 3.2 Reference Specification（非公式な日本語訳）

HTML 4.0、HTML 4.01[編集]

1997年12月18日に、W3C勧告としてHTML 4.0の仕様が発表された。HTML 4.0は1998年4月24日に仕様が改訂（revised）された。この仕様にいくらかのマイナーな修正が加えられたHTML 4.01は1999年12月24日にW3C勧告となった。Strict DTDの他にHTML 3.2からの移行過渡期のためのTransitional DTDとフレームを使うことのできるFrameset DTDの3つのスキーマを持つ。

この後、HTML 4.01をベースとしてXHTML 1.0が策定されることになる。

HTML 4.0 Specification
HTML 4.0 Specification（revised）（非公式な日本語訳）
HTML 4.01 Specification（非公式な日本語訳）

ISO/IEC 15445:2000[編集]

ISO/IEC JTC 1による規格。HTML 4.01を参考にし、より厳密に規格化された。これは2000年に翻訳されJIS X 4156:2000というJIS規格になった。

ISO/IEC 15445:2000は2003年に改正版（Corrected version）が発行された（ただし改正後も名称はISO/IEC 15445:2000のまま）。JIS X 4156も2005年に改正され、JIS X 4156:2005となっている。

HTML5[編集]

詳細は「HTML5」を参照

ブログや記事向けの「article」要素やマルチメディアのための「audio」および「video」要素などをはじめとした新要素・属性が追加・変更・削除される。2014年頃に正式に勧告される予定である^[10]。詳細はHTML5におけるHTML4からの変更点などのウェブサイトを参照のこと。スマートフォンサイトのマークアップではすでに使用されている。

HTML形式の電子メール[編集]

詳細は「電子メール#メール形式」を参照

脚注[編集]

[ヘルプ]

^ 英: Strict
^ 英: Transitional
^ 英: Frameset
^ BR 要素、IMG 要素など
^ TABLE 要素の frame 属性、INPUT 要素の disabled 属性など。属性値の省略ではない。
^ 英: Elements are not tags.
^ W3C "HTML 4.01 Specification" 3.2.1 Elements, 24 December 1999
^ Tim Berners-Lee. “Information Management: A Proposal”. CERN (March 1989, May 1990). 2012年11月28日閲覧。
^ Raggett, Dave (1998). Raggett on HTML 4. Addison-Wesley. pp. chap. 2: A history of HTML. ISBN 0-201-17805-2.
^ http://www.w3.org/html/wiki/FAQs#When_will_HTML5_be_done.3F

外部リンク[編集]

ウィクショナリーにHTMLの項目があります。

ウィキブックスにHTML関連の解説書・教科書があります。

ウィキメディア・コモンズには、HTMLに関連するカテゴリがあります。

RFC 2854 - The 'text/html' Media Type. （英語）
W3C Markup Validation Service （英語） - W3Cによる構文チェック
HTMLアナライザ（英語）
ごく簡単なHTMLの説明（日本語）

wiki en

[Wiki en表示]

For the use of HTML on Wikipedia, see Help:HTML in wikitext.

HyperText Markup Language (HTML) is the main markup language for creating web pages and other information that can be displayed in a web browser.

HTML is written in the form of HTML elements consisting of tags enclosed in angle brackets (like <html>), within the web page content. HTML tags most commonly come in pairs like <h1> and </h1>, although some tags represent empty elements and so are unpaired, for example <img>. The first tag in a pair is the start tag, and the second tag is the end tag (they are also called opening tags and closing tags). In between these tags web designers can add text, further tags, comments and other types of text-based content.

The purpose of a web browser is to read HTML documents and compose them into visible or audible web pages. The browser does not display the HTML tags, but uses the tags to interpret the content of the page.

HTML elements form the building blocks of all websites. HTML allows images and objects to be embedded and can be used to create interactive forms. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It can embed scripts written in languages such as JavaScript which affect the behavior of HTML web pages.

Web browsers can also refer to Cascading Style Sheets (CSS) to define the appearance and layout of text and other material. The W3C, maintainer of both the HTML and the CSS standards, encourages the use of CSS over explicit presentational HTML markup.^[1]

1 History
- 1.1 Development
- 1.2 Version history of the standard
- 1.3 HTML versions timeline
  - 1.3.1 HTML draft version timeline
  - 1.3.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 Current 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
- 5.5 WhatWG HTML versus HTML5
6 Hypertext features not in HTML
7 WYSIWYG editors
8 See also
9 References
10 External links

History[edit source | edit]

The historic logo made by the W3C

Development[edit source | edit]

Tim Berners-Lee

In 1980, physicist Tim Berners-Lee, who was 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.^[2] Berners-Lee specified HTML and wrote the browser and server software in the last part of 1990. In 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^[3] from 1990 he listed^[4] "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 Berners-Lee in late 1991.^[5]^[6] 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 SGML-based documentation format at CERN. Eleven of these elements still exist in HTML 4.^[7]

HyperText Markup Language 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: "Hypertext Markup Language (HTML)" Internet-Draft by Berners-Lee and Dan Connolly, which included an SGML Document Type Definition to define the grammar.^[8] 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.^[9] 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.^[10]

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.^[11]

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).^[12] 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.

Version history of the standard[edit source | edit]

HTML versions timeline[edit source | edit]

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 1997

HTML 3.2^[13] 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 in September 1996.^[14]

Initially code-named "Wilbur",^[15] 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.^[12] A markup for mathematical formulas similar to that in HTML was not standardized until 14 months later in MathML.

December 1997

HTML 4.0^[16] 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",^[15] 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.^[17]

April 1998

HTML 4.0^[18] was reissued with minor edits without incrementing the version number.

December 1999

HTML 4.01^[19] was published as a W3C Recommendation. It offers the same three variations as HTML 4.0 and its last errata were published May 12, 2001.

May 2000

ISO/IEC 15445:2000^[20]^[21] ("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).^[20]

As of mid-2008, HTML 4.01 and ISO/IEC 15445:2000 are the most recent versions of HTML. Development of the parallel, XML-based language XHTML occupied the W3C's HTML Working Group through the early and mid-2000s.

HTML draft version timeline[edit source | edit]

Logo of HTML5

October 1991: HTML Tags,^[5] an informal CERN document listing 18 HTML tags, was first mentioned in public.
June 1992: First informal draft of the HTML DTD,^[22] with seven^[23]^[24]^[25] 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^[25]
June 1993: Hypertext Markup Language^[26] 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^[27] one month later, followed by six further drafts published by IETF itself^[28] that finally led to HTML 2.0 in RFC1866
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^[29] was proposed as a standard to the IETF, but the proposal expired five months later 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.^[30]; W3C began development of its own Arena browser as a test bed for HTML 3 and Cascading Style Sheets,^[31]^[32]^[33] 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.^[12] 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.^[12] (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."^[12] 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."^[12]
January 2008: HTML5 was published as a Working Draft (link) by the W3C.^[34]; 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.^[35]
May 2011: 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 is developing a comprehensive test suite to achieve broad interoperability for the full specification by 2014, which is now the target date for Recommendation.^[36]

XHTML versions[edit source | edit]

Main article: XHTML

XHTML is a separate language that began as a reformulation of HTML 4.01 using XML 1.0. It continues to be developed:

XHTML 1.0,^[37] published January 26, 2000, as a W3C Recommendation, later revised and republished 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,^[38] published May 31, 2001, as a W3C Recommendation. It is based on XHTML 1.0 Strict, but includes minor changes, can be customized, is reformulated using modules from Modularization of XHTML, which was published April 10, 2001, as a W3C Recommendation.
XHTML 2.0 was a working draft, but work on it was abandoned in 2009 in favor of work on HTML5 and XHTML5.^[39]^[40]^[41] 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.
XHTML5, which is an update to XHTML 1.x, is being defined alongside HTML5 in the HTML5 draft.^[42]

Markup[edit source | edit]

HTML markup consists of several key components, including elements (and their attributes), character-based data types, character references and entity references. Another important component is the 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 lines of code:

<!DOCTYPE html>
<html>
  <head>
    <title>This is a title</title>
  </head>
  <body>
    <p>Hello world!</p>
  </body>
</html>

(The text between <html> and </html> describes the web page, and the text between <body> and </body> is the visible page content. The markup text '<title>This is a title</title>' defines the browser page title.)

This Document Type Declaration is for HTML5. If the <!DOCTYPE html> declaration is not included, various browsers will revert to "quirks mode" for rendering.^[43]

Elements[edit source | edit]

Main article: HTML element

HTML documents are composed entirely of HTML elements that, in their most general form have three components: a pair of tags, a "start tag" and "end tag"; some attributes within the start tag; and finally, any textual and graphical content between the start and end tags, perhaps including other nested elements. The HTML element is everything between and including the start and end tags. Each tag is enclosed in angle brackets.

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 BR tag or the inline IMG 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[edit source | edit]

Header of the HTML document:<head>...</head>. Usually the title should be included in the head, for example:

<head>
  <title>The Title</title>
</head>

Headings: HTML headings are defined with the <h1> to <h6> tags:

<h1>Heading1</h1>
<h2>Heading2</h2>
<h3>Heading3</h3>
<h4>Heading4</h4>
<h5>Heading5</h5>
<h6>Heading6</h6>

Paragraphs:

<p>Paragraph 1</p>  <p>Paragraph 2</p>

Line breaks:<br />. The difference between <br /> and <p> 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, while it may have attributes, it can take no content and it may not have an end tag.

<p>This <br /> is a paragraph <br /> with <br /> line breaks</p>

Comments:

<!-- This is a comment -->

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 describes the purpose of text: For example, <h2>Golf</h2> 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).
Presentational markup describes the appearance of the text, regardless of its purpose: For example <b>boldface</b> 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 <b>bold</b> and <i>italic</i>, there are other elements that may have equivalent visual renderings but which are more semantic in nature, such as <strong>strong text</strong> and <em>emphasised text</em> 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, <a href="http://www.google.com/">Wikipedia</a>, 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. <a href="http://example.org"><img src="image.gif" alt="descriptive text" width="50" height="50" border="0"></a>.

Attributes[edit source | edit]

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) .^[44]^[45] Leaving attribute values unquoted is considered unsafe.^[46] 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,^[5] like the ismap attribute for the img element.^[47]

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:
```
<p>Oh well, <span lang="fr">c'est la vie</span>, as they say in France.</p>
```

The abbreviation element, abbr, can be used to demonstrate some of these attributes :

<abbr id="anId" class="jargon" style="color:purple;" title="Hypertext Markup Language">HTML</abbr>

This example displays as HTML; in most browsers, pointing the cursor at the abbreviation should display the title text "Hypertext Markup Language."

Most elements also 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.^[48]

Character and entity references[edit source | edit]

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 ' (not as ' except in XHTML documents^[49]) 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 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.^[50]

Data types[edit source | edit]

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[edit source | edit]

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:

<!doctype html>

An example of an HTML 4 doctype is

<!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 as well.the strict tag excludes deprecated tags. Frameset has all tags necessary to make frames on a page along with the tags included in trasitional type^[51]

Semantic HTML[edit source | edit]

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,^[52] but has also included presentational markup, such as <font>, <i> and <center> 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.^[53]

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.^[54] 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.^[55]

Presentational markup tags are deprecated in current HTML and XHTML recommendations and are illegal in HTML5.

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[edit source | edit]

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[edit source | edit]

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.^[56] XHTML 1.1 also states that XHTML 1.1 documents should^[57] be labeled with either MIME type.^[58]

HTML e-mail[edit source | edit]

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 controversial 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[edit source | edit]

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,^[59] limited file extensions to three letters.

HTML Application[edit source | edit]

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 .

Current variations[edit source | edit]

HTML is precisely what we were trying to PREVENT— ever-breaking links, links going outward only, quotes you can't follow to their origins, no version management, no rights management.

Ted Nelson^[60]

Since its inception, HTML and its associated protocols gained acceptance relatively quickly. 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,^[61] 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^[62] 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[edit source | edit]

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: <br/>. 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: <br />.^[63]

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 (<br/> to <br>).

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 <br /> instead of <br/>.
Include explicit close tags for elements that permit content but are left empty (for example, <div></div>, not <div />).
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[edit source | edit]

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[edit source | edit]

In addition to the above transitional differences, the frameset specifications (whether XHTML 1.0 or HTML 4.01) specifies a different content model, with frameset replacing body, that contains either frame elements, or optionally noframes with a body.

Summary of specification versions[edit source | edit]

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

WhatWG HTML versus HTML5[edit source | edit]

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.^[64]^[65]

Hypertext features not in HTML[edit source | edit]

HTML lacks some of the features found in earlier hypertext systems, such as source tracking, fat links and others.^[66] Even some hypertext features that were in early versions of HTML have been ignored by most popular web browsers until recently, 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[edit source | edit]

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,^[67]^[68] 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.^[69]
Often producing extremely verbose and redundant code that fails to make use of the cascading nature of HTML and CSS.
Often producing ungrammatical markup often called tag soup or semantically incorrect markup (such as <em> 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.^[70]

References[edit source | edit]

^ HTML 4 — Conformance: requirements and recommendations. W3.org. Retrieved on 2012-02-16.
^ Tim Berners-Lee, "Information Management: A Proposal." CERN (March 1989, May 1990). W3.org
^ Tim Berners-Lee, "Design Issues"
^ Tim Berners-Lee, "Design Issues"
^ ^a ^b ^c "Tags used in HTML". World Wide Web Consortium. November 3, 1992. Retrieved November 16, 2008.
^ "First mention of HTML Tags on the www-talk mailing list". World Wide Web Consortium. October 29, 1991. Retrieved April 8, 2007.
^ "Index of elements in HTML 4". World Wide Web Consortium. December 24, 1999. Retrieved April 8, 2007.
^ 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."
^ Raymond, Eric. "IETF and the RFC Standards Process". [[The Art of Unix Programming]]. "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." Wikilink embedded in URL title (help)
^ "HTML+ Internet-Draft — Abstract". "Browser writers are experimenting with extensions to HTML and it is now appropriate to draw these ideas together into a revised document format. The new format is designed to allow a gradual roll over from HTML, adding features like tables, captioned figures and fill-out forms for querying remote databases or mailing questionnaires."
^ 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."
^ ^a ^b ^c ^d ^e ^f Raggett, Dave (1998). Raggett on HTML 4. Retrieved July 9, 2007.
^ "HTML 3.2 Reference Specification". World Wide Web Consortium. January 14, 1997. Retrieved November 16, 2008.
^ "IETF HTML WG". Retrieved June 16, 2007. "Note: This working group is closed"
^ ^a ^b Arnoud Engelfriet. "Introduction to Wilbur". Web Design Group. Retrieved June 16, 2007.
^ "HTML 4.0 Specification". World Wide Web Consortium. December 18, 1997. Retrieved November 16, 2008.
^ "HTML 4 – 4 Conformance: requirements and recommendations". Retrieved December 30, 2009.
^ "HTML 4.0 Specification". World Wide Web Consortium. April 24, 1998. Retrieved November 16, 2008.
^ "HTML 4.01 Specification". World Wide Web Consortium. December 24, 1999. Retrieved November 16, 2008.
^ ^a ^b ISO (2000). "ISO/IEC 15445:2000 – Information technology – Document description and processing languages – HyperText Markup Language (HTML)". Retrieved December 26, 2009.
^ Cs.Tcd.Ie. Cs.Tcd.Ie (2000-05-15). Retrieved on 2012-02-16.
^ Connolly, Daniel (6 June 1992). "MIME as a hypertext architecture". CERN. Retrieved 24 October 2010.
^ Connolly, Daniel (15 July 1992). "HTML DTD enclosed". CERN. Retrieved 24 October 2010.
^ 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.
^ ^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"
^ 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.
^ Berners-Lee, Tim; Connolly, Daniel (June 1993). "Hypertext Markup Language (HTML) Internet Draft version 1.2". IETF IIIR Working Group. Retrieved 18 September 2010.
^ Berners-Lee, Tim; Connolly, Daniel (28 November 1994). "HyperText Markup Language Specification – 2.0 INTERNET DRAFT". IETF. Retrieved 24 October 2010.
^ "HTML 3.0 Draft (Expired!) Materials". World Wide Web Consortium. December 21, 1995. Retrieved November 16, 2008.
^ "HyperText Markup Language Specification Version 3.0". Retrieved June 16, 2007.
^ 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.
^ Bowers, Neil. Weblint: Just Another Perl Hack.
^ Lie, Håkon Wium; Bos, Bert (April 1997). Cascading style sheets: designing for the Web. Addison Wesley Longman. p. 263. Retrieved 9 June 2010.
^ "HTML5". World Wide Web Consortium. June 10, 2008. Retrieved November 16, 2008.
^ "HTML5, one vocabulary, two serializations". Retrieved February 25, 2009.
^ "W3C Confirms May 2011 for HTML5 Last Call, Targets 2014 for HTML5 Standard". World Wide Web Consortium. 14 February 2011. Retrieved 18 February 2011.
^ "XHTML 1.0: The Extensible HyperText Markup Language (Second Edition)". World Wide Web Consortium. January 26, 2000. Retrieved November 16, 2008.
^ "XHTML 1.1 – Module-based XHTML — Second Edition". World Wide Web Consortium. February 16, 2007. Retrieved November 16, 2008.
^ "XHTM 2.0". World Wide Web Consortium. July 26, 2006. Retrieved November 16, 2008.
^ "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.
^ "W3C XHTML FAQ".
^ "HTML5". World Wide Web Consortium. October 24, 2008. Retrieved November 16, 2008.
^ Activating Browser Modes with Doctype. Hsivonen.iki.fi. Retrieved on 2012-02-16.
^ "On SGML and HTML". World Wide Web Consortium. Retrieved November 16, 2008.
^ "XHTML 1.0 – Differences with HTML 4". World Wide Web Consortium. Retrieved November 16, 2008.
^ Korpela, Jukka (July 6, 1998). "Why attribute values should always be quoted in HTML". Cs.tut.fi. Retrieved November 16, 2008.
^ "Objects, Images, and Applets in HTML documents". World Wide Web Consortium. December 24, 1999. Retrieved November 16, 2008.
^ "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.
^ "The Named Character Reference '". World Wide Web Consortium. January 26, 2000.
^ "The Unicode Standard: A Technical Introduction". Retrieved 2010-03-16.
^ SAMS teach yourself html and css 8th edition
^ 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 [[Special:BookSources/978-0-06-251587-X|978-0-06-251587-X [[Category:Articles with invalid ISBNs]]]] Check |isbn= value (help).
^ 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.
^ Tim Berners-Lee, James Hendler and Ora Lassila (2001). "The Semantic Web". Scientific American. Retrieved October 2, 2009.
^ Nigel Shadbolt, Wendy Hall and Tim Berners-Lee (2006). "The Semantic Web Revisited". IEEE Intelligent Systems. Retrieved October 2, 2009.
^ "XHTML 1.0 The Extensible HyperText Markup Language (Second Edition)". World Wide Web Consortium. 2000, revised 2002. 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]."
^ "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."
^ "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]."
^ Česky. "File Allocation Table - Wikipedia, the free encyclopedia". En.wikipedia.org. Retrieved 2013-06-15.
^ Ted Nelson (29 January 1999). "Ted Nelson's Computer Paradigm, Expressed as One-Liners". Xanadu. Retrieved 26 July 2010.
^ HTML Design Constraints, W3C Archives
^ WWW:BTB – HTML, Pris Sears
^ Freeman, E (2005). Head First HTML. O'Reilly.
^ Hickson, Ian (2011-01-19). "HTML is the new HTML5". The WHATWG blog. Retrieved 2013-01-14.
^ "HTML5 — Smile, it's a Snapshot!". W3C Blog. 2012-12-17. Retrieved 2013-01-14.
^ Jakob Nielsen (January 3, 2005). "Reviving Advanced Hypertext". Retrieved June 16, 2007.
^ Sauer, C.: WYSIWIKI – Questioning WYSIWYG in the Internet Age. In: Wikimania (2006)
^ 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)
^ XHTML Reference: blockquote. Xhtml.com. Retrieved on 2012-02-16.
^ Doug Engelbart's INVISIBLE REVOLUTION . Invisiblerevolution.net. Retrieved on 2012-02-16.

External links[edit source | edit]

Wikimedia Commons has media related to: HTML

Wikibooks has a book on the topic of: HyperText Markup Language

Wikiversity has learning materials about HTML

Wikiversity has learning materials about HTML Challenges

Look up Appendix:Hyper Text Markup Language in Wiktionary, the free dictionary.

HTML 4.01, the most recent finished specification (1999)
HTML5, the upcoming version of HTML
Dave Raggett's Introduction to HTML
Empty elements in SGML, HTML, XML and XHTML
Tim Berners-Lee Gives the Web a New Definition
HTML analyzer

Tutorials

HTML Dog

UpToDate Contents

全文を閲覧するには購読必要です。 To read the full text you will need to subscribe.

1. ダウン症のマネージメント management of down syndrome

English Journal

Guidelines for the laboratory investigation of heritable disorders of platelet function.

Harrison P, Mackie I, Mumford A, Briggs C, Liesner R, Winter M, Machin S; British Committee for Standards in Haematology.SourceOxford Haemophilia & Thrombosis Centre, Churchill Hospital, Oxford Haemostasis Research Unit, Department of Haematology, University College London, London Bristol Haemophilia Centre, Bristol Haematology and Oncology Centre, Bristol Department of Haematology, University College London Hospitals NHS Trust, London Haemophilia Comprehensive Care Centre, Great Ormond Street Hospital for Children NHS Trust, London Kent Haemophilia Centre, Kent and Canterbury Hospital, Canterbury, Kent, UK.
British journal of haematology.Br J Haematol.2011 Oct;155(1):30-44. doi: 10.1111/j.1365-2141.2011.08793.x. Epub 2011 Jul 26.
The guideline writing group was selected to be representative of UK-based medical experts. MEDLINE was systematically searched for publications in English up to the Summer of 2010 using key words platelet, platelet function testing and platelet aggregometry. Relevant references generated from initia
PMID 21790527

Japanese Journal

HTML要素に基づく有害サイト検出手法

池田和史,柳原正,服部元,松本一則,小野智弘,滝嶋康弘
情報処理学会論文誌 52(8), 2474-2483, 2011-08-15
… 本稿では高速かつ高精度に有害サイトを検出するため, Webサイトの背景色やリンク先, ブラウザに特定の動作をさせるスクリプトなど, 有害サイトに特徴的に見られる傾向をHTML要素から検出する手法を提案する. … 提案手法では有害サイトのHTMLに偏って出現するような文字列を自動的に抽出し, SVM(Support Vector Machine)を用いてこれらの特徴を組み合わせて有害サイトの検出を行う. …
NAID 110008591662

Related Pictures

Make Website Using html& css for $30 - SEOClerks HTML Essential Training A Significant Percentage Of Americans Think That HTML Is An STD – Sick Chirpse A Basic Understanding of HTML | InnovaFire Web Solutions Códigos HMTL para español, carácteres especiales - Tutorial Monsters - Diseño Web Curso Básico de HTML desde 0 - Introducción - YouTube HTML5 interview Basic Questions and Answers tutorial : 10 Commonly asked interview HTML Essential Training | LinkedIn Learning, formerly Lynda.com

★リンクテーブル★

リンク元	「WWW」
関連記事	「HT」

「WWW」

HTML
(HyperText Markup Language)
Filename extension	.html, .htm
Internet media type	text/html
Type code	TEXT
Uniform Type Identifier	public.html
Developed by	World Wide Web Consortium & WHATWG
Type of format	Markup language
Extended from	SGML
Extended to	XHTML
Standard(s)	ISO/IEC 15445; W3C HTML 4.01; W3C HTML5 (draft)

HTML
	; HTMLコードの例。
拡張子	.html, .htm
MIME Type	text/html
タイプコード	TEXT; HTML
UTI	public.html
開発者	World Wide Web Consortium
種別	マークアップ言語
派生元	SGML
拡張	XHTML
国際標準	ISO/IEC 15445:2000
	テンプレートを表示

　　[★]

同: ウェブ Web
関: HTML

「HT」

　　[★]

[1] 英: Strict

[2] 英: Transitional

[3] 英: Frameset

[4] BR 要素、IMG 要素など

[5] TABLE 要素の frame 属性、INPUT 要素の disabled 属性など。属性値の省略ではない。

[6] 英: Elements are not tags.

[7] W3C "HTML 4.01 Specification" 3.2.1 Elements, 24 December 1999

[8] Tim Berners-Lee. “Information Management: A Proposal”. CERN (March 1989, May 1990). 2012年11月28日閲覧。

[9] Raggett, Dave (1998). Raggett on HTML 4. Addison-Wesley. pp. chap. 2: A history of HTML. ISBN 0-201-17805-2.

[10] ttp://www.w3.org/html/wiki/FAQs#When_will_HTML5_be_done.3F

[deprecated-1] HTML 4 — Conformance: requirements and recommendations. W3.org. Retrieved on 2012-02-16.

[2] Tim Berners-Lee, "Information Management: A Proposal." CERN (March 1989, May 1990). W3.org

[3] Tim Berners-Lee, "Design Issues"

[4] Tim Berners-Lee, "Design Issues"

[tagshtml-5] "Tags used in HTML". World Wide Web Consortium. November 3, 1992. Retrieved November 16, 2008.

[6] "First mention of HTML Tags on the www-talk mailing list". World Wide Web Consortium. October 29, 1991. Retrieved April 8, 2007.

[7] "Index of elements in HTML 4". World Wide Web Consortium. December 24, 1999. Retrieved April 8, 2007.

[8] 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."

[raymond-9] Raymond, Eric. "IETF and the RFC Standards Process". [[The Art of Unix Programming]]. "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." Wikilink embedded in URL title (help)

[html.2B-10] "HTML+ Internet-Draft — Abstract". "Browser writers are experimenting with extensions to HTML and it is now appropriate to draw these ideas together into a revised document format. The new format is designed to allow a gradual roll over from HTML, adding features like tables, captioned figures and fill-out forms for querying remote databases or mailing questionnaires."

[11] 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."

[raggett-12] ^ ^a ^b ^c ^d ^e ^f Raggett, Dave (1998). Raggett on HTML 4. Retrieved July 9, 2007.

[13] "HTML 3.2 Reference Specification". World Wide Web Consortium. January 14, 1997. Retrieved November 16, 2008.

[14] "IETF HTML WG". Retrieved June 16, 2007. "Note: This working group is closed"

[engelfriet-15] Arnoud Engelfriet. "Introduction to Wilbur". Web Design Group. Retrieved June 16, 2007.

[16] "HTML 4.0 Specification". World Wide Web Consortium. December 18, 1997. Retrieved November 16, 2008.

[17] "HTML 4 – 4 Conformance: requirements and recommendations". Retrieved December 30, 2009.

[18] "HTML 4.0 Specification". World Wide Web Consortium. April 24, 1998. Retrieved November 16, 2008.

[19] "HTML 4.01 Specification". World Wide Web Consortium. December 24, 1999. Retrieved November 16, 2008.

[iso-html-20] ISO (2000). "ISO/IEC 15445:2000 – Information technology – Document description and processing languages – HyperText Markup Language (HTML)". Retrieved December 26, 2009.

[21] Cs.Tcd.Ie. Cs.Tcd.Ie (2000-05-15). Retrieved on 2012-02-16.

[22] Connolly, Daniel (6 June 1992). "MIME as a hypertext architecture". CERN. Retrieved 24 October 2010.

[23] Connolly, Daniel (15 July 1992). "HTML DTD enclosed". CERN. Retrieved 24 October 2010.

[24] 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.

[html11-25] 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"

[26] 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.

[ietfiiir-27] Berners-Lee, Tim; Connolly, Daniel (June 1993). "Hypertext Markup Language (HTML) Internet Draft version 1.2". IETF IIIR Working Group. Retrieved 18 September 2010.

[28] Berners-Lee, Tim; Connolly, Daniel (28 November 1994). "HyperText Markup Language Specification – 2.0 INTERNET DRAFT". IETF. Retrieved 24 October 2010.

[29] "HTML 3.0 Draft (Expired!) Materials". World Wide Web Consortium. December 21, 1995. Retrieved November 16, 2008.

[30] "HyperText Markup Language Specification Version 3.0". Retrieved June 16, 2007.

[31] 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.

[32] Bowers, Neil. Weblint: Just Another Perl Hack.

[33] Lie, Håkon Wium; Bos, Bert (April 1997). Cascading style sheets: designing for the Web. Addison Wesley Longman. p. 263. Retrieved 9 June 2010.

[34] "HTML5". World Wide Web Consortium. June 10, 2008. Retrieved November 16, 2008.

[35] "HTML5, one vocabulary, two serializations". Retrieved February 25, 2009.

[w3c2014-36] "W3C Confirms May 2011 for HTML5 Last Call, Targets 2014 for HTML5 Standard". World Wide Web Consortium. 14 February 2011. Retrieved 18 February 2011.

[37] "XHTML 1.0: The Extensible HyperText Markup Language (Second Edition)". World Wide Web Consortium. January 26, 2000. Retrieved November 16, 2008.

[38] "XHTML 1.1 – Module-based XHTML — Second Edition". World Wide Web Consortium. February 16, 2007. Retrieved November 16, 2008.

[39] "XHTM 2.0". World Wide Web Consortium. July 26, 2006. Retrieved November 16, 2008.

[40] "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.

[41] "W3C XHTML FAQ".

[42] "HTML5". World Wide Web Consortium. October 24, 2008. Retrieved November 16, 2008.

[hsivonen-43] Activating Browser Modes with Doctype. Hsivonen.iki.fi. Retrieved on 2012-02-16.

[44] "On SGML and HTML". World Wide Web Consortium. Retrieved November 16, 2008.

[45] "XHTML 1.0 – Differences with HTML 4". World Wide Web Consortium. Retrieved November 16, 2008.

[46] Korpela, Jukka (July 6, 1998). "Why attribute values should always be quoted in HTML". Cs.tut.fi. Retrieved November 16, 2008.

[47] "Objects, Images, and Applets in HTML documents". World Wide Web Consortium. December 24, 1999. Retrieved November 16, 2008.

[48] "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.

[aposhtml-49] "The Named Character Reference '". World Wide Web Consortium. January 26, 2000.

[50] "The Unicode Standard: A Technical Introduction". Retrieved 2010-03-16.

[51] SAMS teach yourself html and css 8th edition

[52] 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 [[Special:BookSources/978-0-06-251587-X|978-0-06-251587-X [[Category:Articles with invalid ISBNs]]]] Check |isbn= value (help).

[53] 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.

[54] Tim Berners-Lee, James Hendler and Ora Lassila (2001). "The Semantic Web". Scientific American. Retrieved October 2, 2009.

[Semantic_Web_Revisted-55] Nigel Shadbolt, Wendy Hall and Tim Berners-Lee (2006). "The Semantic Web Revisited". IEEE Intelligent Systems. Retrieved October 2, 2009.

[56] "XHTML 1.0 The Extensible HyperText Markup Language (Second Edition)". World Wide Web Consortium. 2000, revised 2002. 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]."

[57] "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."

[58] "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]."

[59] Česky. "File Allocation Table - Wikipedia, the free encyclopedia". En.wikipedia.org. Retrieved 2013-06-15.

[60] Ted Nelson (29 January 1999). "Ted Nelson's Computer Paradigm, Expressed as One-Liners". Xanadu. Retrieved 26 July 2010.

[61] HTML Design Constraints, W3C Archives

[62] WWW:BTB – HTML, Pris Sears

[63] Freeman, E (2005). Head First HTML. O'Reilly.

[64] Hickson, Ian (2011-01-19). "HTML is the new HTML5". The WHATWG blog. Retrieved 2013-01-14.

[65] "HTML5 — Smile, it's a Snapshot!". W3C Blog. 2012-12-17. Retrieved 2013-01-14.

[66] Jakob Nielsen (January 3, 2005). "Reviving Advanced Hypertext". Retrieved June 16, 2007.

[67] Sauer, C.: WYSIWIKI – Questioning WYSIWYG in the Internet Age. In: Wikimania (2006)

[68] 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)

[69] XHTML Reference: blockquote. Xhtml.com. Retrieved on 2012-02-16.

[70] Doug Engelbart's INVISIBLE REVOLUTION . Invisiblerevolution.net. Retrieved on 2012-02-16.

HTMLコードの例。
拡張子	`.html, .htm`
MIME Type	`text/html`
タイプコード	`TEXT` `HTML`
UTI	public.html
開発者	World Wide Web Consortium
種別	マークアップ言語
派生元	SGML
拡張	XHTML
国際標準	ISO/IEC 15445:2000
テンプレートを表示

HTML

各種項目 HTML・HTML5 ダイナミックHTML XHTML XHTML Mobile Profile・C-HTML canvas要素文字符号化 Document Object Model フォントファミリー HTML エディター HTML要素 HTMLフレーム HTML5ビデオ HTML5オーディオ HTMLスクリプティング HTMLレンダリングエンジン互換モードスタイルシート HTMLのUnicode表記 W3C・WHATWG ウェブカラー WebGL WebCL Webストレージ比較マークアップ言語ウェブブラウザレンダリングエンジンの比較 HTML HTML5 HTML5メディア非標準HTML XHTML
表・話・編・歴

匿名

検索

案内

HTML