summaryrefslogtreecommitdiff
path: root/doc/rfc1866.htm
diff options
context:
space:
mode:
authorJörg Frings-Fürst <debian@jff-webhsoting.net>2019-04-26 17:57:49 +0200
committerJörg Frings-Fürst <debian@jff-webhsoting.net>2019-04-26 17:57:49 +0200
commit1920f1b489a54e8ab97a3e24b1bab64831e32b53 (patch)
tree1cdcec7df7eafec396d29e94bc35554c210fb8db /doc/rfc1866.htm
parent63b80068976fbc5460c284aef0e6560abcf13e68 (diff)
New upstream version 0.9.2upstream/0.9.2
Diffstat (limited to 'doc/rfc1866.htm')
-rw-r--r--doc/rfc1866.htm4446
1 files changed, 4446 insertions, 0 deletions
diff --git a/doc/rfc1866.htm b/doc/rfc1866.htm
new file mode 100644
index 0000000..108a958
--- /dev/null
+++ b/doc/rfc1866.htm
@@ -0,0 +1,4446 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en" xml:lang="en">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
+ <meta name="robots" content="index,follow" />
+ <meta name="creator" content="rfcmarkup version 1.60" />
+ <link rel="icon" href="/images/rfc.png" type="image/png" />
+ <link rel="shortcut icon" href="/images/rfc.png" type="image/png" />
+ <title>RFC 1866 - Hypertext Markup Language - 2.0</title>
+
+ <style type="text/css">
+ body {
+ margin: 0px 8px;
+ font-size: 1em;
+ }
+ h1, h2, h3, h4, h5, h6, .h1, .h2, .h3, .h4, .h5, .h6 {
+ font-weight: bold;
+ line-height: 0pt;
+ display: inline;
+ white-space: pre;
+ font-family: monospace;
+ font-size: 1em;
+ font-weight: bold;
+ }
+ pre {
+ font-size: 1em;
+ }
+ .pre {
+ white-space: pre;
+ font-family: monospace;
+ }
+ .header{
+ font-weight: bold;
+ }
+ .invisible {
+ text-decoration: none;
+ color: white;
+ }
+ @media print {
+ body {
+ font-size: 10.5pt;
+ }
+ h1, h2, h3, h4, h5, h6 {
+ font-size: 10.5pt;
+ }
+
+ a:link, a:visited {
+ color: inherit;
+ text-decoration: none;
+ }
+ .break {
+ page-break-before: always;
+ }
+ .noprint {
+ display: none;
+ }
+ }
+ @media screen {
+ .grey, .grey a:link, .grey a:visited {
+ color: #777;
+ }
+ .docinfo {
+ background-color: #EEE;
+ }
+ .top {
+ border-top: 2px solid #EEE;
+ }
+ .bgwhite { background-color: white; }
+ .bgred { background-color: #F44; }
+ .bggrey { background-color: #666; }
+ .bgbrown { background-color: #840; }
+ .bgorange { background-color: #FA0; }
+ .bgyellow { background-color: #EE0; }
+ .bgmagenta{ background-color: #F4F; }
+ .bgblue { background-color: #66F; }
+ .bgcyan { background-color: #4DD; }
+ .bggreen { background-color: #4F4; }
+
+ .legend { font-size: 90%; }
+ .cplate { font-size: 70%; border: solid grey 1px; }
+ }
+ </style>
+
+ <script type="text/javascript"><!--
+ function addHeaderTags() {
+ var spans = document.getElementsByTagName("span");
+ for (var i=0; i < spans.length; i++) {
+ var elem = spans[i];
+ if (elem) {
+ var level = elem.getAttribute("class");
+ if (level == "h1" || level == "h2" || level == "h3" || level == "h4" || level == "h5" || level == "h6") {
+ elem.innerHTML = "<"+level+">"+elem.innerHTML+"</"+level+">";
+ }
+ }
+ }
+ }
+ var legend_html = "Colour legend:<br /> <table> <tr><td>Unknown:</td> <td><span class='cplate bgwhite'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Draft:</td> <td><span class='cplate bgred'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Informational:</td> <td><span class='cplate bgorange'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Experimental:</td> <td><span class='cplate bgyellow'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Best Common Practice:</td><td><span class='cplate bgmagenta'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Proposed Standard:</td><td><span class='cplate bgblue'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Draft Standard:</td> <td><span class='cplate bgcyan'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Standard:</td> <td><span class='cplate bggreen'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Historic:</td> <td><span class='cplate bggrey'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> <tr><td>Obsolete:</td> <td><span class='cplate bgbrown'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> </table>";
+ function showElem(id) {
+ var elem = document.getElementById(id);
+ elem.innerHTML = eval(id+"_html");
+ elem.style.visibility='visible';
+ }
+ function hideElem(id) {
+ var elem = document.getElementById(id);
+ elem.style.visibility='hidden';
+ elem.innerHTML = "";
+ }
+ // -->
+ </script>
+</head>
+<body onload="addHeaderTags()">
+ <div style="height: 8px;">
+ <div onmouseover="this.style.cursor='pointer';"
+ onclick="showElem('legend');"
+ onmouseout="hideElem('legend')"
+ style="height: 6px; position: absolute;"
+ class="pre noprint docinfo bgbrown"
+ title="Click for colour legend." > </div>
+ <div id="legend"
+ class="docinfo noprint pre legend"
+ style="position:absolute; top: 4px; left: 4ex; visibility:hidden; background-color: white; padding: 4px 9px 5px 7px; border: solid #345 1px; "
+ onmouseover="showElem('legend');"
+ onmouseout="hideElem('legend');">
+ </div>
+ </div>
+<span class="pre noprint docinfo top">[<a href="../html/" title="Document search and retrieval page">RFCs/IDs</a>] [<a href="/rfc/rfc1866.txt" title="Plaintext version of this document">Plain Text</a>] [From <a href="draft-ietf-html-spec">draft-ietf-html-spec</a>] </span><br />
+<span class="pre noprint docinfo"> </span><br />
+<span class="pre noprint docinfo">Obsoleted by: <a href="./rfc2854">2854</a> HISTORIC</span><br />
+<span class="pre noprint docinfo"> </span><br />
+<pre>
+Network Working Group T. Berners-Lee
+Request for Comments: 1866 MIT/W3C
+Category: Standards Track D. Connolly
+ November 1995
+
+
+ <span class="h1">Hypertext Markup Language - 2.0</span>
+
+Status of this Memo
+
+ This document specifies an Internet standards track protocol for the
+ Internet community, and requests discussion and suggestions for
+ improvements. Please refer to the current edition of the "Internet
+ Official Protocol Standards" (STD 1) for the standardization state
+ and status of this protocol. Distribution of this memo is unlimited.
+
+Abstract
+
+ The Hypertext Markup Language (HTML) is a simple markup language used
+ to create hypertext documents that are platform independent. HTML
+ documents are SGML documents with generic semantics that are
+ appropriate for representing information from a wide range of
+ domains. HTML markup can represent hypertext news, mail,
+ documentation, and hypermedia; menus of options; database query
+ results; simple structured documents with in-lined graphics; and
+ hypertext views of existing bodies of information.
+
+ HTML has been in use by the World Wide Web (WWW) global information
+ initiative since 1990. This specification roughly corresponds to the
+ capabilities of HTML in common use prior to June 1994. HTML is an
+ application of ISO Standard 8879:1986 Information Processing Text and
+ Office Systems; Standard Generalized Markup Language (SGML).
+
+ The "text/html" Internet Media Type (<a href="./rfc1590">RFC 1590</a>) and MIME Content Type
+ (<a href="./rfc1521">RFC 1521</a>) is defined by this specification.
+
+Table of Contents
+
+ <a href="#section-1">1</a>. Introduction ........................................... <a href="#page-2">2</a>
+ <a href="#section-1.1">1.1</a> Scope .................................................. <a href="#page-3">3</a>
+ <a href="#section-1.2">1.2</a> Conformance ............................................ <a href="#page-3">3</a>
+ <a href="#section-2">2</a>. Terms .................................................. <a href="#page-6">6</a>
+ <a href="#section-3">3</a>. HTML as an Application of SGML .........................<a href="#page-10">10</a>
+ <a href="#section-3.1">3.1</a> SGML Documents .........................................<a href="#page-10">10</a>
+ <a href="#section-3.2">3.2</a> HTML Lexical Syntax ................................... <a href="#page-12">12</a>
+ <a href="#section-3.3">3.3</a> HTML Public Text Identifiers .......................... <a href="#page-17">17</a>
+ <a href="#section-3.4">3.4</a> Example HTML Document ................................. <a href="#page-17">17</a>
+ <a href="#section-4">4</a>. HTML as an Internet Media Type ........................ <a href="#page-18">18</a>
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 1]</span>
+<a name="page-2" id="page-2" href="#page-2" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ <a href="#section-4.1">4.1</a> text/html media type .................................. <a href="#page-18">18</a>
+ <a href="#section-4.2">4.2</a> HTML Document Representation .......................... <a href="#page-19">19</a>
+ <a href="#section-5">5</a>. Document Structure .................................... <a href="#page-20">20</a>
+ <a href="#section-5.1">5.1</a> Document Element: HTML ................................ <a href="#page-21">21</a>
+ <a href="#section-5.2">5.2</a> Head: HEAD ............................................ <a href="#page-21">21</a>
+ <a href="#section-5.3">5.3</a> Body: BODY ............................................ <a href="#page-24">24</a>
+ <a href="#section-5.4">5.4</a> Headings: H1 ... H6 ................................... <a href="#page-24">24</a>
+ <a href="#section-5.5">5.5</a> Block Structuring Elements ............................ <a href="#page-25">25</a>
+ <a href="#section-5.6">5.6</a> List Elements ......................................... <a href="#page-28">28</a>
+ <a href="#section-5.7">5.7</a> Phrase Markup ......................................... <a href="#page-30">30</a>
+ <a href="#section-5.8">5.8</a> Line Break: BR ........................................ <a href="#page-34">34</a>
+ <a href="#section-5.9">5.9</a> Horizontal Rule: HR ................................... <a href="#page-34">34</a>
+ <a href="#section-5.10">5.10</a> Image: IMG ............................................ <a href="#page-34">34</a>
+ <a href="#section-6">6</a>. Characters, Words, and Paragraphs ..................... <a href="#page-35">35</a>
+ <a href="#section-6.1">6.1</a> The HTML Document Character Set ....................... <a href="#page-36">36</a>
+ <a href="#section-7">7</a>. Hyperlinks ............................................ <a href="#page-36">36</a>
+ <a href="#section-7.1">7.1</a> Accessing Resources ................................... <a href="#page-37">37</a>
+ <a href="#section-7.2">7.2</a> Activation of Hyperlinks .............................. <a href="#page-38">38</a>
+ <a href="#section-7.3">7.3</a> Simultaneous Presentation of Image Resources .......... <a href="#page-38">38</a>
+ <a href="#section-7.4">7.4</a> Fragment Identifiers .................................. <a href="#page-38">38</a>
+ <a href="#section-7.5">7.5</a> Queries and Indexes ................................... <a href="#page-39">39</a>
+ <a href="#section-7.6">7.6</a> Image Maps ............................................ <a href="#page-39">39</a>
+ <a href="#section-8">8</a>. Forms ................................................. <a href="#page-40">40</a>
+ <a href="#section-8.1">8.1</a> Form Elements ......................................... <a href="#page-40">40</a>
+ <a href="#section-8.2">8.2</a> Form Submission ....................................... <a href="#page-45">45</a>
+ <a href="#section-9">9</a>. HTML Public Text ...................................... <a href="#page-49">49</a>
+ <a href="#section-9.1">9.1</a> HTML DTD .............................................. <a href="#page-49">49</a>
+ <a href="#section-9.2">9.2</a> Strict HTML DTD ....................................... <a href="#page-61">61</a>
+ <a href="#section-9.3">9.3</a> Level 1 HTML DTD ...................................... <a href="#page-62">62</a>
+ <a href="#section-9.4">9.4</a> Strict Level 1 HTML DTD ............................... <a href="#page-63">63</a>
+ <a href="#section-9.5">9.5</a> SGML Declaration for HTML ............................. <a href="#page-64">64</a>
+ <a href="#section-9.6">9.6</a> Sample SGML Open Entity Catalog for HTML .............. <a href="#page-65">65</a>
+ <a href="#section-9.7">9.7</a> Character Entity Sets ................................. <a href="#page-66">66</a>
+ <a href="#section-10">10</a>. Security Considerations ............................... <a href="#page-69">69</a>
+ <a href="#section-11">11</a>. References ............................................ <a href="#page-69">69</a>
+ <a href="#section-12">12</a>. Acknowledgments ....................................... <a href="#page-71">71</a>
+ <a href="#section-12.1">12.1</a> Authors' Addresses .................................... <a href="#page-71">71</a>
+ <a href="#section-13">13</a>. The HTML Coded Character Set .......................... <a href="#page-72">72</a>
+ <a href="#section-14">14</a>. Proposed Entities ..................................... <a href="#page-75">75</a>
+
+<span class="h2"><a name="section-1">1</a>. Introduction</span>
+
+ The HyperText Markup Language (HTML) is a simple data format used to
+ create hypertext documents that are portable from one platform to
+ another. HTML documents are SGML documents with generic semantics
+ that are appropriate for representing information from a wide range
+ of domains.
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 2]</span>
+<a name="page-3" id="page-3" href="#page-3" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ As HTML is an application of SGML, this specification assumes a
+ working knowledge of [<a href="#ref-SGML">SGML</a>].
+
+<span class="h3"><a name="section-1.1">1.1</a>. Scope</span>
+
+ HTML has been in use by the World-Wide Web (WWW) global information
+ initiative since 1990. Previously, informal documentation on HTML has
+ been available from a number of sources on the Internet. This
+ specification brings together, clarifies, and formalizes a set of
+ features that roughly corresponds to the capabilities of HTML in
+ common use prior to June 1994. A number of new features to HTML are
+ being proposed and experimented in the Internet community.
+
+ This document thus defines a 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.
+
+ HTML is an application of ISO Standard 8879:1986, "Information
+ Processing Text and Office Systems; Standard Generalized Markup
+ Language" (SGML). The HTML Document Type Definition (DTD) is a formal
+ definition of the HTML syntax in terms of SGML.
+
+ This specification also defines HTML as an Internet Media
+ Type[IMEDIA] and MIME Content Type[MIME] called `text/html'. As such,
+ it defines the semantics of the HTML syntax and how that syntax
+ should be interpreted by user agents.
+
+<span class="h3"><a name="section-1.2">1.2</a>. Conformance</span>
+
+ This specification governs the syntax of HTML documents and aspects
+ of the behavior of HTML user agents.
+
+<span class="h4"><a name="section-1.2.1">1.2.1</a>. Documents</span>
+
+ A document is a conforming HTML document if:
+
+ * It is a conforming SGML document, and it conforms to the
+ HTML DTD (see 9.1, "HTML DTD").
+
+ NOTE - There are a number of syntactic idioms that
+ are not supported or are supported inconsistently in
+ some historical user agent implementations. These
+ idioms are identified in notes like this throughout
+ this specification.
+
+ * It conforms to the application conventions in this
+ specification. For example, the value of the HREF attribute
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 3]</span>
+<a name="page-4" id="page-4" href="#page-4" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ of the &lt;A&gt; element must conform to the URI syntax.
+
+ * Its document character set includes [<a href="#ref-ISO-8859-1">ISO-8859-1</a>] and
+ agrees with [<a href="#ref-ISO-10646">ISO-10646</a>]; that is, each code position listed
+ in 13, "The HTML Coded Character Set" is included, and each
+ code position in the document character set is mapped to the
+ same character as [<a href="#ref-ISO-10646">ISO-10646</a>] designates for that code
+ position.
+
+ NOTE - The document character set is somewhat
+ independent of the character encoding scheme used to
+ represent a document. For example, the `ISO-2022-JP'
+ character encoding scheme can be used for HTML
+ documents, since its repertoire is a subset of the
+ [<a href="#ref-ISO-10646">ISO-10646</a>] repertoire. The critical distinction is
+ that numeric character references agree with
+ [<a href="#ref-ISO-10646">ISO-10646</a>] regardless of how the document is
+ encoded.
+
+<span class="h4"><a name="section-1.2.2">1.2.2</a>. Feature Test Entities</span>
+
+ The HTML DTD defines a standard HTML document type and several
+ variations, by way of feature test entities. Feature test entities
+ are declarations in the HTML DTD that control the inclusion or
+ exclusion of portions of the DTD.
+
+ HTML.Recommended
+ Certain features of the language are necessary for
+ compatibility with widespread usage, but they may
+ compromise the structural integrity of a document. This
+ feature test entity selects a more prescriptive document
+ type definition that eliminates those features. It is
+ set to `IGNORE' by default.
+
+ For example, in order to preserve the structure of a
+ document, an editing user agent may translate HTML
+ documents to the recommended subset, or it may require
+ that the documents be in the recommended subset for
+ import.
+
+ HTML.Deprecated
+ Certain features of the language are necessary for
+ compatibility with earlier versions of the
+ specification, but they tend to be used and implemented
+ inconsistently, and their use is deprecated. This
+ feature test entity enables a document type definition
+ that allows these features. It is set to `INCLUDE' by
+ default.
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 4]</span>
+<a name="page-5" id="page-5" href="#page-5" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ Documents generated by translation software or editing
+ software should not contain deprecated idioms.
+
+<span class="h4"><a name="section-1.2.3">1.2.3</a>. User Agents</span>
+
+ An HTML user agent conforms to this specification if:
+
+ * It parses the characters of an HTML document into data
+ characters and markup according to [<a href="#ref-SGML">SGML</a>].
+
+ NOTE - In the interest of robustness and
+ extensibility, there are a number of widely deployed
+ conventions for handling non-conforming documents.
+ See 4.2.1, "Undeclared Markup Error Handling" for
+ details.
+
+ * It supports the `ISO-8859-1' character encoding scheme and
+ processes each character in the ISO Latin Alphabet No. 1 as
+ specified in 6.1, "The HTML Document Character Set".
+
+ NOTE - To support non-western writing systems, HTML
+ user agents are encouraged to support
+ `ISO-10646-UCS-2' or similar character encoding
+ schemes and as much of the character repertoire of
+ [<a href="#ref-ISO-10646">ISO-10646</a>] as is practical.
+
+ * It behaves identically for documents whose parsed token
+ sequences are identical.
+
+ For example, comments and the whitespace in tags disappear
+ during tokenization, and hence they do not influence the
+ behavior of conforming user agents.
+
+ * It allows the user to traverse (or at least attempt to
+ traverse, resources permitting) all hyperlinks from &lt;A&gt;
+ elements in an HTML document.
+
+ An HTML user agent is a level 2 user agent if, additionally:
+
+ * It allows the user to express all form field values
+ specified in an HTML document and to (attempt to) submit the
+ values as requests to information services.
+
+
+
+
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 5]</span>
+<a name="page-6" id="page-6" href="#page-6" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h2"><a name="section-2">2</a>. Terms</span>
+
+ absolute URI
+ a URI in absolute form; for example, as per [<a href="#ref-URL" title='"Uniform Resource Locators (URL)"'>URL</a>]
+
+ anchor
+ one of two ends of a hyperlink; typically, a phrase
+ marked as an &lt;A&gt; element.
+
+ base URI
+ an absolute URI used in combination with a relative URI
+ to determine another absolute URI.
+
+ character
+ An atom of information, for example a letter or a digit.
+ Graphic characters have associated glyphs, whereas
+ control characters have associated processing semantics.
+
+ character encoding
+ scheme
+ A function whose domain is the set of sequences of
+ octets, and whose range is the set of sequences of
+ characters from a character repertoire; that is, a
+ sequence of octets and a character encoding scheme
+ determines a sequence of characters.
+
+ character repertoire
+ A finite set of characters; e.g. the range of a coded
+ character set.
+
+ code position
+ An integer. A coded character set and a code position
+ from its domain determine a character.
+
+ coded character set
+ A function whose domain is a subset of the integers and
+ whose range is a character repertoire. That is, for some
+ set of integers (usually of the form {0, 1, 2, ..., N}
+ ), a coded character set and an integer in that set
+ determine a character. Conversely, a character and a
+ coded character set determine the character's code
+ position (or, in rare cases, a few code positions).
+
+ conforming HTML user
+ agent
+ A user agent that conforms to this specification in its
+ processing of the Internet Media Type `text/html'.
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 6]</span>
+<a name="page-7" id="page-7" href="#page-7" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ data character
+ Characters other than markup, which make up the content
+ of elements.
+
+ document character set
+ a coded character set whose range includes all
+ characters used in a document. Every SGML document has
+ exactly one document character set. Numeric character
+ references are resolved via the document character set.
+
+ DTD
+ document type definition. Rules that apply SGML to the
+ markup of documents of a particular type, including a
+ set of element and entity declarations. [<a href="#ref-SGML">SGML</a>]
+
+ element
+ A component of the hierarchical structure defined by a
+ document type definition; it is identified in a document
+ instance by descriptive markup, usually a start-tag and
+ end-tag. [<a href="#ref-SGML">SGML</a>]
+
+ end-tag
+ Descriptive markup that identifies the end of an
+ element. [<a href="#ref-SGML">SGML</a>]
+
+ entity
+ data with an associated notation or interpretation; for
+ example, a sequence of octets associated with an
+ Internet Media Type. [<a href="#ref-SGML">SGML</a>]
+
+ fragment identifier
+ the portion of an HREF attribute value following the `#'
+ character which modifies the presentation of the
+ destination of a hyperlink.
+
+ form data set
+ a sequence of name/value pairs; the names are given by
+ an HTML document and the values are given by a user.
+
+ HTML document
+ An SGML document conforming to this document type
+ definition.
+
+ hyperlink
+ a relationship between two anchors, called the head and
+ the tail. The link goes from the tail to the head. The
+ head and tail are also known as destination and source,
+ respectively.
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 7]</span>
+<a name="page-8" id="page-8" href="#page-8" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ markup
+ Syntactically delimited characters added to the data of
+ a document to represent its structure. There are four
+ different kinds of markup: descriptive markup (tags),
+ references, markup declarations, and processing
+ instructions. [<a href="#ref-SGML">SGML</a>]
+
+ may
+ A document or user interface is conforming whether this
+ statement applies or not.
+
+ media type
+ an Internet Media Type, as per [<a href="#ref-IMEDIA" title='"Media Type Registration Procedure"'>IMEDIA</a>].
+
+ message entity
+ a head and body. The head is a collection of name/value
+ fields, and the body is a sequence of octets. The head
+ defines the content type and content transfer encoding
+ of the body. [<a href="#ref-MIME" title='"MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies"'>MIME</a>]
+
+ minimally conforming
+ HTML user agent
+ A user agent that conforms to this specification except
+ for form processing. It may only process level 1 HTML
+ documents.
+
+ must
+ Documents or user agents in conflict with this statement
+ are not conforming.
+
+ numeric character
+ reference
+ markup that refers to a character by its code position
+ in the document character set.
+
+ SGML document
+ A sequence of characters organized physically as a set
+ of entities and logically into a hierarchy of elements.
+ An SGML document consists of data characters and markup;
+ the markup describes the structure of the information
+ and an instance of that structure. [<a href="#ref-SGML">SGML</a>]
+
+ shall
+ If a document or user agent conflicts with this
+ statement, it does not conform to this specification.
+
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 8]</span>
+<a name="page-9" id="page-9" href="#page-9" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ should
+ If a document or user agent conflicts with this
+ statement, undesirable results may occur in practice
+ even though it conforms to this specification.
+
+ start-tag
+ Descriptive markup that identifies the start of an
+ element and specifies its generic identifier and
+ attributes. [<a href="#ref-SGML">SGML</a>]
+
+ syntax-reference
+ character set
+ A coded character set whose range includes all
+ characters used for markup; e.g. name characters and
+ delimiter characters.
+
+ tag
+ Markup that delimits an element. A tag includes a name
+ which refers to an element declaration in the DTD, and
+ may include attributes. [<a href="#ref-SGML">SGML</a>]
+
+ text entity
+ A finite sequence of characters. A text entity typically
+ takes the form of a sequence of octets with some
+ associated character encoding scheme, transmitted over
+ the network or stored in a file. [<a href="#ref-SGML">SGML</a>]
+
+ typical
+ Typical processing is described for many elements. This
+ is not a mandatory part of the specification but is
+ given as guidance for designers and to help explain the
+ uses for which the elements were intended.
+
+ URI
+ A Uniform Resource Identifier is a formatted string that
+ serves as an identifier for a resource, typically on the
+ Internet. URIs are used in HTML to identify the anchors
+ of hyperlinks. URIs in common practice include Uniform
+ Resource Locators (URLs)[<a href="#ref-URL" title='"Uniform Resource Locators (URL)"'>URL</a>] and Relative URLs
+ [<a href="#ref-RELURL" title='"Relative Uniform Resource Locators"'>RELURL</a>].
+
+ user agent
+ A component of a distributed system that presents an
+ interface and processes requests on behalf of a user;
+ for example, a www browser or a mail user agent.
+
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 9]</span>
+<a name="page-10" id="page-10" href="#page-10" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ WWW
+ The World-Wide Web is a hypertext-based, distributed
+ information system created by researchers at CERN in
+ Switzerland. &lt;URL:http://www.w3.org/&gt;
+
+<span class="h2"><a name="section-3">3</a>. HTML as an Application of SGML</span>
+
+ HTML is an application of ISO 8879:1986 -- Standard Generalized
+ Markup Language (SGML). SGML is a system for defining structured
+ document types and markup languages to represent instances of those
+ document types[SGML]. The public text -- DTD and SGML declaration --
+ of the HTML document type definition are provided in 9, "HTML Public
+ Text".
+
+ The term "HTML" refers to both the document type defined here and the
+ markup language for representing instances of this document type.
+
+<span class="h3"><a name="section-3.1">3.1</a>. SGML Documents</span>
+
+ An HTML document is an SGML document; that is, a sequence of
+ characters organized physically into a set of entities, and logically
+ as a hierarchy of elements.
+
+ In the SGML specification, the first production of the SGML syntax
+ grammar separates an SGML document into three parts: an SGML
+ declaration, a prologue, and an instance. For the purposes of this
+ specification, the prologue is a DTD. This DTD describes another
+ grammar: the start symbol is given in the doctype declaration, the
+ terminals are data characters and tags, and the productions are
+ determined by the element declarations. The instance must conform to
+ the DTD, that is, it must be in the language defined by this grammar.
+
+ The SGML declaration determines the lexicon of the grammar. It
+ specifies the document character set, which determines a character
+ repertoire that contains all characters that occur in all text
+ entities in the document, and the code positions associated with
+ those characters.
+
+ The SGML declaration also specifies the syntax-reference character
+ set of the document, and a few other parameters that bind the
+ abstract syntax of SGML to a concrete syntax. This concrete syntax
+ determines how the sequence of characters of the document is mapped
+ to a sequence of terminals in the grammar of the prologue.
+
+
+
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 10]</span>
+<a name="page-11" id="page-11" href="#page-11" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ For example, consider the following document:
+
+ &lt;!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN"&gt;
+ &lt;title&gt;Parsing Example&lt;/title&gt;
+ &lt;p&gt;Some text. &lt;em&gt;&amp;#42;wow&amp;#42;&lt;/em&gt;&lt;/p&gt;
+
+ An HTML user agent should use the SGML declaration that is given in
+ 9.5, "SGML Declaration for HTML". According to its document character
+ set, `&amp;#42;' refers to an asterisk character, `*'.
+
+ The instance above is regarded as the following sequence of
+ terminals:
+
+ 1. start-tag: TITLE
+
+ 2. data characters: "Parsing Example"
+
+ 3. end-tag: TITLE
+
+ 4. start-tag: P
+
+ 5. data characters "Some text."
+
+ 6. start-tag: EM
+
+ 7. data characters: "*wow*"
+
+ 8. end-tag: EM
+
+ 9. end-tag: P
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 11]</span>
+<a name="page-12" id="page-12" href="#page-12" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ The start symbol of the DTD grammar is HTML, and the productions are
+ given in the public text identified by `-//IETF//DTD HTML 2.0//EN'
+ (9.1, "HTML DTD"). The terminals above parse as:
+
+ HTML
+ |
+ \-HEAD
+ | |
+ | \-TITLE
+ | |
+ | \-&lt;TITLE&gt;
+ | |
+ | \-"Parsing Example"
+ | |
+ | \-&lt;/TITLE&gt;
+ |
+ \-BODY
+ |
+ \-P
+ |
+ \-&lt;P&gt;
+ |
+ \-"Some text. "
+ |
+ \-EM
+ | |
+ | \-&lt;EM&gt;
+ | |
+ | \-"*wow*"
+ | |
+ | \-&lt;/EM&gt;
+ |
+ \-&lt;/P&gt;
+
+ Some of the elements are delimited explicitly by tags, while the
+ boundaries of others are inferred. The &lt;HTML&gt; element contains a
+ &lt;HEAD&gt; element and a &lt;BODY&gt; element. The &lt;HEAD&gt; contains &lt;TITLE&gt;,
+ which is explicitly delimited by start- and end-tags.
+
+<span class="h3"><a name="section-3.2">3.2</a>. HTML Lexical Syntax</span>
+
+ SGML specifies an abstract syntax and a reference concrete syntax.
+ Aside from certain quantities and capacities (e.g. the limit on the
+ length of a name), all HTML documents use the reference concrete
+ syntax. In particular, all markup characters are in the repertoire of
+ [<a href="#ref-ISO-646" title='"./rfc1866"'>ISO-646</a>]. Data characters are drawn from the document character set
+ (see 6, "Characters, Words, and Paragraphs").
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 12]</span>
+<a name="page-13" id="page-13" href="#page-13" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ A complete discussion of SGML parsing, e.g. the mapping of a sequence
+ of characters to a sequence of tags and data, is left to the SGML
+ standard[SGML]. This section is only a summary.
+
+<span class="h4"><a name="section-3.2.1">3.2.1</a>. Data Characters</span>
+
+ Any sequence of characters that do not constitute markup (see 9.6
+ "Delimiter Recognition" of [<a href="#ref-SGML">SGML</a>]) are mapped directly to strings of
+ data characters. Some markup also maps to data character strings.
+ Numeric character references map to single-character strings, via the
+ document character set. Each reference to one of the general entities
+ defined in the HTML DTD maps to a single-character string.
+
+ For example,
+
+ abc&amp;lt;def =&gt; "abc","&lt;","def"
+ abc&amp;#60;def =&gt; "abc","&lt;","def"
+
+ The terminating semicolon on entity or numeric character references
+ is only necessary when the character following the reference would
+ otherwise be recognized as part of the name (see 9.4.5 "Reference
+ End" in [<a href="#ref-SGML">SGML</a>]).
+
+ abc &amp;lt def =&gt; "abc ","&lt;"," def"
+ abc &amp;#60 def =&gt; "abc ","&lt;"," def"
+
+ An ampersand is only recognized as markup when it is followed by a
+ letter or a `#' and a digit:
+
+ abc &amp; lt def =&gt; "abc &amp; lt def"
+ abc &amp;# 60 def =&gt; "abc &amp;# 60 def"
+
+ A useful technique for translating plain text to HTML is to replace
+ each '&lt;', '&amp;', and '&gt;' by an entity reference or numeric character
+ reference as follows:
+
+ ENTITY NUMERIC
+ CHARACTER REFERENCE CHAR REF CHARACTER DESCRIPTION
+ --------- ---------- ----------- ---------------------
+ &amp; &amp;amp; &amp;#38; Ampersand
+ &lt; &amp;lt; &amp;#60; Less than
+ &gt; &amp;gt; &amp;#62; Greater than
+
+ NOTE - There are SGML mechanisms, CDATA and RCDATA
+ declared content, that allow most `&lt;', `&gt;', and `&amp;'
+ characters to be entered without the use of entity
+ references. Because these mechanisms tend to be used and
+ implemented inconsistently, and because they conflict
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 13]</span>
+<a name="page-14" id="page-14" href="#page-14" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ with techniques for reducing HTML to 7 bit ASCII for
+ transport, they are deprecated in this version of HTML.
+ See 5.5.2.1, "Example and Listing: XMP, LISTING".
+
+<span class="h4"><a name="section-3.2.2">3.2.2</a>. Tags</span>
+
+ Tags delimit elements such as headings, paragraphs, lists, character
+ highlighting, and links. Most HTML elements are identified in a
+ document as a start-tag, which gives the element name and attributes,
+ followed by the content, followed by the end tag. Start-tags are
+ delimited by `&lt;' and `&gt;'; end tags are delimited by `&lt;/' and `&gt;'. An
+ example is:
+
+ &lt;H1&gt;This is a Heading&lt;/H1&gt;
+
+ Some elements only have a start-tag without an end-tag. For example,
+ to create a line break, use the `&lt;BR&gt;' tag. Additionally, the end
+ tags of some other elements, such as Paragraph (`&lt;/P&gt;'), List Item
+ (`&lt;/LI&gt;'), Definition Term (`&lt;/DT&gt;'), and Definition Description
+ (`&lt;/DD&gt;') elements, may be omitted.
+
+ The content of an element is a sequence of data character strings and
+ nested elements. Some elements, such as anchors, cannot be nested.
+ Anchors and character highlighting may be put inside other
+ constructs. See the HTML DTD, 9.1, "HTML DTD" for full details.
+
+ NOTE - The SGML declaration for HTML specifies SHORTTAG YES, which
+ means that there are other valid syntaxes for tags, such as NET
+ tags, `&lt;EM/.../'; empty start tags, `&lt;&gt;'; and empty end-tags,
+ `&lt;/&gt;'. Until support for these idioms is widely deployed, their
+ use is strongly discouraged.
+
+<span class="h4"><a name="section-3.2.3">3.2.3</a>. Names</span>
+
+ A name consists of a letter followed by letters, digits, periods, or
+ hyphens. The length of a name is limited to 72 characters by the
+ `NAMELEN' parameter in the SGML declaration for HTML, 9.5, "SGML
+ Declaration for HTML". Element and attribute names are not case
+ sensitive, but entity names are. For example, `&lt;BLOCKQUOTE&gt;',
+ `&lt;BlockQuote&gt;', and `&lt;blockquote&gt;' are equivalent, whereas `&amp;amp;' is
+ different from `&amp;AMP;'.
+
+ In a start-tag, the element name must immediately follow the tag open
+ delimiter `&lt;'.
+
+
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 14]</span>
+<a name="page-15" id="page-15" href="#page-15" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h4"><a name="section-3.2.4">3.2.4</a>. Attributes</span>
+
+ In a start-tag, white space and attributes are allowed between the
+ element name and the closing delimiter. An attribute specification
+ typically consists of an attribute name, an equal sign, and a value,
+ though some attribute specifications may be just a name token. White
+ space is allowed around the equal sign.
+
+ The value of the attribute may be either:
+
+ * A string literal, delimited by single quotes or double
+ quotes and not containing any occurrences of the delimiting
+ character.
+
+ NOTE - Some historical implementations consider any
+ occurrence of the `&gt;' character to signal the end of
+ a tag. For compatibility with such implementations,
+ when `&gt;' appears in an attribute value, it should be
+ represented with a numeric character reference. For
+ example, `&lt;IMG SRC="eq1.jpg" alt="a&gt;b"&gt;' should be
+ written `&lt;IMG SRC="eq1.jpg" alt="a&amp;#62;b"&gt;' or `&lt;IMG
+ SRC="eq1.jpg" alt="a&amp;gt;b"&gt;'.
+
+ * A name token (a sequence of letters, digits, periods, or
+ hyphens). Name tokens are not case sensitive.
+
+ NOTE - Some historical implementations allow any
+ character except space or `&gt;' in a name token.
+
+ In this example, &lt;img&gt; is the element name, src is the attribute
+ name, and `http://host/dir/file.gif' is the attribute value:
+
+ &lt;img src='http://host/dir/file.gif'&gt;
+
+ A useful technique for computing an attribute value literal for a
+ given string is to replace each quote and white space character by an
+ entity reference or numeric character reference as follows:
+
+ ENTITY NUMERIC
+ CHARACTER REFERENCE CHAR REF CHARACTER DESCRIPTION
+ --------- ---------- ----------- ---------------------
+ HT &amp;#9; Tab
+ LF &amp;#10; Line Feed
+ CR &amp;#13; Carriage Return
+ SP &amp;#32; Space
+ " &amp;quot; &amp;#34; Quotation mark
+ &amp; &amp;amp; &amp;#38; Ampersand
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 15]</span>
+<a name="page-16" id="page-16" href="#page-16" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ For example:
+
+ &lt;IMG SRC="image.jpg" alt="First &amp;quot;real&amp;quot; example"&gt;
+
+ The `NAMELEN' parameter in the SGML declaration (9.5, "SGML
+ Declaration for HTML") limits the length of an attribute value to
+ 1024 characters.
+
+ Attributes such as ISMAP and COMPACT may be written using a minimized
+ syntax (see 7.9.1.2 "Omitted Attribute Name" in [<a href="#ref-SGML">SGML</a>]). The markup:
+
+ &lt;UL COMPACT="compact"&gt;
+
+ can be written using a minimized syntax:
+
+ &lt;UL COMPACT&gt;
+
+ NOTE - Some historical implementations only understand the minimized
+ syntax.
+
+<span class="h4"><a name="section-3.2.5">3.2.5</a>. Comments</span>
+
+ To include comments in an HTML document, use a comment declaration. A
+ comment declaration consists of `&lt;!' followed by zero or more
+ comments followed by `&gt;'. Each comment starts with `--' and includes
+ all text up to and including the next occurrence of `--'. In a
+ comment declaration, white space is allowed after each comment, but
+ not before the first comment. The entire comment declaration is
+ ignored.
+
+ NOTE - Some historical HTML implementations incorrectly consider
+ any `&gt;' character to be the termination of a comment.
+
+ For example:
+
+ &lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"&gt;
+ &lt;HEAD&gt;
+ &lt;TITLE&gt;HTML Comment Example&lt;/TITLE&gt;
+ &lt;!-- Id: html-sgml.sgm,v 1.5 1995/05/26 21:29:50 connolly Exp --&gt;
+ &lt;!-- another -- -- comment --&gt;
+ &lt;!&gt;
+ &lt;/HEAD&gt;
+ &lt;BODY&gt;
+ &lt;p&gt; &lt;!- not a comment, just regular old data characters -&gt;
+
+
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 16]</span>
+<a name="page-17" id="page-17" href="#page-17" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h3"><a name="section-3.3">3.3</a>. HTML Public Text Identifiers</span>
+
+ To identify information as an HTML document conforming to this
+ specification, each document must start with one of the following
+ document type declarations.
+
+ &lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"&gt;
+
+ This document type declaration refers to the HTML DTD in 9.1, "HTML
+ DTD".
+
+ NOTE - If the body of a `text/html' message entity does not begin
+ with a document type declaration, an HTML user agent should infer
+ the above document type declaration.
+
+ &lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Level 2//EN"&gt;
+
+ This document type declaration also refers to the HTML DTD which
+ appears in 9.1, "HTML DTD".
+
+ &lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Level 1//EN"&gt;
+
+ This document type declaration refers to the level 1 HTML DTD in 9.3,
+ "Level 1 HTML DTD". Form elements must not occur in level 1
+ documents.
+
+ &lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Strict//EN"&gt;
+ &lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Strict Level 1//EN"&gt;
+
+ These two document type declarations refer to the HTML DTD in 9.2,
+ "Strict HTML DTD" and 9.4, "Strict Level 1 HTML DTD". They refer to
+ the more structurally rigid definition of HTML.
+
+ HTML user agents may support other document types. In particular,
+ they may support other formal public identifiers, or other document
+ types altogether. They may support an internal declaration subset
+ with supplemental entity, element, and other markup declarations.
+
+<span class="h3"><a name="section-3.4">3.4</a>. Example HTML Document</span>
+
+ &lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"&gt;
+ &lt;HTML&gt;
+ &lt;!-- Here's a good place to put a comment. --&gt;
+ &lt;HEAD&gt;
+ &lt;TITLE&gt;Structural Example&lt;/TITLE&gt;
+ &lt;/HEAD&gt;&lt;BODY&gt;
+ &lt;H1&gt;First Header&lt;/H1&gt;
+ &lt;P&gt;This is a paragraph in the example HTML file. Keep in mind
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 17]</span>
+<a name="page-18" id="page-18" href="#page-18" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ that the title does not appear in the document text, but that
+ the header (defined by H1) does.&lt;/P&gt;
+ &lt;OL&gt;
+ &lt;LI&gt;First item in an ordered list.
+ &lt;LI&gt;Second item in an ordered list.
+ &lt;UL COMPACT&gt;
+ &lt;LI&gt; Note that lists can be nested;
+ &lt;LI&gt; Whitespace may be used to assist in reading the
+ HTML source.
+ &lt;/UL&gt;
+ &lt;LI&gt;Third item in an ordered list.
+ &lt;/OL&gt;
+ &lt;P&gt;This is an additional paragraph. Technically, end tags are
+ not required for paragraphs, although they are allowed. You can
+ include character highlighting in a paragraph. &lt;EM&gt;This sentence
+ of the paragraph is emphasized.&lt;/EM&gt; Note that the &amp;lt;/P&amp;gt;
+ end tag has been omitted.
+ &lt;P&gt;
+ &lt;IMG SRC ="triangle.xbm" alt="Warning: "&gt;
+ Be sure to read these &lt;b&gt;bold instructions&lt;/b&gt;.
+ &lt;/BODY&gt;&lt;/HTML&gt;
+
+<span class="h2"><a name="section-4">4</a>. HTML as an Internet Media Type</span>
+
+ An HTML user agent allows users to interact with resources which have
+ HTML representations. At a minimum, it must allow users to examine
+ and navigate the content of HTML level 1 documents. HTML user agents
+ should be able to preserve all formatting distinctions represented in
+ an HTML document, and be able to simultaneously present resources
+ referred to by IMG elements (they may ignore some formatting
+ distinctions or IMG resources at the request of the user). Level 2
+ HTML user agents should support form entry and submission.
+
+<span class="h3"><a name="section-4.1">4.1</a>. text/html media type</span>
+
+ This specification defines the Internet Media Type [<a href="#ref-IMEDIA" title='"Media Type Registration Procedure"'>IMEDIA</a>] (formerly
+ referred to as the Content Type [<a href="#ref-MIME" title='"MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies"'>MIME</a>]) called `text/html'. The
+ following is to be registered with [<a href="#ref-IANA" title='"Assigned Numbers"'>IANA</a>].
+
+ Media Type name
+ text
+
+ Media subtype name
+ html
+
+ Required parameters
+ none
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 18]</span>
+<a name="page-19" id="page-19" href="#page-19" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ Optional parameters
+ level, charset
+
+ Encoding considerations
+ any encoding is allowed
+
+ Security considerations
+ see 10, "Security Considerations"
+
+ The optional parameters are defined as follows:
+
+ Level
+ The level parameter specifies the feature set used in
+ the document. The level is an integer number, implying
+ that any features of same or lower level may be present
+ in the document. Level 1 is all features defined in this
+ specification except those that require the &lt;FORM&gt;
+ element. Level 2 includes form processing. Level 2 is
+ the default.
+
+ Charset
+ The charset parameter (as defined in <a href="./rfc1521#section-7.1.1">section&nbsp;7.1.1 of
+ RFC 1521</a>[<a href="#ref-MIME" title='"MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies"'>MIME</a>]) may be given to specify the character
+ encoding scheme used to represent the HTML document as a
+ sequence of octets. The default value is outside the
+ scope of this specification; but for example, the
+ default is `US-ASCII' in the context of MIME mail, and
+ `ISO-8859-1' in the context of HTTP [<a href="#ref-HTTP" title='"Hypertext Transfer Protocol - HTTP/1.0"'>HTTP</a>].
+
+<span class="h3"><a name="section-4.2">4.2</a>. HTML Document Representation</span>
+
+ A message entity with a content type of `text/html' represents an
+ HTML document, consisting of a single text entity. The `charset'
+ parameter (whether implicit or explicit) identifies a character
+ encoding scheme. The text entity consists of the characters
+ determined by this character encoding scheme and the octets of the
+ body of the message entity.
+
+<span class="h4"><a name="section-4.2.1">4.2.1</a>. Undeclared Markup Error Handling</span>
+
+ To facilitate experimentation and interoperability between
+ implementations of various versions of HTML, the installed base of
+ HTML user agents supports a superset of the HTML 2.0 language by
+ reducing it to HTML 2.0: markup in the form of a start-tag or end-
+ tag, whose generic identifier is not declared is mapped to nothing
+ during tokenization. Undeclared attributes are treated similarly. The
+ entire attribute specification of an unknown attribute (i.e., the
+ unknown attribute and its value, if any) should be ignored. On the
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 19]</span>
+<a name="page-20" id="page-20" href="#page-20" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ other hand, references to undeclared entities should be treated as
+ data characters.
+
+ For example:
+
+ &lt;div class=chapter&gt;&lt;h1&gt;foo&lt;/h1&gt;&lt;p&gt;...&lt;/div&gt;
+ =&gt; &lt;H1&gt;,"foo",&lt;/H1&gt;,&lt;P&gt;,"..."
+ xxx &lt;P ID=z23&gt; yyy
+ =&gt; "xxx ",&lt;P&gt;," yyy
+ Let &amp;alpha; &amp;amp; &amp;beta; be finite sets.
+ =&gt; "Let &amp;alpha; &amp; &amp;beta; be finite sets."
+
+ Support for notifying the user of such errors is encouraged.
+
+ Information providers are warned that this convention is not binding:
+ unspecified behavior may result, as such markup does not conform to
+ this specification.
+
+<span class="h4"><a name="section-4.2.2">4.2.2</a>. Conventional Representation of Newlines</span>
+
+ SGML specifies that a text entity is a sequence of records, each
+ beginning with a record start character and ending with a record end
+ character (code positions 10 and 13 respectively) (<a href="#section-7.6.1">section 7.6.1</a>,
+ "Record Boundaries" in [<a href="#ref-SGML">SGML</a>]).
+
+ [<a name="ref-MIME" id="ref-MIME">MIME</a>] specifies that a body of type `text/*' is a sequence of lines,
+ each terminated by CRLF, that is, octets 13, 10.
+
+ In practice, HTML documents are frequently represented and
+ transmitted using an end of line convention that depends on the
+ conventions of the source of the document; frequently, that
+ representation consists of CR only, LF only, or a CR LF sequence.
+ Hence the decoding of the octets will often result in a text entity
+ with some missing record start and record end characters.
+
+ Since there is no ambiguity, HTML user agents are encouraged to infer
+ the missing record start and end characters.
+
+ An HTML user agent should treat end of line in any of its variations
+ as a word space in all contexts except preformatted text. Within
+ preformatted text, an HTML user agent should treat any of the three
+ common representations of end-of-line as starting a new line.
+
+<span class="h2"><a name="section-5">5</a>. Document Structure</span>
+
+ An HTML document is a tree of elements, including a head and body,
+ headings, paragraphs, lists, etc. Form elements are discussed in 8,
+ "Forms".
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 20]</span>
+<a name="page-21" id="page-21" href="#page-21" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h3"><a name="section-5.1">5.1</a>. Document Element: HTML</span>
+
+ The HTML document element consists of a head and a body, much like a
+ memo or a mail message. The head contains the title and optional
+ elements. The body is a text flow consisting of paragraphs, lists,
+ and other elements.
+
+<span class="h3"><a name="section-5.2">5.2</a>. Head: HEAD</span>
+
+ The head of an HTML document is an unordered collection of
+ information about the document. For example:
+
+ &lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"&gt;
+ &lt;HEAD&gt;
+ &lt;TITLE&gt;Introduction to HTML&lt;/TITLE&gt;
+ &lt;/HEAD&gt;
+ ...
+
+<span class="h4"><a name="section-5.2.1">5.2.1</a>. Title: TITLE</span>
+
+ Every HTML document must contain a &lt;TITLE&gt; element.
+
+ The title should identify the contents of the document in a global
+ context. A short title, such as "Introduction" may be meaningless out
+ of context. A title such as "Introduction to HTML Elements" is more
+ appropriate.
+
+ NOTE - The length of a title is not limited; however, long titles
+ may be truncated in some applications. To minimize this
+ possibility, titles should be fewer than 64 characters.
+
+ A user agent may display the title of a document in a history list or
+ as a label for the window displaying the document. This differs from
+ headings (5.4, "Headings: H1 ... H6"), which are typically displayed
+ within the body text flow.
+
+<span class="h4"><a name="section-5.2.2">5.2.2</a>. Base Address: BASE</span>
+
+ The optional &lt;BASE&gt; element provides a base address for interpreting
+ relative URLs when the document is read out of context (see 7,
+ "Hyperlinks"). The value of the HREF attribute must be an absolute
+ URI.
+
+<span class="h4"><a name="section-5.2.3">5.2.3</a>. Keyword Index: ISINDEX</span>
+
+ The &lt;ISINDEX&gt; element indicates that the user agent should allow the
+ user to search an index by giving keywords. See 7.5, "Queries and
+ Indexes" for details.
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 21]</span>
+<a name="page-22" id="page-22" href="#page-22" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h4"><a name="section-5.2.4">5.2.4</a>. Link: LINK</span>
+
+ The &lt;LINK&gt; element represents a hyperlink (see 7, "Hyperlinks"). Any
+ number of LINK elements may occur in the &lt;HEAD&gt; element of an HTML
+ document. It has the same attributes as the &lt;A&gt; element (see 5.7.3,
+ "Anchor: A").
+
+ The &lt;LINK&gt; element is typically used to indicate authorship, related
+ indexes and glossaries, older or more recent versions, document
+ hierarchy, associated resources such as style sheets, etc.
+
+<span class="h4"><a name="section-5.2.5">5.2.5</a>. Associated Meta-information: META</span>
+
+ The &lt;META&gt; element is an extensible container for use in identifying
+ specialized document meta-information. Meta-information has two main
+ functions:
+
+ * to provide a means to discover that the data set exists
+ and how it might be obtained or accessed; and
+
+ * to document the content, quality, and features of a data
+ set, indicating its fitness for use.
+
+ Each &lt;META&gt; element specifies a name/value pair. If multiple META
+ elements are provided with the same name, their combined contents--
+ concatenated as a comma-separated list--is the value associated with
+ that name.
+
+ NOTE - The &lt;META&gt; element should not be used where a
+ specific element, such as &lt;TITLE&gt;, would be more
+ appropriate. Rather than a &lt;META&gt; element with a URI as
+ the value of the CONTENT attribute, use a &lt;LINK&gt;
+ element.
+
+ HTTP servers may read the content of the document &lt;HEAD&gt; to generate
+ header fields corresponding to any elements defining a value for the
+ attribute HTTP-EQUIV.
+
+ NOTE - The method by which the server extracts document
+ meta-information is unspecified and not mandatory. The
+ &lt;META&gt; element only provides an extensible mechanism for
+ identifying and embedding document meta-information --
+ how it may be used is up to the individual server
+ implementation and the HTML user agent.
+
+
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 22]</span>
+<a name="page-23" id="page-23" href="#page-23" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ Attributes of the META element:
+
+ HTTP-EQUIV
+ binds the element to an HTTP header field. An HTTP
+ server may use this information to process the document.
+ In particular, it may include a header field in the
+ responses to requests for this document: the header name
+ is taken from the HTTP-EQUIV attribute value, and the
+ header value is taken from the value of the CONTENT
+ attribute. HTTP header names are not case sensitive.
+
+ NAME
+ specifies the name of the name/value pair. If not
+ present, HTTP-EQUIV gives the name.
+
+ CONTENT
+ specifies the value of the name/value pair.
+
+ Examples
+
+ If the document contains:
+
+ &lt;META HTTP-EQUIV="Expires"
+ CONTENT="Tue, 04 Dec 1993 21:29:02 GMT"&gt;
+ &lt;meta http-equiv="Keywords" CONTENT="Fred"&gt;
+ &lt;META HTTP-EQUIV="Reply-to"
+ content="fielding@ics.uci.edu (Roy Fielding)"&gt;
+ &lt;Meta Http-equiv="Keywords" CONTENT="Barney"&gt;
+
+ then the server may include the following header fields:
+
+ Expires: Tue, 04 Dec 1993 21:29:02 GMT
+ Keywords: Fred, Barney
+ Reply-to: fielding@ics.uci.edu (Roy Fielding)
+
+ as part of the HTTP response to a `GET' or `HEAD' request for
+ that document.
+
+ An HTTP server must not use the &lt;META&gt; element to form an HTTP
+ response header unless the HTTP-EQUIV attribute is present.
+
+ An HTTP server may disregard any &lt;META&gt; elements that specify
+ information controlled by the HTTP server, for example `Server',
+
+ `Date', and `Last-modified'.
+
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 23]</span>
+<a name="page-24" id="page-24" href="#page-24" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h4"><a name="section-5.2.6">5.2.6</a>. Next Id: NEXTID</span>
+
+ The &lt;NEXTID&gt; element is included for historical reasons only. HTML
+ documents should not contain &lt;NEXTID&gt; elements.
+
+ The &lt;NEXTID&gt; element gives a hint for the name to use for a new &lt;A&gt;
+ element when editing an HTML document. It should be distinct from all
+ NAME attribute values on &lt;A&gt; elements. For example:
+
+ &lt;NEXTID N=Z27&gt;
+
+<span class="h3"><a name="section-5.3">5.3</a>. Body: BODY</span>
+
+ The &lt;BODY&gt; element contains the text flow of the document, including
+ headings, paragraphs, lists, etc.
+
+ For example:
+
+ &lt;BODY&gt;
+ &lt;h1&gt;Important Stuff&lt;/h1&gt;
+ &lt;p&gt;Explanation about important stuff...
+ &lt;/BODY&gt;
+
+<a href="#section-5.4">5.4</a>. Headings: H1 ... H6
+
+ The six heading elements, &lt;H1&gt; through &lt;H6&gt;, denote section headings.
+ Although the order and occurrence of headings is not constrained by
+ the HTML DTD, documents should not skip levels (for example, from H1
+ to H3), as converting such documents to other representations is
+ often problematic.
+
+ Example of use:
+
+ &lt;H1&gt;This is a heading&lt;/H1&gt;
+ Here is some text
+ &lt;H2&gt;Second level heading&lt;/H2&gt;
+ Here is some more text.
+
+ Typical renderings are:
+
+ H1
+ Bold, very-large font, centered. One or two blank lines
+ above and below.
+
+ H2
+ Bold, large font, flush-left. One or two blank lines
+ above and below.
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 24]</span>
+<a name="page-25" id="page-25" href="#page-25" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ H3
+ Italic, large font, slightly indented from the left
+ margin. One or two blank lines above and below.
+
+ H4
+ Bold, normal font, indented more than H3. One blank line
+ above and below.
+
+ H5
+ Italic, normal font, indented as H4. One blank line
+ above.
+
+ H6
+ Bold, indented same as normal text, more than H5. One
+ blank line above.
+
+<span class="h3"><a name="section-5.5">5.5</a>. Block Structuring Elements</span>
+
+ Block structuring elements include paragraphs, lists, and block
+ quotes. They must not contain heading elements, but they may contain
+ phrase markup, and in some cases, they may be nested.
+
+<span class="h4"><a name="section-5.5.1">5.5.1</a>. Paragraph: P</span>
+
+ The &lt;P&gt; element indicates a paragraph. The exact indentation, leading
+ space, etc. of a paragraph is not specified and may be a function of
+ other tags, style sheets, etc.
+
+ Typically, paragraphs are surrounded by a vertical space of one line
+ or half a line. The first line in a paragraph is indented in some
+ cases.
+
+ Example of use:
+
+ &lt;H1&gt;This Heading Precedes the Paragraph&lt;/H1&gt;
+ &lt;P&gt;This is the text of the first paragraph.
+ &lt;P&gt;This is the text of the second paragraph. Although you do not
+ need to start paragraphs on new lines, maintaining this
+ convention facilitates document maintenance.&lt;/P&gt;
+ &lt;P&gt;This is the text of a third paragraph.&lt;/P&gt;
+
+<span class="h4"><a name="section-5.5.2">5.5.2</a>. Preformatted Text: PRE</span>
+
+ The &lt;PRE&gt; element represents a character cell block of text and is
+ suitable for text that has been formatted for a monospaced font.
+
+ The &lt;PRE&gt; tag may be used with the optional WIDTH attribute. The
+ WIDTH attribute specifies the maximum number of characters for a line
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 25]</span>
+<a name="page-26" id="page-26" href="#page-26" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ and allows the HTML user agent to select a suitable font and
+ indentation.
+
+ Within preformatted text:
+
+ * Line breaks within the text are rendered as a move to the
+ beginning of the next line.
+
+ NOTE - References to the "beginning of a new line"
+ do not imply that the renderer is forbidden from
+ using a constant left indent for rendering
+ preformatted text. The left indent may be
+ constrained by the width required.
+
+ * Anchor elements and phrase markup may be used.
+
+ NOTE - Constraints on the processing of &lt;PRE&gt;
+ content may limit or prevent the ability of the HTML
+ user agent to faithfully render phrase markup.
+
+ * Elements that define paragraph formatting (headings,
+ address, etc.) must not be used.
+
+ NOTE - Some historical documents contain &lt;P&gt; tags in
+ &lt;PRE&gt; elements. User agents are encouraged to treat
+ this as a line break. A &lt;P&gt; tag followed by a
+ newline character should produce only one line
+ break, not a line break plus a blank line.
+
+ * The horizontal tab character (code position 9 in the HTML
+ document character set) must be interpreted as the smallest
+ positive nonzero number of spaces which will leave the
+ number of characters so far on the line as a multiple of 8.
+ Documents should not contain tab characters, as they are not
+ supported consistently.
+
+ Example of use:
+
+ &lt;PRE&gt;
+ Line 1.
+ Line 2 is to the right of line 1. &lt;a href="abc"&gt;abc&lt;/a&gt;
+ Line 3 aligns with line 2. &lt;a href="def"&gt;def&lt;/a&gt;
+ &lt;/PRE&gt;
+
+
+
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 26]</span>
+<a name="page-27" id="page-27" href="#page-27" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h5"><a name="section-5.5.2.1">5.5.2.1</a>. Example and Listing: XMP, LISTING</span>
+
+ The &lt;XMP&gt; and &lt;LISTING&gt; elements are similar to the &lt;PRE&gt; element,
+ but they have a different syntax. Their content is declared as CDATA,
+ which means that no markup except the end-tag open delimiter-in-
+ context is recognized (see 9.6 "Delimiter Recognition" of [<a href="#ref-SGML">SGML</a>]).
+
+ NOTE - In a previous draft of the HTML specification, the syntax
+ of &lt;XMP&gt; and &lt;LISTING&gt; elements allowed closing tags to be treated
+ as data characters, as long as the tag name was not &lt;XMP&gt; or
+ &lt;LISTING&gt;, respectively.
+
+ Since CDATA declared content has a number of unfortunate interactions
+ with processing techniques and tends to be used and implemented
+ inconsistently, HTML documents should not contain &lt;XMP&gt; nor &lt;LISTING&gt;
+ elements -- the &lt;PRE&gt; tag is more expressive and more consistently
+ supported.
+
+ The &lt;LISTING&gt; element should be rendered so that at least 132
+ characters fit on a line. The &lt;XMP&gt; element should be rendered so
+ that at least 80 characters fit on a line but is otherwise identical
+ to the &lt;LISTING&gt; element.
+
+ NOTE - In a previous draft, HTML included a &lt;PLAINTEXT&gt; element
+ that is similar to the &lt;LISTING&gt; element, except that there is no
+ closing tag: all characters after the &lt;PLAINTEXT&gt; start-tag are
+ data.
+
+<span class="h4"><a name="section-5.5.3">5.5.3</a>. Address: ADDRESS</span>
+
+ The &lt;ADDRESS&gt; element contains such information as address, signature
+ and authorship, often at the beginning or end of the body of a
+ document.
+
+ Typically, the &lt;ADDRESS&gt; element is rendered in an italic typeface
+ and may be indented.
+
+ Example of use:
+
+ &lt;ADDRESS&gt;
+ Newsletter editor&lt;BR&gt;
+ J.R. Brown&lt;BR&gt;
+ JimquickPost News, Jimquick, CT 01234&lt;BR&gt;
+ Tel (123) 456 7890
+ &lt;/ADDRESS&gt;
+
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 27]</span>
+<a name="page-28" id="page-28" href="#page-28" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h4"><a name="section-5.5.4">5.5.4</a>. Block Quote: BLOCKQUOTE</span>
+
+ The &lt;BLOCKQUOTE&gt; element contains text quoted from another source.
+
+ A typical rendering might be a slight extra left and right indent,
+ and/or italic font. The &lt;BLOCKQUOTE&gt; typically provides space above
+ and below the quote.
+
+ Single-font rendition may reflect the quotation style of Internet
+ mail by putting a vertical line of graphic characters, such as the
+ greater than symbol (&gt;), in the left margin.
+
+ Example of use:
+
+ I think the play ends
+ &lt;BLOCKQUOTE&gt;
+ &lt;P&gt;Soft you now, the fair Ophelia. Nymph, in thy orisons, be all
+ my sins remembered.
+ &lt;/BLOCKQUOTE&gt;
+ but I am not sure.
+
+<span class="h3"><a name="section-5.6">5.6</a>. List Elements</span>
+
+ HTML includes a number of list elements. They may be used in
+ combination; for example, a &lt;OL&gt; may be nested in an &lt;LI&gt; element of
+ a &lt;UL&gt;.
+
+ The COMPACT attribute suggests that a compact rendering be used.
+
+<span class="h4"><a name="section-5.6.1">5.6.1</a>. Unordered List: UL, LI</span>
+
+ The &lt;UL&gt; represents a list of items -- typically rendered as a
+ bulleted list.
+
+ The content of a &lt;UL&gt; element is a sequence of &lt;LI&gt; elements. For
+ example:
+
+ &lt;UL&gt;
+ &lt;LI&gt;First list item
+ &lt;LI&gt;Second list item
+ &lt;p&gt;second paragraph of second item
+ &lt;LI&gt;Third list item
+ &lt;/UL&gt;
+
+<span class="h4"><a name="section-5.6.2">5.6.2</a>. Ordered List: OL</span>
+
+ The &lt;OL&gt; element represents an ordered list of items, sorted by
+ sequence or order of importance. It is typically rendered as a
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 28]</span>
+<a name="page-29" id="page-29" href="#page-29" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ numbered list.
+
+ The content of a &lt;OL&gt; element is a sequence of &lt;LI&gt; elements. For
+ example:
+
+ &lt;OL&gt;
+ &lt;LI&gt;Click the Web button to open URI window.
+ &lt;LI&gt;Enter the URI number in the text field of the Open URI
+ window. The Web document you specified is displayed.
+ &lt;ol&gt;
+ &lt;li&gt;substep 1
+ &lt;li&gt;substep 2
+ &lt;/ol&gt;
+ &lt;LI&gt;Click highlighted text to move from one link to another.
+ &lt;/OL&gt;
+
+<span class="h4"><a name="section-5.6.3">5.6.3</a>. Directory List: DIR</span>
+
+ The &lt;DIR&gt; element is similar to the &lt;UL&gt; element. It represents a
+ list of short items, typically up to 20 characters each. Items in a
+ directory list may be arranged in columns, typically 24 characters
+ wide.
+
+ The content of a &lt;DIR&gt; element is a sequence of &lt;LI&gt; elements.
+ Nested block elements are not allowed in the content of &lt;DIR&gt;
+ elements. For example:
+
+ &lt;DIR&gt;
+ &lt;LI&gt;A-H&lt;LI&gt;I-M
+ &lt;LI&gt;M-R&lt;LI&gt;S-Z
+ &lt;/DIR&gt;
+
+<span class="h4"><a name="section-5.6.4">5.6.4</a>. Menu List: MENU</span>
+
+ The &lt;MENU&gt; element is a list of items with typically one line per
+ item. The menu list style is typically more compact than the style of
+ an unordered list.
+
+ The content of a &lt;MENU&gt; element is a sequence of &lt;LI&gt; elements.
+ Nested block elements are not allowed in the content of &lt;MENU&gt;
+ elements. For example:
+
+ &lt;MENU&gt;
+ &lt;LI&gt;First item in the list.
+ &lt;LI&gt;Second item in the list.
+ &lt;LI&gt;Third item in the list.
+ &lt;/MENU&gt;
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 29]</span>
+<a name="page-30" id="page-30" href="#page-30" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h4"><a name="section-5.6.5">5.6.5</a>. Definition List: DL, DT, DD</span>
+
+ A definition list is a list of terms and corresponding definitions.
+ Definition lists are typically formatted with the term flush-left and
+ the definition, formatted paragraph style, indented after the term.
+
+ The content of a &lt;DL&gt; element is a sequence of &lt;DT&gt; elements and/or
+ &lt;DD&gt; elements, usually in pairs. Multiple &lt;DT&gt; may be paired with a
+ single &lt;DD&gt; element. Documents should not contain multiple
+ consecutive &lt;DD&gt; elements.
+
+ Example of use:
+
+ &lt;DL&gt;
+ &lt;DT&gt;Term&lt;DD&gt;This is the definition of the first term.
+ &lt;DT&gt;Term&lt;DD&gt;This is the definition of the second term.
+ &lt;/DL&gt;
+
+ If the DT term does not fit in the DT column (typically one third of
+ the display area), it may be extended across the page with the DD
+ section moved to the next line, or it may be wrapped onto successive
+ lines of the left hand column.
+
+ The optional COMPACT attribute suggests that a compact rendering be
+ used, because the list items are small and/or the entire list is
+ large.
+
+ Unless the COMPACT attribute is present, an HTML user agent may leave
+ white space between successive DT, DD pairs. The COMPACT attribute
+ may also reduce the width of the left-hand (DT) column.
+
+ &lt;DL COMPACT&gt;
+ &lt;DT&gt;Term&lt;DD&gt;This is the first definition in compact format.
+ &lt;DT&gt;Term&lt;DD&gt;This is the second definition in compact format.
+ &lt;/DL&gt;
+
+<span class="h3"><a name="section-5.7">5.7</a>. Phrase Markup</span>
+
+ Phrases may be marked up according to idiomatic usage, typographic
+ appearance, or for use as hyperlink anchors.
+
+ User agents must render highlighted phrases distinctly from plain
+ text. Additionally, &lt;EM&gt; content must be rendered as distinct from
+ &lt;STRONG&gt; content, and &lt;B&gt; content must rendered as distinct from &lt;I&gt;
+ content.
+
+ Phrase elements may be nested within the content of other phrase
+ elements; however, HTML user agents may render nested phrase elements
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 30]</span>
+<a name="page-31" id="page-31" href="#page-31" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ indistinctly from non-nested elements:
+
+ plain &lt;B&gt;bold &lt;I&gt;italic&lt;/I&gt;&lt;/B&gt; may be rendered
+ the same as plain &lt;B&gt;bold &lt;/B&gt;&lt;I&gt;italic&lt;/I&gt;
+
+<span class="h4"><a name="section-5.7.1">5.7.1</a>. Idiomatic Elements</span>
+
+ Phrases may be marked up to indicate certain idioms.
+
+ NOTE - User agents may support the &lt;DFN&gt; element, not included in
+ this specification, as it has been deployed to some extent. It is
+ used to indicate the defining instance of a term, and it is
+ typically rendered in italic or bold italic.
+
+<span class="h5"><a name="section-5.7.1.1">5.7.1.1</a>. Citation: CITE</span>
+
+ The &lt;CITE&gt; element is used to indicate the title of a book or
+ other citation. It is typically rendered as italics. For example:
+
+ He just couldn't get enough of &lt;cite&gt;The Grapes of Wrath&lt;/cite&gt;.
+
+<span class="h5"><a name="section-5.7.1.2">5.7.1.2</a>. Code: CODE</span>
+
+ The &lt;CODE&gt; element indicates an example of code, typically
+ rendered in a mono-spaced font. The &lt;CODE&gt; element is intended for
+ short words or phrases of code; the &lt;PRE&gt; block structuring
+ element (5.5.2, "Preformatted Text: PRE") is more appropriate
+ for multiple-line listings. For example:
+
+ The expression &lt;code&gt;x += 1&lt;/code&gt;
+ is short for &lt;code&gt;x = x + 1&lt;/code&gt;.
+
+<span class="h5"><a name="section-5.7.1.3">5.7.1.3</a>. Emphasis: EM</span>
+
+ The &lt;EM&gt; element indicates an emphasized phrase, typically
+ rendered as italics. For example:
+
+ A singular subject &lt;em&gt;always&lt;/em&gt; takes a singular verb.
+
+<span class="h5"><a name="section-5.7.1.4">5.7.1.4</a>. Keyboard: KBD</span>
+
+ The &lt;KBD&gt; element indicates text typed by a user, typically
+ rendered in a mono-spaced font. This is commonly used in
+ instruction manuals. For example:
+
+ Enter &lt;kbd&gt;FIND IT&lt;/kbd&gt; to search the database.
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 31]</span>
+<a name="page-32" id="page-32" href="#page-32" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h5"><a name="section-5.7.1.5">5.7.1.5</a>. Sample: SAMP</span>
+
+ The &lt;SAMP&gt; element indicates a sequence of literal characters,
+ typically rendered in a mono-spaced font. For example:
+
+ The only word containing the letters &lt;samp&gt;mt&lt;/samp&gt; is dreamt.
+
+<span class="h5"><a name="section-5.7.1.6">5.7.1.6</a>. Strong Emphasis: STRONG</span>
+
+ The &lt;STRONG&gt; element indicates strong emphasis, typically rendered
+ in bold. For example:
+
+ &lt;strong&gt;STOP&lt;/strong&gt;, or I'll say "&lt;strong&gt;STOP&lt;/strong&gt;" again!
+
+<span class="h5"><a name="section-5.7.1.7">5.7.1.7</a>. Variable: VAR</span>
+
+ The &lt;VAR&gt; element indicates a placeholder variable, typically
+ rendered as italic. For example:
+
+ Type &lt;SAMP&gt;html-check &lt;VAR&gt;file&lt;/VAR&gt; | more&lt;/SAMP&gt;
+ to check &lt;VAR&gt;file&lt;/VAR&gt; for markup errors.
+
+<span class="h4"><a name="section-5.7.2">5.7.2</a>. Typographic Elements</span>
+
+ Typographic elements are used to specify the format of marked
+ text.
+
+ Typical renderings for idiomatic elements may vary between user
+ agents. If a specific rendering is necessary -- for example, when
+ referring to a specific text attribute as in "The italic parts are
+ mandatory" -- a typographic element can be used to ensure that the
+ intended typography is used where possible.
+
+ NOTE - User agents may support some typographic elements not
+ included in this specification, as they have been deployed to some
+ extent. The &lt;STRIKE&gt; element indicates horizontal line through the
+ characters, and the &lt;U&gt; element indicates an underline.
+
+<span class="h5"><a name="section-5.7.2.1">5.7.2.1</a>. Bold: B</span>
+
+ The &lt;B&gt; element indicates bold text. Where bold typography is
+ unavailable, an alternative representation may be used.
+
+<span class="h5"><a name="section-5.7.2.2">5.7.2.2</a>. Italic: I</span>
+
+ The &lt;I&gt; element indicates italic text. Where italic typography is
+ unavailable, an alternative representation may be used.
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 32]</span>
+<a name="page-33" id="page-33" href="#page-33" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h5"><a name="section-5.7.2.3">5.7.2.3</a>. Teletype: TT</span>
+
+ The &lt;TT&gt; element indicates teletype (monospaced )text. Where a
+ teletype font is unavailable, an alternative representation may be
+ used.
+
+<span class="h4"><a name="section-5.7.3">5.7.3</a>. Anchor: A</span>
+
+ The &lt;A&gt; element indicates a hyperlink anchor (see 7, "Hyperlinks").
+ At least one of the NAME and HREF attributes should be present.
+ Attributes of the &lt;A&gt; element:
+
+ HREF
+ gives the URI of the head anchor of a hyperlink.
+
+ NAME
+ gives the name of the anchor, and makes it available as
+ a head of a hyperlink.
+
+ TITLE
+ suggests a title for the destination resource --
+ advisory only. The TITLE attribute may be used:
+
+ * for display prior to accessing the destination
+ resource, for example, as a margin note or on a
+ small box while the mouse is over the anchor, or
+ while the document is being loaded;
+
+ * for resources that do not include a title, such as
+ graphics, plain text and Gopher menus, for use as a
+ window title.
+
+ REL
+ The REL attribute gives the relationship(s) described by
+ the hyperlink. The value is a whitespace separated list
+ of relationship names. The semantics of link
+ relationships are not specified in this document.
+
+ REV
+ same as the REL attribute, but the semantics of the
+ relationship are in the reverse direction. A link from A
+ to B with REL="X" expresses the same relationship as a
+ link from B to A with REV="X". An anchor may have both
+ REL and REV attributes.
+
+ URN
+ specifies a preferred, more persistent identifier for
+ the head anchor of the hyperlink. The syntax and
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 33]</span>
+<a name="page-34" id="page-34" href="#page-34" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ semantics of the URN attribute are not yet specified.
+
+ METHODS
+ specifies methods to be used in accessing the
+ destination, as a whitespace-separated list of names.
+ The set of applicable names is a function of the scheme
+ of the URI in the HREF attribute. For similar reasons as
+ for the TITLE attribute, it may be useful to include the
+ information in advance in the link. For example, the
+ HTML user agent may chose a different rendering as a
+ function of the methods allowed; for example, something
+ that is searchable may get a different icon.
+
+<span class="h3"><a name="section-5.8">5.8</a>. Line Break: BR</span>
+
+ The &lt;BR&gt; element specifies a line break between words (see 6,
+ "Characters, Words, and Paragraphs"). For example:
+
+ &lt;P&gt; Pease porridge hot&lt;BR&gt;
+ Pease porridge cold&lt;BR&gt;
+ Pease porridge in the pot&lt;BR&gt;
+ Nine days old.
+
+<span class="h3"><a name="section-5.9">5.9</a>. Horizontal Rule: HR</span>
+
+ The &lt;HR&gt; element is a divider between sections of text; typically a
+ full width horizontal rule or equivalent graphic. For example:
+
+ &lt;HR&gt;
+ &lt;ADDRESS&gt;February 8, 1995, CERN&lt;/ADDRESS&gt;
+ &lt;/BODY&gt;
+
+<span class="h3"><a name="section-5.10">5.10</a>. Image: IMG</span>
+
+ The &lt;IMG&gt; element refers to an image or icon via a hyperlink (see
+ 7.3, "Simultaneous Presentation of Image Resources").
+
+ HTML user agents may process the value of the ALT attribute as an
+ alternative to processing the image resource indicated by the SRC
+ attribute.
+
+ NOTE - Some HTML user agents can process graphics linked via
+ anchors, but not &lt;IMG&gt; graphics. If a graphic is essential, it
+ should be referenced from an &lt;A&gt; element rather than an &lt;IMG&gt;
+ element. If the graphic is not essential, then the &lt;IMG&gt; element
+ is appropriate.
+
+ Attributes of the &lt;IMG&gt; element:
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 34]</span>
+<a name="page-35" id="page-35" href="#page-35" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ ALIGN
+ alignment of the image with respect to the text
+ baseline.
+
+ * `TOP' specifies that the top of the image aligns
+ with the tallest item on the line containing the
+ image.
+
+ * `MIDDLE' specifies that the center of the image
+ aligns with the baseline of the line containing the
+ image.
+
+ * `BOTTOM' specifies that the bottom of the image
+ aligns with the baseline of the line containing the
+ image.
+
+ ALT
+ text to use in place of the referenced image resource,
+ for example due to processing constraints or user
+ preference.
+
+ ISMAP
+ indicates an image map (see 7.6, "Image Maps").
+
+ SRC
+ specifies the URI of the image resource.
+
+ NOTE - In practice, the media types of image
+ resources are limited to a few raster graphic
+ formats: typically `image/gif', `image/jpeg'. In
+ particular, `text/html' resources are not
+ intended to be used as image resources.
+
+ Examples of use:
+
+ &lt;IMG SRC="triangle.xbm" ALT="Warning:"&gt; Be sure
+ to read these instructions.
+
+ &lt;a href="http://machine/htbin/imagemap/sample"&gt;
+ &lt;IMG SRC="sample.xbm" ISMAP&gt;
+ &lt;/a&gt;
+
+<span class="h2"><a name="section-6">6</a>. Characters, Words, and Paragraphs</span>
+
+ An HTML user agent should present the body of an HTML document as a
+ collection of typeset paragraphs and preformatted text. Except for
+ preformatted elements (&lt;PRE&gt;, &lt;XMP&gt;, &lt;LISTING&gt;, &lt;TEXTAREA&gt;), each
+ block structuring element is regarded as a paragraph by taking the
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 35]</span>
+<a name="page-36" id="page-36" href="#page-36" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ data characters in its content and the content of its descendant
+ elements, concatenating them, and splitting the result into words,
+ separated by space, tab, or record end characters (and perhaps hyphen
+ characters). The sequence of words is typeset as a paragraph by
+ breaking it into lines.
+
+<span class="h3"><a name="section-6.1">6.1</a>. The HTML Document Character Set</span>
+
+ The document character set specified in 9.5, "SGML Declaration for
+ HTML" must be supported by HTML user agents. It includes the graphic
+ characters of Latin Alphabet No. 1, or simply Latin-1. Latin-1
+ comprises 191 graphic characters, including the alphabets of most
+ Western European languages.
+
+ NOTE - Use of the non-breaking space and soft hyphen indicator
+ characters is discouraged because support for them is not widely
+ deployed.
+
+ NOTE - To support non-western writing systems, a larger character
+ repertoire will be specified in a future version of HTML. The
+ document character set will be [<a href="#ref-ISO-10646">ISO-10646</a>], or some subset that
+ agrees with [<a href="#ref-ISO-10646">ISO-10646</a>]; in particular, all numeric character
+ references must use code positions assigned by [<a href="#ref-ISO-10646">ISO-10646</a>].
+
+ In SGML applications, the use of control characters is limited in
+ order to maximize the chance of successful interchange over
+ heterogeneous networks and operating systems. In the HTML document
+ character set only three control characters are allowed: Horizontal
+ Tab, Carriage Return, and Line Feed (code positions 9, 13, and 10).
+
+ The HTML DTD references the Added Latin 1 entity set, to allow
+ mnemonic representation of selected Latin 1 characters using only the
+ widely supported ASCII character repertoire. For example:
+
+ Kurt G&amp;ouml;del was a famous logician and mathematician.
+
+ See 9.7.2, "ISO Latin 1 Character Entity Set" for a table of the
+ "Added Latin 1" entities, and 13, "The HTML Coded Character Set" for
+ a table of the code positions of [ISO 8859-1] and the control
+ characters in the HTML document character set.
+
+<span class="h2"><a name="section-7">7</a>. Hyperlinks</span>
+
+ In addition to general purpose elements such as paragraphs and lists,
+ HTML documents can express hyperlinks. An HTML user agent allows the
+ user to navigate these hyperlinks.
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 36]</span>
+<a name="page-37" id="page-37" href="#page-37" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ A hyperlink is a relationship between two anchors, called the head
+ and the tail of the hyperlink[DEXTER]. Anchors are identified by an
+ anchor address: an absolute Uniform Resource Identifier (URI),
+ optionally followed by a '#' and a sequence of characters called a
+ fragment identifier. For example:
+
+ <a href="http://www.w3.org/hypertext/WWW/TheProject.html">http://www.w3.org/hypertext/WWW/TheProject.html</a>
+ <a href="http://www.w3.org/hypertext/WWW/TheProject.html#z31">http://www.w3.org/hypertext/WWW/TheProject.html#z31</a>
+
+ In an anchor address, the URI refers to a resource; it may be used in
+ a variety of information retrieval protocols to obtain an entity that
+ represents the resource, such as an HTML document. The fragment
+ identifier, if present, refers to some view on, or portion of the
+ resource.
+
+ Each of the following markup constructs indicates the tail anchor of
+ a hyperlink or set of hyperlinks:
+
+ * &lt;A&gt; elements with HREF present.
+
+ * &lt;LINK&gt; elements.
+
+ * &lt;IMG&gt; elements.
+
+ * &lt;INPUT&gt; elements with the SRC attribute present.
+
+ * &lt;ISINDEX&gt; elements.
+
+ * &lt;FORM&gt; elements with `METHOD=GET'.
+
+ These markup constructs refer to head anchors by a URI, either
+ absolute or relative, or a fragment identifier, or both.
+
+ In the case of a relative URI, the absolute URI in the address of the
+ head anchor is the result of combining the relative URI with a base
+ absolute URI as in [<a href="#ref-RELURL" title='"Relative Uniform Resource Locators"'>RELURL</a>]. The base document is taken from the
+ document's &lt;BASE&gt; element, if present; else, it is determined as in
+ [<a href="#ref-RELURL" title='"Relative Uniform Resource Locators"'>RELURL</a>].
+
+<span class="h3"><a name="section-7.1">7.1</a>. Accessing Resources</span>
+
+ Once the address of the head anchor is determined, the user agent may
+ obtain a representation of the resource.
+
+ For example, if the base URI is `http://host/x/y.html' and the
+ document contains:
+
+ &lt;img src="../icons/abc.gif"&gt;
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 37]</span>
+<a name="page-38" id="page-38" href="#page-38" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ then the user agent uses the URI `http://host/icons/abc.gif' to
+ access the resource, as in [<a href="#ref-URL" title='"Uniform Resource Locators (URL)"'>URL</a>]..
+
+<span class="h3"><a name="section-7.2">7.2</a>. Activation of Hyperlinks</span>
+
+ An HTML user agent allows the user to navigate the content of the
+ document and request activation of hyperlinks denoted by &lt;A&gt;
+ elements. HTML user agents should also allow activation of &lt;LINK&gt;
+ element hyperlinks.
+
+ To activate a link, the user agent obtains a representation of the
+ resource identified in the address of the head anchor. If the
+ representation is another HTML document, navigation may begin again
+ with this new document.
+
+<span class="h3"><a name="section-7.3">7.3</a>. Simultaneous Presentation of Image Resources</span>
+
+ An HTML user agent may activate hyperlinks indicated by &lt;IMG&gt; and
+ &lt;INPUT&gt; elements concurrently with processing the document; that is,
+ image hyperlinks may be processed without explicit request by the
+ user. Image resources should be embedded in the presentation at the
+ point of the tail anchor, that is the &lt;IMG&gt; or &lt;INPUT&gt; element.
+
+ &lt;LINK&gt; hyperlinks may also be processed without explicit user
+ request; for example, style sheet resources may be processed before
+ or during the processing of the document.
+
+<span class="h3"><a name="section-7.4">7.4</a>. Fragment Identifiers</span>
+
+ Any characters following a `#' character in a hypertext address
+ constitute a fragment identifier. In particular, an address of the
+ form `#fragment' refers to an anchor in the same document.
+
+ The meaning of fragment identifiers depends on the media type of the
+ representation of the anchor's resource. For `text/html'
+ representations, it refers to the &lt;A&gt; element with a NAME attribute
+ whose value is the same as the fragment identifier. The matching is
+ case sensitive. The document should have exactly one such element.
+ The user agent should indicate the anchor element, for example by
+ scrolling to and/or highlighting the phrase.
+
+ For example, if the base URI is `http://host/x/y.html' and the user
+ activated the link denoted by the following markup:
+
+ &lt;p&gt; See: &lt;a href="app1.html#bananas"&gt;appendix 1&lt;/a&gt;
+ for more detail on bananas.
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 38]</span>
+<a name="page-39" id="page-39" href="#page-39" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ Then the user agent accesses the resource identified by
+ `http://host/x/app1.html'. Assuming the resource is represented using
+ the `text/html' media type, the user agent must locate the &lt;A&gt;
+ element whose NAME attribute is `bananas' and begin navigation there.
+
+<span class="h3"><a name="section-7.5">7.5</a>. Queries and Indexes</span>
+
+ The &lt;ISINDEX&gt; element represents a set of hyperlinks. The user can
+ choose from the set by providing keywords to the user agent. The
+ user agent computes the head URI by appending `?' and the keywords to
+ the base URI. The keywords are escaped according to [<a href="#ref-URL" title='"Uniform Resource Locators (URL)"'>URL</a>] and joined
+ by `+'. For example, if a document contains:
+
+ &lt;BASE HREF="http://host/index"&gt;
+ &lt;ISINDEX&gt;
+
+ and the user provides the keywords `apple' and `berry', then the
+ user agent must access the resource
+ `http://host/index?apple+berry'.
+
+ &lt;FORM&gt; elements with `METHOD=GET' also represent sets of
+ hyperlinks. See 8.2.2, "Query Forms: METHOD=GET" for details.
+
+<span class="h3"><a name="section-7.6">7.6</a>. Image Maps</span>
+
+ If the ISMAP attribute is present on an &lt;IMG&gt; element, the &lt;IMG&gt;
+ element must be contained in an &lt;A&gt; element with an HREF present.
+ This construct represents a set of hyperlinks. The user can choose
+ from the set by choosing a pixel of the image. The user agent
+ computes the head URI by appending `?' and the x and y coordinates of
+ the pixel to the URI given in the &lt;A&gt; element. For example, if a
+ document contains:
+
+ &lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"&gt;
+ &lt;head&gt;&lt;title&gt;ImageMap Example&lt;/title&gt;
+ &lt;BASE HREF="http://host/index"&gt;&lt;/head&gt;
+ &lt;body&gt;
+ &lt;p&gt; Choose any of these icons:&lt;br&gt;
+ &lt;a href="/cgi-bin/imagemap"&gt;&lt;img ismap src="icons.gif"&gt;&lt;/a&gt;
+
+ and the user chooses the upper-leftmost pixel, the chosen
+ hyperlink is the one with the URI
+ `http://host/cgi-bin/imagemap?0,0'.
+
+
+
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 39]</span>
+<a name="page-40" id="page-40" href="#page-40" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h2"><a name="section-8">8</a>. Forms</span>
+
+ A form is a template for a form data set and an associated
+ method and action URI. A form data set is a sequence of
+ name/value pair fields. The names are specified on the NAME
+ attributes of form input elements, and the values are given
+ initial values by various forms of markup and edited by the
+ user. The resulting form data set is used to access an
+ information service as a function of the action and method.
+
+ Forms elements can be mixed in with document structuring
+ elements. For example, a &lt;PRE&gt; element may contain a &lt;FORM&gt;
+ element, or a &lt;FORM&gt; element may contain lists which contain
+ &lt;INPUT&gt; elements. This gives considerable flexibility in
+ designing the layout of forms.
+
+ Form processing is a level 2 feature.
+
+<span class="h3"><a name="section-8.1">8.1</a>. Form Elements</span>
+
+<span class="h4"><a name="section-8.1.1">8.1.1</a>. Form: FORM</span>
+
+ The &lt;FORM&gt; element contains a sequence of input elements, along
+ with document structuring elements. The attributes are:
+
+ ACTION
+ specifies the action URI for the form. The action URI of
+ a form defaults to the base URI of the document (see 7,
+ "Hyperlinks").
+
+ METHOD
+ selects a method of accessing the action URI. The set of
+ applicable methods is a function of the scheme of the
+ action URI of the form. See 8.2.2, "Query Forms:
+ METHOD=GET" and 8.2.3, "Forms with Side-Effects:
+ METHOD=POST".
+
+ ENCTYPE
+ specifies the media type used to encode the name/value
+ pairs for transport, in case the protocol does not
+ itself impose a format. See 8.2.1, "The form-urlencoded
+ Media Type".
+
+<span class="h4"><a name="section-8.1.2">8.1.2</a>. Input Field: INPUT</span>
+
+ The &lt;INPUT&gt; element represents a field for user input. The TYPE
+ attribute discriminates between several variations of fields.
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 40]</span>
+<a name="page-41" id="page-41" href="#page-41" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ The &lt;INPUT&gt; element has a number of attributes. The set of applicable
+ attributes depends on the value of the TYPE attribute.
+
+<span class="h5"><a name="section-8.1.2.1">8.1.2.1</a>. Text Field: INPUT TYPE=TEXT</span>
+
+ The default value of the TYPE attribute is `TEXT', indicating a
+ single line text entry field. (Use the &lt;TEXTAREA&gt; element for multi-
+ line text fields.)
+
+ Required attributes are:
+
+ NAME
+ name for the form field corresponding to this element.
+
+ The optional attributes are:
+
+ MAXLENGTH
+ constrains the number of characters that can be entered
+ into a text input field. If the value of MAXLENGTH is
+ greater the the value of the SIZE attribute, the field
+ should scroll appropriately. The default number of
+ characters is unlimited.
+
+ SIZE
+ specifies the amount of display space allocated to this
+ input field according to its type. The default depends
+ on the user agent.
+
+ VALUE
+ The initial value of the field.
+
+ For example:
+
+&lt;p&gt;Street Address: &lt;input name=street&gt;&lt;br&gt;
+Postal City code: &lt;input name=city size=16 maxlength=16&gt;&lt;br&gt;
+Zip Code: &lt;input name=zip size=10 maxlength=10 value="99999-9999"&gt;&lt;br&gt;
+
+<span class="h5"><a name="section-8.1.2.2">8.1.2.2</a>. Password Field: INPUT TYPE=PASSWORD</span>
+
+ An &lt;INPUT&gt; element with `TYPE=PASSWORD' is a text field as above,
+ except that the value is obscured as it is entered. (see also: 10,
+ "Security Considerations").
+
+ For example:
+
+&lt;p&gt;Name: &lt;input name=login&gt; Password: &lt;input type=password name=passwd&gt;
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 41]</span>
+<a name="page-42" id="page-42" href="#page-42" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h5"><a name="section-8.1.2.3">8.1.2.3</a>. Check Box: INPUT TYPE=CHECKBOX</span>
+
+ An &lt;INPUT&gt; element with `TYPE=CHECKBOX' represents a boolean choice.
+ A set of such elements with the same name represents an n-of-many
+ choice field. Required attributes are:
+
+ NAME
+ symbolic name for the form field corresponding to this
+ element or group of elements.
+
+ VALUE
+ The portion of the value of the field contributed by
+ this element.
+
+ Optional attributes are:
+
+ CHECKED
+ indicates that the initial state is on.
+
+ For example:
+
+ &lt;p&gt;What flavors do you like?
+ &lt;input type=checkbox name=flavor value=vanilla&gt;Vanilla&lt;br&gt;
+ &lt;input type=checkbox name=flavor value=strawberry&gt;Strawberry&lt;br&gt;
+ &lt;input type=checkbox name=flavor value=chocolate checked&gt;Chocolate&lt;br&gt;
+
+<span class="h5"><a name="section-8.1.2.4">8.1.2.4</a>. Radio Button: INPUT TYPE=RADIO</span>
+
+ An &lt;INPUT&gt; element with `TYPE=RADIO' represents a boolean choice. A
+ set of such elements with the same name represents a 1-of-many choice
+ field. The NAME and VALUE attributes are required as for check boxes.
+ Optional attributes are:
+
+ CHECKED
+ indicates that the initial state is on.
+ At all times, exactly one of the radio buttons in a set is checked.
+ If none of the &lt;INPUT&gt; elements of a set of radio buttons specifies
+ `CHECKED', then the user agent must check the first radio button of
+ the set initially.
+
+ For example:
+
+ &lt;p&gt;Which is your favorite?
+ &lt;input type=radio name=flavor value=vanilla&gt;Vanilla&lt;br&gt;
+ &lt;input type=radio name=flavor value=strawberry&gt;Strawberry&lt;br&gt;
+ &lt;input type=radio name=flavor value=chocolate&gt;Chocolate&lt;br&gt;
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 42]</span>
+<a name="page-43" id="page-43" href="#page-43" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h5"><a name="section-8.1.2.5">8.1.2.5</a>. Image Pixel: INPUT TYPE=IMAGE</span>
+
+ An &lt;INPUT&gt; element with `TYPE=IMAGE' specifies an image resource to
+ display, and allows input of two form fields: the x and y coordinate
+ of a pixel chosen from the image. The names of the fields are the
+ name of the field with `.x' and `.y' appended. `TYPE=IMAGE' implies
+ `TYPE=SUBMIT' processing; that is, when a pixel is chosen, the form
+ as a whole is submitted.
+
+ The NAME attribute is required as for other input fields. The SRC
+ attribute is required and the ALIGN is optional as for the &lt;IMG&gt;
+ element (see 5.10, "Image: IMG").
+
+ For example:
+
+ &lt;p&gt;Choose a point on the map:
+ &lt;input type=image name=point src="map.gif"&gt;
+
+<span class="h5"><a name="section-8.1.2.6">8.1.2.6</a>. Hidden Field: INPUT TYPE=HIDDEN</span>
+
+ An &lt;INPUT&gt; element with `TYPE=HIDDEN' represents a hidden field.The
+ user does not interact with this field; instead, the VALUE attribute
+ specifies the value of the field. The NAME and VALUE attributes are
+ required.
+
+ For example:
+
+ &lt;input type=hidden name=context value="l2k3j4l2k3j4l2k3j4lk23"&gt;
+
+<span class="h5"><a name="section-8.1.2.7">8.1.2.7</a>. Submit Button: INPUT TYPE=SUBMIT</span>
+
+ An &lt;INPUT&gt; element with `TYPE=SUBMIT' represents an input option,
+ typically a button, that instructs the user agent to submit the form.
+ Optional attributes are:
+
+ NAME
+ indicates that this element contributes a form field
+ whose value is given by the VALUE attribute. If the NAME
+ attribute is not present, this element does not
+ contribute a form field.
+
+ VALUE
+ indicates a label for the input (button).
+
+ You may submit this request internally:
+ &lt;input type=submit name=recipient value=internal&gt;&lt;br&gt;
+ or to the external world:
+ &lt;input type=submit name=recipient value=world&gt;
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 43]</span>
+<a name="page-44" id="page-44" href="#page-44" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h5"><a name="section-8.1.2.8">8.1.2.8</a>. Reset Button: INPUT TYPE=RESET</span>
+
+ An &lt;INPUT&gt; element with `TYPE=RESET' represents an input option,
+ typically a button, that instructs the user agent to reset the form's
+ fields to their initial states. The VALUE attribute, if present,
+ indicates a label for the input (button).
+
+ When you are finished, you may submit this request:
+ &lt;input type=submit&gt;&lt;br&gt;
+ You may clear the form and start over at any time: &lt;input type=reset&gt;
+
+<span class="h4"><a name="section-8.1.3">8.1.3</a>. Selection: SELECT</span>
+
+ The &lt;SELECT&gt; element constrains the form field to an enumerated list
+ of values. The values are given in &lt;OPTION&gt; elements. Attributes
+ are:
+
+ MULTIPLE
+ indicates that more than one option may be included in
+ the value.
+
+ NAME
+ specifies the name of the form field.
+
+ SIZE
+ specifies the number of visible items. Select fields of
+ size one are typically pop-down menus, whereas select
+ fields with size greater than one are typically lists.
+
+ For example:
+
+ &lt;SELECT NAME="flavor"&gt;
+ &lt;OPTION&gt;Vanilla
+ &lt;OPTION&gt;Strawberry
+ &lt;OPTION value="RumRasin"&gt;Rum and Raisin
+ &lt;OPTION selected&gt;Peach and Orange
+ &lt;/SELECT&gt;
+
+ The initial state has the first option selected, unless a SELECTED
+ attribute is present on any of the &lt;OPTION&gt; elements.
+
+<span class="h5"><a name="section-8.1.3.1">8.1.3.1</a>. Option: OPTION</span>
+
+ The Option element can only occur within a Select element. It
+ represents one choice, and has the following attributes:
+
+ SELECTED
+ Indicates that this option is initially selected.
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 44]</span>
+<a name="page-45" id="page-45" href="#page-45" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ VALUE
+ indicates the value to be returned if this option is
+ chosen. The field value defaults to the content of the
+ &lt;OPTION&gt; element.
+
+ The content of the &lt;OPTION&gt; element is presented to the user to
+ represent the option. It is used as a returned value if the VALUE
+ attribute is not present.
+
+<span class="h4"><a name="section-8.1.4">8.1.4</a>. Text Area: TEXTAREA</span>
+
+ The &lt;TEXTAREA&gt; element represents a multi-line text field.
+ Attributes are:
+
+ COLS
+ the number of visible columns to display for the text
+ area, in characters.
+
+ NAME
+ Specifies the name of the form field.
+
+ ROWS
+ The number of visible rows to display for the text area,
+ in characters.
+
+ For example:
+
+ &lt;TEXTAREA NAME="address" ROWS=6 COLS=64&gt;
+ HaL Computer Systems
+ 1315 Dell Avenue
+ Campbell, California 95008
+ &lt;/TEXTAREA&gt;
+
+ The content of the &lt;TEXTAREA&gt; element is the field's initial value.
+
+ Typically, the ROWS and COLS attributes determine the visible
+ dimension of the field in characters. The field is typically rendered
+ in a fixed-width font. HTML user agents should allow text to extend
+ beyond these limits by scrolling as needed.
+
+<span class="h3"><a name="section-8.2">8.2</a>. Form Submission</span>
+
+ An HTML user agent begins processing a form by presenting the
+ document with the fields in their initial state. The user is allowed
+ to modify the fields, constrained by the field type etc. When the
+ user indicates that the form should be submitted (using a submit
+ button or image input), the form data set is processed according to
+ its method, action URI and enctype.
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 45]</span>
+<a name="page-46" id="page-46" href="#page-46" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ When there is only one single-line text input field in a form, the
+ user agent should accept Enter in that field as a request to submit
+ the form.
+
+<span class="h4"><a name="section-8.2.1">8.2.1</a>. The form-urlencoded Media Type</span>
+
+ The default encoding for all forms is `application/x-www-form-
+ urlencoded'. A form data set is represented in this media type as
+ follows:
+
+ 1. The form field names and values are escaped: space
+ characters are replaced by `+', and then reserved characters
+ are escaped as per [<a href="#ref-URL" title='"Uniform Resource Locators (URL)"'>URL</a>]; that is, non-alphanumeric
+ characters are replaced by `%HH', a percent sign and two
+ hexadecimal digits representing the ASCII code of the
+ character. Line breaks, as in multi-line text field values,
+ are represented as CR LF pairs, i.e. `%0D%0A'.
+
+ 2. The fields are listed in the order they appear in the
+ document with the name separated from the value by `=' and
+ the pairs separated from each other by `&amp;'. Fields with null
+ values may be omitted. In particular, unselected radio
+ buttons and checkboxes should not appear in the encoded
+ data, but hidden fields with VALUE attributes present
+ should.
+
+ NOTE - The URI from a query form submission can be
+ used in a normal anchor style hyperlink.
+ Unfortunately, the use of the `&amp;' character to
+ separate form fields interacts with its use in SGML
+ attribute values as an entity reference delimiter.
+ For example, the URI `http://host/?x=1&amp;y=2' must be
+ written `&lt;a href="http://host/?x=1&amp;#38;y=2"' or `&lt;a
+ href="http://host/?x=1&amp;amp;y=2"&gt;'.
+
+ HTTP server implementors, and in particular, CGI
+ implementors are encouraged to support the use of
+ `;' in place of `&amp;' to save users the trouble of
+ escaping `&amp;' characters this way.
+
+<span class="h4"><a name="section-8.2.2">8.2.2</a>. Query Forms: METHOD=GET</span>
+
+ If the processing of a form is idempotent (i.e. it has no lasting
+ observable effect on the state of the world), then the form method
+ should be `GET'. Many database searches have no visible side-effects
+ and make ideal applications of query forms.
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 46]</span>
+<a name="page-47" id="page-47" href="#page-47" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ To process a form whose action URL is an HTTP URL and whose method is
+ `GET', the user agent starts with the action URI and appends a `?'
+ and the form data set, in `application/x-www-form-urlencoded' format
+ as above. The user agent then traverses the link to this URI just as
+ if it were an anchor (see 7.2, "Activation of Hyperlinks").
+
+ NOTE - The URL encoding may result in very long URIs, which cause
+ some historical HTTP server implementations to exhibit defective
+ behavior. As a result, some HTML forms are written using
+ `METHOD=POST' even though the form submission has no side-effects.
+
+<span class="h4"><a name="section-8.2.3">8.2.3</a>. Forms with Side-Effects: METHOD=POST</span>
+
+ If the service associated with the processing of a form has side
+ effects (for example, modification of a database or subscription to a
+ service), the method should be `POST'.
+
+ To process a form whose action URL is an HTTP URL and whose method is
+ `POST', the user agent conducts an HTTP POST transaction using the
+ action URI, and a message body of type `application/x-www-form-
+ urlencoded' format as above. The user agent should display the
+ response from the HTTP POST interaction just as it would display the
+ response from an HTTP GET above.
+
+<span class="h4"><a name="section-8.2.4">8.2.4</a>. Example Form Submission: Questionnaire Form</span>
+
+ Consider the following document:
+
+ &lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"&gt;
+ &lt;title&gt;Sample of HTML Form Submission&lt;/title&gt;
+ &lt;H1&gt;Sample Questionnaire&lt;/H1&gt;
+ &lt;P&gt;Please fill out this questionnaire:
+ &lt;FORM METHOD="POST" ACTION="http://www.w3.org/sample"&gt;
+ &lt;P&gt;Your name: &lt;INPUT NAME="name" size="48"&gt;
+ &lt;P&gt;Male &lt;INPUT NAME="gender" TYPE=RADIO VALUE="male"&gt;
+ &lt;P&gt;Female &lt;INPUT NAME="gender" TYPE=RADIO VALUE="female"&gt;
+ &lt;P&gt;Number in family: &lt;INPUT NAME="family" TYPE=text&gt;
+ &lt;P&gt;Cities in which you maintain a residence:
+ &lt;UL&gt;
+ &lt;LI&gt;Kent &lt;INPUT NAME="city" TYPE=checkbox VALUE="kent"&gt;
+ &lt;LI&gt;Miami &lt;INPUT NAME="city" TYPE=checkbox VALUE="miami"&gt;
+ &lt;LI&gt;Other &lt;TEXTAREA NAME="other" cols=48 rows=4&gt;&lt;/textarea&gt;
+ &lt;/UL&gt;
+ Nickname: &lt;INPUT NAME="nickname" SIZE="42"&gt;
+ &lt;P&gt;Thank you for responding to this questionnaire.
+ &lt;P&gt;&lt;INPUT TYPE=SUBMIT&gt; &lt;INPUT TYPE=RESET&gt;
+ &lt;/FORM&gt;
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 47]</span>
+<a name="page-48" id="page-48" href="#page-48" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ The initial state of the form data set is:
+
+ name
+ ""
+
+ gender
+ "male"
+
+ family
+ ""
+
+ other
+ ""
+
+ nickname
+ ""
+
+ Note that the radio input has an initial value, while the
+ checkbox has none.
+
+ The user might edit the fields and request that the form be
+ submitted. At that point, suppose the values are:
+
+ name
+ "John Doe"
+
+ gender
+ "male"
+
+ family
+ "5"
+
+ city
+ "kent"
+
+ city
+ "miami"
+
+ other
+ "abc\ndefk"
+
+ nickname
+ "J&amp;D"
+
+ The user agent then conducts an HTTP POST transaction using the URI
+ `http://www.w3.org/sample'. The message body would be (ignore the
+ line break):
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 48]</span>
+<a name="page-49" id="page-49" href="#page-49" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ name=John+Doe&amp;gender=male&amp;family=5&amp;city=kent&amp;city=miami&amp;
+ other=abc%0D%0Adef&amp;nickname=J%26D
+
+<span class="h2"><a name="section-9">9</a>. HTML Public Text</span>
+
+<span class="h3"><a name="section-9.1">9.1</a>. HTML DTD</span>
+
+ This is the Document Type Definition for the HyperText Markup
+ Language, level 2.
+
+&lt;!-- html.dtd
+
+ Document Type Definition for the HyperText Markup Language
+ (HTML DTD)
+
+ $Id: html.dtd,v 1.30 1995/09/21 23:30:19 connolly Exp $
+
+ Author: Daniel W. Connolly &lt;connolly@w3.org&gt;
+ See Also: html.decl, html-1.dtd
+ <a href="http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html">http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html</a>
+--&gt;
+
+&lt;!ENTITY % HTML.Version
+ "-//IETF//DTD HTML 2.0//EN"
+
+ -- Typical usage:
+
+ &lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"&gt;
+ &lt;html&gt;
+ ...
+ &lt;/html&gt;
+ --
+ &gt;
+
+
+&lt;!--============ Feature Test Entities ========================--&gt;
+
+&lt;!ENTITY % HTML.Recommended "IGNORE"
+ -- Certain features of the language are necessary for
+ compatibility with widespread usage, but they may
+ compromise the structural integrity of a document.
+ This feature test entity enables a more prescriptive
+ document type definition that eliminates
+ those features.
+ --&gt;
+
+&lt;![ %HTML.Recommended [
+ &lt;!ENTITY % HTML.Deprecated "IGNORE"&gt;
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 49]</span>
+<a name="page-50" id="page-50" href="#page-50" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+]]&gt;
+
+&lt;!ENTITY % HTML.Deprecated "INCLUDE"
+ -- Certain features of the language are necessary for
+ compatibility with earlier versions of the specification,
+ but they tend to be used and implemented inconsistently,
+ and their use is deprecated. This feature test entity
+ enables a document type definition that eliminates
+ these features.
+ --&gt;
+
+&lt;!ENTITY % HTML.Highlighting "INCLUDE"
+ -- Use this feature test entity to validate that a
+ document uses no highlighting tags, which may be
+ ignored on minimal implementations.
+ --&gt;
+
+&lt;!ENTITY % HTML.Forms "INCLUDE"
+ -- Use this feature test entity to validate that a document
+ contains no forms, which may not be supported in minimal
+ implementations
+ --&gt;
+
+&lt;!--============== Imported Names ==============================--&gt;
+
+&lt;!ENTITY % Content-Type "CDATA"
+ -- meaning an internet media type
+ (aka MIME content type, as per <a href="./rfc1521">RFC1521</a>)
+ --&gt;
+
+&lt;!ENTITY % HTTP-Method "GET | POST"
+ -- as per HTTP specification, in progress
+ --&gt;
+
+&lt;!--========= DTD "Macros" =====================--&gt;
+
+&lt;!ENTITY % heading "H1|H2|H3|H4|H5|H6"&gt;
+
+&lt;!ENTITY % list " UL | OL | DIR | MENU " &gt;
+
+
+&lt;!--======= Character mnemonic entities =================--&gt;
+
+&lt;!ENTITY % ISOlat1 PUBLIC
+ "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML"&gt;
+%ISOlat1;
+
+&lt;!ENTITY amp CDATA "&amp;#38;" -- ampersand --&gt;
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 50]</span>
+<a name="page-51" id="page-51" href="#page-51" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+&lt;!ENTITY gt CDATA "&amp;#62;" -- greater than --&gt;
+&lt;!ENTITY lt CDATA "&amp;#60;" -- less than --&gt;
+&lt;!ENTITY quot CDATA "&amp;#34;" -- double quote --&gt;
+
+
+&lt;!--========= SGML Document Access (SDA) Parameter Entities =====--&gt;
+
+&lt;!-- HTML 2.0 contains SGML Document Access (SDA) fixed attributes
+in support of easy transformation to the International Committee
+for Accessible Document Design (ICADD) DTD
+ "-//EC-USA-CDA/ICADD//DTD ICADD22//EN".
+<span class="h1"><a name="appendix-ICADD">ICADD</a> applications are designed to support usable access to</span>
+structured information by print-impaired individuals through
+Braille, large print and voice synthesis. For more information on
+<span class="h1"><a name="appendix-SDA">SDA</a> &amp; ICADD:</span>
+ - ISO 12083:1993, Annex A.8, Facilities for Braille,
+ large print and computer voice
+ - ICADD ListServ
+ &lt;ICADD%ASUACAD.BITNET@ARIZVM1.ccit.arizona.edu&gt;
+ - Usenet news group bit.listserv.easi
+ - Recording for the Blind, +1 800 221 4792
+--&gt;
+
+&lt;!ENTITY % SDAFORM "SDAFORM CDATA #FIXED"
+ -- one to one mapping --&gt;
+&lt;!ENTITY % SDARULE "SDARULE CDATA #FIXED"
+ -- context-sensitive mapping --&gt;
+&lt;!ENTITY % SDAPREF "SDAPREF CDATA #FIXED"
+ -- generated text prefix --&gt;
+&lt;!ENTITY % SDASUFF "SDASUFF CDATA #FIXED"
+ -- generated text suffix --&gt;
+&lt;!ENTITY % SDASUSP "SDASUSP NAME #FIXED"
+ -- suspend transform process --&gt;
+
+
+&lt;!--========== Text Markup =====================--&gt;
+
+&lt;![ %HTML.Highlighting [
+
+&lt;!ENTITY % font " TT | B | I "&gt;
+
+&lt;!ENTITY % phrase "EM | STRONG | CODE | SAMP | KBD | VAR | CITE "&gt;
+
+&lt;!ENTITY % text "#PCDATA | A | IMG | BR | %phrase | %font"&gt;
+
+&lt;!ELEMENT (%font;|%phrase) - - (%text)*&gt;
+&lt;!ATTLIST ( TT | CODE | SAMP | KBD | VAR )
+ %SDAFORM; "Lit"
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 51]</span>
+<a name="page-52" id="page-52" href="#page-52" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ &gt;
+&lt;!ATTLIST ( B | STRONG )
+ %SDAFORM; "B"
+ &gt;
+&lt;!ATTLIST ( I | EM | CITE )
+ %SDAFORM; "It"
+ &gt;
+
+&lt;!-- &lt;TT&gt; Typewriter text --&gt;
+&lt;!-- &lt;B&gt; Bold text --&gt;
+&lt;!-- &lt;I&gt; Italic text --&gt;
+
+&lt;!-- &lt;EM&gt; Emphasized phrase --&gt;
+&lt;!-- &lt;STRONG&gt; Strong emphasis --&gt;
+&lt;!-- &lt;CODE&gt; Source code phrase --&gt;
+&lt;!-- &lt;SAMP&gt; Sample text or characters --&gt;
+&lt;!-- &lt;KBD&gt; Keyboard phrase, e.g. user input --&gt;
+&lt;!-- &lt;VAR&gt; Variable phrase or substitutable --&gt;
+&lt;!-- &lt;CITE&gt; Name or title of cited work --&gt;
+
+&lt;!ENTITY % pre.content "#PCDATA | A | HR | BR | %font | %phrase"&gt;
+
+]]&gt;
+
+&lt;!ENTITY % text "#PCDATA | A | IMG | BR"&gt;
+
+&lt;!ELEMENT BR - O EMPTY&gt;
+&lt;!ATTLIST BR
+ %SDAPREF; "&amp;#RE;"
+ &gt;
+
+&lt;!-- &lt;BR&gt; Line break --&gt;
+
+
+&lt;!--========= Link Markup ======================--&gt;
+
+&lt;!ENTITY % linkType "NAMES"&gt;
+
+&lt;!ENTITY % linkExtraAttributes
+ "REL %linkType #IMPLIED
+ REV %linkType #IMPLIED
+ URN CDATA #IMPLIED
+ TITLE CDATA #IMPLIED
+ METHODS NAMES #IMPLIED
+ "&gt;
+
+&lt;![ %HTML.Recommended [
+ &lt;!ENTITY % A.content "(%text)*"
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 52]</span>
+<a name="page-53" id="page-53" href="#page-53" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ -- &lt;H1&gt;&lt;a name="xxx"&gt;Heading&lt;/a&gt;&lt;/H1&gt;
+ is preferred to
+ &lt;a name="xxx"&gt;&lt;H1&gt;Heading&lt;/H1&gt;&lt;/a&gt;
+ --&gt;
+]]&gt;
+
+&lt;!ENTITY % A.content "(%heading|%text)*"&gt;
+
+&lt;!ELEMENT A - - %A.content -(A)&gt;
+&lt;!ATTLIST A
+ HREF CDATA #IMPLIED
+ NAME CDATA #IMPLIED
+ %linkExtraAttributes;
+ %SDAPREF; "&lt;Anchor: #AttList&gt;"
+ &gt;
+&lt;!-- &lt;A&gt; Anchor; source/destination of link --&gt;
+&lt;!-- &lt;A NAME="..."&gt; Name of this anchor --&gt;
+&lt;!-- &lt;A HREF="..."&gt; Address of link destination --&gt;
+&lt;!-- &lt;A URN="..."&gt; Permanent address of destination --&gt;
+&lt;!-- &lt;A REL=...&gt; Relationship to destination --&gt;
+&lt;!-- &lt;A REV=...&gt; Relationship of destination to this --&gt;
+&lt;!-- &lt;A TITLE="..."&gt; Title of destination (advisory) --&gt;
+&lt;!-- &lt;A METHODS="..."&gt; Operations on destination (advisory) --&gt;
+
+
+&lt;!--========== Images ==========================--&gt;
+
+&lt;!ELEMENT IMG - O EMPTY&gt;
+&lt;!ATTLIST IMG
+ SRC CDATA #REQUIRED
+ ALT CDATA #IMPLIED
+ ALIGN (top|middle|bottom) #IMPLIED
+ ISMAP (ISMAP) #IMPLIED
+ %SDAPREF; "&lt;Fig&gt;&lt;?SDATrans Img: #AttList&gt;#AttVal(Alt)&lt;/Fig&gt;"
+ &gt;
+
+&lt;!-- &lt;IMG&gt; Image; icon, glyph or illustration --&gt;
+&lt;!-- &lt;IMG SRC="..."&gt; Address of image object --&gt;
+&lt;!-- &lt;IMG ALT="..."&gt; Textual alternative --&gt;
+&lt;!-- &lt;IMG ALIGN=...&gt; Position relative to text --&gt;
+&lt;!-- &lt;IMG ISMAP&gt; Each pixel can be a link --&gt;
+
+&lt;!--========== Paragraphs=======================--&gt;
+
+&lt;!ELEMENT P - O (%text)*&gt;
+&lt;!ATTLIST P
+ %SDAFORM; "Para"
+ &gt;
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 53]</span>
+<a name="page-54" id="page-54" href="#page-54" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+&lt;!-- &lt;P&gt; Paragraph --&gt;
+
+
+&lt;!--========== Headings, Titles, Sections ===============--&gt;
+
+&lt;!ELEMENT HR - O EMPTY&gt;
+&lt;!ATTLIST HR
+ %SDAPREF; "&amp;#RE;&amp;#RE;"
+ &gt;
+
+&lt;!-- &lt;HR&gt; Horizontal rule --&gt;
+
+&lt;!ELEMENT ( %heading ) - - (%text;)*&gt;
+&lt;!ATTLIST H1
+ %SDAFORM; "H1"
+ &gt;
+&lt;!ATTLIST H2
+ %SDAFORM; "H2"
+ &gt;
+&lt;!ATTLIST H3
+ %SDAFORM; "H3"
+ &gt;
+&lt;!ATTLIST H4
+ %SDAFORM; "H4"
+ &gt;
+&lt;!ATTLIST H5
+ %SDAFORM; "H5"
+ &gt;
+&lt;!ATTLIST H6
+ %SDAFORM; "H6"
+ &gt;
+
+&lt;!-- &lt;H1&gt; Heading, level 1 --&gt;
+&lt;!-- &lt;H2&gt; Heading, level 2 --&gt;
+&lt;!-- &lt;H3&gt; Heading, level 3 --&gt;
+&lt;!-- &lt;H4&gt; Heading, level 4 --&gt;
+&lt;!-- &lt;H5&gt; Heading, level 5 --&gt;
+&lt;!-- &lt;H6&gt; Heading, level 6 --&gt;
+
+
+&lt;!--========== Text Flows ======================--&gt;
+
+&lt;![ %HTML.Forms [
+ &lt;!ENTITY % block.forms "BLOCKQUOTE | FORM | ISINDEX"&gt;
+]]&gt;
+
+&lt;!ENTITY % block.forms "BLOCKQUOTE"&gt;
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 54]</span>
+<a name="page-55" id="page-55" href="#page-55" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+&lt;![ %HTML.Deprecated [
+ &lt;!ENTITY % preformatted "PRE | XMP | LISTING"&gt;
+]]&gt;
+
+&lt;!ENTITY % preformatted "PRE"&gt;
+
+&lt;!ENTITY % block "P | %list | DL
+ | %preformatted
+ | %block.forms"&gt;
+
+&lt;!ENTITY % flow "(%text|%block)*"&gt;
+
+&lt;!ENTITY % pre.content "#PCDATA | A | HR | BR"&gt;
+&lt;!ELEMENT PRE - - (%pre.content)*&gt;
+&lt;!ATTLIST PRE
+ WIDTH NUMBER #implied
+ %SDAFORM; "Lit"
+ &gt;
+
+&lt;!-- &lt;PRE&gt; Preformatted text --&gt;
+&lt;!-- &lt;PRE WIDTH=...&gt; Maximum characters per line --&gt;
+
+&lt;![ %HTML.Deprecated [
+
+&lt;!ENTITY % literal "CDATA"
+ -- historical, non-conforming parsing mode where
+ the only markup signal is the end tag
+ in full
+ --&gt;
+
+&lt;!ELEMENT (XMP|LISTING) - - %literal&gt;
+&lt;!ATTLIST XMP
+ %SDAFORM; "Lit"
+ %SDAPREF; "Example:&amp;#RE;"
+ &gt;
+&lt;!ATTLIST LISTING
+ %SDAFORM; "Lit"
+ %SDAPREF; "Listing:&amp;#RE;"
+ &gt;
+
+&lt;!-- &lt;XMP&gt; Example section --&gt;
+&lt;!-- &lt;LISTING&gt; Computer listing --&gt;
+
+&lt;!ELEMENT PLAINTEXT - O %literal&gt;
+&lt;!-- &lt;PLAINTEXT&gt; Plain text passage --&gt;
+
+&lt;!ATTLIST PLAINTEXT
+ %SDAFORM; "Lit"
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 55]</span>
+<a name="page-56" id="page-56" href="#page-56" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ &gt;
+]]&gt;
+
+&lt;!--========== Lists ==================--&gt;
+
+&lt;!ELEMENT DL - - (DT | DD)+&gt;
+&lt;!ATTLIST DL
+ COMPACT (COMPACT) #IMPLIED
+ %SDAFORM; "List"
+ %SDAPREF; "Definition List:"
+ &gt;
+
+&lt;!ELEMENT DT - O (%text)*&gt;
+&lt;!ATTLIST DT
+ %SDAFORM; "Term"
+ &gt;
+
+&lt;!ELEMENT DD - O %flow&gt;
+&lt;!ATTLIST DD
+ %SDAFORM; "LItem"
+ &gt;
+
+&lt;!-- &lt;DL&gt; Definition list, or glossary --&gt;
+&lt;!-- &lt;DL COMPACT&gt; Compact style list --&gt;
+&lt;!-- &lt;DT&gt; Term in definition list --&gt;
+&lt;!-- &lt;DD&gt; Definition of term --&gt;
+
+&lt;!ELEMENT (OL|UL) - - (LI)+&gt;
+&lt;!ATTLIST OL
+ COMPACT (COMPACT) #IMPLIED
+ %SDAFORM; "List"
+ &gt;
+&lt;!ATTLIST UL
+ COMPACT (COMPACT) #IMPLIED
+ %SDAFORM; "List"
+ &gt;
+&lt;!-- &lt;UL&gt; Unordered list --&gt;
+&lt;!-- &lt;UL COMPACT&gt; Compact list style --&gt;
+&lt;!-- &lt;OL&gt; Ordered, or numbered list --&gt;
+&lt;!-- &lt;OL COMPACT&gt; Compact list style --&gt;
+
+
+&lt;!ELEMENT (DIR|MENU) - - (LI)+ -(%block)&gt;
+&lt;!ATTLIST DIR
+ COMPACT (COMPACT) #IMPLIED
+ %SDAFORM; "List"
+ %SDAPREF; "&lt;LHead&gt;Directory&lt;/LHead&gt;"
+ &gt;
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 56]</span>
+<a name="page-57" id="page-57" href="#page-57" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+&lt;!ATTLIST MENU
+ COMPACT (COMPACT) #IMPLIED
+ %SDAFORM; "List"
+ %SDAPREF; "&lt;LHead&gt;Menu&lt;/LHead&gt;"
+ &gt;
+
+&lt;!-- &lt;DIR&gt; Directory list --&gt;
+&lt;!-- &lt;DIR COMPACT&gt; Compact list style --&gt;
+&lt;!-- &lt;MENU&gt; Menu list --&gt;
+&lt;!-- &lt;MENU COMPACT&gt; Compact list style --&gt;
+
+&lt;!ELEMENT LI - O %flow&gt;
+&lt;!ATTLIST LI
+ %SDAFORM; "LItem"
+ &gt;
+
+&lt;!-- &lt;LI&gt; List item --&gt;
+
+&lt;!--========== Document Body ===================--&gt;
+
+&lt;![ %HTML.Recommended [
+ &lt;!ENTITY % body.content "(%heading|%block|HR|ADDRESS|IMG)*"
+ -- &lt;h1&gt;Heading&lt;/h1&gt;
+ &lt;p&gt;Text ...
+ is preferred to
+ &lt;h1&gt;Heading&lt;/h1&gt;
+ Text ...
+ --&gt;
+]]&gt;
+
+&lt;!ENTITY % body.content "(%heading | %text | %block |
+ HR | ADDRESS)*"&gt;
+
+&lt;!ELEMENT BODY O O %body.content&gt;
+
+&lt;!-- &lt;BODY&gt; Document body --&gt;
+
+&lt;!ELEMENT BLOCKQUOTE - - %body.content&gt;
+&lt;!ATTLIST BLOCKQUOTE
+ %SDAFORM; "BQ"
+ &gt;
+
+&lt;!-- &lt;BLOCKQUOTE&gt; Quoted passage --&gt;
+
+&lt;!ELEMENT ADDRESS - - (%text|P)*&gt;
+&lt;!ATTLIST ADDRESS
+ %SDAFORM; "Lit"
+ %SDAPREF; "Address:&amp;#RE;"
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 57]</span>
+<a name="page-58" id="page-58" href="#page-58" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ &gt;
+
+&lt;!-- &lt;ADDRESS&gt; Address, signature, or byline --&gt;
+
+
+&lt;!--======= Forms ====================--&gt;
+
+&lt;![ %HTML.Forms [
+
+&lt;!ELEMENT FORM - - %body.content -(FORM) +(INPUT|SELECT|TEXTAREA)&gt;
+&lt;!ATTLIST FORM
+ ACTION CDATA #IMPLIED
+ METHOD (%HTTP-Method) GET
+ ENCTYPE %Content-Type; "application/x-www-form-urlencoded"
+ %SDAPREF; "&lt;Para&gt;Form:&lt;/Para&gt;"
+ %SDASUFF; "&lt;Para&gt;Form End.&lt;/Para&gt;"
+ &gt;
+
+&lt;!-- &lt;FORM&gt; Fill-out or data-entry form --&gt;
+&lt;!-- &lt;FORM ACTION="..."&gt; Address for completed form --&gt;
+&lt;!-- &lt;FORM METHOD=...&gt; Method of submitting form --&gt;
+&lt;!-- &lt;FORM ENCTYPE="..."&gt; Representation of form data --&gt;
+
+&lt;!ENTITY % InputType "(TEXT | PASSWORD | CHECKBOX |
+ RADIO | SUBMIT | RESET |
+ IMAGE | HIDDEN )"&gt;
+&lt;!ELEMENT INPUT - O EMPTY&gt;
+&lt;!ATTLIST INPUT
+ TYPE %InputType TEXT
+ NAME CDATA #IMPLIED
+ VALUE CDATA #IMPLIED
+ SRC CDATA #IMPLIED
+ CHECKED (CHECKED) #IMPLIED
+ SIZE CDATA #IMPLIED
+ MAXLENGTH NUMBER #IMPLIED
+ ALIGN (top|middle|bottom) #IMPLIED
+ %SDAPREF; "Input: "
+ &gt;
+
+&lt;!-- &lt;INPUT&gt; Form input datum --&gt;
+&lt;!-- &lt;INPUT TYPE=...&gt; Type of input interaction --&gt;
+&lt;!-- &lt;INPUT NAME=...&gt; Name of form datum --&gt;
+&lt;!-- &lt;INPUT VALUE="..."&gt; Default/initial/selected value --&gt;
+&lt;!-- &lt;INPUT SRC="..."&gt; Address of image --&gt;
+&lt;!-- &lt;INPUT CHECKED&gt; Initial state is "on" --&gt;
+&lt;!-- &lt;INPUT SIZE=...&gt; Field size hint --&gt;
+&lt;!-- &lt;INPUT MAXLENGTH=...&gt; Data length maximum --&gt;
+&lt;!-- &lt;INPUT ALIGN=...&gt; Image alignment --&gt;
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 58]</span>
+<a name="page-59" id="page-59" href="#page-59" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+&lt;!ELEMENT SELECT - - (OPTION+) -(INPUT|SELECT|TEXTAREA)&gt;
+&lt;!ATTLIST SELECT
+ NAME CDATA #REQUIRED
+ SIZE NUMBER #IMPLIED
+ MULTIPLE (MULTIPLE) #IMPLIED
+ %SDAFORM; "List"
+ %SDAPREF;
+ "&lt;LHead&gt;Select #AttVal(Multiple)&lt;/LHead&gt;"
+ &gt;
+
+&lt;!-- &lt;SELECT&gt; Selection of option(s) --&gt;
+&lt;!-- &lt;SELECT NAME=...&gt; Name of form datum --&gt;
+&lt;!-- &lt;SELECT SIZE=...&gt; Options displayed at a time --&gt;
+&lt;!-- &lt;SELECT MULTIPLE&gt; Multiple selections allowed --&gt;
+
+&lt;!ELEMENT OPTION - O (#PCDATA)*&gt;
+&lt;!ATTLIST OPTION
+ SELECTED (SELECTED) #IMPLIED
+ VALUE CDATA #IMPLIED
+ %SDAFORM; "LItem"
+ %SDAPREF;
+ "Option: #AttVal(Value) #AttVal(Selected)"
+ &gt;
+
+&lt;!-- &lt;OPTION&gt; A selection option --&gt;
+&lt;!-- &lt;OPTION SELECTED&gt; Initial state --&gt;
+&lt;!-- &lt;OPTION VALUE="..."&gt; Form datum value for this option--&gt;
+
+&lt;!ELEMENT TEXTAREA - - (#PCDATA)* -(INPUT|SELECT|TEXTAREA)&gt;
+&lt;!ATTLIST TEXTAREA
+ NAME CDATA #REQUIRED
+ ROWS NUMBER #REQUIRED
+ COLS NUMBER #REQUIRED
+ %SDAFORM; "Para"
+ %SDAPREF; "Input Text -- #AttVal(Name): "
+ &gt;
+
+&lt;!-- &lt;TEXTAREA&gt; An area for text input --&gt;
+&lt;!-- &lt;TEXTAREA NAME=...&gt; Name of form datum --&gt;
+&lt;!-- &lt;TEXTAREA ROWS=...&gt; Height of area --&gt;
+&lt;!-- &lt;TEXTAREA COLS=...&gt; Width of area --&gt;
+
+]]&gt;
+
+
+&lt;!--======= Document Head ======================--&gt;
+
+&lt;![ %HTML.Recommended [
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 59]</span>
+<a name="page-60" id="page-60" href="#page-60" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ &lt;!ENTITY % head.extra ""&gt;
+]]&gt;
+&lt;!ENTITY % head.extra "&amp; NEXTID?"&gt;
+
+&lt;!ENTITY % head.content "TITLE &amp; ISINDEX? &amp; BASE? %head.extra"&gt;
+
+&lt;!ELEMENT HEAD O O (%head.content) +(META|LINK)&gt;
+
+&lt;!-- &lt;HEAD&gt; Document head --&gt;
+
+&lt;!ELEMENT TITLE - - (#PCDATA)* -(META|LINK)&gt;
+&lt;!ATTLIST TITLE
+ %SDAFORM; "Ti" &gt;
+
+&lt;!-- &lt;TITLE&gt; Title of document --&gt;
+
+&lt;!ELEMENT LINK - O EMPTY&gt;
+&lt;!ATTLIST LINK
+ HREF CDATA #REQUIRED
+ %linkExtraAttributes;
+ %SDAPREF; "Linked to : #AttVal (TITLE) (URN) (HREF)&gt;" &gt;
+
+&lt;!-- &lt;LINK&gt; Link from this document --&gt;
+&lt;!-- &lt;LINK HREF="..."&gt; Address of link destination --&gt;
+&lt;!-- &lt;LINK URN="..."&gt; Lasting name of destination --&gt;
+&lt;!-- &lt;LINK REL=...&gt; Relationship to destination --&gt;
+&lt;!-- &lt;LINK REV=...&gt; Relationship of destination to this --&gt;
+&lt;!-- &lt;LINK TITLE="..."&gt; Title of destination (advisory) --&gt;
+&lt;!-- &lt;LINK METHODS="..."&gt; Operations allowed (advisory) --&gt;
+
+&lt;!ELEMENT ISINDEX - O EMPTY&gt;
+&lt;!ATTLIST ISINDEX
+ %SDAPREF;
+ "&lt;Para&gt;[Document is indexed/searchable.]&lt;/Para&gt;"&gt;
+
+&lt;!-- &lt;ISINDEX&gt; Document is a searchable index --&gt;
+
+&lt;!ELEMENT BASE - O EMPTY&gt;
+&lt;!ATTLIST BASE
+ HREF CDATA #REQUIRED &gt;
+
+&lt;!-- &lt;BASE&gt; Base context document --&gt;
+&lt;!-- &lt;BASE HREF="..."&gt; Address for this document --&gt;
+
+&lt;!ELEMENT NEXTID - O EMPTY&gt;
+&lt;!ATTLIST NEXTID
+ N CDATA #REQUIRED &gt;
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 60]</span>
+<a name="page-61" id="page-61" href="#page-61" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+&lt;!-- &lt;NEXTID&gt; Next ID to use for link name --&gt;
+&lt;!-- &lt;NEXTID N=...&gt; Next ID to use for link name --&gt;
+
+&lt;!ELEMENT META - O EMPTY&gt;
+&lt;!ATTLIST META
+ HTTP-EQUIV NAME #IMPLIED
+ NAME NAME #IMPLIED
+ CONTENT CDATA #REQUIRED &gt;
+
+&lt;!-- &lt;META&gt; Generic Meta-information --&gt;
+&lt;!-- &lt;META HTTP-EQUIV=...&gt; HTTP response header name --&gt;
+&lt;!-- &lt;META NAME=...&gt; Meta-information name --&gt;
+&lt;!-- &lt;META CONTENT="..."&gt; Associated information --&gt;
+
+&lt;!--======= Document Structure =================--&gt;
+
+&lt;![ %HTML.Deprecated [
+ &lt;!ENTITY % html.content "HEAD, BODY, PLAINTEXT?"&gt;
+]]&gt;
+&lt;!ENTITY % html.content "HEAD, BODY"&gt;
+
+&lt;!ELEMENT HTML O O (%html.content)&gt;
+&lt;!ENTITY % version.attr "VERSION CDATA #FIXED '%HTML.Version;'"&gt;
+
+&lt;!ATTLIST HTML
+ %version.attr;
+ %SDAFORM; "Book"
+ &gt;
+
+&lt;!-- &lt;HTML&gt; HTML Document --&gt;
+
+<span class="h3"><a name="section-9.2">9.2</a>. Strict HTML DTD</span>
+
+ This document type declaration refers to the HTML DTD with the
+ `HTML.Recommended' entity defined as `INCLUDE' rather than IGNORE;
+ that is, it refers to the more structurally rigid definition of HTML.
+
+&lt;!-- html-s.dtd
+
+ Document Type Definition for the HyperText Markup Language
+ with strict validation (HTML Strict DTD).
+
+ $Id: html-s.dtd,v 1.3 1995/06/02 18:55:46 connolly Exp $
+
+ Author: Daniel W. Connolly &lt;connolly@w3.org&gt;
+ See Also: <a href="http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html">http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html</a>
+--&gt;
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 61]</span>
+<a name="page-62" id="page-62" href="#page-62" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+&lt;!ENTITY % HTML.Version
+ "-//IETF//DTD HTML 2.0 Strict//EN"
+
+ -- Typical usage:
+
+ &lt;!DOCTYPE HTML PUBLIC
+ "-//IETF//DTD HTML Strict//EN"&gt;
+ &lt;html&gt;
+ ...
+ &lt;/html&gt;
+ --
+ &gt;
+
+&lt;!-- Feature Test Entities --&gt;
+&lt;!ENTITY % HTML.Recommended "INCLUDE"&gt;
+
+&lt;!ENTITY % html PUBLIC "-//IETF//DTD HTML 2.0//EN"&gt;
+%html;
+
+<span class="h3"><a name="section-9.3">9.3</a>. Level 1 HTML DTD</span>
+
+ This document type declaration refers to the HTML DTD with the
+ `HTML.Forms' entity defined as `IGNORE' rather than `INCLUDE'.
+ Documents which contain &lt;FORM&gt; elements do not conform to this DTD,
+ and must use the level 2 DTD.
+
+&lt;!-- html-1.dtd
+
+ Document Type Definition for the HyperText Markup Language
+ with Level 1 Extensions (HTML Level 1 DTD).
+
+ $Id: html-1.dtd,v 1.2 1995/03/29 18:53:10 connolly Exp $
+
+ Author: Daniel W. Connolly &lt;connolly@w3.org&gt;
+ See Also: <a href="http://info.cern.ch/hypertext/WWW/MarkUp/MarkUp.html">http://info.cern.ch/hypertext/WWW/MarkUp/MarkUp.html</a>
+
+--&gt;
+
+&lt;!ENTITY % HTML.Version
+ "-//IETF//DTD HTML 2.0 Level 1//EN"
+
+ -- Typical usage:
+
+ &lt;!DOCTYPE HTML PUBLIC
+ "-//IETF//DTD HTML Level 1//EN"&gt;
+ &lt;html&gt;
+ ...
+ &lt;/html&gt;
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 62]</span>
+<a name="page-63" id="page-63" href="#page-63" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ --
+ &gt;
+
+&lt;!-- Feature Test Entities --&gt;
+&lt;!ENTITY % HTML.Forms "IGNORE"&gt;
+
+&lt;!ENTITY % html PUBLIC "-//IETF//DTD HTML 2.0//EN"&gt;
+%html;
+
+<span class="h3"><a name="section-9.4">9.4</a>. Strict Level 1 HTML DTD</span>
+
+ This document type declaration refers to the level 1 HTML DTD with
+ the `HTML.Recommended' entity defined as `INCLUDE' rather than
+ IGNORE; that is, it refers to the more structurally rigid definition
+ of HTML.
+
+&lt;!-- html-1s.dtd
+
+ Document Type Definition for the HyperText Markup Language
+ Struct Level 1
+
+ $Id: html-1s.dtd,v 1.3 1995/06/02 18:55:43 connolly Exp $
+
+ Author: Daniel W. Connolly &lt;connolly@w3.org&gt;
+ See Also: <a href="http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html">http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html</a>
+--&gt;
+
+&lt;!ENTITY % HTML.Version
+ "-//IETF//DTD HTML 2.0 Strict Level 1//EN"
+
+ -- Typical usage:
+
+ &lt;!DOCTYPE HTML PUBLIC
+ "-//IETF//DTD HTML Strict Level 1//EN"&gt;
+ &lt;html&gt;
+ ...
+ &lt;/html&gt;
+ --
+ &gt;
+
+&lt;!-- Feature Test Entities --&gt;
+
+
+&lt;!ENTITY % HTML.Recommended "INCLUDE"&gt;
+
+&lt;!ENTITY % html-1 PUBLIC "-//IETF//DTD HTML 2.0 Level 1//EN"&gt;
+%html-1;
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 63]</span>
+<a name="page-64" id="page-64" href="#page-64" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h3"><a name="section-9.5">9.5</a>. SGML Declaration for HTML</span>
+
+ This is the SGML Declaration for HyperText Markup Language.
+
+&lt;!SGML "ISO 8879:1986"
+--
+ SGML Declaration for HyperText Markup Language (HTML).
+
+--
+
+CHARSET
+ BASESET "ISO 646:1983//CHARSET
+ International Reference Version
+ (IRV)//ESC 2/5 4/0"
+ DESCSET 0 9 UNUSED
+ 9 2 9
+ 11 2 UNUSED
+ 13 1 13
+ 14 18 UNUSED
+ 32 95 32
+ 127 1 UNUSED
+ BASESET "ISO Registration Number 100//CHARSET
+ ECMA-94 Right Part of
+ Latin Alphabet Nr. 1//ESC 2/13 4/1"
+
+ DESCSET 128 32 UNUSED
+ 160 96 32
+
+<span class="h1"><a name="appendix-CAPACITY">CAPACITY</a> SGMLREF</span>
+ TOTALCAP 150000
+ GRPCAP 150000
+ ENTCAP 150000
+
+<span class="h1"><a name="appendix-SCOPE">SCOPE</a> DOCUMENT</span>
+SYNTAX
+ SHUNCHAR CONTROLS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
+ 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 127
+ BASESET "ISO 646:1983//CHARSET
+ International Reference Version
+ (IRV)//ESC 2/5 4/0"
+ DESCSET 0 128 0
+ FUNCTION
+ RE 13
+ RS 10
+ SPACE 32
+ TAB SEPCHAR 9
+ NAMING LCNMSTRT ""
+ UCNMSTRT ""
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 64]</span>
+<a name="page-65" id="page-65" href="#page-65" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ LCNMCHAR ".-"
+ UCNMCHAR ".-"
+ NAMECASE GENERAL YES
+ ENTITY NO
+ DELIM GENERAL SGMLREF
+ SHORTREF SGMLREF
+ NAMES SGMLREF
+ QUANTITY SGMLREF
+ ATTSPLEN 2100
+ LITLEN 1024
+ NAMELEN 72 -- somewhat arbitrary; taken from
+ internet line length conventions --
+ PILEN 1024
+ TAGLVL 100
+ TAGLEN 2100
+ GRPGTCNT 150
+ GRPCNT 64
+
+FEATURES
+ MINIMIZE
+ DATATAG NO
+ OMITTAG YES
+ RANK NO
+ SHORTTAG YES
+ LINK
+ SIMPLE NO
+ IMPLICIT NO
+ EXPLICIT NO
+ OTHER
+ CONCUR NO
+ SUBDOC NO
+ FORMAL YES
+ APPINFO "SDA" -- conforming SGML Document Access application
+ --
+&gt;
+&lt;!--
+ $Id: html.decl,v 1.17 1995/06/08 14:59:32 connolly Exp $
+
+ Author: Daniel W. Connolly &lt;connolly@w3.org&gt;
+
+ See also: <a href="http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html">http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html</a>
+ --&gt;
+
+<span class="h3"><a name="section-9.6">9.6</a>. Sample SGML Open Entity Catalog for HTML</span>
+
+ The SGML standard describes an "entity manager" as the portion or
+ component of an SGML system that maps SGML entities into the actual
+ storage model (e.g., the file system). The standard itself does not
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 65]</span>
+<a name="page-66" id="page-66" href="#page-66" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ define a particular mapping methodology or notation.
+
+ To assist the interoperability among various SGML tools and systems,
+ the SGML Open consortium has passed a technical resolution that
+ defines a format for an application-independent entity catalog that
+ maps external identifiers and/or entity names to file names.
+
+ Each entry in the catalog associates a storage object identifier
+ (such as a file name) with information about the external entity that
+ appears in the SGML document. In addition to entries that associate
+ public identifiers, a catalog entry can associate an entity name with
+ a storage object identifier. For example, the following are possible
+ catalog entries:
+
+ -- catalog: SGML Open style entity catalog for HTML --
+ -- $Id: catalog,v 1.3 1995/09/21 23:30:23 connolly Exp $ --
+
+ -- Ways to refer to Level 2: most general to most specific --
+<span class="h1"><a name="appendix-PUBLIC">PUBLIC</a> "-//IETF//DTD HTML//EN" html.dtd</span>
+<span class="h1"><a name="appendix-PUBLIC">PUBLIC</a> "-//IETF//DTD HTML 2.0//EN" html.dtd</span>
+<span class="h1"><a name="appendix-PUBLIC">PUBLIC</a> "-//IETF//DTD HTML Level 2//EN" html.dtd</span>
+<span class="h1"><a name="appendix-PUBLIC">PUBLIC</a> "-//IETF//DTD HTML 2.0 Level 2//EN" html.dtd</span>
+
+ -- Ways to refer to Level 1: most general to most specific --
+<span class="h1"><a name="appendix-PUBLIC">PUBLIC</a> "-//IETF//DTD HTML Level 1//EN" html-1.dtd</span>
+<span class="h1"><a name="appendix-PUBLIC">PUBLIC</a> "-//IETF//DTD HTML 2.0 Level 1//EN" html-1.dtd</span>
+
+ -- Ways to refer to
+ Strict Level 2: most general to most specific --
+<span class="h1"><a name="appendix-PUBLIC">PUBLIC</a> "-//IETF//DTD HTML Strict//EN" html-s.dtd</span>
+<span class="h1"><a name="appendix-PUBLIC">PUBLIC</a> "-//IETF//DTD HTML 2.0 Strict//EN" html-s.dtd</span>
+<span class="h1"><a name="appendix-PUBLIC">PUBLIC</a> "-//IETF//DTD HTML Strict Level 2//EN" html-s.dtd</span>
+<span class="h1"><a name="appendix-PUBLIC">PUBLIC</a> "-//IETF//DTD HTML 2.0 Strict Level 2//EN" html-s.dtd</span>
+
+ -- Ways to refer to
+ Strict Level 1: most general to most specific --
+<span class="h1"><a name="appendix-PUBLIC">PUBLIC</a> "-//IETF//DTD HTML Strict Level 1//EN" html-1s.dtd</span>
+<span class="h1"><a name="appendix-PUBLIC">PUBLIC</a> "-//IETF//DTD HTML 2.0 Strict Level 1//EN" html-1s.dtd</span>
+
+ -- ISO latin 1 entity set for HTML --
+<span class="h1"><a name="appendix-PUBLIC">PUBLIC</a> "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML" ISOlat1\</span>
+sgml
+
+<span class="h3"><a name="section-9.7">9.7</a>. Character Entity Sets</span>
+
+ The HTML DTD defines the following entities. They represent
+ particular graphic characters which have special meanings in places
+ in the markup, or may not be part of the character set available to
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 66]</span>
+<a name="page-67" id="page-67" href="#page-67" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ the writer.
+
+<span class="h4"><a name="section-9.7.1">9.7.1</a>. Numeric and Special Graphic Entity Set</span>
+
+ The following table lists each of the characters included from the
+ Numeric and Special Graphic entity set, along with its name, syntax
+ for use, and description. This list is derived from `ISO Standard
+ 8879:1986//ENTITIES Numeric and Special Graphic//EN'. However, HTML
+ does not include for the entire entity set -- only the entities
+ listed below are included.
+
+ GLYPH NAME SYNTAX DESCRIPTION
+ &lt; lt &amp;lt; Less than sign
+ &gt; gt &amp;gt; Greater than signn
+ &amp; amp &amp;amp; Ampersand
+ " quot &amp;quot; Double quote sign
+
+<span class="h4"><a name="section-9.7.2">9.7.2</a>. ISO Latin 1 Character Entity Set</span>
+
+ The following public text lists each of the characters specified in
+ the Added Latin 1 entity set, along with its name, syntax for use,
+ and description. This list is derived from ISO Standard
+ 8879:1986//ENTITIES Added Latin 1//EN. HTML includes the entire
+ entity set.
+
+&lt;!-- (C) International Organization for Standardization 1986
+ Permission to copy in any form is granted for use with
+ conforming SGML systems and applications as defined in
+ ISO 8879, provided this notice is included in all copies.
+--&gt;
+&lt;!-- Character entity set. Typical invocation:
+ &lt;!ENTITY % ISOlat1 PUBLIC
+ "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML"&gt;
+ %ISOlat1;
+--&gt;
+&lt;!-- Modified for use in HTML
+ $Id: ISOlat1.sgml,v 1.2 1994/11/30 23:45:12 connolly Exp $ --&gt;
+&lt;!ENTITY AElig CDATA "&amp;#198;" -- capital AE diphthong (ligature) --&gt;
+&lt;!ENTITY Aacute CDATA "&amp;#193;" -- capital A, acute accent --&gt;
+&lt;!ENTITY Acirc CDATA "&amp;#194;" -- capital A, circumflex accent --&gt;
+&lt;!ENTITY Agrave CDATA "&amp;#192;" -- capital A, grave accent --&gt;
+&lt;!ENTITY Aring CDATA "&amp;#197;" -- capital A, ring --&gt;
+&lt;!ENTITY Atilde CDATA "&amp;#195;" -- capital A, tilde --&gt;
+&lt;!ENTITY Auml CDATA "&amp;#196;" -- capital A, dieresis or umlaut mark --&gt;
+&lt;!ENTITY Ccedil CDATA "&amp;#199;" -- capital C, cedilla --&gt;
+&lt;!ENTITY ETH CDATA "&amp;#208;" -- capital Eth, Icelandic --&gt;
+&lt;!ENTITY Eacute CDATA "&amp;#201;" -- capital E, acute accent --&gt;
+&lt;!ENTITY Ecirc CDATA "&amp;#202;" -- capital E, circumflex accent --&gt;
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 67]</span>
+<a name="page-68" id="page-68" href="#page-68" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+&lt;!ENTITY Egrave CDATA "&amp;#200;" -- capital E, grave accent --&gt;
+&lt;!ENTITY Euml CDATA "&amp;#203;" -- capital E, dieresis or umlaut mark --&gt;
+&lt;!ENTITY Iacute CDATA "&amp;#205;" -- capital I, acute accent --&gt;
+&lt;!ENTITY Icirc CDATA "&amp;#206;" -- capital I, circumflex accent --&gt;
+&lt;!ENTITY Igrave CDATA "&amp;#204;" -- capital I, grave accent --&gt;
+&lt;!ENTITY Iuml CDATA "&amp;#207;" -- capital I, dieresis or umlaut mark --&gt;
+&lt;!ENTITY Ntilde CDATA "&amp;#209;" -- capital N, tilde --&gt;
+&lt;!ENTITY Oacute CDATA "&amp;#211;" -- capital O, acute accent --&gt;
+&lt;!ENTITY Ocirc CDATA "&amp;#212;" -- capital O, circumflex accent --&gt;
+&lt;!ENTITY Ograve CDATA "&amp;#210;" -- capital O, grave accent --&gt;
+&lt;!ENTITY Oslash CDATA "&amp;#216;" -- capital O, slash --&gt;
+&lt;!ENTITY Otilde CDATA "&amp;#213;" -- capital O, tilde --&gt;
+&lt;!ENTITY Ouml CDATA "&amp;#214;" -- capital O, dieresis or umlaut mark --&gt;
+&lt;!ENTITY THORN CDATA "&amp;#222;" -- capital THORN, Icelandic --&gt;
+&lt;!ENTITY Uacute CDATA "&amp;#218;" -- capital U, acute accent --&gt;
+&lt;!ENTITY Ucirc CDATA "&amp;#219;" -- capital U, circumflex accent --&gt;
+&lt;!ENTITY Ugrave CDATA "&amp;#217;" -- capital U, grave accent --&gt;
+&lt;!ENTITY Uuml CDATA "&amp;#220;" -- capital U, dieresis or umlaut mark --&gt;
+&lt;!ENTITY Yacute CDATA "&amp;#221;" -- capital Y, acute accent --&gt;
+&lt;!ENTITY aacute CDATA "&amp;#225;" -- small a, acute accent --&gt;
+&lt;!ENTITY acirc CDATA "&amp;#226;" -- small a, circumflex accent --&gt;
+&lt;!ENTITY aelig CDATA "&amp;#230;" -- small ae diphthong (ligature) --&gt;
+&lt;!ENTITY agrave CDATA "&amp;#224;" -- small a, grave accent --&gt;
+&lt;!ENTITY aring CDATA "&amp;#229;" -- small a, ring --&gt;
+&lt;!ENTITY atilde CDATA "&amp;#227;" -- small a, tilde --&gt;
+&lt;!ENTITY auml CDATA "&amp;#228;" -- small a, dieresis or umlaut mark --&gt;
+&lt;!ENTITY ccedil CDATA "&amp;#231;" -- small c, cedilla --&gt;
+&lt;!ENTITY eacute CDATA "&amp;#233;" -- small e, acute accent --&gt;
+&lt;!ENTITY ecirc CDATA "&amp;#234;" -- small e, circumflex accent --&gt;
+&lt;!ENTITY egrave CDATA "&amp;#232;" -- small e, grave accent --&gt;
+&lt;!ENTITY eth CDATA "&amp;#240;" -- small eth, Icelandic --&gt;
+&lt;!ENTITY euml CDATA "&amp;#235;" -- small e, dieresis or umlaut mark --&gt;
+&lt;!ENTITY iacute CDATA "&amp;#237;" -- small i, acute accent --&gt;
+&lt;!ENTITY icirc CDATA "&amp;#238;" -- small i, circumflex accent --&gt;
+&lt;!ENTITY igrave CDATA "&amp;#236;" -- small i, grave accent --&gt;
+&lt;!ENTITY iuml CDATA "&amp;#239;" -- small i, dieresis or umlaut mark --&gt;
+&lt;!ENTITY ntilde CDATA "&amp;#241;" -- small n, tilde --&gt;
+&lt;!ENTITY oacute CDATA "&amp;#243;" -- small o, acute accent --&gt;
+&lt;!ENTITY ocirc CDATA "&amp;#244;" -- small o, circumflex accent --&gt;
+&lt;!ENTITY ograve CDATA "&amp;#242;" -- small o, grave accent --&gt;
+&lt;!ENTITY oslash CDATA "&amp;#248;" -- small o, slash --&gt;
+&lt;!ENTITY otilde CDATA "&amp;#245;" -- small o, tilde --&gt;
+&lt;!ENTITY ouml CDATA "&amp;#246;" -- small o, dieresis or umlaut mark --&gt;
+&lt;!ENTITY szlig CDATA "&amp;#223;" -- small sharp s, German (sz ligature)-&gt;
+&lt;!ENTITY thorn CDATA "&amp;#254;" -- small thorn, Icelandic --&gt;
+&lt;!ENTITY uacute CDATA "&amp;#250;" -- small u, acute accent --&gt;
+&lt;!ENTITY ucirc CDATA "&amp;#251;" -- small u, circumflex accent --&gt;
+&lt;!ENTITY ugrave CDATA "&amp;#249;" -- small u, grave accent --&gt;
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 68]</span>
+<a name="page-69" id="page-69" href="#page-69" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+&lt;!ENTITY uuml CDATA "&amp;#252;" -- small u, dieresis or umlaut mark --&gt;
+&lt;!ENTITY yacute CDATA "&amp;#253;" -- small y, acute accent --&gt;
+&lt;!ENTITY yuml CDATA "&amp;#255;" -- small y, dieresis or umlaut mark --&gt;
+
+<span class="h2"><a name="section-10">10</a>. Security Considerations</span>
+
+ Anchors, embedded images, and all other elements which contain URIs
+ as parameters may cause the URI to be dereferenced in response to
+ user input. In this case, the security considerations of [<a href="#ref-URL" title='"Uniform Resource Locators (URL)"'>URL</a>] apply.
+
+ The widely deployed methods for submitting forms requests -- HTTP and
+ SMTP -- provide little assurance of confidentiality. Information
+ providers who request sensitive information via forms -- especially
+ by way of the `PASSWORD' type input field (see 8.1.2, "Input Field:
+ INPUT") -- should be aware and make their users aware of the lack of
+ confidentiality.
+
+<span class="h2"><a name="section-11">11</a>. References</span>
+
+ [<a name="ref-URI" id="ref-URI">URI</a>]
+ Berners-Lee, T., "Universal Resource Identifiers in WWW:
+ A Unifying Syntax for the Expression of Names and
+ Addresses of Objects on the Network as used in the
+ World- Wide Web", <a href="./rfc1630">RFC 1630</a>, CERN, June 1994.
+ &lt;URL:ftp://ds.internic.net/rfc/rfc1630.txt&gt;
+
+ [<a name="ref-URL" id="ref-URL">URL</a>]
+ Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform
+ Resource Locators (URL)", <a href="./rfc1738">RFC 1738</a>, CERN, Xerox PARC,
+ University of Minnesota, December 1994.
+ &lt;URL:ftp://ds.internic.net/rfc/rfc1738.txt&gt;
+
+ [<a name="ref-HTTP" id="ref-HTTP">HTTP</a>]
+ Berners-Lee, T., Fielding, R., and H. Frystyk Nielsen,
+ "Hypertext Transfer Protocol - HTTP/1.0", Work in
+ Progress, MIT, UC Irvine, CERN, March 1995.
+
+ [<a name="ref-MIME" id="ref-MIME">MIME</a>]
+ Borenstein, N., and N. Freed. "MIME (Multipurpose
+ Internet Mail Extensions) Part One: Mechanisms for
+ Specifying and Describing the Format of Internet Message
+ Bodies", <a href="./rfc1521">RFC 1521</a>, Bellcore, Innosoft, September 1993.
+ &lt;URL:ftp://ds.internic.net/rfc/rfc1521.txt&gt;
+
+ [<a name="ref-RELURL" id="ref-RELURL">RELURL</a>]
+ Fielding, R., "Relative Uniform Resource Locators", <a href="./rfc1808">RFC</a>
+ <a href="./rfc1808">1808</a>, June 1995
+ &lt;URL:ftp://ds.internic.net/rfc/rfc1808.txt&gt;
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 69]</span>
+<a name="page-70" id="page-70" href="#page-70" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ [<a name="ref-GOLD90" id="ref-GOLD90">GOLD90</a>]
+ Goldfarb, C., "The SGML Handbook", Y. Rubinsky, Ed.,
+ Oxford University Press, 1990.
+
+ [<a name="ref-DEXTER" id="ref-DEXTER">DEXTER</a>]
+ Frank Halasz and Mayer Schwartz, "The Dexter Hypertext
+ Reference Model", Communications of the ACM, pp.
+ 30-39, vol. 37 no. 2, Feb 1994.
+
+ [<a name="ref-IMEDIA" id="ref-IMEDIA">IMEDIA</a>]
+ Postel, J., "Media Type Registration Procedure",
+ <a href="./rfc1590">RFC 1590</a>, USC/Information Sciences Institute, March 1994.
+ &lt;URL:ftp://ds.internic.net/rfc/rfc1590.txt&gt;
+
+ [<a name="ref-IANA" id="ref-IANA">IANA</a>]
+ Reynolds, J., and J. Postel, "Assigned Numbers", STD 2,
+ <a href="./rfc1700">RFC 1700</a>, USC/Information Sciecnes Institute, October
+ 1994. &lt;URL:ftp://ds.internic.net/rfc/rfc1700.txt&gt;
+
+ [<a name="ref-SQ91" id="ref-SQ91">SQ91</a>]
+ SoftQuad. "The SGML Primer", 3rd ed., SoftQuad Inc.,
+ 1991. &lt;URL:http://www.sq.com/&gt;
+
+ [<a name="ref-ISO-646" id="ref-ISO-646">ISO-646</a>]
+ ISO/IEC 646:1991 Information technology -- ISO 7-bit
+ coded character set for information interchange
+ &lt;URL:http://www.iso.ch/cate/d4777.html&gt;
+
+ [<a name="ref-ISO-10646" id="ref-ISO-10646">ISO-10646</a>]
+ ISO/IEC 10646-1:1993 Information technology -- Universal
+ Multiple-Octet Coded Character Set (UCS) -- Part 1:
+ Architecture and Basic Multilingual Plane
+ &lt;URL:http://www.iso.ch/cate/d18741.html&gt;
+
+ [<a name="ref-ISO-8859-1" id="ref-ISO-8859-1">ISO-8859-1</a>]
+ ISO 8859. International Standard -- Information
+ Processing -- 8-bit Single-Byte Coded Graphic Character
+ Sets -- Part 1: Latin Alphabet No. 1, ISO 8859-1:1987.
+ &lt;URL:http://www.iso.ch/cate/d16338.html&gt;
+
+ [<a name="ref-SGML" id="ref-SGML">SGML</a>]
+ ISO 8879. Information Processing -- Text and Office
+ Systems - Standard Generalized Markup Language (SGML),
+ 1986. &lt;URL:http://www.iso.ch/cate/d16387.html&gt;
+
+
+
+
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 70]</span>
+<a name="page-71" id="page-71" href="#page-71" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h2"><a name="section-12">12</a>. Acknowledgments</span>
+
+ The HTML document type was designed by Tim Berners-Lee at CERN as
+ part of the 1990 World Wide Web project. In 1992, Dan Connolly wrote
+ the HTML Document Type Definition (DTD) and a brief HTML
+ specification.
+
+ Since 1993, a wide variety of Internet participants have contributed
+ to the evolution of HTML, which has included the addition of in-line
+ images introduced by the NCSA Mosaic software for WWW. Dave Raggett
+ played an important role in deriving the forms material from the
+ HTML+ specification.
+
+ Dan Connolly and Karen Olson Muldrow rewrote the HTML Specification
+ in 1994. The document was then edited by the HTML working group as a
+ whole, with updates being made by Eric Schieler, Mike Knezovich, and
+ Eric W. Sink at Spyglass, Inc. Finally, Roy Fielding restructured
+ the entire draft into its current form.
+
+ Special thanks to the many active participants in the HTML working
+ group, too numerous to list individually, without whom there would be
+ no standards process and no standard. That this document approaches
+ its objective of carefully converging a description of current
+ practice and formalization of HTML's relationship to SGML is a
+ tribute to their effort.
+
+<span class="h3"><a name="section-12.1">12.1</a>. Authors' Addresses</span>
+
+ Tim Berners-Lee
+ Director, W3 Consortium
+ MIT Laboratory for Computer Science
+ 545 Technology Square
+ Cambridge, MA 02139, U.S.A.
+
+ Phone: +1 (617) 253 9670
+ Fax: +1 (617) 258 8682
+ EMail: timbl@w3.org
+
+
+ Daniel W. Connolly
+ Research Technical Staff, W3 Consortium
+ MIT Laboratory for Computer Science
+ 545 Technology Square
+ Cambridge, MA 02139, U.S.A.
+
+ Phone: +1 (617) 258 8682
+ EMail: connolly@w3.org
+ URI: <a href="http://www.w3.org/hypertext/WWW/People/Connolly/">http://www.w3.org/hypertext/WWW/People/Connolly/</a>
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 71]</span>
+<a name="page-72" id="page-72" href="#page-72" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+<span class="h2"><a name="section-13">13</a>. The HTML Coded Character Set</span>
+
+ This list details the code positions and characters of the HTML
+ document character set, specified in 9.5, "SGML Declaration for
+ HTML". This coded character set is based on [<a href="#ref-ISO-8859-1">ISO-8859-1</a>].
+
+ REFERENCE DESCRIPTION
+ -------------- -----------
+ &amp;#00; - &amp;#08; Unused
+ &amp;#09; Horizontal tab
+ &amp;#10; Line feed
+ &amp;#11; - &amp;#12; Unused
+ &amp;#13; Carriage Return
+ &amp;#14; - &amp;#31; Unused
+ &amp;#32; Space
+ &amp;#33; Exclamation mark
+ &amp;#34; Quotation mark
+ &amp;#35; Number sign
+ &amp;#36; Dollar sign
+ &amp;#37; Percent sign
+ &amp;#38; Ampersand
+ &amp;#39; Apostrophe
+ &amp;#40; Left parenthesis
+ &amp;#41; Right parenthesis
+ &amp;#42; Asterisk
+ &amp;#43; Plus sign
+ &amp;#44; Comma
+ &amp;#45; Hyphen
+ &amp;#46; Period (fullstop)
+ &amp;#47; Solidus (slash)
+ &amp;#48; - &amp;#57; Digits 0-9
+ &amp;#58; Colon
+ &amp;#59; Semi-colon
+ &amp;#60; Less than
+ &amp;#61; Equals sign
+ &amp;#62; Greater than
+ &amp;#63; Question mark
+ &amp;#64; Commercial at
+ &amp;#65; - &amp;#90; Letters A-Z
+ &amp;#91; Left square bracket
+ &amp;#92; Reverse solidus (backslash)
+ &amp;#93; Right square bracket
+ &amp;#94; Caret
+ &amp;#95; Horizontal bar (underscore)
+ &amp;#96; Acute accent
+ &amp;#97; - &amp;#122; Letters a-z
+ &amp;#123; Left curly brace
+ &amp;#124; Vertical bar
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 72]</span>
+<a name="page-73" id="page-73" href="#page-73" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ &amp;#125; Right curly brace
+ &amp;#126; Tilde
+ &amp;#127; - &amp;#159; Unused
+ &amp;#160; Non-breaking Space
+ &amp;#161; Inverted exclamation
+ &amp;#162; Cent sign
+ &amp;#163; Pound sterling
+ &amp;#164; General currency sign
+ &amp;#165; Yen sign
+ &amp;#166; Broken vertical bar
+ &amp;#167; Section sign
+ &amp;#168; Umlaut (dieresis)
+ &amp;#169; Copyright
+ &amp;#170; Feminine ordinal
+ &amp;#171; Left angle quote, guillemotleft
+ &amp;#172; Not sign
+ &amp;#173; Soft hyphen
+ &amp;#174; Registered trademark
+ &amp;#175; Macron accent
+ &amp;#176; Degree sign
+ &amp;#177; Plus or minus
+ &amp;#178; Superscript two
+ &amp;#179; Superscript three
+ &amp;#180; Acute accent
+ &amp;#181; Micro sign
+ &amp;#182; Paragraph sign
+ &amp;#183; Middle dot
+ &amp;#184; Cedilla
+ &amp;#185; Superscript one
+ &amp;#186; Masculine ordinal
+ &amp;#187; Right angle quote, guillemotright
+ &amp;#188; Fraction one-fourth
+ &amp;#189; Fraction one-half
+ &amp;#190; Fraction three-fourths
+ &amp;#191; Inverted question mark
+ &amp;#192; Capital A, grave accent
+ &amp;#193; Capital A, acute accent
+ &amp;#194; Capital A, circumflex accent
+ &amp;#195; Capital A, tilde
+ &amp;#196; Capital A, dieresis or umlaut mark
+ &amp;#197; Capital A, ring
+ &amp;#198; Capital AE dipthong (ligature)
+ &amp;#199; Capital C, cedilla
+ &amp;#200; Capital E, grave accent
+ &amp;#201; Capital E, acute accent
+ &amp;#202; Capital E, circumflex accent
+ &amp;#203; Capital E, dieresis or umlaut mark
+ &amp;#204; Capital I, grave accent
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 73]</span>
+<a name="page-74" id="page-74" href="#page-74" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ &amp;#205; Capital I, acute accent
+ &amp;#206; Capital I, circumflex accent
+ &amp;#207; Capital I, dieresis or umlaut mark
+ &amp;#208; Capital Eth, Icelandic
+ &amp;#209; Capital N, tilde
+ &amp;#210; Capital O, grave accent
+ &amp;#211; Capital O, acute accent
+ &amp;#212; Capital O, circumflex accent
+ &amp;#213; Capital O, tilde
+ &amp;#214; Capital O, dieresis or umlaut mark
+ &amp;#215; Multiply sign
+ &amp;#216; Capital O, slash
+ &amp;#217; Capital U, grave accent
+ &amp;#218; Capital U, acute accent
+ &amp;#219; Capital U, circumflex accent
+ &amp;#220; Capital U, dieresis or umlaut mark
+ &amp;#221; Capital Y, acute accent
+ &amp;#222; Capital THORN, Icelandic
+ &amp;#223; Small sharp s, German (sz ligature)
+ &amp;#224; Small a, grave accent
+ &amp;#225; Small a, acute accent
+ &amp;#226; Small a, circumflex accent
+ &amp;#227; Small a, tilde
+ &amp;#228; Small a, dieresis or umlaut mark
+ &amp;#229; Small a, ring
+ &amp;#230; Small ae dipthong (ligature)
+ &amp;#231; Small c, cedilla
+ &amp;#232; Small e, grave accent
+ &amp;#233; Small e, acute accent
+ &amp;#234; Small e, circumflex accent
+ &amp;#235; Small e, dieresis or umlaut mark
+ &amp;#236; Small i, grave accent
+ &amp;#237; Small i, acute accent
+ &amp;#238; Small i, circumflex accent
+ &amp;#239; Small i, dieresis or umlaut mark
+ &amp;#240; Small eth, Icelandic
+ &amp;#241; Small n, tilde
+ &amp;#242; Small o, grave accent
+ &amp;#243; Small o, acute accent
+ &amp;#244; Small o, circumflex accent
+ &amp;#245; Small o, tilde
+ &amp;#246; Small o, dieresis or umlaut mark
+ &amp;#247; Division sign
+ &amp;#248; Small o, slash
+ &amp;#249; Small u, grave accent
+ &amp;#250; Small u, acute accent
+ &amp;#251; Small u, circumflex accent
+ &amp;#252; Small u, dieresis or umlaut mark
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 74]</span>
+<a name="page-75" id="page-75" href="#page-75" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ &amp;#253; Small y, acute accent
+ &amp;#254; Small thorn, Icelandic
+ &amp;#255; Small y, dieresis or umlaut mark
+
+<span class="h2"><a name="section-14">14</a>. Proposed Entities</span>
+
+ The HTML DTD references the "Added Latin 1" entity set, which only
+ supplies named entities for a subset of the non-ASCII characters in
+ [<a href="#ref-ISO-8859-1">ISO-8859-1</a>], namely the accented characters. The following entities
+ should be supported so that all ISO 8859-1 characters may only be
+ referenced symbolically. The names for these entities are taken from
+ the appendixes of [<a href="#ref-SGML">SGML</a>].
+
+ &lt;!ENTITY nbsp CDATA "&amp;#160;" -- no-break space --&gt;
+ &lt;!ENTITY iexcl CDATA "&amp;#161;" -- inverted exclamation mark --&gt;
+ &lt;!ENTITY cent CDATA "&amp;#162;" -- cent sign --&gt;
+ &lt;!ENTITY pound CDATA "&amp;#163;" -- pound sterling sign --&gt;
+ &lt;!ENTITY curren CDATA "&amp;#164;" -- general currency sign --&gt;
+ &lt;!ENTITY yen CDATA "&amp;#165;" -- yen sign --&gt;
+ &lt;!ENTITY brvbar CDATA "&amp;#166;" -- broken (vertical) bar --&gt;
+ &lt;!ENTITY sect CDATA "&amp;#167;" -- section sign --&gt;
+ &lt;!ENTITY uml CDATA "&amp;#168;" -- umlaut (dieresis) --&gt;
+ &lt;!ENTITY copy CDATA "&amp;#169;" -- copyright sign --&gt;
+ &lt;!ENTITY ordf CDATA "&amp;#170;" -- ordinal indicator, feminine --&gt;
+ &lt;!ENTITY laquo CDATA "&amp;#171;" -- angle quotation mark, left --&gt;
+ &lt;!ENTITY not CDATA "&amp;#172;" -- not sign --&gt;
+ &lt;!ENTITY shy CDATA "&amp;#173;" -- soft hyphen --&gt;
+ &lt;!ENTITY reg CDATA "&amp;#174;" -- registered sign --&gt;
+ &lt;!ENTITY macr CDATA "&amp;#175;" -- macron --&gt;
+ &lt;!ENTITY deg CDATA "&amp;#176;" -- degree sign --&gt;
+ &lt;!ENTITY plusmn CDATA "&amp;#177;" -- plus-or-minus sign --&gt;
+ &lt;!ENTITY sup2 CDATA "&amp;#178;" -- superscript two --&gt;
+ &lt;!ENTITY sup3 CDATA "&amp;#179;" -- superscript three --&gt;
+ &lt;!ENTITY acute CDATA "&amp;#180;" -- acute accent --&gt;
+ &lt;!ENTITY micro CDATA "&amp;#181;" -- micro sign --&gt;
+ &lt;!ENTITY para CDATA "&amp;#182;" -- pilcrow (paragraph sign) --&gt;
+ &lt;!ENTITY middot CDATA "&amp;#183;" -- middle dot --&gt;
+ &lt;!ENTITY cedil CDATA "&amp;#184;" -- cedilla --&gt;
+ &lt;!ENTITY sup1 CDATA "&amp;#185;" -- superscript one --&gt;
+ &lt;!ENTITY ordm CDATA "&amp;#186;" -- ordinal indicator, masculine --&gt;
+ &lt;!ENTITY raquo CDATA "&amp;#187;" -- angle quotation mark, right --&gt;
+ &lt;!ENTITY frac14 CDATA "&amp;#188;" -- fraction one-quarter --&gt;
+ &lt;!ENTITY frac12 CDATA "&amp;#189;" -- fraction one-half --&gt;
+ &lt;!ENTITY frac34 CDATA "&amp;#190;" -- fraction three-quarters --&gt;
+ &lt;!ENTITY iquest CDATA "&amp;#191;" -- inverted question mark --&gt;
+ &lt;!ENTITY Agrave CDATA "&amp;#192;" -- capital A, grave accent --&gt;
+ &lt;!ENTITY Aacute CDATA "&amp;#193;" -- capital A, acute accent --&gt;
+ &lt;!ENTITY Acirc CDATA "&amp;#194;" -- capital A, circumflex accent --&gt;
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 75]</span>
+<a name="page-76" id="page-76" href="#page-76" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ &lt;!ENTITY Atilde CDATA "&amp;#195;" -- capital A, tilde --&gt;
+ &lt;!ENTITY Auml CDATA "&amp;#196;" -- capital A, dieresis or umlaut mark --&gt;
+ &lt;!ENTITY Aring CDATA "&amp;#197;" -- capital A, ring --&gt;
+ &lt;!ENTITY AElig CDATA "&amp;#198;" -- capital AE diphthong (ligature) --&gt;
+ &lt;!ENTITY Ccedil CDATA "&amp;#199;" -- capital C, cedilla --&gt;
+ &lt;!ENTITY Egrave CDATA "&amp;#200;" -- capital E, grave accent --&gt;
+ &lt;!ENTITY Eacute CDATA "&amp;#201;" -- capital E, acute accent --&gt;
+ &lt;!ENTITY Ecirc CDATA "&amp;#202;" -- capital E, circumflex accent --&gt;
+ &lt;!ENTITY Euml CDATA "&amp;#203;" -- capital E, dieresis or umlaut mark --&gt;
+ &lt;!ENTITY Igrave CDATA "&amp;#204;" -- capital I, grave accent --&gt;
+ &lt;!ENTITY Iacute CDATA "&amp;#205;" -- capital I, acute accent --&gt;
+ &lt;!ENTITY Icirc CDATA "&amp;#206;" -- capital I, circumflex accent --&gt;
+ &lt;!ENTITY Iuml CDATA "&amp;#207;" -- capital I, dieresis or umlaut mark --&gt;
+ &lt;!ENTITY ETH CDATA "&amp;#208;" -- capital Eth, Icelandic --&gt;
+ &lt;!ENTITY Ntilde CDATA "&amp;#209;" -- capital N, tilde --&gt;
+ &lt;!ENTITY Ograve CDATA "&amp;#210;" -- capital O, grave accent --&gt;
+ &lt;!ENTITY Oacute CDATA "&amp;#211;" -- capital O, acute accent --&gt;
+ &lt;!ENTITY Ocirc CDATA "&amp;#212;" -- capital O, circumflex accent --&gt;
+ &lt;!ENTITY Otilde CDATA "&amp;#213;" -- capital O, tilde --&gt;
+ &lt;!ENTITY Ouml CDATA "&amp;#214;" -- capital O, dieresis or umlaut mark --&gt;
+ &lt;!ENTITY times CDATA "&amp;#215;" -- multiply sign --&gt;
+ &lt;!ENTITY Oslash CDATA "&amp;#216;" -- capital O, slash --&gt;
+ &lt;!ENTITY Ugrave CDATA "&amp;#217;" -- capital U, grave accent --&gt;
+ &lt;!ENTITY Uacute CDATA "&amp;#218;" -- capital U, acute accent --&gt;
+ &lt;!ENTITY Ucirc CDATA "&amp;#219;" -- capital U, circumflex accent --&gt;
+ &lt;!ENTITY Uuml CDATA "&amp;#220;" -- capital U, dieresis or umlaut mark --&gt;
+ &lt;!ENTITY Yacute CDATA "&amp;#221;" -- capital Y, acute accent --&gt;
+ &lt;!ENTITY THORN CDATA "&amp;#222;" -- capital THORN, Icelandic --&gt;
+ &lt;!ENTITY szlig CDATA "&amp;#223;" -- small sharp s, German (sz ligature) --&gt;
+ &lt;!ENTITY agrave CDATA "&amp;#224;" -- small a, grave accent --&gt;
+ &lt;!ENTITY aacute CDATA "&amp;#225;" -- small a, acute accent --&gt;
+ &lt;!ENTITY acirc CDATA "&amp;#226;" -- small a, circumflex accent --&gt;
+ &lt;!ENTITY atilde CDATA "&amp;#227;" -- small a, tilde --&gt;
+ &lt;!ENTITY auml CDATA "&amp;#228;" -- small a, dieresis or umlaut mark --&gt;
+ &lt;!ENTITY aring CDATA "&amp;#229;" -- small a, ring --&gt;
+ &lt;!ENTITY aelig CDATA "&amp;#230;" -- small ae diphthong (ligature) --&gt;
+ &lt;!ENTITY ccedil CDATA "&amp;#231;" -- small c, cedilla --&gt;
+ &lt;!ENTITY egrave CDATA "&amp;#232;" -- small e, grave accent --&gt;
+ &lt;!ENTITY eacute CDATA "&amp;#233;" -- small e, acute accent --&gt;
+ &lt;!ENTITY ecirc CDATA "&amp;#234;" -- small e, circumflex accent --&gt;
+ &lt;!ENTITY euml CDATA "&amp;#235;" -- small e, dieresis or umlaut mark --&gt;
+ &lt;!ENTITY igrave CDATA "&amp;#236;" -- small i, grave accent --&gt;
+ &lt;!ENTITY iacute CDATA "&amp;#237;" -- small i, acute accent --&gt;
+ &lt;!ENTITY icirc CDATA "&amp;#238;" -- small i, circumflex accent --&gt;
+ &lt;!ENTITY iuml CDATA "&amp;#239;" -- small i, dieresis or umlaut mark --&gt;
+ &lt;!ENTITY eth CDATA "&amp;#240;" -- small eth, Icelandic --&gt;
+ &lt;!ENTITY ntilde CDATA "&amp;#241;" -- small n, tilde --&gt;
+ &lt;!ENTITY ograve CDATA "&amp;#242;" -- small o, grave accent --&gt;
+
+
+
+<span class="grey">Berners-Lee &amp; Connolly Standards Track [Page 76]</span>
+<a name="page-77" id="page-77" href="#page-77" class="invisible"><span class="break"> </span></a>
+<span class="grey"><a href="./rfc1866">RFC 1866</a> Hypertext Markup Language - 2.0 November 1995</span>
+
+
+ &lt;!ENTITY oacute CDATA "&amp;#243;" -- small o, acute accent --&gt;
+ &lt;!ENTITY ocirc CDATA "&amp;#244;" -- small o, circumflex accent --&gt;
+ &lt;!ENTITY otilde CDATA "&amp;#245;" -- small o, tilde --&gt;
+ &lt;!ENTITY ouml CDATA "&amp;#246;" -- small o, dieresis or umlaut mark --&gt;
+ &lt;!ENTITY divide CDATA "&amp;#247;" -- divide sign --&gt;
+ &lt;!ENTITY oslash CDATA "&amp;#248;" -- small o, slash --&gt;
+ &lt;!ENTITY ugrave CDATA "&amp;#249;" -- small u, grave accent --&gt;
+ &lt;!ENTITY uacute CDATA "&amp;#250;" -- small u, acute accent --&gt;
+ &lt;!ENTITY ucirc CDATA "&amp;#251;" -- small u, circumflex accent --&gt;
+ &lt;!ENTITY uuml CDATA "&amp;#252;" -- small u, dieresis or umlaut mark --&gt;
+ &lt;!ENTITY yacute CDATA "&amp;#253;" -- small y, acute accent --&gt;
+ &lt;!ENTITY thorn CDATA "&amp;#254;" -- small thorn, Icelandic --&gt;
+ &lt;!ENTITY yuml CDATA "&amp;#255;" -- small y, dieresis or umlaut mark --&gt;
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Berners-Lee &amp; Connolly Standards Track [Page 77]
+<span class="break"> </span>
+
+</pre><br />
+<span class="noprint"><small><small>Html markup produced by rfcmarkup 1.60, available from
+<a href="http://tools.ietf.org/tools/rfcmarkup/">http://tools.ietf.org/tools/rfcmarkup/</a>
+</small></small></span>
+</body></html>