view Side-By-Side changes

INTERNET DRAFT                                         February 8, 1995
Expires in


HTML Working Group                                         T. Berners-Lee
INTERNET-DRAFT                                                    MIT/W3C
<draft-ietf-html-spec-02.txt>                                 D. Connolly
Expires: In six months


                   HyperText                                        May 6, 1995


                   Hypertext Markup Language Specification - 2.0
                         <draft-ietf-html-spec-01.txt>

STATUS OF THIS MEMO


                               CONTENTS


     1.  Introduction
     2.  HTML as an Application of SGML
     3.  HTML as an Internet Media Type
     4.  Document Structure Elements
     5.  Character Content
     6.  Data Elements
     7.  Character Format Elements
     8.  Hyperlink Elements
     9.  Block Structuring Elements
     10.  Form-based Input Elements
     11.  HTML Public Text
     12.  Glossary
     13.  Bibliography
     14.  Appendices
     15.  Acknowledgments



Status of this Memo

This document is an Internet draft.  Internet drafts Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute
working documents as
   Internet drafts.

   Internet drafts Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet drafts Internet-Drafts as reference material
or to cite them other than as "work ``work in progress." progress.''

To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt"
1id-abstracts.txt listing contained in the Internet- Drafts Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast).

Distribution of this document is unlimited. Please send comments to
the HTML working group (HTML-WG) of the Internet Engineering Task
Force (IETF) at <html-
   wg@oclc.org>. <html-wg@oclc.org>. Discussions of the group are
archived at
   URL: http://www.acl.lanl.gov/HTML_WG/archives.html.

Abstract <URL:http://www.acl.lanl.gov/HTML_WG/archives.html>.


                          ABSTRACT

     The HyperText Hypertext Markup Language (HTML) is a simple markup
     language used to create hypertext documents that are
   portable from one
     platform to another. independent. HTML documents are SGML documents with
     generic semantics that are appropriate for representing
     information from a wide range of applications. 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

Berners-Lee, Connolly, et. al.                                  Page 1

                                HTML 2.0                February 8, 1995 common
     use prior to June 1994. It HTML is defined as an application of ISO
     Standard 8879:1986 Information Processing Text and Office
     Systems; Standard Generalized Markup Language (SGML).

     The "text/html; version=2.0" `"text/html; version=2.0"' Internet Media Type (RFC
     1590) and MIME Content Type (RFC 1521) is defined by this
     specification.

Contents

   Overview


1. Introduction 

     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.


1.1. Scope 

     HTML Specification........................  2 has been in use by the World-Wide Web (WWW) global
     information initiative since 1990. This specification
     corresponds to the capabilities of HTML Specification.................................... 11

   Security Considerations............................... 52

   Obsolete in common use prior
     to June 1994 and Proposed Features........................ 53 referred to as ``HTML 2.0''.

     HTML Document Type Definitions........................ 56

   Glossary.............................................. 74

   References............................................ 77

   Acknowledgments....................................... 78

   Author's Addresses.................................... 80


1. Overview is an application of ISO Standard 8879:1986
     _Information Processing Text and Office Systems; Standard
     Generalized Markup Language_ (SGML). The HTML Specification

   This chapter Document Type
     Definition (DTD) is a summary formal definition of the HTML specification. See
   Section 2. for the complete specification. syntax
     in terms of SGML.

     This specification also defines HTML describes the structure as an Internet Media
     Type[IMEDIA] and organization of a
   document. It only suggests appropriate presentations MIME Content Type[MIME] called `text/html',
     or `text/html; version=2.0'. As such, it defines the
     semantics of the document when processed.

   In HTML documents, tags define the start syntax and end how that syntax should be
     interpreted by user agents.


1.2. Conformance 

     This specification governs the syntax of
   headings, paragraphs, lists, character highlighting HTML documents and
   links. Most
     the behaviour of HTML elements are identified in a user agents.


1.2.1. Documents 

     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 < and >, and end tags
   are delimited by </ and >.

   Example:


Berners-Lee, Connolly, et. al.                                  Page 2

                                HTML 2.0                February 8, 1995


   <H1>This is a heading</H1>

   Every HTML document starts with a conforming HTML document
   identifier which contains two sections, only if:

          * It is a head conforming SGML document, and a
   body. The head contains HTML elements which describe it conforms to
          the
   documents title, usage and relationship with other
   documents. The body contains other HTML elements with DTD (see 11.1, "HTML DTD")
          * It conforms to the entire text and graphics of application conventions in this
          specification. For example, the document.

   This overview briefly describes value of the syntax `HREF'
          attribute of HTML
   elements the <A> element must conform to the URI
          syntax.
          * Its document character set includes ISO-8859-1 and provides an example HTML document.

   NOTE: The term "HTML user agent"
          agrees with ISO10646; that is, each code position
          listed in 14.1, "The ISO-8859-1 Coded Character Set" is used
          included, and each code position in this the document
          character set is mapped to describe applications the same character as
          ISO10646 designates for that are used with
   HTML documents.

   1.1 HTML Elements

      1.1.1 Document Structure Elements

         HTML Identifier

            <HTML> ... </HTML> code position.
          NOTE - The HTML identifier defines the document as containing 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 elements. It contains only
          documents, since its repertoire is a subset of the Head and Body
            elements.

         Head

            <HEAD> ... </HEAD>
          ISO10646 repertoire. The Head element contains HTML elements crititcal distinction is that describe
            the documents title, usage and relationship
          numeric character references agree with other
            documents.

         Body

            <BODY> ... </BODY>

            The Body element contains the text and its associated
            HTML elements ISO10646
          regardless of how the document.

         Example document is encoded.

          NOTE - There are a number of Document Structure Elements

            <HTML>
            <HEAD>
            <TITLE>The Document's Title</TITLE>
            </HEAD>
            <BODY>

Berners-Lee, Connolly, et. al.                                  Page 3 syntactic idioms that are
          not supported or are supported inconsistently in some
          historical user agent implementations. These idioms are
          called out in notes like this throughout this
          specification.

          HTML 2.0                February 8, 1995 documents should not contain these idioms, at
          least until such time as support for them is widely
          deployed.

     The document's text.
            </BODY>

      1.1.2 Anchor Element

         Anchor

            <A> ... </A>

            An anchor specifies HTML DTD defines a link to another location (<A
            HREF>) or standard HTML document type and
     several variations, based on feature test entities:

     
     HTML.Recommended
                    Certain features of the value to use when linking to this location
            from another location (<A NAME>):

            See <A HREF="http://www.hal.com/">HaL</A>'s
            information for more details.

            <A NAME="B">Section B</A> describes...
            ...
            See <A HREF="#B">Section B</A> language are necessary for more information.

      1.1.3 Block Formatting Elements

         Address

            <ADDRESS> ... </ADDRESS>

            <ADDRESS>
            Newsletter editor<BR>
            J.R. Brown<BR>
            JimquickPost News, Jumquick, CT 01234<BR>
            Tel (123) 456 7890
            </ADDRESS>

         Body

            <BODY> ... </BODY>

            Place the <BODY> and </BODY> tags above and below
                    compatibility with widespread usage, but they may
                    compromise the
            body structural integrity of a document.
                    This feature test entity enables a more
                    prescriptive document type definition that
                    eliminates those features.

                    For example, in order to preserve the text (not including the head) structure of your
                    a document, an editing user agent may translate
                    HTML
            document.

         Blockquote

            <BLOCKQUOTE>... </BLOCKQUOTE>
            I think documents to the recommended subset, or it ends
            <BLOCKQUOTE>
            <P>Soft you now,
                    may require that the fair Ophelia. Nymph, in thy
            orisons, documents be all my sins remembered.
            </BLOCKQUOTE>

Berners-Lee, Connolly, et. al.                                  Page 4

                                HTML 2.0                February 8, 1995


            but I am not sure.

         Head

            <HEAD> ... </HEAD>

            Every HTML document must have a head, which provides a
            title. Example:

            <HTML>
            <HEAD>
            <TITLE>Introduction to HTML</TITLE>
            </HEAD>

         Headings

            <H1>This is a first level heading</H1>
            <P>There in the
                    recommended subset for import.

     HTML.Deprecated
                    Certain features of the language are six levels necessary for
                    compatibility with earlier versions of headings.
            <H2>Second level heading</H2>
            <P>This text appears under the second level heading

         Horizontal Rule

            <HR>

            Inserts
                    specification, but they tend to be used an
                    implemented inconsistently, and their use is
                    deprecated. This feature test entity enables a horizontal rule
                    document type definition that spans eliminates these
                    features.

                    Documents generated by tranlation software or
                    editing software should not contain these idioms.


1.2.2. User Agents 

     An HTML user agent conforms to this specification if:

          * It parses the width characters of the
            document. Example:

            <HR>
            <ADDRESS>February 8, 1995, CERN</ADDRESS>
            </BODY>

         HTML Identifier

            <HTML> ... </HTML>

            An an HTML document begins with an <HTML> tag into
          data characters and ends with markup as per [SGML].
          * It supports the </HTML> tag.

         Line Break

            <BR>

            Forces a line break:

            Name<BR>
            Street address<BR>
            City, State Zip

         Paragraph

Berners-Lee, Connolly, et. al.                                  Page 5

                                HTML 2.0                February 8, 1995



            <P> ... </P>

            <H1>This Heading Precedes ISO-8859-1 character encoding scheme,
          and processes each character in the Paragraph</H1>
            <P>This is ISO Latin Alphabet
          Nr. 1 as specified in 5.1, "The ISO Latin 1 Character
          Repertoire".
          NOTE - To support non-western writing systems, HTML
          user agents should support the text Unicode-1-1-UTF-8 and
          Unicode-1-1-UCS-2 encodings and as much of the first paragraph.
            <P>This is the text
          character repertoire of ISO10646 as is possible as
          well.
          * It behaves identically for documents whose parsed
          token sequences are identical.
          For example, comments and the second paragraph. Although
            you whitespace in tags
          disappear during tokenization, and hence they do not need to start paragraphs on new lines,
            maintaining this convention facilitates document
            maintenance.
            <P>This is
          influence the text of a third paragraph.

         Preformatted Text

            <PRE> ... </PRE>

            <PRE WIDTH="80">
            This is an example behaviour of preformatted text.
            </PRE>

         Title

            <TITLE> ... </TITLE>

            <TITLE>Title of document</TITLE>

       1.1.4 List Elements

         Definition List

            <DL> ... <DT>term<DD>definition... </DL>

            <DL>
            <DT>Term<DD>This is the first definition.
            <DT>Term<DD>This is the second definition.
            </DL>

         Directory List

            <DIR> ... <LI>List item... </DIR>

            <DIR>
            <LI>A-H<LI>I-M
            <LI>M-R<LI>S-Z
            </DIR>

         Menu List

            <MENU> ... <LI>List item... </MENU>

            <MENU>

Berners-Lee, Connolly, et. al.                                  Page 6

                                HTML 2.0                February 8, 1995


            <LI>First item in the list.
            <LI>Second item in the list.
            <LI>Third item in the list.
            </MENU>

         Ordered List

            <OL> ... <LI>List item... </OL>

            <OL>
            <LI>Click conforming user agents.
          * It allows the Web button user to open the Open the URL
            window.
            <LI>Enter the URL number traverse (or at least attempt
          to traverse, resources permitting) all hyperlinks in an
          HTML document.
          * It allows the text user to express all form field of the Open
            URL window. The Web document you values
          specified is displayed.
            <LI>Click highlighted text to move from one link in an HTML document and to
            another.
            </OL>

         Unordered List

            <UL> ... <LI>List item... </UL>

            <UL>
            <LI>This is (attempt to)
          submit the first item in values as requests to information services.

          NOTE - In the list.
            <LI>This interest of robustness and extensibility,
          there are a number of widely deployed conventions for
          handling non-conforming documents. See 3.2.1,
          "Undeclared Markup Error Handling" for details.


2. HTML as an Application of SGML 

     HTML is the second item in the list.
            <LI>This an application of ISO Standard 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 third item HTML
     document type definition are provided in 11, "HTML Public
     Text".

     The term _HTML_ refers to both the list.
            </UL>

       1.1.5 Information Type document type defined
     here and Character Formatting Elements

         Bold

            <B> ... </B>

            Suggests the rendering markup language for representing instances of the text in boldface. If
            boldface
     this document type.


2.1. SGML Documents 

     An HTML document is not available, alternative mapping is
            allowed.

         Citation

            <CITE> ... </CITE>

            Specifies a citation; typically rendered as italic.

         Code

            <CODE> ... </CODE>

            Indicates an inline example SGML document; that is, a sequence of code; typically rendered
     characters organized physically into a set of entities, and
     logically as monospaced.. Do not confuse with a hierarchy of elements.

     The first production of the <PRE> tag.

Berners-Lee, Connolly, et. al.                                  Page 7

                                HTML 2.0                February 8, 1995



         Emphasis

            <EM> ... </EM>

            Provides typographic emphasis; typically rendered as
            italics.

         Italics

            <I> ... </I>

            Suggests SGML grammar separates an SGML
     document into three parts: an SGML declaration, a prologue,
     and an instance. For the rendering purposes of text in italic font, or
            slanted if italic this specification, the
     prologue is not available.

         Keyboard

            <KBD> ... </KBD>

            Indicates text typed by a user; typically rendered as
            monospaced.

         Sample

            <SAMP> ... </SAMP>

            Indicates a sequence of literal characters; typically
            rendered as monospaced..

         Strong

            <STRONG> ... </STRONG>

            Provides strong typographic emphasis; typically rendered
            as bold.

         Typetype

            <TT> ... </TT>

            Specifies that DTD. This DTD describes another grammar: the text be rendered
     start symbol is given in fixed-width font.

         Variable

            <VAR> ... </VAR>

            Indicates a variable name; typically rendered as italic.

       1.1.6 Image Element


Berners-Lee, Connolly, et. al.                                  Page 8

                                HTML 2.0                February 8, 1995


         Image

            <IMG>

            Inserts the referenced graphic image into doctype declaration; the document
            at
     terminals are data characters and tags, and the location where productions
     are determined by the element occurs.

            Example:

            <IMG SRC ="triangle.gif" ALT="Warning:"> Be sure to read
            these instructions.

      1.1.7 Form Elements

         Form

            <FORM> ... </FORM> declarations. The Form element contains nested elements (described
            below) which define user input controls and allow
            descriptive text instance
     must conform to the DTD, that is, it must be displayed when in the document is
            processed.

         Input

            <INPUT>

            Takes these attributes: ALIGN, MAXLENGTH, NAME, SIZE,
            SRC, TYPE, VALUE. language
     defined by this grammar.

     The type attribute can define these
            field types: CHECKBOX, HIDDEN, IMAGE, PASSWORD, RADIO,
            RESET, SUBMIT, TEXT.

            Example:

            <FORM METHOD="POST" action="http://www.hal.com/sample">
            <P>Your name: <INPUT NAME="name" SIZE="48">
            <P>Male <INPUT NAME="gender" TYPE=RADIO VALUE="male">
            <P>Female <INPUT NAME="gender" TYPE=RADIO
            VALUE="female">
            </FORM>

         Option

            <OPTION>

            The Option element can only occur within a Select
            element. It represents one choice.

         Select


Berners-Lee, Connolly, et. al.                                  Page 9

                                HTML 2.0                February 8, 1995


            <SELECT NAME="..." > ... </SELECT>

            Select provides a list of choices.

            <SELECT NAME="flavor">
            <OPTION>Vanilla
            <OPTION>Strawberry
            <OPTION>Rum and Raisin
            <OPTION>Peach and Orange
            </SELECT>

         Textarea

            <TEXTAREA> ... </TEXTAREA>

            Textarea defines a multi-line text entry input control.
            It contains SGML declaration determines the initial text contents lexicon of the control.

            <TEXTAREA NAME="address" ROWS=64 COLS=6>
            HaL Computer Systems
            1314 Dell Avenue
            Campbell California 95008
            </TEXTAREA>

      1.1.8 Character Data in HTML

         Representing Graphic Characters in HTML

         Because of grammar.
     It specifies the way special document character set, which determines a
     character repertoire that contains all characters are used that occur
     in all text entities in
         marking up HTML text, character strings are used to
         represent the less than (<) and greater than (>) symbols document, and the ampersand (&) as shown in Section 2.17.1.

         Representing Special Characters in HTML

         HTML inherits both from code positions
     associated with those characters.

     The SGML and from MIME in its description declaration also specifies the syntax-reference
     character set of characters the document, and character sets. The result is a small
         amount of duplication few other parameters
     that bind the abstract syntax of function: there are multiple ways SGML to
         code a concrete syntax.
     This concrete syntax determines how the sequence of
     characters of the document is mapped to a sequence of
     terminals in HTML.

         HTML documents are encoded in some character encoding; the character encoding may be specified, for grammar of the prologue.

     For example,
         by consider the "charset" parameter associated with following document:

     <!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
     <title>Parsing Example</title>
     <p>Some text. <em>&#42;wow&#42;</em></p>

     An HTML user agent should use the "text/html"
         media type.
         
         Independent of SGML declaration is given
     in 11.2, "SGML Declaration for HTML". According to the
     document character encoding used,
         HTML also allows references set there,`&#42;' refers to any of an asterisk
     character.

     The instance above is regarded as the ISO Latin-1
         alphabet, using following sequence of
     terminals:

          1. TITLE start-tag
          2. data characters: ``Parsing Example''
          3. TITLE end-tag
          4. P start-tag
          5. data characters ``Some text. ''
          6. EM start-tag
          7. ``*wow*''
          8. EM end-tag

     The start symbol of the names DTD grammar is HTML, and the
     productions are given in the table ISO Latin-1
         Character Representations, which is derived from ISO
         Standard 8879:1986//ENTITIES Added Latin 1//EN. For

Berners-Lee, Connolly, et. al.                                  Page 10 public text identified by
     `-//IETF//DTD HTML 2.0                February 8, 1995


         details, see 2.17.2.

   1.2 Example 2.0//EN' (11.1, "HTML DTD"). Hence the
     terminals above parse as:

        HTML Document

      <HTML>
      <HEAD>
      <TITLE>Structural Example</TITLE>
      </HEAD>
      <BODY>
      <H1>First Header</H1>
      <P>This is
         |
         \-HEAD
         |  |
         |  \-TITLE
         |      |
         |      \-<TITLE>
         |      |
         |      \-"Parsing Example"
         |      |
         |      \-</TITLE>
         |
         \-BODY
           |
           \-P
             |
             \-<P>
             |
             \-"Some text. "
             |
             \-EM
             |  |
             |  \-<EM>
             |  |
             |  \-"*wow*"
             |  |
             |  \-</EM>
             |
             \-</P>


2.2. HTML Lexical Syntax 

     SGML specifies an abstract syntax and a paragraph in reference concrete
     syntax. Aside from certain quantities and capacities (e.g.
     the example limit on the length of a name), all HTML file.
      Keep in mind that documents use
     the title does not appear reference concrete syntax. In particular, all markup
     characters are in the
      document text, but that the header (defined by H1) does.
      <UL>
      <LI>First item in an unordered list.
      <LI>Second item in an unordered list.
      </UL>
      <P>This is an additional paragraph. Technically, end
      tags
      are not required for paragraphs, although they ISO-646-IRV character repertoire. Data
     characters are
      allowed.
      You can include drawn from the document character highlighting in a paragraph.
      <I>This sentence set (see 5,
     "Character Content").

     A complete discussion of SGML parsing, e.g. the paragraph mapping of a
     sequence of characters to a sequence of tags and data is in italics.</I>
      <IMG SRC ="triangle.gif" alt="Warning:"> Be sure
     left to read
      these instructions.
      </BODY>
      </HTML>

2. HTML Specification

   HTML has been in use by the World Wide Web (WWW) global
   information initiative since 1990. SGML standard[SGML]. This specification
   corresponds section is only a
     summary.


2.2.1. Data Characters 

     Any sequence of characters that do not constitute markup
     (see 9.6 ``Delimiter Recognition'' of [SGML]) are mapped
     directly to strings of data characters. Some markup also
     maps to data character strings. Numeric character references
     also map to single-character strings, via the legitimate capabilities document
     character set. Each reference to one of HTML the general entities
     defined in
   common use prior the HTML DTD also maps to June 1994. It a single-character
     string.

     For example,

     abc&lt;def    => "abc","<","def"
     abc&#60;def   => "abc","<","def"

     Note that the terminating semicolon is defined only necessary when
     the character following the reference would otherwise be
     recognized as markup:

     abc &lt def     => "abc ","<"," def"
     abc &#60 def    => "abc ","<"," def"

     And note that an
   application of ISO Standard 8879:1986: Standard
   Generalized Markup Language (SGML). This specification ampersand is proposed only recognized as the Internet Media Type (RFC 1590) and
   MIME Content Type (RFC 1521) called "text/html", markup when
     it is followed by a letter or
   "text/html; version=2.0".

   This specification also includes:

   -  5.1 SGML Declaration digit:

     abc & lt def    => "abc & lt def"
     abc & 60 def    => "abc & 60 def"

     A useful technique for translating plain text to HTML is to
     replace each '<', '&', and '>' by an entity reference or
     numeric character reference as follows:

                      ENTITY      NUMERIC
            CHARACTER REFERENCE   CHAR REF     CHARACTER DESCRIPTION
              &       &amp;       &#38;        Ampersand
              <       &lt;        &#60;        Less than
              >       &gt;        &#62;        Greater than

          NOTE -  5.1.1 Sample There are SGML Open Style Entity Catalog for HTML

   -  5.2 HTML DTD

   This specification is currently available on the World
   Wide Web at URL: http://www.hal.com/%7Econnolly/html-spec

Berners-Lee, Connolly, et. al.                                  Page 11

                                HTML 2.0                February 8, 1995



   Please send comments mechanisms, CDATA and RCDATA, to
          allow most `<', `>', and `&' characters to be entered
          without the discussion list at: html-
   wg@oclc.org

   2.1 Levels of Conformance

      Version 2.0 use of the entity references. Because these
          features tend to be used and implemented
          inconsistently, and because they conflict with
          techinques for reducing HTML specification introduces forms to 7 bit ASCII for user input
          transport, they are not used in this version of information, and adds a distinction
      between levels of conformance:

      Level 0

         Indicates the minimum conformance level. When writing
         Level 0 documents, authors can be confident that the
         rendering at different sites will reflect their intent.

      Level 1

         Includes Level 0 features plus features
          HTML DTD.


2.2.2. Tags 

     Tags delimit elements such as headings, paragraphs, lists,
     character highlighting and images.

      Level 2

         Includes all Level 0 and Level 1 features, plus forms.
         Features of higher levels, such links. Most HTML elements are
     identified in a document as tables, figures, a start-tag, which gives the
     element name and
         mathematical formulae, attributes, followed by the content,
     followed by the end tag. Start-tags are under discussion delimited by `<' and
     `>'; end tags are
         described as proposed where mentioned.

   2.2 Undefined Tag delimited by `</' and Attribute Names `>'. An accepted networking principle example is:

     <H1>This is a Heading</H1>

     Some elements only have a start-tag without an end-tag. For
     example, to be conservative
      in that which one produces, and liberal in that which
      one accepts. HTML user agents should be liberal except
      when verifying code. HTML generators should generate
      strictly conforming HTML.

      The behavior create a line break, you use the `<BR>' tag.
     Additionally, the end tags of HTML user agents reading HTML documents some other elements, such as
     Paragraph (`</P>'), List Item (`</LI>'), Definition Term
     (`</DT>'), and discovering tag or attribute names which they do not
      understand should Definition Description (`<DD>') elements, may
     be to behave as though, in the case of
      a tag, the whole tag had not been there but its omitted.

     The content
      had, or in the case of an attribute, that the attribute
      had not been present.

   2.3 Deprecated element is a sequence of data character
     strings and Recommended Sections in DTDs

      In Section 5., optional "deprecated" nested elements. Some elements, such as anchors,
     cannot be nested. Anchors and "recommended"
      sections are used. Conformance with this specification
      is defined with these sections disabled. In character highlighting may be
     put inside other constructs. See the liberal
      spirit of Section 2.2, HTML user agents reading HTML
      documents should accept syntax corresponding to the

Berners-Lee, Connolly, et. al.                                  Page 12

                                HTML 2.0                February 8, 1995


      specification with "deprecated" turned on. HTML user
      agents generating DTD, 11.1, "HTML
     DTD" for full details.

          NOTE - The SGML declaration for HTML may in the spirit of
      conservation, generate documents specifies SHORTTAG
          YES, which means that conform to the
      specification with the "recommended" sections turned on.

   2.4 HTML there are other valid syntaxes
          for tags, such as an Internet Media Type

      This (and upward compatible specifications) define the Internet
      Media Type (RFC 1590) NET tags, `<EM/.../'; empty start
          tags, `<>'; and MIME Content Type (RFC 1521) called
      "text/html".

      The type "text/html" accepts the following parameters:

      Level

         The level parameter specifies the feature set used in
         the document. The level empty end-tags, `</>'. Until support
          for these idioms is an integer number, implying
         that any features widely deployed, their use is
          strongly discouraged.


2.2.3. Names 

     A name consists of same a letter followed by up to 71 letters,
     digits, periods, or lower level may be present
         in the document. Levels 0, 1 hyphens. Element names are not case
     sensitive, but entity names are. For example,
     `<BLOCKQUOTE>', `<BlockQuote>', and 2 `<blockquote>' are defined by this
         specification.

      Version

         To help avoid future compatibility problems, the version
         parameter may be used to give the version number of the
         specification to which
     equivalent, whereas `&amp;' is different from `&AMP;'.

     In a start-tag, the document conforms. The
         version number appears at element name must immediately follow the front of this document
     tag open delimiter `<'.


2.2.4. Attributes 

     In a start-tag, white space and
         within attributes are allowed
     between the public identifier for element name and the SGML DTD. This
         specification defines version 2.0.

      Charset

         The charset parameter (as defined in section 7.1.1 closing delimiter. An
     attribute typically consists of
         RFC 1521) an attribute name, an equal
     sign, and a value, though some attributes may be used with the text/html to specify
         the encoding used to represent the HTML document as
         a sequence of bytes. Normally, text/* media types
         specify just a default
     value. White space is allowed around the equal sign.

     The value of US-ASCII for the charset
         parameter. However, for text/html, if attribute may be either:

          * A string literal, delimited by single quotes or
          double quotes and not containing any occurrences of the byte stream
         contains data that
          delimiting character.
          * A name token (a sequence of letters, digits, periods,
          or hyphens)

     In this example, img is not in the 7-bit US-ASCII set, element name, `src' is the
         HTML interpreting agent should assume a default charset of
         ISO-8859-1.

         When an HTML document
     attribute name, and `http://host/dir/file.gif' is encoded using US-ASCII, the mechanisms
     attribute value:

     <img src="http://host/dir/file.gif">

          NOTE - Some historical implementations consider any
          occurrence of numeric character references (see
         Section 2.16.2) and the `>' character entity references (see
         Section 2.16.3) may be used to encode additional characters
         from ISO-8859-1.

         Other values for signal the charset parameter are not defined end of a
          tag. For ompatibility with such implementations, when
          `>' appears in this specification, but may an attribute value, it should be specified in future

Berners-Lee, Connolly, et. al.                                  Page 13

                                HTML 2.0                February 8, 1995


         levels or versions of HTML.

         It is envisioned that HTML will use the charset parameter
         to allow support for non-Latin characters
          represented with a numeric character reference, such as
         Greek, Arabic, Hebrew, Japanese, rather than relying on
         any SGML mechanism
          in: `<IMG SRC="eq1.jpg" alt="a>b">'.

     A useful technique for doing so.

   2.5 Understanding HTML and SGML

      HTML is computing an application of ISO Standard 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. The SGML declaration attribute value literal
     for HTML is a given
      in Section 5.1. It string is implicit among HTML user agents.

      If the HTML specification to replace each quote and SGML standard conflict, space
     character by an entity reference or numeric character
     reference as follows:

                      ENTITY      NUMERIC
            CHARACTER REFERENCE   CHAR REF     CHARACTER DESCRIPTION
              TAB                 &#9;         Tab
              LF                  &#10;        Line Feed
              CR                  &#13;        Carriage Return
                                  &#32;        Space
              "       &quot;      &#34;        Quotation mark
              &       &amp;       &#38;        Ampersand

     For example:

     <IMG SRC="image.jpg" alt="First &quot;real&quot; example">

          NOTE - Some historical implementations allow any
          character except space or `>' in a name token.
          Attributes values must be quoted only if they don't
          satisfy the SGML standard is definitive.

      Every SGML document has three parts:

      SGML declaration

         Binds SGML processing quantities and syntax token names
         to specific values. For example, for a name token.

     Note that the SGML declaration in section 13.3 limits the
     length of an attribute value to 1024 characters.

     Attributes such as ISMAP and COMPACT, may be written using a
     minimized syntax. The markup:

     <UL COMPACT="compact">

     can be written using a minimized syntax:

     <UL COMPACT>

          NOTE - Some historical implementations only understand
          the minimized syntax.


2.2.5. Comments 

     To include comments in an HTML DTD specifies document that will be
     eliminated in the string that opens an end
         tag is </ mapping to terminals, surround them with
     `<!--' and `-->'. After the maximum length comment delimiter, all text up
     to the next occurrence of a name `-->' is 72
         characters.

      Prologue

         Includes one or more document type declarations, which
         specify ignored. Hence comments
     cannot be nested. White space is allowed between the element types, element relationships closing
     `--' and
         attributes.

      Instance

         Contains `>', but not between the data opening `<!' and markup of the document. `--'.

     For example:

     <HEAD>
     <TITLE>HTML Guide: Recommended Usage</TITLE>
     <!-- $Id: html-sgml.sgm,v 1.4 1995/05/06 01:44:46 connolly Exp $ -->
     </HEAD>

          NOTE - Some historical HTML refers implementations incorrectly
          consider any `>' character to be the document type as well as the markup
      language for representing instances termination of that document
      type.

   2.6 Working with Structured Text

      An HTML document is like a text file, except that some
      of the characters are markup. Markup (tags) define the
      structure of the document.

      To identify information as HTML, each HTML document

Berners-Lee, Connolly, et. al.                                  Page 14
          comment.


2.2.6. Example HTML 2.0                February 8, 1995


      should start with the prologue: Document 

     <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN//2.0">

      NOTE: If the body of HTML//EN">
     <HTML>
     <!-- Here's a text/html body part does not
      begin with good place to put a document type declaration, an HTML user
      agent should infer comment. -->
     <HEAD>
     <TITLE>Structural Example</TITLE>
     </HEAD><BODY>
     <H1>First Header</H1>
     <P>This is a paragraph in the above document type declaration. example HTML documents should also contain an <HTML> tag at file. Keep in mind
     that the
      beginning of title does not appear in the file, after document text, but that
     the prologue, and header (defined by H1) does.</P>
     <OL>
     <LI>First item in an
      </HTML> tag at the end. Within those tags, ordered list.
     <LI>Second item in an HTML
      document is organized as a head and a body, much like
      memo or a mail message. Within the head, you ordered list.
       <UL COMPACT>
       <LI> Note that lists can specify
      the title and other information about the document.
      Within be nested;
       <LI> Whitespace may be used to assist in reading the body, you can structure text into paragraphs
      and lists as well as highlighting phrases and creating
      links. You do this using
            HTML elements.

         NOTE: source.
       </UL>
     <LI>Third item in an ordered list.
     </OL>
     <P>This is an additional paragraph. Technically, the start and end tags are
     not required for HTML,
         Head, and Body elements paragraphs, although they are omissible; however, this allowed. You can
     include character highlighting in a paragraph. <EM>This sentence
     of the paragraph is
         not recommended since emphasized.</EM> Note that the head/ body structure allows an
         implementation to determine certain properties of a
         document, such &lt;/P&gt;
     end tag has been omitted.
     <P>
     <IMG SRC ="triangle.xbm" alt="Warning: ">
     Be sure to read these <b>bold instructions</b>.
     </BODY></HTML>


3. HTML as the title, without parsing the entire
         document.

   2.6.1 an Internet Media Type 

     An HTML Elements

      In user agent allows users to interact with resources
     which have HTML documents, tags define the start representations. At a minimum, it must allow
     users to examine and end navigate the content of
      headings, paragraphs, lists, character highlighting and
      links. Most HTML elements are identified documents.
     HTML user agents should be able to preserve all formatting
     distinctions represented in a document
      as a start tag, which gives the element name an HTML document, and
      attributes, followed be able to
     simultaneously present resources referred to by IMG
     elements. (they may ignore some formatting distinctions or
     IMG resources at the content, followed by request of the end
      tag. Start tags are delimited by < and >, and end tags
      are delimited by </ user). Conforming HTML
     user agents should support form entry and >.

      Example:

      <H1>This is a Heading</H1>

      Some elements only have a start tag without an end tag.
      For example, to create a line break, you use the <BR>
      tag. Additionally, submission.


3.1. text/html media type 

     This specification defines the end tags of some other elements,
      such Internet Media Type[IMEDIA]
     (formerly referred to as Paragraph (<P>), List Item (<LI>), Definition
      Term (<DT>), and Definition Description (<DD>) elements,
      may be omitted. the Content Type[MIME]) called
     `text/html'. The content of an element following is a sequence of characters
      and nested elements. Some elements, such as anchors,
      cannot be nested. Anchors and character highlighting may to be put inside other constructs.

Berners-Lee, Connolly, et. al.                                  Page 15

                                HTML 2.0                February 8, 1995



      NOTE: registered with [IANA].

     Media Type name
                    text

     Media subtype
     name
                    html

     Required
     parameters
                    none

     Optional
     parameters
                    version, charset

     Encoding
     considerations
                    any encoding is allowed

     Security
     considerations
                    see 3.3, "Security Considerations"

     The SGML declaration for HTML specifies SHORTTAG
      YES, which means that there optional parameters are other valid syntaxes for
      tags, such defined as NET tags, <EM/.../; empty start tags, <>;
      and empty end tags, </>. Until support for these idioms
      is widely deployed, their use is strongly discouraged.

   2.6.2 Names

      A name consists of a letter followed by up follows:

     Version
                    To help avoid future compatibility problems, the
                    version parameter may be used to 71
      letters, digits, periods, or hyphens. Element names are
      not case sensitive, but entity names are. For example,
      <BLOCKQUOTE>, <BlockQuote>, and <blockquote> are
      equivalent, whereas &amp; is different from &AMP;.

      In a start tag, give the element name must immediately follow version
                    number of the tag open delimiter <.

   2.6.3 Attributes

      In a start tag, white space and attributes are allowed
      between specification to which the element name and document
                    conforms. The version number appears at the closing delimiter. An
      attribute typically consists front
                    of an attribute name, an
      equal sign, this document and a value (although some attributes may be
      just a value). White space is allowed around within the equal
      sign.

      The value public identifier
                    of the attribute HTML DTD. This specification defines
                    version 2.0. There is no default.

     Charset
                    The charset parameter (as defined in section 7.1.1
                    of RFC 1521[MIME]) may be either:

      -  A string literal, delimited by single quotes or
         double quotes and not containing any occurrences of given to specify the
         delimiting character.

      -  A name token (a
                    character encoding scheme used to represent the
                    HTML document as a sequence of letters, digits,
         periods, or hyphens)

      In octets. The default
                    value is outside the scope of this specification;
                    but for example, A is the element name, HREF default is US-ASCII in the
      attribute name,
                    context of MIME mail, and http://host/dir/file.html is ISO-8859-1 in the
      attribute value:

      <A HREF="http://host/dir/file.html">

         NOTE: Some non-SGML implementations consider any
         occurrence of the > character to signal the end
                    context of a
         tag. For compatibility with such implementations, when >
         appears in an attribute value, you may want to represent
         it HTTP.


3.2. HTML Document Representation 

     A message entity with a content type of `text/html'
     represents an entity or numeric character reference (see
         Section 2.17.1), such as: <IMG SRC="eq1.jpg" alt="a &#62;
         b">


Berners-Lee, Connolly, et. al.                                  Page 16 HTML 2.0                February 8, 1995


      To put quotes inside document, consisting of quotes, you may use the a single text
     entity. The `charset' parameter (whether implicit or
     explicit) identifies a character representation &quot; as in:

      <IMG SRC="image.jpg" alt="First &quot;real&quot;
      example"> encoding scheme. The length text
     entity consists of an attribute value is limited to 1024 the characters after replacing entity and numeric determined by this
     character
      references.

         NOTE: Some non-SGML encoding scheme and the octets of the body of the
     message entity.


3.2.1. Undeclared Markup Error Handling 

     To facilitate experimentation and interoperability between
     implementations allow any character
         except space or > in a name token. Attributes values
         must be quoted only if they don't satisfy of various versions of HTML, the syntax for installed
     base of HTML user agents supports a name token.

      Attributes with 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 value is mapped to nothing during tokenization.
     Undeclared attributes are treated similarly. The entire
     attribute specification of NAME, such as ISMAP an unknown attribute (i.e., the
     unknown attribute and COMPACT, may be written using a minimized syntax.
      The markup:

         <UL COMPACT="compact">

      can its value, if any) should be written using a minimized syntax:

         <UL COMPACT>

         NOTE: Some non-SGML implementations only understand ignored.
     On the
         minimized syntax.

   2.6.4 Special Characters

      Characters that are used other hand, references to represent markup (such as
      ampersand (&), lesser (<) and greater (>)) undeclared entities should themselves
     be represented by markup, using either entity or numeric
      character references. treated as data characters.

     For more information, see
      Section 2.16.

   2.6.5 Comments

      To include comments in an HTML document that will example:

     <div class=chapter><h1>foo</h1><p>...</div>
       => <H1>,"foo",</H1>,<P>,"..."
     xxx <P ID=z23> yyy
       => "xxx ",<P>," yyy
     Let &alpha; and &beta; be
      ignored by the HTML user agent, surround them with <!-- finite sets.
       => "Let &alpha; and -->. After the comment delimiter, all text up to &beta; be finite sets."

     Support for notifying the
      next occurrence user of --> such errors is ignored. Hence comments cannot
      be nested. White space encouraged.

     Information providers are warned that this convention is allowed between the closing --
      and >, but not between the opening <! and --.

      For example:

      <HEAD>
      <TITLE>HTML Guide: Recommended Usage</TITLE>
      <!-- Id: Text.html,v 1.6 1994/04/25 17:33:48 connolly Exp -->

Berners-Lee, Connolly, et. al.                                  Page 17

                                HTML 2.0                February 8, 1995


      </HEAD>

      NOTE: Some historical HTML user agents incorrectly
      consider a > sign
     binding: unspecified behavior may result, as such markup is
     not conforming to terminate this specification.


3.2.2. Conventional Representation of Newlines 

     SGML specifies that a comment.

   2.7 The Head Element text entity is a sequence of records,
     each beginning with a record start character and Related Elements

      Only certain elements are allowed ending with
     a record end character (code positions 10 and 13
     respectively). (section 7.6.1, ``Record Boundaries'' in the head of an HTML
      document. Elements
     [SGML])

     [MIME] specifies that may be included in the head a body of type `text/*' is a
      document are:

      2.7.1 Head

         <HEAD> ... </HEAD>

         Level 0

         The head sequence
     of an HTML document lines, each terminated by CRLF, that is octets 10, 13.

     In practice, HTML documents are frequently represented and
     transmitted using an unordered collection end of information about the document. It requires the Title
         element between <HEAD> and </HEAD> tags in this format:

         <HEAD>
         <TITLE>Introduction to HTML</TITLE>
         </HEAD>

       2.7.2 Base

         Level 0

         The Base element allows line convention that depends on
     the URL conventions of the document itself
         to be recorded in situations in which the document may
         be read out source of context. URLs within the document may be
         in a "partial" form relative to this base address.

         Where document; frequently,
     that representation consists of CR only, LF only, or CR LF
     combination. Hence the base address is not specified, 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
         agent uses the URL it used to access the document agents are encouraged
     to
         resolve any relative URLs.

         The Base element has one attribute, HREF, which
         identifies the URL.

      2.7.3 Isindex

         Level 0

         The Isindex element tells infer the missing record start and end characters.

     An HTML user agent that the
         document is an index document. As well as reading it,
         the reader may use a keyword search.

         The document can be queried with a keyword search by

Berners-Lee, Connolly, et. al.                                  Page 18

                                HTML 2.0                February 8, 1995


         adding a question mark to the should treat end of the document
         address, followed by a list line in any of keywords separated by
         plus signs.

         NOTE: The Isindex element is usually generated
         automatically by its
     variations as a server. If added manually to word space in all contexts except
     preformatted text. Within preformatted text, an HTML
         document, the HTML user
     agent assumes that should expect to treat any of the server
         can handle three common
     representations of end-of-line as starting a search on new line.


3.3. Security Considerations 

     Anchors, embedded images, and all other elements which
     contain URIs as parameters may cause the document. To use URI to be
     dereferenced in response to user input. In this case, the Isindex
         element,
     security considerations of the server must have a search engine that
         supports this element.

      2.7.4 Link

         Level 1 URI specification apply.

     The Link element indicates a relationship between the
         document widely deployed methods for submitting forms requests --
     HTTP and some other object. A document may have any
         number SMTP -- provide little assurance of
     confidentiality. Information providers who request sensitive
     information via forms -- especially by way of Link elements.

         The Link element is empty (does not have a closing tag),
         but takes the same attributes as the Anchor element.

         Typical uses are to indicate authorship, related indexes `PASSWORD'
     type input field -- should be aware and glossaries, older or more recent versions, etc.
         Links can indicate a static tree structure in which make their users
     aware of the lack of confidentiality.

     >


4. Document Structure Elements 

     To identify information as an HTML document was authored by pointing to a "parent" and
         "next" and "previous" document, for example.

         Servers may also allow links conforming to be added by those who do
         not have
     this specification, each document should start with the right to alter
     prologue:

     <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

          NOTE - If the body of a document.

      2.7.5 Nextid

         Level 0

         The Nextid element is a parameter read by and generated
         by text editing software to create unique identifiers.
         This tag takes a single attribute which is the next
         document-wide alpha-numeric identifier to be allocated
         of the form z123:

         <NEXTID N=Z27>

         When modifying a document, existing anchor identifiers
         should text/html body part does not be reused, as these identifiers may be
         referenced by other documents. Human writers of
          begin with a document type declaration, an HTML
         usually use mnemonic alphabetical identifiers. user
          agent should infer the above document type declaration.

     HTML user agents may ignore are required to support the Nextid element. Support
         for above document
     type declaration, the Nextid element does not impact following document type declarations,
     and no others.

     <!DOCTYPE HTML user agents

Berners-Lee, Connolly, et. al.                                  Page 19 PUBLIC "-//IETF//DTD HTML 2.0                February 8, 1995


         in any way.

      2.7.6 Title Strict//EN">
     <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">

     In particular, they may support other formal public
     identifiers, or document types altogether. They may support
     an internal declaration subset with supplemental entity,
     element, and other markup declarations, or they may not.


4.1. HTML Document Element 

     <HTML> ... </HTML> Level 0

     The HTML document element is organized as a head and a body,
     much like a memo or a mail message. Within the head, you can
     specify the title and other information about the document.
     Within the body, you can structure text into paragraphs and
     lists, as well as highlight phrases and create links, using
     HTML elements.

          NOTE - The start and end tags for HTML, Head, and Body
          elements are omissible; however, this is not
          recommended since the head/body structure allows an
          implementation to determine certain properties of a
          document, such as the title, without parsing the entire
          document.

     <


4.2. Head 

     <HEAD> ... </HEAD> Level 0

     The head of an HTML document is an unordered collection of
     information about the document. The Title element is
     required.

     <HEAD>
     <TITLE>Introduction to HTML</TITLE>
     </HEAD>


4.3. Body 

     <BODY> ... </BODY> Level 0

     The Body element identifies the body component of an HTML
     document. Specifically, the body of a document may contain
     links, text, and formatting information within <BODY> and
     </BODY> tags.


4.4. Title 

     <TITLE> ... </TITLE> Level 0

     Every HTML document must contain a Title element. The title
     should identify the contents of the document in a global
     context, and may be used in a history lists and as a label for
     the window displaying the document. Unlike headings, titles
     are not typically rendered in the text of a document itself.

     The Title element must occur within the head of the
     document, and may must not contain anchors, paragraph tags, or
     highlighting. Only one title is allowed in a document.

         NOTE:

          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. Also keep in mind that a short title,
          such as Introduction, may be meaningless out of
          context. An example of a meaningful title might be "Introduction
          ``Introduction to HTML Elements."

      2.7.7 Meta Elements.''


4.5. Base 

     <BASE> Level 1 0

     The Meta Base element is used within allows the URI of the Head element to
         embed document meta-information not defined by other
         HTML elements. Such information can itself to be extracted by
         servers/clients for use
     recorded in identifying, indexing, and
         cataloging specialized situations in which the document meta-information.

         Although it is generally preferable to use named
         elements that have well-defined semantics for each type
         of meta-information, such as a title, this element is
         provided for situations where strict SGML parsing is
         necessary and the local DTD is not extensible.

         In addition, HTTP servers can may be read the content out
     of context. URIs within the document head to generate response headers corresponding
         to any elements defining may be in a value for ``partial''
     form relative to this base address[RELURL].

     The Base element has one attribute, HREF, which identifies
     the attribute HTTP-
         EQUIV. This provides document authors a mechanism (not
         necessarily absolute base URI.


4.6. Isindex 

     <ISINDEX> Level 0

     The Isindex element tells the preferred one) for identifying
         information interpreter that should be included in the response

Berners-Lee, Connolly, et. al.                                  Page 20

                                HTML 2.0                February 8, 1995


         headers for document
     is an HTTP request.

         Attributes of the Meta element:

         HTTP-EQUIV index. This attribute binds means that the element reader may request a
     keyword search on the resource by adding a question mark to an HTTP response
            header. If
     the semantics end of the HTTP response header
            named document address, followed by this attribute is known, then the contents can
            be processed based on a well-defined syntactic mapping
            whether or not list of
     keywords separated by plus signs.

     The Isindex element is usually generated by the DTD includes anything about it. HTTP
            header names are not case sensitive. If not present, network
     server from which the
            NAME attribute should be used to identify document was obtained via a URI. The
     server must have a search engine that supports this meta-
            information and it should not be used within an HTTP
            response header.

         NAME

            Meta-information name. feature
     for the resource. If the NAME attribute document URI is not
            present, the name can be assumed equal unknown to the value of
            HTTP-EQUIV.

         CONTENT

            The meta-information content to
     interpreter, <isindex> must be associated with the
            given name and/or HTTP response header.

         Examples

         If ignored.


4.7. Link 

     <LINK> Level 0

     The Link element indicates a relationship between the
     document contains:

         <META HTTP-EQUIV="Expires" CONTENT="Tue, 04 Dec 1993 21:29:02
         GMT">
         <META HTTP-EQUIV="Keywords" CONTENT="Fred, Barney">
         <META HTTP-EQUIV="Reply-
         to" content="fielding@ics.uci.edu (Roy Fielding)">

         Expires: Tue, 04 Dec 1993 21:29:02 GMT
         Keywords: Fred, Barney
         Reply-to: fielding@ics.uci.edu (Roy Fielding)

         When the HTTP-EQUIV attribute and some other object. A document may have any
     number of Link elements.

     The Link element is empty (does not present, have a closing tag), but
     takes the server
         should not generate an HTTP response header for this
         meta-information; e.g.,

         <META NAME="IndexType" CONTENT="Service">

         Do not use same attributes as the Meta element to define information that
         should be associated with an existing HTML Anchor element.


Berners-Lee, Connolly, et. al.                                  Page 21

                                HTML 2.0                February 8, 1995


         Example of an inappropriate use of the Meta element:

         <META NAME="Title" CONTENT="The Etymology of Dunsel">

         Do not name an HTTP-EQUIV equal to a response header
         that should typically only be generated by the HTTP
         server. Some inappropriate names

     Typical uses are "Server", "Date", to indicate authorship, related indexes and "Last-modified". Whether
     glossaries, older or more recent versions, etc. Links can
     indicate a name is inappropriate
         depends on static tree structure in which the particular server implementation. It is
         recommended that servers ignore any Meta elements that
         specify HTTP-equivalents equal (case-insensitively) document was
     authored by pointing to
         their own reserved response headers.

   2.8 The Body Element a ``parent'' and Related Elements

      The following elements ``next'' and
     ``previous'' document, for example.

     Servers may also allow links to be included in added by those who do not
     have the right to alter the body of an
      HTML document:

      2.8.1 Body

         <BODY> ... </BODY> a document.


4.8. Meta 

     <META> Level 0

     The Body META element identifies is used within the body component of an
         HTML document. Specifically, the body of a HEAD element to embed
     document may
         contain links, text, and formatting information within
         <BODY> metainformation not defined by other HTML elements.
     META elements can be extracted by servers and/or clients for
     use in identifying, indexing, and </BODY> tags.

      2.8.2 Address

         <ADDRESS> ... </ADDRESS>

         Level 0

         The Address cataloging specialized
     document metainformation.

     Although it is generally preferable to use named elements
     which have well-defined semantics for each type of
     metainformation (e.g. TITLE), the META element specifies such information as
         address, signature is provided
     for situations where strict SGML parsing is necessary and authorship, often at
     the top or
         bottom of a document.

         Typically, an Address local DTD is rendered in an italic typeface
         and not extensible. HTML interpreters may be indented. The Address element implies a
         paragraph break before use
     the META element's content if they recognize and after.

         Example of use:

         <ADDRESS>
         Newsletter editor<BR>
         J.R. Brown<BR>
         JimquickPost News, Jumquick, CT 01234<BR>
         Tel (123) 456 7890

Berners-Lee, Connolly, et. al.                                  Page 22

                                HTML 2.0                February 8, 1995


         </ADDRESS>

      2.8.3 Anchor

         <A> ... </A>

         Level 0

         An anchor is a marked text that is understand
     the start and/or
         destination of a hypertext link. Anchor elements are
         defined semantics identified by the <A> tag. The <A> tag accepts several
         attributes, but either the NAME or HREF attribute is
         required.

         Attributes of HTTP-EQUIV
     attributes, and may treat the <A> tag:

         HREF

            Level 0

            If content as metainformation
     (and not render it) even when they do not recognize the HREF attribute is present,
     name.

     In addition, HTTP servers may wish to read the text between content of
     the
            opening and closing anchor tags becomes hypertext. If
            this hypertext is selected by readers, they are moved document HEAD to
            another document, or generate header fields corresponding to
     any elements defining a different location in value for the
            current document, whose network address is defined attribute HTTP-EQUIV.
     Note, however, that the method by which the value server extracts
     document metainformation is not part of the HREF attribute.

            Example:

            See <A HREF="http://www.hal.com/">HaL</A>'s information
            for more details.

            In this example, selecting "HaL" takes the reader to a
            document at http://www.hal.com. The format specification,
     nor can it be assumed by authors that any given server will
     be capable of the
            network address extracting it. The META element only provides
     an extensible mechanism for identifying and embedding
     document metainformation - how it may be used is specified in up to the URI specification
            for print readers.

            With
     individual server implementation and the HREF attribute, HTML interpreter.

     Attributes of the form HREF="#identifier" can
            refer META element:

     HTTP-EQUIV
                    This attribute binds the element to another anchor in an HTTP header
                    field. It means that if you know the same document.

            Example:

            The <A HREF="document.html#glossary">glossary</A>
            defines terms used in this document.

            In this example, selecting "glossary" takes semantics of
                    the reader
            to another anchor (i.e., <A
            NAME="glossary">Glossary</A>) in HTTP header field named by this attribute,
                    then you can process the same document
            (document.html). The NAME attribute is described below. contents based on a
                    well-defined syntactic mapping, whether or not
                    your DTD tells you anything about it. HTTP header
                    field names are not case sensitive. If not
                    present, the anchor is in another document, the HREF attribute

Berners-Lee, Connolly, et. al.                                  Page 23

                                HTML 2.0                February 8, 1995


            may NAME should be relative used to
                    identify this metainformation and the document's address or the
            specified base address (see 2.7.2 Base). content
                    should not be used within an HTTP response header.

     NAME

            Level 0
                    Metainformation name. If present, the NAME attribute allows is not
                    present, the anchor name can be assumed to be equal to
                    the target of a link. The value of HTTP-EQUIV.

     CONTENT
                    The metainformation content to be associated with
                    the NAME attribute is
            an identifier for the anchor. Identifiers given name. If multiple META elements are arbitrary
            strings but must be unique within
                    provided with the HTML document.

            Example of use:

            <A NAME="coffee">Coffee</A> is an example of ...
            ...
            An example of this is <A HREF="#coffee">coffee</A>.

            Another document can then make same name, their combined
                    contents-concatenated as a reference explicitly to
            this anchor by putting the identifier after comma-separated list-is
                    the address,
            separated by a hash sign:

            <A NAME="drinks.html#coffee">

         TITLE

            Level 1

            The TITLE attribute is informational only. value associated with that name.

     Examples

     If present,
            the TITLE attribute should provide the title of the document whose address is given by contains:

     <META HTTP-EQUIV="Expires"
     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CONTENT="Tue, 04 Dec 1993 21:29:02 GMT">
     <meta http-equiv="Keywords" CONTENT="Fred, Barney">
     <META HTTP-EQUIV="Reply-to"
     &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;content="fielding@ics.uci.edu (Roy Fielding)">

     then the HREF attribute.
 
            The TITLE attribute is useful for at least two reasons.
            The HTML user agent server (if so configured) may display include the title following
     headers:

     Expires: Tue, 04 Dec 1993 21:29:02 GMT
     Keywords: Fred, Barney
     Reply-to: fielding@ics.uci.edu (Roy Fielding)

     as part of the
            document prior HTTP response to retrieving it, for example, as a
            margin note GET or on a small box while HEAD request for
     that document.

     When the mouse HTTP-EQUIV attribute is over
            the anchor, or while not present, the document is being loaded.
            Another reason is that documents that are server
     should not marked up
            text, such as graphics, plain text generate an HTTP response header for the
     metainformation; e.g.,

     <META NAME="IndexType" CONTENT="Service">

     would never generate an HTTP response header, but would
     still allow HTML interpreters to identify and Gopher menus, do
            not have titles. make use of
     that metainformation.

     The TITLE attribute can Meta element should never be used to
            provide a title to such documents. When using the TITLE
            attribute, the title define information
     that should be valid and unique for the
            destination document.

         REL

            Level 1

            The REL attribute gives the relationship(s) described by
            the hypertext link from associated with an existing HTML element. An
     example of an inappropriate use of the anchor Meta element is:

     <META NAME="Title" CONTENT="The Etymology of
     Dunsel">

     Do not name an HTTP-EQUIV equal to the target. The

Berners-Lee, Connolly, et. al.                                  Page 24

                                HTML 2.0                February 8, 1995


            value is a comma-separated list of relationship values.
            Values and their semantics will response header that
     should normally only be registered generated by the
            HTML registration authority. The default relationship if
            none other is given is void. The REL attribute is only
            used when HTTP server.
     Example names that are inappropriate include ``Server'',
     ``Date'', and ``Last-modified'' - the HREF attribute exact list of
     inappropriate names is present.

         REV dependent on the particular server
     implementation. We recommend that servers ignore any META
     elements which specify HTTP-equivalents which are equal
     (case-insensitively) to their own reserved response headers.


4.9. Nextid 

     <NEXTID> Level 1 0

     The REV Nextid element is a parameter read and generated by text
     editing software to create unique identifiers. This tag
     takes a single attribute which is the same as the REL attribute, but
            the semantics of the link type are in the reverse
            direction. A link from A next document-wide
     alpha- numeric identifier to B with REL="X" expresses be allocated of the
            same relationship as form z123:

     <NEXTID N=Z27>

     When modifying a link from B to A with REV="X". An document, existing anchor identifiers
     should not be reused, as these identifiers may have both REL and REV attributes.

         URN

            Level 1

            If present, the URN attribute specifies a uniform
            resource name (URN) for a target document. The format of
            URNs is under discussion (1994) be referenced
     by various working
            groups of the Internet Engineering Task Force.

         METHODS

            The METHODS attributes other documents. Human writers of anchors and links provide
            information about the functions that the user HTML usually use
     mnemonic alphabetical identifiers.

     HTML interpreters may
            perform on an object. These are more accurately given by ignore the HTTP protocol when it is used, but it may, for
            similar reasons as Nextid element. Support for
     the TITLE attribute, be useful to
            include the information in advance Nextid element does not impact HTML interpreters in the link. For
            example, the any
     way.


5. Character Content 

     An HTML user agent may chose a different
            rendering should present the body of an HTML
     document as a function collection of the methods allowed; typeset paragraphs and
     preformatted text. Except for
            example, something that the <PRE> element, each block
     structuring element is searchable may get regarded as a
            different icon.

            The value paragraph by taking the
     data characters in its content and the content of its
     descendant elements, concatenating them, and splitting the METHODS attribute is a comma
     result into words, separated
            list of HTTP methods supported by the object for public
            use.

            See also: 2.7.4 Link

      2.8.4 Blockquote

         <BLOCKQUOTE> ... </BLOCKQUOTE>

         Level 0


Berners-Lee, Connolly, et. al.                                  Page 25

                                HTML 2.0                February 8, 1995 space, tab, or record end
     characters (and perhaps hyphen characters). The Blockquote element sequence of
     words is used to contain text quoted
         from another source.

         A typical rendering might be a slight extra left and
         right indent, and/or italic font. The Blockquote element
         causes typeset as a paragraph break, and typically provides space
         above and below the quote.

         Single-font rendition may reflect the quotation style of
         Internet mail by putting breaking it into lines.


5.1. The ISO Latin 1 Character Repertoire 

     The minimum character repertoire supported by all conforming
     HTML user agents is Latin Alphabet Nr. 1, or simply Latin-1.
     Latin-1 includes characters from most Western European
     languages, as well as a vertical line number of graphic control characters.
     Latin-1 also includes a non-breaking space, a soft hyphen
     indicator, 93 graphical characters, such as 8 unassigned characters,
     and 25 control characters.

          NOTE - Use the greater than symbol (>), in non-breaking space and soft hyphen
          indicator characters is discouraged because support for
          them is not widely deployed.

     In SGML applications, the
         left margin.

         Example use of use:

         I think the poem ends
         <BLOCKQUOTE>
         <P>Soft you now, control characters is
     limited in order to maximize the fair Ophelia. Nymph, chance of successful
     interchange over heterogeneous networks and operating
     systems. In HTML, only three control characters are allowed:
     Horizontal Tab (HT, encoded as 9 decimal in thy orisons, be all my sins remembered.
         </BLOCKQUOTE>
         but I am not sure.

      2.8.5 Headings

         <H1> ... </H1> through <H6> ... </H6>
   
         Level 0 US-ASCII and
     ISO-8859-1), Carriage Return, and Line Feed.

     The HTML defines six levels DTD references the Added Latin 1 entity set, to
     allow mnemonic representation of heading. A Heading element
         implies all Latin 1 characters using
     only the font changes, paragraph breaks before widely supported ASCII character repertoire. For
     example:

     Kurt G&ouml;del was a famous logician and after, mathematician.

     See 11.4.2, "ISO Latin 1 Character Entity Set" for a table
     of the ``Added Latin 1'' entities, and white space necessary to render 14.1, "The ISO-8859-1
     Coded Character Set" for a table of the
         heading.

         The highest level code positions of headings is H1, followed by H2 ...
         H6.

         Example
     ISO-8859-1.


6. Data Elements 


6.1. Line Break 

     <BR> Level 0

     The Line Break element specifies that a new line must be
     started at the given point. A new line indents the same as
     that of line-wrapped text.

     Example of use:

         <H1>This

     <P> Pease porridge hot<BR>
     Pease porridge cold<BR>
     Pease porridge in the pot<BR>
     Nine days old.


6.2. Horizontal Rule 

     <HR> Level 0

     A Horizontal Rule element is a heading</H1>
         Here is some divider between sections of
     text
         <H2>Second level heading</H2>
         Here is some more text.

         The rendering such as a full width horizontal rule or equivalent
     graphic.

     Example of headings use:

     <HR>
     <ADDRESS>February 8, 1995, CERN</ADDRESS>
     </BODY>


6.3. Image 

     <IMG> Level 0

     The Image element is determined by used to incorporate in-line graphics
     (typically icons or small graphics) into an HTML document.
     This element cannot be used for embedding other HTML text.

     HTML interpreters that cannot render in-line images ignore
     the Image element unless it contains the ALT attribute. Note
     that some HTML user
         agent, interpreters can render linked graphics but typical renderings are:

         <H1> ... </H1>

            Bold, very-large font, centered. One
     not in-line graphics. If a graphic is essential, you may
     want to create a link to it rather than to put it in-line.
     If the graphic is not essential, then the Image element is
     appropriate.

     The Image element, which is empty (no closing tag), has
     these attributes:

     ALIGN
                    The ALIGN attribute accepts the values TOP or two blank lines
            above and below.

Berners-Lee, Connolly, et. al.                                  Page 26

                                HTML 2.0                February 8, 1995



         <H2> ... </H2>

            Bold, large font, flush-left. One
                    MIDDLE or two blank lines
            above and below.

         <H3> ... </H3>

            Italic, large font, slightly indented from BOTTOM, which specifies if the left
            margin. One or two blank lines above and below.

         <H4> ... </H4>

            Bold, normal font, indented more than H3. One blank following
                    line
            above and below.

         <H5> ... </H5>

            Italic, normal font, indented of text is aligned with the top, middle, or
                    bottom of the graphic.

     ALT
                    Optional text as H4. One blank line
            above.

         <H6> ... </H6>

            Bold, indented same an alternative to the graphic for
                    rendering in non-graphical environments. Alternate
                    text should be provided whenever the graphic is
                    not rendered. Alternate text is mandatory for
                    Level 0 documents. Example of use:

     <IMG SRC="triangle.xbm" ALT="Warning:"> Be sure
     to read these instructions.

     ISMAP
                    The ISMAP (is map) attribute identifies an image
                    as normal text, more than H5. One
            blank line above.

         Although heading levels an image map. Image maps are graphics in which
                    certain regions are mapped to URIs. By clicking on
                    different regions, different resources can be skipped (for example,
                    accessed from H1 the same graphic. Example of use:

     <A HREF="http://machine/htbin/imagemap/sample">
     <IMG SRC="sample.xbm" ISMAP>
     </A>

     SRC
                    The value of the SRC attribute is the URI of the
                    document to H3), this practice be embedded; only images can be
                    embedded, not HTML text. Its syntax is discouraged the same as skipping
         heading levels may produce unpredictable results when
         generating other representations from HTML.

   2.9 Overview
                    that of the HREF attribute of the `<A>' tag. SRC
                    is mandatory. Image elements are allowed within
                    anchors.

     Example of Character-Level use:

     <IMG SRC="triangle.xbm">Be sure to read these
     instructions.


7. Character Format Elements

      Level 2 (all elements)

      Character-level 

     Character format elements are used to specify either the
     logical meaning or the physical appearance of marked text
     without causing a paragraph break. Like most other elements, character-level
     character format elements include both opening and closing
     tags. Only the characters between the tags are affected:

     This is <EM>emphasized</EM> text.

      Character-level

     Character format tags may be ignored by minimal HTML
     applications.

      Character-level

     Character format tags are interpreted from left to right as
     they appear in the flow of text. Level 1 HTML user
      agents interpreters must
     render highlighted text distinctly from

Berners-Lee, Connolly, et. al.                                  Page 27

                                HTML 2.0                February 8, 1995 plain text.
     Additionally, EM content must be rendered as distinct from
     STRONG content, and B content must rendered as distinct from
     I content.

      Character-level

     Character format elements may be nested within the content
     of other character-level elements; character format elements; however, HTML
      user agents
     interpreters are not required to render nested character-
      level character
     format elements distinctly from non-nested elements:

     plain <B>bold <I>italic</I></B> may the rendered
     the same as plain <B>bold </B><I>italic</I>


7.1. Semantic Format Elements 

     Note that typical renderings for information type semantic format elements
     vary between applications. If a specific rendering is necessary,
     necessary - for example, when referring to a specific text
     attribute as in "The ``The italic parts are
      mandatory", mandatory'' - a
     physical formating element can be used to ensure that the
     intended rendered is used where possible.

   2.10 Information Type Elements

     Note that different information type sematic elements may be rendered in the
     same way.

      2.10.1


7.1.1. Citation 

     <CITE>...</CITE> Level 1

     The Citation element specifies a citation; citation, typically
     rendered as italics.

      2.10.2


7.1.2. Code 

     <CODE> ... </CODE> Level 1

     The Code element indicates an example of code; code, typically
     rendered as in a monospaced . Do font. This should not confuse be confused
     with the Preformatted Text element.

      2.10.3


7.1.3. Emphasis 

     <EM> ... </EM> Level 1

     The Emphasis element indicates typographic emphasis,
     typically rendered as italics.

      2.10.4


7.1.4. Keyboard 

     <KBD> ... </KBD>

Berners-Lee, Connolly, et. al.                                  Page 28

                                HTML 2.0                February 8, 1995 Level 1

     The Keyboard element indicates text typed by a user; user,
     typically rendered as in a monospaced . It might font. This is commonly be
     used in an instruction manual.

      2.10.5 manuals.


7.1.5. Sample 

     <SAMP> ... </SAMP> Level 1

     The Sample element indicates a sequence of literal
         characters;
     characters, typically rendered as  monospaced.

      2.10.6 in a monospaced font.


7.1.6. Strong 

     <STRONG> ... </STRONG> Level 1

     The Strong element indicates strong typographic emphasis,
     typically rendered in bold.

      2.10.7


7.1.7. Variable 

     <VAR> ... </VAR> Level 1

     The Variable element indicates a variable name; name, typically
     rendered as italic.

   2.11 Character


7.2. Physical Format Elements

      Character 

     Physical format elements are used to specify the format of
     marked text. Example of use:

      2.11.1


7.2.1. Bold 

     <B> ... </B> Level 1

     The Bold element specifies that the text should be rendered
     in boldface, where available. Otherwise, an alternative
     mapping is allowed.

      2.11.2


7.2.2. Italic 

     <I> ... </I> Level 1

     The Italic element specifies that the text should be
     rendered in an italic font, where available. Otherwise, an
     alternative mapping is allowed.

      2.11.3


7.2.3. Teletype 

     <TT> ... </TT>

Berners-Lee, Connolly, et. al.                                  Page 29

                                HTML 2.0                February 8, 1995 Level 1

     The Teletype element specifies that the text should be
     rendered in a fixed-width typewriter font.

   2.12 Image Element

      <IMG>


8. Hyperlink Elements 


8.1. Anchor 

     <A> ... </A> Level 0

      The Image element

     An anchor is used to incorporate in-line
      graphics (typically icons or small graphics) into an
      HTML document. This element cannot be used for embedding
      other HTML text.

      HTML user agents that cannot render in-line images
      ignore the Image element unless it contains the ALT
      attribute. Note that some HTML user agents can render
      linked graphics but not in-line graphics. If a graphic marked section of text that is essential, you may want to create a link to it rather
      than to put it in-line. If the graphic is not essential,
      then start
     and/or destination of a hypertext link. Anchor elements are
     defined by the Image element is appropriate.

      The Image element, which is empty (no closing tag), has
      these attributes:

      ALIGN `<A>' tag. The ALIGN attribute `<A>' tag accepts the values TOP or MIDDLE or
         BOTTOM, which specifies if the following line several
     attributes; at least one of text is
         aligned with the top, middle, or bottom NAME and HREF attributes is
     required.

     Attributes of the graphic.

      ALT

         Optional text as an alternative to the graphic for
         rendering in non-graphical environments. Alternate text
         should be provided whenever `<A>' tag:


8.1.1. HREF 

     If the graphic HREF attribute is not rendered.
         Alternate present, the text between the
     opening and closing anchor tags becomes hypertext. If this
     hypertext is mandatory for Level 0 documents.
         Example of use:

         <IMG SRC="triangle.gif" ALT="Warning:"> Be sure to read
         these instructions.

      ISMAP

         The ISMAP (is map) attribute identifies an image as an
         image map. Image maps are graphics in which certain
         regions selected by readers, they are mapped moved to URLs. By clicking on different
         regions, another
     document, or to a different resources can be accessed from location in the
         same graphic. Example current
     document, whose network address is defined by the value of use:

Berners-Lee, Connolly, et. al.                                  Page 30

                                HTML 2.0                February 8, 1995
     the HREF attribute.

     Example:

     See <A HREF="http://machine/htbin/imagemap/sample">
         <IMG SRC="sample.gif" ISMAP>
         </A>
  
      SRC HREF="http://www.hal.com/">HaL</A>'s
     information for more details.

     In this example, selecting ``HaL'' takes the reader to a
     document at http://www.hal.com. The value format of the SRC attribute network
     address is specified in the URL of URI specification for print
     readers.

     With the
         document to be embedded; only images HREF attribute, the form HREF=``#identifier'' can be embedded,
         not HTML text. Its syntax is
     refer to another anchor in the same as that of document.

     Example:

     The <A HREF="#glossary">glossary</A> defines
     terms used in this document.

     In this example, selecting ``glossary'' takes the
         HREF reader to
     another anchor (i.e., <A NAME=``glossary''>Glossary</A>) in
     the same document. The NAME attribute of is described below. If
     the <A> tag. SRC anchor is mandatory. Image
         elements are allowed within anchors.

         Example of use:

         <IMG SRC ="triangle.gif">Be sure in another document, the HREF attribute may be
     relative to the document's address or the specified base
     address (see 4.5, "Base").


8.1.2. NAME 

     If present, the NAME attribute allows the anchor to read these
         instructions.

   2.13 List Elements

      HTML supports several types of lists, all of which may be nested.

      2.13.1 Definition List

         <DL> ... </DL>

         Level 0

         A definition list is the
     target of a list link. The value of terms and corresponding
         definitions. Definition lists are typically formatted
         with the term flush-left and NAME attribute is an
     identifier for the definition, formatted
         paragraph style, indented after anchor. Identifiers are arbitrary strings
     but must be unique within the term. HTML document.

     Example of use:

         <DL>
         <DT>Term<DD>This

     <A NAME="coffee">Coffee</A> is the definition an example of the first term.
         <DT>Term<DD>This ...
     ... An example of this is <A HREF="#coffee">coffee</A>.

     Another document can then make a reference explicitly to
     this anchor by putting the definition of identifier after the second term.
         </DL> address,
     separated by a hash sign:

     <A HREF="drinks.html#coffee">


8.1.3. TITLE 

     The TITLE attribute is informational only. If present, the DT term does not fit in
     TITLE attribute should provide the DT column (one third title of the display area), it may be extended across the page
         with the DD section moved to document
     whose address is given by the next line, or it HREF attribute. The TITLE
     attribute is useful for at least two reasons. The HTML
     interpreter may be
         wrapped onto successive lines of display the left hand column.

         Single occurrences title of the document prior to
     retrieving it, for example, as a <DT> tag without margin note or on a subsequent
         <DD> tag are allowed, and have small
     box while the same significance as
         if mouse is over the <DD> tag had been present with no text.


Berners-Lee, Connolly, et. al.                                  Page 31

                                HTML 2.0                February 8, 1995


         The opening list tag must be <DL> and must be
         immediately followed by anchor, or while the first term (<DT>).
     document is being loaded. Another reason is that documents
     that are not marked up text, such as graphics, plain text
     and Gopher menus, do not have titles. The definition list type TITLE attribute
     can take the COMPACT attribute,
         which suggests that a compact rendering be used, because
         the list items are small and/or the entire list is
         large.

         Unless you used to provide a title to such documents. When using
     the COMPACT TITLE attribute, the HTML user
         agent may leave white space between successive DT, DD
         pairs.The COMPACT title should be valid and unique
     for the destination document.


8.1.4. REL 

     The REL attribute may also reduce gives the width of relationship(s) described by the left-hand (DT) column.

         If using
     hypertext link from the COMPACT attribute, anchor to the opening target. The value is a
     whitespace-separated list tag
         must be <DL COMPACT>, which must of relationship names.
     Relationship names and their semantics will be immediately followed registered by
     the first <DT> tag:

         <DL COMPACT>
         <DT>Term<DD>This W3 Consortium. The default relationship is void. The REL
     attribute is only used when the first definition in compact format.
         <DT>Term<DD>This HREF attribute is present.


8.1.5. REV 

     The REV attribute is the second definition same as the REL attribute, but the
     semantics of the link type are in compact format.
         </DL>

      2.13.2 Directory List

         <DIR> ... </DIR>

         Level 0 the reverse direction. A
     link from A Directory List element is used to present B with REL=``X'' expresses the same
     relationship as a list of
         items containing up link from B to 20 characters each. Items in a
         directory list A with REV=``X''. An anchor
     may be arranged in columns, typically 24
         characters wide. have both REL and REV attributes.


8.1.6. URN 

     If present, the HTML user agent can optimize the
         column width as function URN attribute specifies a uniform resource
     name (URN) for a target document. The format of URNs is
     under discussion (1995) by various working groups of the widths
     Internet Engineering Task Force.


8.1.7. METHODS 

     The METHODS attributes of individual
         elements, so much anchors and links provide
     information about the better.

         A directory list must begin with functions that the <DIR> tag which is
         immediately followed user may perform on
     an object. These are more accurately given by a <LI> (list item) tag:

         <DIR>
         <LI>A-H<LI>I-M
         <LI>M-R<LI>S-Z
         </DIR>

      2.13.3 Menu List

         <MENU> ... </MENU>

         Level 0

         A menu list the HTTP
     protocol when it is used, but it may, for similar reasons as
     for the TITLE attribute, be useful to include the
     information in advance in the link. For example, the HTML
     interpreter may chose a list different rendering as a function of items with typically one line

Berners-Lee, Connolly, et. al.                                  Page 32

                                HTML 2.0                February 8, 1995


         per item. The menu list style is more compact than
     the
         style of an unordered list.

         A menu list must begin with a <MENU> tag which methods allowed; for example, something that is
         immediately followed by
     searchable may get a <LI> (list item) tag:

         <MENU>
         <LI>First item in different icon.

     The value of the list.
         <LI>Second item in METHODS attribute is a whitespace-separated
     list of HTTP methods supported by the list.
         <LI>Third item object for public use.


9. Block Structuring Elements 

     The following elements may be included in the list.
         </MENU>

      2.13.4 Ordered List

         <OL> body of an
     HTML document:


9.1. Paragraph 

     <P> ... </OL>
  
         Level 0

         The Ordered List element is used to present a numbered
         list of items, sorted by sequence or order of
         importance.

         An ordered list must begin with the <OL> tag which is
         immediately followed by a <LI> (list item) tag:

         <OL>
         <LI>Click the Web button to open the Open the URL window.
         <LI>Enter the URL number in the text field of the Open URL
         window. The Web document you specified is displayed.
         <LI>Click highlighted text to move from one link to another.
         </OL>

         The Ordered List element can take the COMPACT attribute,
         which suggests that a compact rendering be used.

      2.13.5 Unordered List

         <UL> ... </UL>

         Level 0

         The Unordered List element is used to present a list of
         items which is typically separated by white space and/or
         marked by bullets.

         An unordered list must begin with the <UL> tag which is
         immediately followed by a <LI> (list item) tag:

         <UL>
         <LI>First list item

Berners-Lee, Connolly, et. al.                                  Page 33

                                HTML 2.0                February 8, 1995


         <LI>Second list item
         <LI>Third list item
         </UL>

   2.14 Other Elements

      2.14.1 Paragraph

         <P> </P> Level 0

     The Paragraph element indicates a paragraph. The exact
     indentation, leading, leading space, etc. of a paragraph is not
     defined 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. This is typically not the case
     within the Address element and or is never the case within the
     Preformatted Text element. With some HTML
         user agents, interpreters, the
     first line in a paragraph is indented.

     Example of use:

     <H1>This Heading Precedes the Paragraph</H1>
     <P>This is the text of the first paragraph.
     <P>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. maintenance.</P>
     <P>This is the text of a third paragraph.

      2.14.2 paragraph.</P>


9.2. Preformatted Text 

     <PRE> ... </PRE> Level 0

     The Preformatted Text element presents blocks of text in
     fixed-width font, and so is suitable for text that has been
     formatted on screen.

     The <PRE> tag may be used with the optional WIDTH
         attribute, which is a Level 1 feature. attribute.
     The WIDTH attribute specifies the maximum number of
     characters for a line and allows the HTML user agent interpreter to
     select a suitable font and indentation. If the WIDTH
     attribute is not present, a width of 80 characters is
     assumed. Where the WIDTH attribute is supported, widths of
     40, 80 and 132 characters should be presented optimally,
     with other widths being rounded up.

Berners-Lee, Connolly, et. al.                                  Page 34

                                HTML 2.0                February 8, 1995

     Within preformatted text:

         -

          * Line breaks within the text are rendered as a move to
          the beginning of the next line.

         -  The <P> tag should not be used. If found, it should
            be rendered as a move to the beginning of the next line.

         -
          * Anchor elements and character highlighting elements
          may be used.

         -
          * Elements that define paragraph formatting (headings,
          address, etc.) must not be used.

         -
          * The horizontal tab character (encoded in US-ASCII and
          ISO-8859-1 as decimal 9) 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. Its use is not recommended however.

         NOTE:

          NOTE - Som historical documents contain <P> tags in
          <PRE> elements. User agents are engcouraged to treat
          this a a line break. A <P> tag followed by a newline
          character should produce only one line break, not a
          line break plus a blank line.

          NOTE - References to the "beginning ``beginning of a new line" 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.

     Example of use:

     <PRE WIDTH="80">
     This is an example line.
     </PRE>

         NOTE:

          NOTE - Within a Preformatted Text element, the
          constraint that the rendering must be on a fixed
          horizontal character pitch may limit or prevent the
          ability of the HTML user agent interpreter to faithfully render highlighting elements
         specially.

      2.14.3 Line Break

         <BR>
          character formatting elements.


9.3. Address 

     <ADDRESS> ... </ADDRESS> Level 0

     The Line Break Address element specifies that a new line must be
         started such information as address,
     signature and authorship, often at the given point. A new line indents the same

Berners-Lee, Connolly, et. al.                                  Page 35

                                HTML 2.0                February 8, 1995


         as that top or bottom of line-wrapped text. a
     document.

     Typically, an Address is rendered in an italic typeface and
     may be indented. The Address element implies a paragraph
     break before and after.

     Example of use:

         <P>
         Pease porridge hot<BR>
         Pease porridge cold<BR>
         Pease porridge in the pot<BR>
         Nine days old.

      2.14.4 Horizontal Rule

         <HR>

     <ADDRESS>
     Newsletter editor<BR>
     J.R. Brown<BR>
     JimquickPost News, Jumquick, CT 01234<BR>
     Tel (123) 456 7890
     </ADDRESS>


9.4. Blockquote 

     <BLOCKQUOTE> ... </BLOCKQUOTE> Level 0

         A Horizontal Rule

     The Blockquote element is used to contain text quoted from
     another source.

     A typical rendering might be a divider between sections slight extra left and right
     indent, and/or italic font. The Blockquote element causes a
     paragraph break, and typically provides space above and
     below the quote.

     Single-font rendition may reflect the quotation style of text
     Internet mail by putting a vertical line of graphic
     characters, such as a full width horizontal rule or
         equivalent graphic. the greater than symbol (>), in the left
     margin.

     Example of use:

         <HR>
         <ADDRESS>February 8, 1995, CERN</ADDRESS>
         </BODY>

   2.15 Form Elements

      Forms are created by placing input fields within
      paragraphs, preformatted/literal text, and lists. This
      gives considerable flexibility in designing

     I think the layout
      of forms.

      The following elements (all are HTML 2 features) are
      used to create forms:

         FORM

            A form within a document.

         INPUT

            One input field.

         OPTION

            One option within a Select element.

         SELECT


Berners-Lee, Connolly, et. al.                                  Page 36

                                HTML 2.0                February 8, 1995


            A selection from a finite set poem ends
     <BLOCKQUOTE>
     <P>Soft you now, the fair Ophelia. Nymph, in thy orisons, be all
     my sins remembered.
     </BLOCKQUOTE>
     but I am not sure.


9.5. Headings 

     <H1> ... </H1> through <H6> ... </H6> Level 0

     HTML defines six levels of options.

         TEXTAREA heading. A multi-line input field.

      Each variable field is defined by an Input, Textarea, or
      Option Heading element
     implies all the font changes, paragraph breaks before and must have an NAME attribute
     after, and white space necessary to
      identify its value in the data returned when render the form heading.

     The highest level of headings is
      submitted. H1, followed by H2 ... H6.

     Example of use (a questionnaire form):

         <H1>Sample Questionnaire</H1>
         <P>Please fill out this questionnaire:
         <FORM METHOD="POST" ACTION="http://www.hal.com/sample">
         <P>Your name: <INPUT NAME="name" size="48">
         <P>Male <INPUT NAME="gender" TYPE=RADIO VALUE="male">
         <P>Female <INPUT NAME="gender" TYPE=RADIO VALUE="female">
         <P>Number in family: <INPUT NAME="family" TYPE=text>
         <P>Cities in which you maintain use:

     <H1>This is a residence:
         <UL>
         <LI>Kent <INPUT NAME="city" TYPE=checkbox VALUE="kent">
         <LI>Miami <INPUT NAME="city" TYPE=checkbox VALUE="miami">
         <LI>Other <TEXTAREA NAME="other" cols=48 rows=4></textarea>
         </UL>
         Nickname: <INPUT NAME="nickname" SIZE="42">
         <P>Thank you for responding to this questionnaire.
         <P><INPUT TYPE=SUBMIT> <INPUT TYPE=RESET>
         </FORM>

      In the example above, the <P> and <UL> tags have been
      used to lay out the heading</H1>
     Here is some text and input fields.
     <H2>Second level heading</H2>
     Here is some more text.

     The HTML user
      agent rendering of headings is responsible for handling which field will
      currently get keyboard input.

      Many platforms have existing conventions for forms, for
      example, using Tab and Shift keys to move the keyboard
      focus forwards and backwards between fields, and using determined by the Enter key to submit the form. In the example, the
      SUBMIT HTML
     interpreter, but typical renderings are:

     <H1> ... </H1>
                    Bold, very-large font, centered. One or two blank
                    lines above and RESET buttons are specified explicitly with
      special purpose fields. The SUBMIT button is used to e-
      mail the form below.

     <H2> ... </H2>
                    Bold, large font, flush-left. One or send its contents to the server as
      specified by the ACTION attribute, while RESET resets
      the fields to their initial values. When the form
      consists of a single text field, it may be appropriate
      to leave such buttons out two blank
                    lines above and rely on the Enter key.

      The Input element is used for a below.

     <H3> ... </H3>
                    Italic, large variety of types
      of input fields.

Berners-Lee, Connolly, et. al.                                  Page 37

                                HTML 2.0                February 8, 1995



      To let users enter font, slightly indented from the
                    left margin. One or two blank lines above and
                    below.

     <H4> ... </H4>
                    Bold, normal font, indented more than one H3. One
                    blank line of text, use the
      Textarea element.

      2.15.1 Representing Choices

         The radio button above and checkbox types of input field below.

     <H5> ... </H5>
                    Italic, normal font, indented as H4. One blank
                    line above.

     <H6> ... </H6>
                    Bold, indented same as normal text, more than H5.
                    One blank line above.

     Although heading levels can be used skipped (for example, from H1
     to specify multiple choice forms in which every
         alternative H3), this practice is visible discouraged as part skipping heading
     levels may produce unpredictable results when generating
     other representations from HTML.


9.6. List Elements 

     HTML supports several types of lists, all of the form. An
         alternative is to use the Select element which is
         typically rendered in a more compact fashion as a pull
         down combo list.

      2.15.2 Form

         <FORM> may be
     nested.


9.6.1. Definition List 

     <DL> ... </FORM> </DL> Level 2

         The Form element 0

     A definition list is used to delimit a data input form.
         There can be several forms in a single document, but list of terms and corresponding
     definitions. Definition lists are typically formatted with
     the
         Form element can't be nested.

         The ACTION attribute is a URL specifying term flush-left and the location to
         which definition, formatted paragraph
     style, indented after the contents term.

     Example of the form is submitted to elicit a
         response. If the ACTION attribute use:

     <DL>
     <DT>Term<DD>This is missing, the URL definition of the document itself is assumed. The way data first term.
     <DT>Term<DD>This is
         submitted varies with the access protocol definition of the URL,
         and with second term.
     </DL>

     If the values of DT term does not fit in the METHOD and ENCTYPE
         attributes.

         In general:

         - DT column (one third of
     the METHOD attribute selects variations in display area), it may be extended across the
            protocol.

         - page with
     the ENCTYPE attribute specifies DD section moved to the format next line, or it may be wrapped
     onto successive lines of the
            submitted data in case the protocol does not impose left hand column.

     Single occurrences of a
            format itself.

         The Level 2 specification defines <DT> tag without a subsequent <DD>
     tag are allowed, and requires support
         for the HTTP access protocol only.

         When have the ACTION attribute is set to an HTTP URL, same significance as if the
         METHOD attribute
     <DD> tag had been present with no text.

     The opening list tag must be set to an HTTP method as
         defined by the HTTP method specification in <DL> and must be immediately
     followed by the IETF
         draft HTTP standard. first term (<DT>).

     The default METHOD is GET, although
         for many applications, definition list type can take the POST method may COMPACT attribute,
     which suggests that a compact rendering be preferred.
         With used, because the post method,
     list items are small and/or the ENCTYPE attribute entire list is a MIME
         type specifying large.

     Unless you provide the format of COMPACT attribute, the posted data; by

Berners-Lee, Connolly, et. al.                                  Page 38 HTML 2.0                February 8, 1995


         default, is application/x-www-form-urlencoded.

         Under any protocol, the submitted contents of the form
         logically consist of name/value
     interpreter may leave white space between successive DT, DD
     pairs. The names are
         usually equal to COMPACT attribute may also reduce the NAME attributes width of
     the various
         interactive elements in left-hand (DT) column.

     If using the form.

         NOTE: The names are not guaranteed to be unique keys,
         nor are COMPACT attribute, the names of form elements required to opening list tag must be
         distinct. The values encode
     <DL COMPACT>, which must be immediately followed by the user's input to
     first <DT> tag:

     <DL COMPACT>
     <DT>Term<DD>This is the
         corresponding interactive elements. Elements capable of
         displaying a textual or numerical value will return a
         name/value pair even when they receive no explicit user
         input.

      2.15.3 Input

      <INPUT> first definition in compact format.
     <DT>Term<DD>This is the second definition in compact format.
     </DL>


9.6.2. Directory List 

     <DIR> ... </DIR> Level 2

      The Input 0

     A Directory List element represents is used to present a field whose contents list of items
     containing up to 20 characters each. Items in a directory
     list may be edited by arranged in columns, typically 24 characters
     wide. If the user.

      Attributes HTML interpreter can optimize the column width
     as function of the Input element:

      ALIGN

         Vertical alignment widths of individual elements, so much
     the image. For use only better.

     A directory list must begin with
         TYPE=IMAGE in HTML level 2. The possible values are
         exactly the same as for the ALIGN attribute of the image
         element.

      CHECKED

         Indicates that <DIR> tag which is
     immediately followed by a checkbox or radio button <LI> (list item) tag:

     <DIR>
     <LI>A-H<LI>I-M
     <LI>M-R<LI>S-Z
     </DIR>


9.6.3. Menu List 

     <MENU> ... </MENU> Level 0

     A menu list is selected.
         Unselected checkboxes and radio buttons do not return
         name/value pairs when the form a list of items with typically one line per
     item. The menu list style is submitted.

      MAXLENGTH

         Indicates more compact than the maximum number style of characters that can be
         entered into
     an unordered list.

     A menu list must begin with a text field. This can be greater than
         specified <MENU> tag which is
     immediately followed by a <LI> (list item) tag:

     <MENU>
     <LI>First item in the SIZE attribute, list.
     <LI>Second item in which case the field
         will scroll appropriately. The default number of
         characters is unlimited.

      NAME

         Symbolic name used when transferring list.
     <LI>Third item in the form's

Berners-Lee, Connolly, et. al.                                  Page 39

                                HTML 2.0                February 8, 1995


         contents. list.
     </MENU>


9.6.4. Ordered List 

     <OL> ... </OL> Level 0

     The NAME attribute is required for most input
         types and Ordered List element is normally used to provide a unique
         identifier for a field, or for present a logically related group numbered list
     of fields.

      SIZE

         Specifies the size items, sorted by sequence or precision order of the field according
         to its type. For example, to specify a field importance.

     An ordered list must begin with the <OL> tag which is
     immediately followed by a
         visible width of 24 characters:

         INPUT TYPE=text SIZE="24"

      SRC

         A URL or URN specifying an image. For use only with
         TYPE=IMAGE in HTML Level 2.

      TYPE

         Defines the type of data <LI> (list item) tag:

     <OL>
     <LI>Click the field accepts. Defaults Web button to
         free text. Several types of fields can be defined with open the type attribute:

         CHECKBOX

            Used for simple Boolean attributes, or for attributes
            that can take multiple values at Open the same time. The
            latter is represented by a number of checkbox fields
            each of which has URI window.
     <LI>Enter the same name. Each selected checkbox
            generates a separate name/value pair URI number in the submitted
            data, even if this results in duplicate names. The
            default value for checkboxes is "on".

         HIDDEN

            No text field is presented to the user, but the content of the field Open URI
     window. The Web document you specified is sent with the submitted form. This value
            may be used displayed.
     <LI>Click highlighted text to transmit state information about
            client/server interaction.

         IMAGE

            An image field upon which you move from one link to another.
     </OL>

     The Ordered List element can click with a pointing
            device, causing take the form to COMPACT attribute,
     which suggests that a compact rendering be immediately submitted. used.


9.6.5. Unordered List 

     <UL> ... </UL> Level 0

     The coordinates of the selected point are measured in
            pixel units from the upper-left corner Unordered List element is used to present a list of the image, and
            are returned (along
     items which is typically separated by white space and/or
     marked by bullets.

     An unordered list must begin with the other contents of the form)
            in two name/value pairs. The x-coordinate <UL> tag which is submitted
            under the name of the field with .x appended,
     immediately followed by a <LI> (list item) tag:

     <UL>
     <LI>First list item
     <LI>Second list item
     <LI>Third list item
     </UL>


10. Form-based Input Elements 

     Forms are created by placing input fields within paragraphs,
     preformatted/literal text, and lists. This gives
     considerable flexibility in designing the y-

Berners-Lee, Connolly, et. al.                                  Page 40

                                HTML 2.0                February 8, 1995


            coordinate is submitted under the name layout of the field with
            .y appended. Any VALUE attribute is ignored. forms.

     The image
            itself is specified by the SRC attribute, exactly as for
            the Image element.

            NOTE: In following elements are used to create forms:

     FORM
                    A form within a future version of the HTML specification, the
            IMAGE functionality may be folded into an enhanced
            SUBMIT document.

     INPUT
                    One input field.

         PASSWORD is the same as the TEXT attribute, except that
         text is not displayed as it is entered.

         RADIO is used for attributes that accept

     OPTION
                    One option within a single value Select element.

     SELECT
                    A selection from a finite set of alternatives. options.

     TEXTAREA
                    A multi-line input field.

     Each radio button variable field in
         the group should be given the same name. Only the
         selected radio button in the group generates a
         name/value pair in the submitted data. Radio buttons
         require an explicit VALUE attribute.

         RESET is a button that when pressed resets the form's
         fields to their specified initial values. The label defined by an Input, Textarea, or
     Option element and must have an NAME attribute to
         be displayed on the button may be specified just as for identify
     its value in the SUBMIT button.

         SUBMIT is a button that data returned when pressed submits the form.
         You can form is submitted.

     Example of use the VALUE attribute to provide (a questionnaire form):

     <H1>Sample Questionnaire</H1>
     <P>Please fill out this questionnaire:
     <FORM METHOD="POST" ACTION="http://www.w3.org/sample">
     <P>Your name: <INPUT NAME="name" size="48">
     <P>Male <INPUT NAME="gender" TYPE=RADIO VALUE="male">
     <P>Female <INPUT NAME="gender" TYPE=RADIO VALUE="female">
     <P>Number in family: <INPUT NAME="family" TYPE=text>
     <P>Cities in which you maintain a non-
         editable label residence:
     <UL>
     <LI>Kent <INPUT NAME="city" TYPE=checkbox VALUE="kent">
     <LI>Miami <INPUT NAME="city" TYPE=checkbox VALUE="miami">
     <LI>Other <TEXTAREA NAME="other" cols=48 rows=4></textarea>
     </UL>
     Nickname: <INPUT NAME="nickname" SIZE="42">
     <P>Thank you for responding to be displayed on this questionnaire.
     <P><INPUT TYPE=SUBMIT> <INPUT TYPE=RESET>
     </FORM>

     In the button. example above, the <P> and <UL> tags have been used
     to lay out the text and input fields. The
         default label is application-specific.  If a SUBMIT
         button HTML interpreter
     is pressed in order responsible for handling which field will currently get
     keyboard input.

     Many platforms have existing conventions for forms, for
     example, using Tab and Shift keys to submit move the form, keyboard focus
     forwards and that
         button has a NAME attribute specified, then that button
         contributes a name/value pair backwards between fields, and using the Enter
     key to submit the submitted data.
         Otherwise, a form. In the example, the SUBMIT and RESET
     buttons are specified explicitly with special purpose
     fields. The SUBMIT button makes no contribution to the
         submitted data.

         TEXT is used for a single line text entry fields. Use in
         conjunction with to e-mail the SIZE and MAXLENGTH attributes. Use form or send
     its contents to the server as specified by the ACTION
     attribute, while RESET resets the Textarea element for text fields which can accept
         multiple lines.

      VALUE

         The to their initial displayed value of
     values. When the field, if it displays
         a textual or numerical value; or the value to form consists of a single text field, it
     may be
         returned when appropriate to leave such buttons out and rely on the field is selected, if it displays a
         Boolean value. This attribute is required for radio
         buttons.

      2.15.4 Option

         <OPTION>

Berners-Lee, Connolly, et. al.                                  Page 41

                                HTML 2.0                February 8, 1995



         Level 2
     Enter key.

     The Option Input element can only occur within is used for a Select
         element. It represents large variety of types of
     input fields.

     To let users enter more than one choice, and can take these
         attributes:

         DISABLED

            Proposed.

         SELECTED

            Indicates that this option is initially selected.

         VALUE

            When present indicates the value to be returned if this
            option is chosen. The returned value defaults to the
            contents line of text, use the Option
     Textarea element.

     The contents radio button and checkbox types of the Option element is presented input field can be
     used to specify multiple choice forms in which every
     alternative is visible as part of the
            user form. An alternative
     is to represent use the option. It Select element which is used typically rendered in
     a more compact fashion as a returned
            value if the VALUE attribute is not present.

      2.15.5 Select

         <SELECT NAME=... > pull down combo list.


10.1. Form 

     <FORM> ... </SELECT> </FORM> Level 2

     The Select Form element allows the user is used to chose one of delimit a set
         of alternatives described by textual labels. Every
         alternative is represented by data input form. There
     can be several forms in a single document, but the Option element.

         Attributes are:

         ERROR

            Proposed.

         MULTIPLE Form
     element can't be nested.

     The MULTIPLE ACTION attribute is needed when users are allowed
            to make several selections, e.g. <SELECT MULTIPLE>.

         NAME

            Specifies a URI specifying the name that will submitted as a name/value
            pair.

Berners-Lee, Connolly, et. al.                                  Page 42

                                HTML 2.0                February 8, 1995



         SIZE

            Specifies location to
     which the number contents of visible items. If this is
            greater than one, then the resulting form control will
            be a list.

         The Select element is typically rendered as submitted to elicit a pull down
         or pop-up list. For example:

         <SELECT NAME="flavor">
         <OPTION>Vanilla
         <OPTION>Strawberry
         <OPTION>Rum and Raisin
         <OPTION>Peach and Orange
         </SELECT>
     response. If no option is initially marked as selected, then the
         first item listed ACTION attribute is selected.

      2.15.6 Text Area

         <TEXTAREA> ... </TEXTAREA>

         Level 2

         The Textarea element lets users enter more than one line missing, the URI of text. For example:

         <TEXTAREA NAME="address" ROWS=64 COLS=6>
         HaL Computer Systems
         1315 Dell Avenue
         Campbell, California 95008
         </TEXTAREA>

         The text up to the end tag (</TEXTAREA>)
     document itself is used to
         initialize the field's value. This end tag assumed. The way data is always
         required even if submitted varies
     with the field is initially blank. When
         submitting a form, lines in a TEXTAREA should be
         terminated using CR/LF.

         In a typical rendering, access protocol of the ROWS URI, and COLS attributes
         determine with the visible dimension values of
     the field METHOD and ENCTYPE attributes.

     In general:

          * the METHOD attribute selects variations in
         characters. The field is rendered the
          protocol.
          * the ENCTYPE attribute specifies the format of the
          submitted data in case the protocol does not impose a fixed-width font.
         HTML user agents should allow text
          format itself.

     When the ACTION attribute is set to extend beyond
         these limits by scrolling as needed.

         NOTE: In an HTTP URL, the initial design METHOD
     attribute must be set to an HTTP method [HTTP]. The default
     method is GET, although for forms, multi-line text
         fields were supported by many applications the Input element with
         TYPE=TEXT. Unfortunately, this causes problems for

Berners-Lee, Connolly, et. al.                                  Page 43

                                HTML 2.0                February 8, 1995


         fields with long text values. SGML's default (Reference
         Quantity Set) limits POST
     method is preferred. With the length of attribute literals to
         only 240 characters. The HTML 2.0 SGML declaration
         increases POST method, the limit to 1024 characters.

   2.16 Character Data

      Level 0

      The characters between HTML tags represent text. A HTML document
      (including tags and text) ENCTYPE
     attribute is encoded using the coded character
      set specified by a media type specifying the "charset" parameter format of the "text/html"
      media type.  For levels defined in this specification,
     posted data; the
      "charset" parameter default is restricted to "US-ASCII" or "ISO-8859-1".
      ISO-8859-1 encodes a set of characters known as Latin Alphabet
      No. 1, or simply Latin-1.  Latin-1 includes characters from most
      Western European languages, as well as a number
     ``application/x-www-form-urlencoded''.

     The submitted contents of control
      characters.  Latin-1 also includes a non-breaking space, a soft
      hyphen indicator, 93 graphical characters, 8 unassigned
      characters, and 25 control characters.

      Because non-breaking space and soft hyphen indicator are
      not recognized and interpreted by all HTML user agents,
      their use is discouraged.

      There are 58 character positions occupied by control
      characters. See Section 2.16.2 for details on the
      interpretation form logically consist of control characters.

      Because certain special characters
     name/value pairs. The names are subject usually equal to
      interpretation and special processing, information
      providers and HTML user agent implementors should follow the guidelines NAME
     attributes of the various interactive elements in Section 2.16.1.

      In addition, HTML provides
      character entity references (see Section 2.17.2) and
      numerical character references (see Section 2.17.3) the form.

          NOTE - The names are not guaranteed to
      facilitate be unique keys,
          nor are the entry and interpretation names of characters by
      name and by numerical position.

      Because certain characters will form elements required to be interpreted as
      markup, they must
          distinct. The values encode the user's input to the
          corresponding interactive elements. Fields with null
          values may be represented omitted from the returned list of
          name/value pairs, whereas those with non-null values
          should be included (even if the value was not altered
          by entity references as described
      in Section 2.16.3 the user). In particular, unselected radio buttons
          and Section 2.16.4.

      2.16.1 Special Characters

         Certain characters have special meaning in HTML
         documents. There are two printing characters which checkboxes should be excluded from the contents
          list.


10.2. Input 

     <INPUT> Level 2

     The Input element represents a field whose contents may be interpreted
     edited by an HTML application to have an effect the user.

     Attributes of the format Input element:

     ALIGN
                    Vertical alignment of the text:

Berners-Lee, Connolly, et. al.                                  Page 44

                                HTML 2.0                February 8, 1995



         Space

         -  Interpreted as a word space (place where a line can
            be broken) in all contexts except image. For use only with
                    TYPE=IMAGE. The possible values are exactly the Preformatted Text
            element.

         -  Interpreted
                    same as a nonbreaking space within for the
            Preformatted Text ALIGN attribute of the image
                    element.

         Hyphen

         -  Interpreted as a hyphen glyph in all contexts

         -  Interpreted as a potential word space by
            hyphenation engine

      2.16.2 Control Characters

         Control characters are non-printable characters

     CHECKED
                    Indicates that are
         typically used for communication and device control, as
         format effectors, a checkbox or radio button is
                    selected. Unselected checkboxes and as information separators.

         In SGML applications, radio buttons
                    do not return name/value pairs when the use form is
                    submitted.

     MAXLENGTH
                    Indicates the maximum number of control characters is
         limited that
                    can be entered into a text field. This can be
                    greater than specified by the SIZE attribute, in order to maximize
                    which case the chance field will scroll appropriately.
                    The default number of successful
         interchange over heterogenous networks and operating
         systems. In HTML, only three control characters are
         used: Horizontal Tab (HT, encoded as 9 decimal
         in US-ASCII and ISO-8859-1), Carriage Return, and 
         Line Feed.

         Horizontal Tab is interpreted as a word space in all contexts
         except preformatted text. Within preformatted text, the tab
         should be interpreted to shift the horizontal column position
         to unlimited.

     NAME
                    Symbolic name used when transferring the next position which form's
                    contents. The NAME attribute is a multiple of 8 on the same
         line; that is, col := (col+8) mod 8.

         Carriage Return required for most
                    input types and Line Feed are conventionally is normally used to represent end provide a
                    unique identifier for a field, or for a logically
                    related group of line. For Internet Media Types defined as
         "text/*", fields.

     SIZE
                    Specifies the sequence CR LF is used size or precision of the field
                    according to represent an end its type. For example, to specify a
                    field with a visible width of
         line. In practice, text/html documents are frequently
         represented and transmitted using 24 characters:

     INPUT TYPE=text SIZE="24"

     SRC
                    A URI specifying an end of line convention 
         that depends on image. For use only with
                    TYPE=IMAGE.

     TYPE
                    Defines the conventions type of data the source field accepts.
                    Defaults to free text. Several types of fields can
                    be defined with the
         document; frequently, that representation consists of CR
         only, LF only, type attribute:

     CHECKBOX
                    Used for simple Boolean attributes, or CR LF combination. In HTML, end for
                    attributes that can take multiple values at the
                    same time. The latter is represented by a number
                    of line in
         any checkbox fields each of its variations is interpreted as which has the same
                    name. Each selected checkbox generates a word space separate
                    name/value pair in all
         contexts except preformatted text. Within preformatted text,
         HTML interpreting agents should expect the submitted data, even if
                    this results in duplicate names. The default value
                    for checkboxes is ``on''.

     HIDDEN
                    No field is presented to treat any of the
         three common representations user, but the content
                    of end-of-line as starting
         a new line.

Berners-Lee, Connolly, et. al.                                  Page 45

                                HTML 2.0                February 8, 1995



      2.16.3 Numeric Character References

         In addition the field is sent with the submitted form. This
                    value may be used to any mechanism by transmit state information
                    about client/server interaction.

     IMAGE
                    An image field upon which characters may you can click with a
                    pointing device, causing the form to be
         represented by
                    immediately submitted. The coordinates of the encoding
                    selected point are measured in pixel units from
                    the upper-left corner of the HTML document, it is
         possible to explicitly reference image, and are
                    returned (along with the printing characters other contents of the ISO-8859-1 character encoding using a numeric character
         reference. See Section
         2.17.1 for a list
                    form) in two name/value pairs. The x-coordinate is
                    submitted under the name of the characters, their names field with ``.x''
                    appended, and
         input syntax.

         Two reasons for using a numeric character reference:

         - the keyboard does not provide a key for y-coordinate is submitted under
                    the
            character, such name of the field with ``.y'' appended. Any
                    VALUE attribute is ignored. The image itself is
                    specified by the SRC attribute, exactly as on U.S. keyboards which do not
            provide European characters for the
                    Image element.

          NOTE - In a future version of the character HTML specification,
          the IMAGE functionality may be interpreted as SGML coding,
            such folded into an enhanced
          SUBMIT field.

     PASSWORD
                    The same as the ampersand (&), double quotes ("), the lesser
            (<) and greater (>) characters

         Numeric character references are represented in an HTML
         document TEXT attribute, except that text
                    is not displayed as SGML entities whose name it is number sign (#)
         followed by entered.

     RADIO
                    Used for attributes that accept a numeral single value
                    from 32-126 and 161-255. The HTML
         DTD includes a numeric character for each of the
         printing characters of the ISO-8859-1 encoding, so that one
         may reference them by number if it is inconvenient to enter
         them directly:

         the ampersand (&#38;), double quotes (&#34;),
         lesser (&#60;) and greater (&#62;) characters

      2.16.4 Character Entities

         In addition, many of the Latin alphabet No. 1 set of printing
         characters may alternatives. Each radio button
                    field in the group should be represented within given the text of an HTML
         document by a character entity. See 2.17.2 for a list of same name.
                    Only the characters, names, input syntax, and descriptions.
         See 5.2.1 for selected radio button in the SGML entity definitions of "Added
         Latin 1 for HTML".

         Two reasons for using group
                    generates a character entity:

         - name/value pair in the keyboard does not provide a key for submitted data.
                    Radio buttons require an explicit VALUE attribute.

     RESET
                    A button that when pressed resets the
            character, such as form's
                    fields to their specified initial values. The
                    label to be displayed on U.S. keyboards which do not
            provide European characters
      
         - the character button may be interpreted as SGML coding,
            such
                    specified just as for the ampersand (&), double quotes ("), the lesser
            (<) and greater (>) characters

Berners-Lee, Connolly, et. al.                                  Page 46

                                HTML 2.0                February 8, 1995 SUBMIT button.

     SUBMIT
                    A character entity button that when pressed submits the form. You
                    can use the VALUE attribute to provide a
                    non-editable label to be displayed on the button.
                    The default label is represented in an HTML document as
         an SGML entity whose name application-specific. If a
                    SUBMIT button is defined pressed in order to submit the HTML DTD.
         The HTML DTD includes
                    form, and that button has a character entity NAME attribute
                    specified, then that button contributes a
                    name/value pair to the submitted data. Otherwise,
                    a SUBMIT button makes no contribution to the
                    submitted data.

     TEXT
                    Used for each of a single line text entry fields. Use in
                    conjunction with the
         SGML markup characters SIZE and MAXLENGTH
                    attributes. Use the Textarea element for each text
                    fields which can accept multiple lines.

     VALUE
                    The initial displayed value of the printing
         characters in the upper half of Latin-1, so that one may
         reference them by name field, if it is inconvenient
                    displays a textual or numerical value; or the
                    value to enter
         them directly: be returned when the ampersand (&amp;), double quotes (&quot;),
         lesser (&lt;) and greater (&gt;) characters

         Kurt G&ouml;del was field is selected,
                    if it displays a famous logician Boolean value. This attribute is
                    required for radio buttons.


10.3. Option 

     <OPTION> Level 2

     The Option element can only occur within a Select element.
     It represents one choice, and mathematician.

         NOTE: To ensure can take these attributes:

     SELECTED
                    Indicates that a string of characters this option is not
         interpreted as markup, represent all occurrences of <,
         >, and & by character or entity references.

         NOTE: There are SGML features, CDATA and RCDATA, to
         allow most <, >, and & characters to be entered without initially selected.

     VALUE
                    When present indicates the use of entity or character references. Because these
         features tend value to be used and implemented inconsistently,
         and because they require 8-bit characters to represent
         non-ASCII characters, they are not used in returned if
                    this version option is chosen. The returned value defaults
                    to the contents of the HTML DTD. An earlier HTML specification included
         an Example Option element.

     The contents of the Option element (<XMP>) whose syntax is not
         expressible in SGML. No markup was recognized inside of
         the Example element except presented to the </XMP> end tag. While
         HTML user agents are encouraged
     to support this idiom,
         its use represent the option. It is deprecated.

   2.17 Character Entity Sets

      The following entity names are used in HTML, always
      prefixed by ampersand (&) and followed by a semicolon as
      shown.

      They represent particular graphic characters which have
      special meanings in places in a returned value if
     the markup, or may VALUE attribute is not be
      part of present.


10.4. Select 

     <SELECT NAME=... > ... </SELECT> Level 2

     The Select element allows the character set available user to chose one of a set of
     alternatives described by textual labels. Every alternative
     is represented by the writer.

      2.17.1 Numeric and Special Graphic Entities Option element. Attributes are:

     MULTIPLE
                    The following table lists each of MULTIPLE attribute is needed when users are
                    allowed to make several selections, e.g. <SELECT
                    MULTIPLE>.

     NAME
                    Specifies the supported
         characters specified in name that will submitted as a
                    name/value pair.

     SIZE
                    Specifies the Numeric number of visible items. If this is
                    greater than one, then the resulting form control
                    will be a list.

     The Select element is typically rendered as a pull down or
     pop-up list. For example:

     <SELECT NAME="flavor">
     <OPTION>Vanilla
     <OPTION>Strawberry
     <OPTION>Rum and Special Graphic
         entity set, along with its name, syntax for use, Raisin
     <OPTION>Peach and
         description. This list Orange
     </SELECT>

     If no option is derived from ISO Standard
         8879:1986//ENTITIES Numeric and Special Graphic//EN
         however HTML does not provide support for the entire
         entity set. Only initially marked as selected, then the entities first
     item listed below are

Berners-Lee, Connolly, et. al.                                  Page 47

                                HTML 2.0                February 8, 1995


         supported.

         GLYPH   NAME            SYNTAX      DESCRIPTION
         <       lt              &lt;        Less than sign
         >       gt              &gt;        Greater is selected.


10.5. Text Area 

     <TEXTAREA> ... </TEXTAREA> Level 2

     The Textarea element lets users enter more than sign
         &       amp             &amp;       Ampersand
         "       quot            &quot;      Double quote sign

      2.17.2 ISO Latin 1 Character Entities one line of
     text. For example:

     <TEXTAREA NAME="address" ROWS=64 COLS=6>
     HaL Computer Systems
     1315 Dell Avenue
     Campbell, California 95008
     </TEXTAREA>

     The following table lists each text up to the end tag (</TEXTAREA>) is used to
     initialize the field's value. This end tag is always
     required even if the field is initially blank. When
     submitting a form, lines in a TEXTAREA should be terminated
     using CRLF.

     In a typical rendering, the ROWS and COLS attributes
     determine the visible dimension of the characters
         specified field in characters.
     The field is rendered in a fixed-width font. HTML
     interpreters should allow text to extend beyond these limits
     by scrolling as needed.

          NOTE - In the Added Latin 1 entity set, along initial design for forms, multi-line text
          fields were supported by the Input element with
         its name, syntax
          TYPE=TEXT. Unfortunately, this causes problems for use, and description.
          fields with long text values. SGML's default (Reference
          Quantity Set) limits the length of attribute literals
          to only 240 characters. The HTML 2.0 SGML declaration
          increases the limit to 1024 characters.


11. HTML Public Text 


11.1. HTML DTD 

     This list is
         derived from ISO Standard 8879:1986//ENTITIES Added
         Latin 1//EN. HTML supports the entire entity set.

         NAME            SYNTAX      DESCRIPTION

         Aacute          &Aacute;    Capital A, acute accent
         Agrave          &Agrave;    Capital A, grave accent
         Acirc           &Acirc;     Capital A, circumflex accent
         Atilde          &Atilde;    Capital A, tilde
         Aring           &Aring;     Capital A, ring
         Auml            &Auml;      Capital A, dieresis or umlaut mark
         AElig           &AElig;     Capital AE dipthong (ligature)
         Ccedil          &Ccedil;    Capital C, cedilla
         Eacute          &Eacute;    Capital E, acute accent
         Egrave          &Egrave;    Capital E, grave accent
         Ecirc           &Ecirc;     Capital E, circumflex accent
         Euml            &Euml;      Capital E, dieresis or umlaut mark
         Iacute          &Iacute;    Capital I, acute accent
         Igrave          &Igrave;    Capital I, grave accent
         Icirc           &Icirc;     Capital I, circumflex accent
         Iuml            &Iuml;      Capital I, dieresis or umlaut mark
         ETH             &ETH;       Capital Eth, Icelandic
         Ntilde          &Ntilde;    Capital N, tilde
         Oacute          &Oacute;    Capital O, acute accent
         Ograve          &Ograve;    Capital O, grave accent
         Ocirc           &Ocirc;     Capital O, circumflex accent
         Otilde          &Otilde;    Capital O, tilde
         Ouml            &Ouml;      Capital O, dieresis or umlaut mark
         Oslash          &Oslash;    Capital O, slash
         Uacute          &Uacute;    Capital U, acute accent
         Ugrave          &Ugrave;    Capital U, grave accent
         Ucirc           &Ucirc;     Capital U, circumflex accent
         Uuml            &Uuml;      Capital U, dieresis or umlaut mark
         Yacute          &Yacute;    Capital Y, acute accent

         THORN           &THORN;     Capital THORN, Icelandic
         szlig           &szlig;     Small sharp s, German (sz ligature)

Berners-Lee, Connolly, et. al.                                  Page 48

                                HTML 2.0                February 8, 1995



         aacute          &aacute;    Small a, acute accent
         agrave          &agrave;    Small a, grave accent
         acirc           &acirc;     Small a, circumflex accent
         atilde          &atilde;    Small a, tilde
         aring           &aring;     Small a, ring
         auml            &auml;      Small a, dieresis or umlaut mark
         aelig           &aelig;     Small ae dipthong (ligature)
         ccedil          &ccedil;    Small c, cedilla
         eacute          &eacute;    Small e, acute accent
         egrave          &egrave;    Small e, grave accent
         ecirc           &ecirc;     Small e, circumflex accent
         euml            &euml;      Small e, dieresis or umlaut mark
         iacute          &iacute;    Small i, acute accent
         igrave          &igrave;    Small i, grave accent
         icirc           &icirc;     Small i, circumflex accent
         iuml            &iuml;      Small i, dieresis or umlaut mark
         eth             &eth;       Small eth, Icelandic
         ntilde          &ntilde;    Small n, tilde
         oacute          &oacute;    Small o, acute accent
         ograve          &ograve;    Small o, grave accent
         ocirc           &ocirc;     Small o, circumflex accent
         otilde          &otilde;    Small o, tilde
         ouml            &ouml;      Small o, dieresis or umlaut mark
         oslash          &oslash;    Small o, slash
         uacute          &uacute;    Small u, acute accent
         ugrave          &ugrave;    Small u, grave accent
         ucirc           &ucirc;     Small u, circumflex accent
         uuml            &uuml;      Small u, dieresis or umlaut mark
         yacute          &yacute;    Small y, acute accent
         thorn           &thorn;     Small thorn, Icelandic
         yuml            &yuml;      Small y, dieresis or umlaut mark

      2.17.3 Numerical Character References

         This list, sorted numerically, is derived from ISO-8859-1
         8-bit single-byte coded graphic character set:

         REFERENCE           DESCRIPTION

         &#00; - &#08;       Unused
         &#09;               Horizontal tab
         &#10;               Line feed
         &#11; - &#31;       Unused

         &#32;               Space
         &#33;               Exclamation mark
         &#34;               Quotation mark
         &#35;               Number sign
         &#36;               Dollar sign

Berners-Lee, Connolly, et. al.                                  Page 49

                                HTML 2.0                February 8, 1995


         &#37;               Percent sign
         &#38;               Ampersand
         &#39;               Apostrophe
         &#40;               Left parenthesis
         &#41;               Right parenthesis
         &#42;               Asterisk
         &#43;               Plus sign
         &#44;               Comma
         &#45;               Hyphen
         &#46;               Period (fullstop)
         &#47;               Solidus (slash)

         &#48; - &#57;       Digits 0-9

         &#58;               Colon
         &#59;               Semi-colon
         &#60;               Less than
         &#61;               Equals aign
         &#62;               Greater than
         &#63;               Question mark
         &#64;               Commercial at

         &#65; - &#90;       Letters A-Z

         &#91;               Left square bracket
         &#92;               Reverse solidus (backslash)
         &#93;               Right square bracket
         &#94;               Caret
         &#95;               Horizontal bar
         &#96;               Acute accent

         &#97; - &#122;      Letters a-z

         &#123;              Left curly brace
         &#124;              Vertical bar
         &#125;              Right curly brace
         &#126;              Tilde

         &#127; - &#160;     Unused

         &#161;              Inverted exclamation
         &#162;              Cent sign
         &#163;              Pound sterling
         &#164;              General currency sign
         &#165;              Yen sign
         &#166;              Broken vertical bar
         &#167;              Section sign
         &#168;              Umlaut (dieresis)
         &#169;              Copyright
         &#170;              Feminine ordinal

Berners-Lee, Connolly, et. al.                                  Page 50

                                HTML 2.0                February 8, 1995


         &#171;              Left angle quote, guillemotleft
         &#172;              Not sign
         &#173;              Soft hyphen
         &#174;              Registered trademark
         &#175;              Macron accent
         &#176;              Degree sign
         &#177;              Plus or minus
         &#178;              Superscript two
         &#179;              Superscript three
         &#180;              Acute accent
         &#181;              Micro sign
         &#182;              Paragraph sign
         &#183;              Middle dot
         &#184;              Cedilla
         &#185;              Superscript one
         &#186;              Masculine ordinal
         &#187;              Right angle quote, guillemotright
         &#188;              Fraction one-fourth
         &#189;              Fraction one-half
         &#190;              Fraction three-fourths
         &#191;              Inverted question mark

         &#192;              Capital A, acute accent
         &#193;              Capital A, grave accent
         &#194;              Capital A, circumflex accent
         &#195;              Capital A, tilde
         &#196;              Capital A, ring
         &#197;              Capital A, dieresis or umlaut mark
         &#198;              Capital AE dipthong (ligature)
         &#199;              Capital C, cedilla
         &#200;              Capital E, acute accent
         &#201;              Capital E, grave accent
         &#202;              Capital E, circumflex accent
         &#203;              Capital E, dieresis or umlaut mark
         &#204;              Capital I, acute accent
         &#205;              Capital I, grave accent
         &#206;              Capital I, circumflex accent
         &#207;              Capital I, dieresis or umlaut mark
         &#208;              Capital Eth, Icelandic
         &#209;              Capital N, tilde
         &#210;              Capital O, acute accent
         &#211;              Capital O, grave accent
         &#212;              Capital O, circumflex accent
         &#213;              Capital O, tilde
         &#214;              Capital O, dieresis or umlaut mark

         &#215;              Multiply sign

         &#216;              Capital O, slash
         &#217;              Capital U, acute accent

Berners-Lee, Connolly, et. al.                                  Page 51

                                HTML 2.0                February 8, 1995


         &#218;              Capital U, grave accent
         &#219;              Capital U, circumflex accent
         &#220;              Capital U, dieresis or umlaut mark
         &#221;              Capital Y, acute accent

         &#222;              Capital THORN, Icelandic
         &#223;              Small sharp s, German (sz ligature)

         &#224;              Small a, acute accent
         &#225;              Small a, grave accent
         &#226;              Small a, circumflex accent
         &#227;              Small a, tilde
         &#228;              Small a, dieresis or umlaut mark
         &#229;              Small a, ring
         &#230;              Small ae dipthong (ligature)
         &#231;              Small c, cedilla
         &#232;              Small e, acute accent
         &#233;              Small e, grave accent
         &#234;              Small e, circumflex accent
         &#235;              Small e, dieresis or umlaut mark
         &#236;              Small i, acute accent
         &#237;              Small i, grave accent
         &#238;              Small i, circumflex accent
         &#239;              Small i, dieresis or umlaut mark
         &#240;              Small eth, Icelandic
         &#241;              Small n, tilde
         &#242;              Small o, acute accent
         &#243;              Small o, grave accent
         &#244;              Small o, circumflex accent
         &#245;              Small o, tilde
         &#246;              Small o, dieresis or umlaut mark

         &#247;              Division sign

         &#248;              Small o, slash
         &#249;              Small u, acute accent
         &#250;              Small u, grave accent
         &#251;              Small u, circumflex accent
         &#252;              Small u, dieresis or umlaut mark
         &#253;              Small y, acute accent
         &#254;              Small thorn, Icelandic
         &#255;              Small y, dieresis or umlaut mark

3. Security Considerations

   Anchors, embedded images, and all other elements which
   contain URIs as parameters may cause Document Type Definition for the URI to be
   dereferenced in response to user input. In this case, HyperText
     Markup Language.

     <!--    html.dtd
     
             Document Type Definition for the security considerations HyperText Markup Language
                      (HTML DTD)
  5  
             $Id: html.dtd,v 1.25 1995/03/29 18:53:13 connolly Exp $
     
             Author: Daniel W. Connolly <connolly@w3.org>
             See Also: html.decl, html-0.dtd, html-1.dtd
 10            http://info.cern.ch/hypertext/WWW/MarkUp/MarkUp.html
     -->
     
     <!ENTITY % HTML.Version
             "-//IETF//DTD HTML 2.0//EN"
 15  
             -- Typical usage:
     
                 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
                 <html>
 20              ...
                 </html>
             --
             >
     
 25  
     <!--============ Feature Test Entities ========================-->
     
     <!ENTITY % HTML.Recommended "IGNORE"
             -- Certain features of the URI specification
   apply.

Berners-Lee, Connolly, et. al.                                  Page 52

                                HTML 2.0                February 8, 1995



   Documents language are necessary for
 30             compatibility with widespread usage, but they may be constructed whose visible contents
   mislead
                compromise the reader to follow structural integrity of a link to unsuitable or
   offensive material.

4. Obsolete and Proposed Features

   4.1 Obsolete Features document.
                This section describes elements feature test entity enables a more prescriptive
                document type definition that are no longer part eliminates
                those features.
 35          -->
     
     <![ %HTML.Recommended [
             <!ENTITY % HTML.Deprecated "IGNORE">
     ]]>
 40  
     <!ENTITY % HTML.Deprecated "INCLUDE"
             -- Certain features of HTML. Client implementors should implement these
   obsolete elements the language are necessary for
                compatibility with previous earlier versions of the HTML specification.

      4.1.1 Comment

         The Comment element is used to delimit unneeded text and
         comments. The Comment element has been introduced in
         some HTML applications specification,
                but should be replaced by the
         SGML comment feature in new HTML user agents (see
         Section 2.6.5).

      4.1.2 Highlighted Phrase

         The Highlighted Phrase element (<HP>) should they tend to be ignored
         if not implemented. This element has been replaced by
         more meaningful elements (see Section 2.9).

         Example of use:

         <HP1>first highlighted phrase</HP1>non

         highlighted text<HP2>second highlighted
         phrase</HP2> etc.

       4.1.3 Plain Text

         <PLAINTEXT>

         The Plain Text element is used an implemented inconsistently,
 45             and their use is deprecated. This feature test entity
                enables a document type definition that eliminates
                these features.
             -->
     
 50  <!ENTITY % HTML.Highlighting "INCLUDE"
             -- Use this feature test entity to terminates the HTML validate that a
                document uses no highlighting tags, which may be
                ignored on minimal implementations.
             -->
 55  
     <!ENTITY % HTML.Forms "INCLUDE"
             -- Use this feature test entity and to indicate validate that what follows is not SGML a document
                contains no forms, which does may not require parsing. Instead, be supported in minimal
                implementations
 60          -->
     
     <!--============== Imported Names ==============================-->
     
     <!ENTITY % Content-Type "CDATA"
 65          -- meaning an old internet media type
                (aka MIME content type, as per RFC1521)
             -->
     
     <!ENTITY % HTTP-Method "GET | POST"
 70          -- as per HTTP
         convention specified that what followed was an ASCII
         (MIME "text/plain") body. Its presence is an
         optimization. There is no closing tag.

         Example of use:

         <PLAINTEXT>
         0001 This specification, in progress
             -->
     
     <!ENTITY % URI "CDATA"
             -- The term URI means a CDATA attribute
 75             whose value is line one a Uniform Resource Identifier,
                as defined by 
             "Universal Resource Identifiers" by Tim Berners-Lee
             aka RFC 1630
     
 80          Note that CDATA attributes are limited by the LITLEN
             capacity (1024 in the current version of html.decl),
             so that URIs in HTML have a long listing

Berners-Lee, Connolly, et. al.                                  Page 53 bounded length.
     
             -->
 85  
     
     <!--========= DTD "Macros" =====================-->
     
     <!ENTITY % heading "H1|H2|H3|H4|H5|H6">
 90  
     <!ENTITY % list " UL | OL | DIR | MENU " >
     
     
     <!--======= Character mnemonic entities =================-->
 95  
     <!ENTITY % ISOlat1 PUBLIC
       "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML">
     %ISOlat1;
     
100  <!ENTITY amp CDATA "&#38;"     -- ampersand          -->
     <!ENTITY gt CDATA "&#62;"      -- greater than       -->
     <!ENTITY lt CDATA "&#60;"      -- less than          -->
     <!ENTITY quot CDATA "&#34;"    -- double quote       -->
     
105  
     <!--========= SGML Document Access (SDA) Parameter Entities =====-->
     
     <!-- HTML 2.0                February 8, 1995


         0002 file from <ANY@HOST.INC.COM> which is sent

      4.1.4 Example and Listing

         <XMP> ... </XMP> and <LISTING> ... </LISTING>

         The Example element and Listing element have been
         replaced by the Preformatted Text element.

         These styles allow text contains SGML Document Access (SDA) fixed attributes
     in support of fixed-width characters easy transformation to be
         embedded absolutely as is into the document. The syntax
         is:

         <LISTING>
         ...
         </LISTING>

         or

         <XMP>
         ...
         </XMP>

         The text between these tags is typically rendered in a
         monospaced font so that any formatting done International Committee
110  for Accessible Document Design (ICADD) DTD
              "-//EC-USA-CDA/ICADD//DTD ICADD22//EN".
     ICADD applications are designed to support usable access to
     structured information by character
         spacing on successive lines will be maintained.

         Between the opening print-impaired individuals through
     Braille, large print and closing tags: voice synthesis.  For more information on
115  SDA & ICADD:  
             -  The text may contain any ISO Latin-1 printable
            characters, expect 12083:1993, Annex A.8, Facilities for the end tag opener. The Example Braille,
               large print and Listing elements have historically used
            specifications which do not conform to SGML.
            Specifically, computer voice
             - ICADD ListServ
               <ICADD%ASUACAD.BITNET@ARIZVM1.ccit.arizona.edu>
120          - Usenet news group bit.listserv.easi
             - Recording for the Blind, +1 800 221 4792
     -->
     
     <!ENTITY % SDAFORM  "SDAFORM  CDATA  #FIXED"
125            -- one to one mapping        -->
     <!ENTITY % SDARULE  "SDARULE  CDATA  #FIXED"
               -- context-sensitive mapping -->
     <!ENTITY % SDAPREF  "SDAPREF  CDATA  #FIXED"
               -- generated text prefix     -->
130  <!ENTITY % SDASUFF  "SDASUFF  CDATA  #FIXED"
               -- generated text suffix     -->
     <!ENTITY % SDASUSP  "SDASUSP  NAME   #FIXED"
               -- suspend transform process -->
     
135  
     <!--========== Text Markup =====================-->
     
     <![ %HTML.Highlighting [
     
140  <!ENTITY % font " TT | B | I ">
     
     <!ENTITY % phrase "EM | STRONG | CODE | SAMP | KBD | VAR | CITE ">
     
     <!ENTITY % text may contain ISO Latin printable
            characters, including the tag opener, as long it they
            does not contain the closing tag in full. "#PCDATA | A | IMG | BR | %phrase | %font">
145  
     <!ELEMENT (%font;|%phrase) -  SGML does not support this form. HTML user agents
            may vary on how they interpret other tags within Example
            and Listing elements. -  Line boundaries within the (%text)*>
     <!ATTLIST ( TT | CODE | SAMP | KBD | VAR )
             %SDAFORM; "Lit"
             >
150  <!ATTLIST ( B | STRONG )
             %SDAFORM; "B"
             >
     <!ATTLIST ( I | EM | CITE )
             %SDAFORM; "It"
155          >
     
     <!-- <TT>       Typewriter text                         -->
     <!-- <B>        Bold text                               -->
     <!-- <I>        Italic text                             -->
160  
     <!-- <EM>       Emphasized phrase                       -->
     <!-- <STRONG>   Strong emphais                          -->
     <!-- <CODE>     Source code phrase                      -->
     <!-- <SAMP>     Sample text are rendered as a
            move to the beginning of the next line, except for one
            immediately following a start tag or immediately
            preceding an end tag.

         -  The horizontal tab character 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. Its use is not

Berners-Lee, Connolly, et. al.                                  Page 54

                                HTML 2.0                February 8, 1995


            recommended.

      The Listing element is rendered so that at least 132
      characters fit on a line. The Example element is
      rendered to that at least 80 characters fit on a line
      but is otherwise identical to the Listing element.

   4.2 Proposed Features

      This section describes proposed HTML elements and
      entities that are not currently supported under HTML
      Levels 0, 1, or 2, but may be supported in the future.

      4.2.1 Defining Instance

         <DFN> ... </DFN>

         The Defining Instance element indicates the defining
         instance of a term. The typical rendering is bold characters               -->
165  <!-- <KBD>      Keyboard phrase, e.g. user input        -->
     <!-- <VAR>      Variable phrase or
         bold italic. This element is not widely supported.

      4.2.2 Special Characters

         To indicate special characters, HTML uses entity substituable         -->
     <!-- <CITE>     Name or
         numeric representations. Additional character
         presentations are proposed:

         CHARACTER                  REPRESENTATION

         Non-breaking space         &nbsp;
         Soft-hyphen                &shy;
         Registered                 &reg;
         Copyright                  &copy;

      4.2.3 Strike

         <STRIKE> ... </STRIKE>

         The Strike element is proposed to indicate
         strikethrough, a font style in which a horizontal line
         appears through characters. This element is not widely
         supported.

      4.2.4 Underline

         <U> ... </U>

         The Underline element is proposed to indicate that the
         text should be rendered as underlined. This proposed tag
         is not supported by all HTML user agents.

Berners-Lee, Connolly, et. al.                                  Page 55

                                HTML 2.0                February 8, 1995



         Example title of use:

         The cited work             -->
     
     <!ENTITY % pre.content "#PCDATA | A | HR | BR | %font | %phrase">
170  
     ]]>
     
     <!ENTITY % text <U>shown here</U> is rendered in the document
         as underlined.

5. HTML Document Type Definitions

   5.1 SGML Declaration for HTML

This is the SGML Declaration for HyperText Markup Language
(HTML) as used by the World Wide Web (WWW) application:

<!SGML  "ISO 8879:1986"
--
	SGML Declaration for HyperText "#PCDATA | A | IMG | BR">
     
175  <!ELEMENT BR    - O EMPTY>
     <!ATTLIST BR
             %SDAPREF; "&#RE;"
             >
     
180  <!-- <BR>       Line break      -->
     
     
     <!--========= Link Markup Language (HTML). ======================-->
     
185  <![ %HTML.Recommended [
             <!ENTITY % linkName "ID">
     ]]>
     
     <!ENTITY % linkName "CDATA">
190  
     <!ENTITY % linkType "NAME"
             --

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 a list of
                Latin Alphabet Nr. 1//ESC 2/13 4/1"

         DESCSET  128  32   UNUSED
                  160  96    32

CAPACITY        SGMLREF
                TOTALCAP        150000
                GRPCAP          150000
  
SCOPE    DOCUMENT
SYNTAX   
         SHUNCHAR CONTROLS 0 these will be specified at a later date -->
     
     <!ENTITY % linkExtraAttributes
195          "REL %linkType #IMPLIED
             REV %linkType #IMPLIED
             URN CDATA #IMPLIED
             TITLE CDATA #IMPLIED
             METHODS NAMES #IMPLIED
200          ">
     
     <![ %HTML.Recommended [
             <!ENTITY % A.content   "(%text)*"
             -- <H1><a name="xxx">Heading</a></H1>
205                  is preferred to
                <a name="xxx"><H1>Heading</H1></a>
             -->
     ]]>
     
210  <!ENTITY % A.content   "(%heading|%text)*">
     
     <!ELEMENT A     - - %A.content -(A)>
     <!ATTLIST A
             HREF %URI #IMPLIED
215          NAME %linkName #IMPLIED
             %linkExtraAttributes;
             %SDAPREF; "<Anchor: #AttList>"
             >
     <!-- <A>                Anchor; source/destination of link      -->
220  <!-- <A NAME="...">     Name of this anchor                     -->
     <!-- <A HREF="...">     Address of link destination             -->
     <!-- <A URN="...">      Permanent address of destination        -->
     <!-- <A REL=...>        Relationship to destination             -->
     <!-- <A REV=...>        Relationship of destination to this     -->
225  <!-- <A TITLE="...">    Title of destination (advisory)         -->
     <!-- <A METHODS="...">  Operations on destination (advisory)    -->
     
     
     <!--========== Images ==========================-->
230  
     <!ELEMENT IMG    - O EMPTY>
     <!ATTLIST IMG
             SRC %URI;  #REQUIRED
             ALT CDATA #IMPLIED
235          ALIGN (top|middle|bottom) #IMPLIED
             ISMAP (ISMAP) #IMPLIED
             %SDAPREF; "<Fig><?SDATrans Img: #AttList>#AttVal(Alt)</Fig>"
             >
     
240  <!-- <IMG>              Image; icon, glyph or illustration      -->
     <!-- <IMG SRC="...">    Address of image object                 -->
     <!-- <IMG ALT="...">    Textual alternative                     -->
     <!-- <IMG ALIGN=...>    Position relative to text               -->
     <!-- <IMG ISMAP>        Each pixel can be a link                -->
245  
     <!--========== Paragraphs=======================-->
     
     <!ELEMENT P     - O (%text)*>
     <!ATTLIST P
250          %SDAFORM; "Para"
             >
     
     <!-- <P>        Paragraph       -->
     
255  
     <!--========== Headings, Titles, Sections ===============-->
     
     <!ELEMENT HR    - O EMPTY>
     <!ATTLIST HR
260          %SDAPREF; "&#RE;&#RE;"
             >
     
     <!-- <HR>       Horizontal rule -->
     
265  <!ELEMENT ( %heading )  - -  (%text;)*>
     <!ATTLIST H1
             %SDAFORM; "H1"
             >
     <!ATTLIST H2
270          %SDAFORM; "H2"
             >
     <!ATTLIST H3
             %SDAFORM; "H3"
             >
275  <!ATTLIST H4
             %SDAFORM; "H4"
             >
     <!ATTLIST H5
             %SDAFORM; "H5"
280          >
     <!ATTLIST H6
             %SDAFORM; "H6"
             >
     
285  <!-- <H1>       Heading, level 1 -->
     <!-- <H2>       Heading, level 2 -->
     <!-- <H3>       Heading, level 3 -->
     <!-- <H4>       Heading, level 4 -->
     <!-- <H5>       Heading, level 5 -->
290  <!-- <H6>       Heading, level 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

Berners-Lee, Connolly, et. al.                                  Page 56

                                HTML 2.0                February 8, 1995


		  RE          13
                  RS          10
                  SPACE       32
                  TAB SEPCHAR  9
	

         NAMING   LCNMSTRT ""
                  UCNMSTRT ""
                  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 -->
     
     
     <!--========== Text Flows ======================-->
     
295  <![ %HTML.Forms [
             <!ENTITY % block.forms "BLOCKQUOTE | FORM | ISINDEX">
     ]]>
     
     <!ENTITY % block.forms "BLOCKQUOTE">
300  
     <![ %HTML.Deprecated [
             <!ENTITY % preformatted "PRE | XMP | LISTING">
     ]]>
     
305  <!ENTITY % preformatted "PRE">
     
     <!ENTITY % block "P | %list | DL
             | %preformatted
             | %block.forms">
310  
     <!ENTITY % flow "(%text|%block)*">
     
     <!ENTITY % pre.content "#PCDATA | A | HR | BR">
     <!ELEMENT PRE - - (%pre.content)*>
315  <!ATTLIST PRE
             WIDTH NUMBER #implied
             %SDAFORM; "Lit"
             >
     
320  <!-- <PRE>              Preformatted text               -->
     <!-- <PRE WIDTH=...>    Maximum characters per line length conventions --
                  PILEN    1024
                  TAGLEN   2100

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"     -->
     
     <![ %HTML.Deprecated [
     
325  <!ENTITY % literal "CDATA"
             -- conforming SGML historical, non-conforming parsing mode where
                the only markup signal is the end tag
                in full
             -->
330  
     <!ELEMENT (XMP|LISTING) - -  %literal>
     <!ATTLIST XMP
             %SDAFORM; "Lit"
             %SDAPREF; "Example:&#RE;"
335          >
     <!ATTLIST LISTING
             %SDAFORM; "Lit"
             %SDAPREF; "Listing:&#RE;"
             >
340  
     <!-- <XMP>              Example section         -->
     <!-- <LISTING>          Computer listing        -->
     
     <!ELEMENT PLAINTEXT - O %literal>
345  <!-- <PLAINTEXT>        Plain text passage      -->
     
     <!ATTLIST PLAINTEXT
             %SDAFORM; "Lit"
             >
350  ]]>
     
     
     <!--========== Lists ==================-->
     
355  <!ELEMENT DL    - -  (DT | DD)+>
     <!ATTLIST DL
             COMPACT (COMPACT) #IMPLIED
             %SDAFORM; "List"
             %SDAPREF; "Definition List:"
360          >
     
     <!ELEMENT DT    - O (%text)*>
     <!ATTLIST DT
             %SDAFORM; "Term"
365          >
     
     <!ELEMENT DD    - O %flow>
     <!ATTLIST DD
             %SDAFORM; "LItem"
370          >
     
     <!-- <DL>               Definition list, or glossary    -->
     <!-- <DL COMPACT>       Compact style list              -->
     <!-- <DT>               Term in definition list         -->
375  <!-- <DD>               Definition of term              -->
     
     <!ELEMENT (OL|UL) - -  (LI)+>
     <!ATTLIST OL
             COMPACT (COMPACT) #IMPLIED
380          %SDAFORM; "List"
             >
     <!ATTLIST UL
             COMPACT (COMPACT) #IMPLIED
             %SDAFORM; "List"
385          >
     <!-- <UL>               Unordered list                  -->
     <!-- <UL COMPACT>       Compact list style              -->
     <!-- <OL>               Ordered, or numbered list       -->
     <!-- <OL COMPACT>       Compact list style              -->
390  
     
     <!ELEMENT (DIR|MENU) - -  (LI)+ -(%block)>
     <!ATTLIST DIR
             COMPACT (COMPACT) #IMPLIED
395          %SDAFORM; "List"
             %SDAPREF; "<LHead>Directory</LHead>"
             >
     <!ATTLIST MENU
             COMPACT (COMPACT) #IMPLIED
400          %SDAFORM; "List"
             %SDAPREF; "<LHead>Menu</LHead>"
             >
     
     <!-- <DIR>              Directory list                  -->
405  <!-- <DIR COMPACT>      Compact list style              -->
     <!-- <MENU>             Menu list                       -->
     <!-- <MENU COMPACT>     Compact list style              -->
     
     <!ELEMENT LI    - O %flow>
410  <!ATTLIST LI
             %SDAFORM; "LItem"
             >
     
     <!-- <LI>               List item                       -->
415  
     <!--========== Document Access application Body ===================-->
     
     <![ %HTML.Recommended [
             <!ENTITY % body.content "(%heading|%block|HR|ADDRESS|IMG)*"
420          -- <h1>Heading</h1>
                <p>Text ...
                     is preferred to
                <h1>Heading</h1>
                Text ...
425          -->
     ]]>
     
     <!ENTITY % body.content "(%heading | %text | %block |
                                      HR | ADDRESS)*">
430  
     <!ELEMENT BODY O O  %body.content>
     
     <!-- <BODY>     Document body   -->
     
435  <!ELEMENT BLOCKQUOTE - - %body.content>
     <!ATTLIST BLOCKQUOTE
             %SDAFORM; "BQ"
             >
     
440  <!-- <BLOCKQUOTE>       Quoted passage  -->
     
     <!ELEMENT ADDRESS - - (%text|P)*>
     <!ATTLIST  ADDRESS
             %SDAFORM; "Lit"
445          %SDAPREF; "Address:&#RE;"
             >
     
     <!-- <ADDRESS>  Address, signature, or byline   -->
     
450  
     <!--======= Forms ====================-->
     
     <![ %HTML.Forms [
     
455  <!ELEMENT FORM - - %body.content -(FORM) +(INPUT|SELECT|TEXTAREA)>
     <!ATTLIST FORM
             ACTION %URI #IMPLIED
             METHOD (%HTTP-Method) GET
             ENCTYPE %Content-Type; "application/x-www-form-urlencoded"
460          %SDAPREF; "<Para>Form:</Para>"
             %SDASUFF; "<Para>Form End.</Para>"
             >
     
     <!-- <FORM>                     Fill-out or data-entry form     -->
465  <!-- <FORM ACTION="...">        Address for completed form      -->
     <!-- <FORM METHOD=...>          Method of submitting form       -->
     <!-- <FORM ENCTYPE="...">       Representation of form data     -->
     
     <!ENTITY % InputType "(TEXT | PASSWORD | CHECKBOX |
470                          RADIO | SUBMIT | RESET |
                             IMAGE | HIDDEN )">
     <!ELEMENT INPUT - O EMPTY>
     <!ATTLIST INPUT
             TYPE %InputType TEXT
475          NAME CDATA #IMPLIED
             VALUE CDATA #IMPLIED
             SRC %URI #IMPLIED
             CHECKED (CHECKED) #IMPLIED
             SIZE CDATA #IMPLIED
480          MAXLENGTH NUMBER #IMPLIED
             ALIGN (top|middle|bottom) #IMPLIED
             %SDAPREF; "Input: "
             >
     
485  <!-- 
	$Id: html.decl,v 1.13 1995/02/08 08:29:33 connolly Exp $

	Author: Daniel W. Connolly <connolly@hal.com>

	See also: http://www.hal.com/%7Econnolly/html-spec
	  http://info.cern.ch/hypertext/WWW/MarkUp/MarkUp.html <INPUT>                    Form input datum                -->

   5.1.1 Sample SGML Open Style Entity Catalog for HTML

Berners-Lee, Connolly, et. al.                                  Page 57

                                HTML 2.0                February 8, 1995



      The SGML standard describes an "entity manager" as the
      portion or component
     <!-- <INPUT TYPE=...>           Type of an SGML system that maps SGML
      entities into the actual storage model (e.g., the file
      system).  The standard itself does not 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 input interaction       -->
     <!-- <INPUT NAME=...>           Name of form datum              -->
     <!-- <INPUT VALUE="...">        Default/initial/selected value  -->
     <!-- <INPUT SRC="...">          Address of image                -->
490  <!-- <INPUT CHECKED>            Initial state is "on"           -->
     <!-- <INPUT SIZE=...>           Field size hint                 -->
     <!-- <INPUT MAXLENGTH=...>      Data length maximum             -->
     <!-- <INPUT ALIGN=...>          Image alignment                 -->
     
495  <!ELEMENT SELECT - - (OPTION+) -(INPUT|SELECT|TEXTAREA)>
     <!ATTLIST SELECT
             NAME CDATA #REQUIRED
             SIZE NUMBER #IMPLIED
             MULTIPLE (MULTIPLE) #IMPLIED
500          %SDAFORM; "List"
             %SDAPREF;
             "<LHead>Select #AttVal(Multiple)</LHead>"
             >
     
505  <!-- <SELECT>                   Selection of option(s)          -->
     <!-- <SELECT NAME=...>          Name of form datum              -->
     <!-- <SELECT SIZE=...>          Options displayed at a storage
      object indentifier.  For example, the following are
      possible catalog entries:

PUBLIC "ISO 8879:1986//ENTITIES Added Latin 1//EN" "iso-lat1.gml"
PUBLIC "-//ACME DTD Writers//DTD General Report//EN" report.dtd
ENTITY "graph1" "graphics\graph1.cgm"
In particular, the following shows entries relevant to HTML.
        -- catalog: SGML Open style entity catalog time     -->
     <!-- <SELECT MULTIPLE>          Multiple selections allowed     -->
     
510  <!ELEMENT OPTION - O (#PCDATA)*>
     <!ATTLIST OPTION
             SELECTED (SELECTED) #IMPLIED
             VALUE CDATA #IMPLIED
             %SDAFORM; "LItem"
515          %SDAPREF;
             "Option: #AttVal(Value) #AttVal(Selected)"
             >
     
     <!-- <OPTION>                   A selection option              -->
520  <!-- <OPTION SELECTED>          Initial state                   -->
     <!-- <OPTION VALUE="...">       Form datum value for HTML --
        -- $Id: catalog,v 1.1 1994/10/07 21:35:07 connolly Exp $ --

        -- Ways to refer to Level 2: most general to most specific --
PUBLIC  "-//IETF//DTD HTML//EN"                 html.dtd
PUBLIC  "-//IETF//DTD HTML//EN//2.0"            html.dtd
PUBLIC  "-//IETF//DTD HTML Level 2//EN"         html.dtd
PUBLIC  "-//IETF//DTD HTML Level 2//EN//2.0"    html.dtd this option-->
     
     <!ELEMENT TEXTAREA - - (#PCDATA)* -(INPUT|SELECT|TEXTAREA)>
     <!ATTLIST TEXTAREA
525          NAME CDATA #REQUIRED
             ROWS NUMBER #REQUIRED
             COLS NUMBER #REQUIRED
             %SDAFORM; "Para"
             %SDAPREF; "Input Text -- Ways to refer #AttVal(Name): "
530          >
     
     <!-- <TEXTAREA>                 An area for text input          -->
     <!-- <TEXTAREA NAME=...>        Name of form datum              -->
     <!-- <TEXTAREA ROWS=...>        Height of area                  -->
535  <!-- <TEXTAREA COLS=...>        Width of area                   -->
     
     ]]>
     
     
540  <!--======= Document Head ======================-->
     
     <![ %HTML.Recommended [
             <!ENTITY % head.extra "META* & LINK*">
     ]]>
545  
     <!ENTITY % head.extra "NEXTID? & META* & LINK*">
     
     <!ENTITY % head.content "TITLE & ISINDEX? & BASE? &
                              (%head.extra)">
550  
     <!ELEMENT HEAD O O  (%head.content)>
     
     <!-- <HEAD>     Document head   -->
     
555  <!ELEMENT TITLE - -  (#PCDATA)*>
     <!ATTLIST TITLE
             %SDAFORM; "Ti"    >
     
     <!-- <TITLE>    Title of document -->
560  
     <!ELEMENT LINK - O EMPTY>
     <!ATTLIST LINK
             HREF %URI #REQUIRED
             %linkExtraAttributes;
565          %SDAPREF; "Linked to Level 1: most general : #AttVal (TITLE) (URN) (HREF)>"    >
     
     <!-- <LINK>             Link from this document                 -->
     <!-- <LINK HREF="...">  Address of link destination             -->
     <!-- <LINK URN="...">   Lasting name of destination             -->
570  <!-- <LINK REL=...>     Relationship to most specific --
PUBLIC  "-//IETF//DTD HTML Level 1//EN"         html-1.dtd
PUBLIC  "-//IETF//DTD HTML Level 1//EN//2.0"    html-1.dtd

        -- Ways destination             -->
     <!-- <LINK REV=...>     Relationship of destination to refer this     -->
     <!-- <LINK TITLE="..."> Title of destination (advisory)         -->
     <!-- <LINK METHODS="..."> Operations allowed (advisory)         -->
     
575  <!ELEMENT ISINDEX - O EMPTY>
     <!ATTLIST ISINDEX
             %SDAPREF;
        "<Para>[Document is indexed/searchable.]</Para>">
     
580  <!-- <ISINDEX>          Document is a searchable index          -->
     
     <!ELEMENT BASE - O EMPTY>
     <!ATTLIST BASE
             HREF %URI; #REQUIRED     >
585  
     <!-- <BASE>             Base context document                   -->
     <!-- <BASE HREF="...">  Address for this document               -->
     
     <!ELEMENT NEXTID - O EMPTY>
590  <!ATTLIST NEXTID
             N %linkName #REQUIRED     >
     
     <!-- <NEXTID>           Next ID to Level 0: most general use for link name            -->
     <!-- <NEXTID N=...>     Next ID to most specific --
PUBLIC  "-//IETF//DTD use for link name            -->
595  
     <!ELEMENT META - O EMPTY>
     <!ATTLIST META
             HTTP-EQUIV  NAME    #IMPLIED
             NAME        NAME    #IMPLIED
600          CONTENT     CDATA   #REQUIRED    >
     
     <!-- <META>                     Generic Metainformation         -->
     <!-- <META HTTP-EQUIV=...>      HTTP response header name       -->
     <!-- <META NAME=...>            Metainformation name            -->
605  <!-- <META CONTENT="...">       Associated information          -->
     
     <!--======= Document Structure =================-->
     
     <![ %HTML.Deprecated [
610          <!ENTITY % html.content "HEAD, BODY, PLAINTEXT?">
     ]]>
     <!ENTITY % html.content "HEAD, BODY">
     
     <!ELEMENT HTML O O  (%html.content)>
615  <!ENTITY % version.attr "VERSION CDATA #FIXED '%HTML.Version;'">
     
     <!ATTLIST HTML Level 0//EN"         html-0.dtd
PUBLIC  "-//IETF//DTD
             %version.attr;
             %SDAFORM; "Book"
620          >
     
     <!-- <HTML>                     HTML Level 0//EN//2.0"    html-0.dtd

        -- ISO latin 1 entity set Document   -->


11.2. SGML Declaration for HTML 

     This is the SGML Declaration for HyperText Markup Language
     (HTML) as used by the World Wide Web (WWW) application:

     <!SGML  "ISO 8879:1986"
     --
             SGML Declaration for HyperText Markup Language (HTML).
     
  5  --
     
     CHARSET
              BASESET  "ISO 646:1983//CHARSET
                        International Reference Version
 10                     (IRV)//ESC 2/5 4/0"
              DESCSET  0   9   UNUSED
                       9   2   9
                       11  2   UNUSED
                       13  1   13
 15                    14  18  UNUSED
                       32  95  32
                       127 1   UNUSED
          BASESET   "ISO Registration Number 100//CHARSET
                     ECMA-94 Right Part of
 20                  Latin Alphabet Nr. 1//ESC 2/13 4/1"
     
              DESCSET  128  32   UNUSED
                       160  96    32
     
 25  CAPACITY        SGMLREF
                     TOTALCAP        150000
                     GRPCAP          150000
                     ENTCAP          150000
       
 30  SCOPE    DOCUMENT
     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
 35                     International Reference Version
                        (IRV)//ESC 2/5 4/0"
              DESCSET  0 128 0
              FUNCTION
                       RE          13
 40                    RS          10
                       SPACE       32
                       TAB SEPCHAR  9
             
     
 45           NAMING   LCNMSTRT ""
                       UCNMSTRT ""
                       LCNMCHAR ".-"
                       UCNMCHAR ".-"
                       NAMECASE GENERAL YES
 50                             ENTITY  NO
              DELIM    GENERAL  SGMLREF
                       SHORTREF SGMLREF
              NAMES    SGMLREF
              QUANTITY SGMLREF
 55                    ATTSPLEN 2100
                       LITLEN   1024
                       NAMELEN  72    -- somewhat arbitrary; taken from
                                     internet line length conventions --
                       PILEN    1024
 60                    TAGLEN   2100
                       GRPGTCNT 150
                       GRPCNT   64                   
     
     FEATURES
 65    MINIMIZE
         DATATAG  NO
         OMITTAG  YES
         RANK     NO
         SHORTTAG YES
 70    LINK
         SIMPLE   NO
         IMPLICIT NO
         EXPLICIT NO
       OTHER
 75      CONCUR   NO
         SUBDOC   NO
         FORMAL   YES
       APPINFO    "SDA"  --
PUBLIC  "-//IETF//ENTITIES Added Latin 1//EN"   ISOlat1.sgml

   5.2 HTML DTD

   This is the conforming SGML Document Type Definition for the
   HyperText Markup Language (HTML DTD):


Berners-Lee, Connolly, et. al.                                  Page 58

                                HTML 2.0                February 8, 1995 Access application
                         --
 80  >
     <!--    html.dtd

        Document Type Definition for the HyperText Markup Language
		 (HTML DTD) 
             $Id: html.dtd,v 1.24 1995/02/06 21:28:45 html.decl,v 1.15 1995/05/06 01:44:47 connolly Exp $
     
             Author: Daniel W. Connolly <connolly@hal.com>
 85  
             See Also: html.decl, html-0.dtd, html-1.dtd
	  http://www.hal.com/%7Econnolly/html-spec/index.html
	  http://info.cern.ch/hypertext/WWW/MarkUp2/MarkUp.html also: http://www.hal.com/%7Econnolly/html-spec
               http://info.cern.ch/hypertext/WWW/MarkUp/MarkUp.html
      -->

<!ENTITY % HTML.Version
        "-//IETF//DTD HTML 2.0//EN"

        -- Typical usage:

            <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
            <html>
            ...
            </html>
        --
        >


<!--============ Feature Test Entities ========================-->

<!ENTITY % HTML.Recommended "IGNORE"
	-- Certain features of the language are necessary


11.3. Sample SGML Open Entity Catalog for
	   compatibility with widespread usage, but they may
	   compromise HTML 

     The SGML standard describes an ``entity manager'' as the structural integrity
     portion or component of a document.
	   This feature test entity enables a more prescriptive
	   document type definition an SGML system that eliminates
	   those features.
	-->

<![ %HTML.Recommended [
        <!ENTITY % HTML.Deprecated "IGNORE">
]]>

<!ENTITY % HTML.Deprecated "INCLUDE"
	-- Certain features of maps SGML
     entities into the language are necessary for
	   compatibility with earlier versions of actual storage model (e.g., the specification,
	   but they tend to be used an implemented inconsistently,
	   and their use is deprecated. This feature test entity
	   enables a document type definition that eliminates
	   these features.
	-->


Berners-Lee, Connolly, et. al.                                  Page 59

                                HTML 2.0                February 8, 1995


<!ENTITY % HTML.Highlighting "INCLUDE"
	-- Use this feature test entity to validate that file
     system). The standard itself does not define a
	   document uses no highlighting tags, which may be
	   ignored on minimal implementations.
	-->

<!ENTITY % HTML.Forms "INCLUDE"
        -- Use this feature test entity to validate 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 document
           contains no forms, which may not be supported in minimal
           implementations
        -->

<!--============== Imported Names ==============================-->

<!ENTITY % Content-Type "CDATA"
        -- meaning format for an internet media type
           (aka MIME content type, as per RFC1521)
        -->

<!ENTITY % HTTP-Method "GET | POST"
        -- as per HTTP specification, application-
     independent entity catalog that maps external identifiers
     and/or entity names to file names.

     Each entry in progress
        -->

<!ENTITY % URI "CDATA"
        -- The term URI means a CDATA attribute
           whose value is the catalog associates a Uniform Resource Identifier, storage object
     identifier (such as defined by 
	"Universal Resource Identifiers" by Tim Berners-Lee
	aka RFC 1630

	Note that CDATA attributes are limited by a file name) with information about the LITLEN
	capacity (1024
     external entity that appears in the current version of html.decl),
	so SGML document. In
     addition to entries that URIs in HTML have associate public identifiers, a bounded length.

        -->


<!--========= DTD "Macros" =====================-->

<!ENTITY % heading "H1|H2|H3|H4|H5|H6">

<!ENTITY % list " UL | OL | DIR | MENU " >


<!--======= Character mnemonic entities =================-->

<!ENTITY % ISOlat1
     catalog entry can associate an entity name with a storage
     object indentifier. For example, the following are possible
     catalog entries:

             -- catalog: SGML Open style entity catalog for HTML --
             -- $Id: catalog,v 1.2 1994/11/30 23:45:18 connolly Exp $ --
     
             -- Ways to refer to Level 2: most general to most specific --
  5  PUBLIC  "-//IETF//DTD HTML//EN"                 html.dtd
     PUBLIC  "-//IETF//DTD HTML 2.0//EN"             html.dtd
     PUBLIC  "-//IETF//DTD HTML Level 2//EN"         html.dtd
     PUBLIC
  "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML">
%ISOlat1;


Berners-Lee, Connolly, et. al.                                  Page 60  "-//IETF//DTD HTML 2.0                February 8, 1995


<!ENTITY amp CDATA "&#38;" Level 2//EN"     html.dtd
     
 10          -- ampersand          -->
<!ENTITY gt CDATA "&#62;" Ways to refer to Level 1: most general to most specific -- greater than       -->
<!ENTITY lt CDATA "&#60;"
     PUBLIC  "-//IETF//DTD HTML Level 1//EN"         html-1.dtd
     PUBLIC  "-//IETF//DTD HTML 2.0 Level 1//EN"     html-1.dtd
     
             -- less than          -->
<!ENTITY quot CDATA "&#34;" Ways to refer to Level 0: most general to most specific -- double quote       -->


<!--========= SGML Document Access (SDA) Parameter Entities =====-->

<!--
 15  PUBLIC  "-//IETF//DTD HTML Level 0//EN"         html-0.dtd
     PUBLIC  "-//IETF//DTD HTML 2.0 contains SGML Document Access (SDA) fixed attributes
in support of easy transformation Level 0//EN"     html-0.dtd
     
     
             -- Ways to the International Committee
for Accessible Document Design (ICADD) DTD
	 "-//EC-USA-CDA/ICADD//DTD ICADD22//EN".
ICADD applications are designed refer to support usable access Strict Level 2: most general to
structured information by print-impaired individuals through
Braille, large print and voice synthesis.  For more information on
SDA most specific \
  & ICADD:  
        - ISO 12083:1993, Annex A.8, Facilities for Braille,
	  large print and computer voice
        - ICADD ListServ
	  <ICADD%ASUACAD.BITNET@ARIZVM1.ccit.arizona.edu>
        - Usenet news group bit.listserv.easi
        - Recording for the Blind, +1 800 221 4792
-->

<!ENTITY % SDAFORM  "SDAFORM  CDATA  #FIXED"
	  -- one to one mapping        -->
<!ENTITY % SDARULE  "SDARULE  CDATA  #FIXED"
	  -- context-sensitive mapping -->
<!ENTITY % SDAPREF  "SDAPREF  CDATA  #FIXED"  -- generated text prefix     -->
<!ENTITY % SDASUFF  "SDASUFF  CDATA  #FIXED"
 20  PUBLIC  "-//IETF//DTD HTML Strict//EN"                  html-s.dtd
     PUBLIC  "-//IETF//DTD HTML 2.0 Strict//EN"              html-s.dtd
     PUBLIC  "-//IETF//DTD HTML Strict Level 2//EN"          html-s.dtd
     PUBLIC  "-//IETF//DTD HTML 2.0 Strict Level 2//EN"      html-s.dtd
     
 25          -- generated text suffix     -->
<!ENTITY % SDASUSP  "SDASUSP  NAME   #FIXED" Ways to refer to Strict Level 1: most general to most specific \
  &  -- suspend transform process -->


<!--========== Text Markup =====================-->

<![ %HTML.Highlighting [

<!ENTITY % font " TT | B | I ">

<!ENTITY % phrase "EM | STRONG | CODE | SAMP | KBD | VAR | CITE ">

<!ENTITY % text "#PCDATA | A | IMG | BR | %phrase | %font">

<!ELEMENT (%font;|%phrase) - - (%text)*>
<!ATTLIST ( TT | CODE | SAMP | KBD | VAR )
        %SDAFORM; "Lit"
        >

Berners-Lee, Connolly, et. al.                                  Page 61
     PUBLIC  "-//IETF//DTD HTML Strict Level 1//EN"          html-1s.dtd
     PUBLIC  "-//IETF//DTD HTML 2.0                February 8, 1995


<!ATTLIST ( B | STRONG )
        %SDAFORM; "B"
        >
<!ATTLIST ( I | EM | CITE )
        %SDAFORM; "It"
        >

<!-- <TT>       Typewriter text                         -->
<!-- <B>        Bold text                               -->
<!-- <I>        Italic text                             -->

<!-- <EM>       Emphasized phrase                       -->
<!-- <STRONG>   Strong emphais                          -->
<!-- <CODE>     Source code phrase                      -->
<!-- <SAMP>     Sample text or characters               -->
<!-- <KBD>      Keyboard phrase, e.g. user input        -->
<!-- <VAR>      Variable phrase or substituable         -->
<!-- <CITE>     Name or title of cited work             -->

<!ENTITY % pre.content "#PCDATA | A | HR | BR | %font | %phrase">

]]>

<!ENTITY % text "#PCDATA | A | IMG | BR">

<!ELEMENT BR    - O EMPTY>
<!ATTLIST BR
        %SDAPREF; "&#RE;"
        >

<!-- <BR>       Line break      -->


<!--========= Link Markup ======================-->

<![ %HTML.Recommended [
        <!ENTITY % linkName "ID">
]]>

<!ENTITY % linkName "CDATA">

<!ENTITY % linkType "NAME" Strict Level 1//EN"      html-1s.dtd
     
             -- Ways to refer to Strict Level 0: most general to most specific \
  &  --
 30  PUBLIC  "-//IETF//DTD HTML Strict Level 0//EN"          html-0s.dtd
     PUBLIC  "-//IETF//DTD HTML 2.0 Strict Level 0//EN"      html-0s.dtd
     
             -- a ISO latin 1 entity set for HTML -- 
     PUBLIC  "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML"       ISOlat1.sg\
  &  ml


11.4. Character Entity Sets 

     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 the writer.


11.4.1. Numeric and Special Graphic Entity Set 

     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;    Less than sign
     >       gt      &gt;    Greater than sign
     &       amp     &amp;   Ampersand
     "       quot    &quot;  Double quote sign


11.4.2. ISO Latin 1 Character Entity Set 

     The following public text lists each of these will be the characters
     specified at a later date -->

<!ENTITY % linkExtraAttributes
        "REL %linkType #IMPLIED
        REV %linkType #IMPLIED
        URN CDATA #IMPLIED
        TITLE CDATA #IMPLIED
        METHODS NAMES #IMPLIED

Berners-Lee, Connolly, et. al.                                  Page 62 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 2.0                February 8, 1995


        ">

<![ %HTML.Recommended [
        <!ENTITY % A.content   "(%text)*"
        -- <H1><a name="xxx">Heading</a></H1> includes the entire entity set.

     <!-- (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 preferred to
           <a name="xxx"><H1>Heading</H1></a> included in all copies.
  5  -->
]]>
     <!-- Character entity set. Typical invocation:
          <!ENTITY % A.content   "(%heading|%text)*">

<!ELEMENT A     - - %A.content -(A)>
<!ATTLIST A
        HREF %URI #IMPLIED
        NAME %linkName #IMPLIED
        %linkExtraAttributes;
        %SDAPREF; "<Anchor: #AttList>"
        >
<!-- <A>		Anchor; source/destination of link ISOlat1 PUBLIC
            "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML">
          %ISOlat1;
 10  -->
     <!-- <A NAME="...">	Name of this anchor    Modified for use in HTML
             $Id: ISOlat1.sgml,v 1.2 1994/11/30 23:45:12 connolly Exp $ -->
<!-- <A HREF="...">	Address of link destination
     <!ENTITY AElig  CDATA "&#198;" -- capital AE diphthong (ligature) -->
<!-- <A URN="...">	Permanent address of destination
     <!ENTITY Aacute CDATA "&#193;" -- capital A, acute accent -->
<!-- <A REL=...>	Relationship to destination
 15  <!ENTITY Acirc  CDATA "&#194;" -- capital A, circumflex accent -->
<!-- <A REV=...>	Relationship of destination to this
     <!ENTITY Agrave CDATA "&#192;" -- capital A, grave accent -->
<!-- <A TITLE="...">	Title of destination (advisory)
     <!ENTITY Aring  CDATA "&#197;" -- capital A, ring -->
<!-- <A METHODS="...">	Operations on destination (advisory)
     <!ENTITY Atilde CDATA "&#195;" -- capital A, tilde -->


<!--========== Images ==========================-->

<!ELEMENT IMG    - O EMPTY>
<!ATTLIST IMG
        SRC %URI;  #REQUIRED
        ALT
     <!ENTITY Auml   CDATA #IMPLIED
        ALIGN (top|middle|bottom) #IMPLIED
        ISMAP (ISMAP) #IMPLIED
        %SDAPREF; "<Fig><?SDATrans Img: #AttList>#AttVal(Alt)</Fig>"
        >

<!-- <IMG>              Image; icon, glyph "&#196;" -- capital A, dieresis or illustration      -->
<!-- <IMG SRC="...">    Address of image object umlaut mark -->
<!-- <IMG ALT="...">    Textual alternative
 20  <!ENTITY Ccedil CDATA "&#199;" -- capital C, cedilla -->
<!-- <IMG ALIGN=...>    Position relative to text
     <!ENTITY ETH    CDATA "&#208;" -- capital Eth, Icelandic -->
<!-- <IMG ISMAP>        Each pixel can be a link
     <!ENTITY Eacute CDATA "&#201;" -- capital E, acute accent -->

<!--========== Paragraphs=======================-->

<!ELEMENT P     - O (%text)*>
<!ATTLIST P

Berners-Lee, Connolly, et. al.                                  Page 63

                                HTML 2.0                February 8, 1995


        %SDAFORM; "Para"
        >

<!-- <P>        Paragraph
     <!ENTITY Ecirc  CDATA "&#202;" -- capital E, circumflex accent -->


<!--========== Headings, Titles, Sections ===============-->

<!ELEMENT HR    - O EMPTY>
<!ATTLIST HR
        %SDAPREF; "&#RE;&#RE;"
        >

<!-- <HR>       Horizontal rule
     <!ENTITY Egrave CDATA "&#200;" -- capital E, grave accent -->

<!ELEMENT ( %heading )  - -  (%text;)*>
<!ATTLIST H1
        %SDAFORM; "H1"
        >
<!ATTLIST H2
        %SDAFORM; "H2"
        >
<!ATTLIST H3
        %SDAFORM; "H3"
        >
<!ATTLIST H4
        %SDAFORM; "H4"
        >
<!ATTLIST H5
        %SDAFORM; "H5"
        >
<!ATTLIST H6
        %SDAFORM; "H6"
        >

<!-- <H1>       Heading, level 1
 25  <!ENTITY Euml   CDATA "&#203;" -- capital E, dieresis or umlaut mark -->
<!-- <H2>       Heading, level 2
     <!ENTITY Iacute CDATA "&#205;" -- capital I, acute accent -->
<!-- <H3>       Heading, level 3
     <!ENTITY Icirc  CDATA "&#206;" -- capital I, circumflex accent -->
<!-- <H4>       Heading, level 4
     <!ENTITY Igrave CDATA "&#204;" -- capital I, grave accent -->
<!-- <H5>       Heading, level 5
     <!ENTITY Iuml   CDATA "&#207;" -- capital I, dieresis or umlaut mark -->
<!-- <H6>       Heading, level 6
 30  <!ENTITY Ntilde CDATA "&#209;" -- capital N, tilde -->


<!--========== Text Flows ======================-->

<![ %HTML.Forms [
     <!ENTITY % block.forms "BLOCKQUOTE | FORM | ISINDEX">
]]> Oacute CDATA "&#211;" -- capital O, acute accent -->
     <!ENTITY % block.forms "BLOCKQUOTE">

Berners-Lee, Connolly, et. al.                                  Page 64

                                HTML 2.0                February 8, 1995



<![ %HTML.Deprecated [ Ocirc  CDATA "&#212;" -- capital O, circumflex accent -->
     <!ENTITY % preformatted "PRE | XMP | LISTING">
]]> Ograve CDATA "&#210;" -- capital O, grave accent -->
     <!ENTITY Oslash CDATA "&#216;" -- capital O, slash -->
 35  <!ENTITY % preformatted "PRE"> Otilde CDATA "&#213;" -- capital O, tilde -->
     <!ENTITY % block "P | %list | DL
        | %preformatted
        | %block.forms"> Ouml   CDATA "&#214;" -- capital O, dieresis or umlaut mark -->
     <!ENTITY % flow "(%text|%block)*"> THORN  CDATA "&#222;" -- capital THORN, Icelandic -->
     <!ENTITY % pre.content "#PCDATA | A | HR | BR">
<!ELEMENT PRE - - (%pre.content)*>
<!ATTLIST PRE
        WIDTH NUMBER #implied
        %SDAFORM; "Lit"
        >

<!-- <PRE>              Preformatted text Uacute CDATA "&#218;" -- capital U, acute accent -->
<!-- <PRE WIDTH=...>    Maximum characters per line
     <!ENTITY Ucirc  CDATA "&#219;" -- capital U, circumflex accent -->

<![ %HTML.Deprecated [
 40  <!ENTITY % literal "CDATA" Ugrave CDATA "&#217;" -- historical, non-conforming parsing mode where
           the only markup signal is the end tag
           in full capital U, grave accent -->

<!ELEMENT (XMP|LISTING) - -  %literal>
<!ATTLIST XMP
        %SDAFORM; "Lit"
        %SDAPREF; "Example:&#RE;"
        >
<!ATTLIST LISTING
        %SDAFORM; "Lit"
        %SDAPREF; "Listing:&#RE;"
        >

<!-- <XMP>              Example section
     <!ENTITY Uuml   CDATA "&#220;" -- capital U, dieresis or umlaut mark -->
<!-- <LISTING>          Computer listing
     <!ENTITY Yacute CDATA "&#221;" -- capital Y, acute accent -->

<!ELEMENT PLAINTEXT - O %literal>
<!-- <PLAINTEXT>        Plain text passage
     <!ENTITY aacute CDATA "&#225;" -- small a, acute accent -->

<!ATTLIST PLAINTEXT
        %SDAFORM; "Lit"
        >

Berners-Lee, Connolly, et. al.                                  Page 65

                                HTML 2.0                February 8, 1995


]]>


<!--========== Lists ==================-->

<!ELEMENT DL    - -  (DT | DD)+>
<!ATTLIST DL
        COMPACT (COMPACT) #IMPLIED
        %SDAFORM; "List"
        %SDAPREF; "Definition List:"
        >

<!ELEMENT DT    - O (%text)*>
<!ATTLIST DT
        %SDAFORM; "Term"
        >

<!ELEMENT DD    - O %flow>
<!ATTLIST DD
        %SDAFORM; "LItem"
        >

<!-- <DL>               Definition list,
     <!ENTITY acirc  CDATA "&#226;" -- small a, circumflex accent -->
 45  <!ENTITY aelig  CDATA "&#230;" -- small ae diphthong (ligature) -->
     <!ENTITY agrave CDATA "&#224;" -- small a, grave accent -->
     <!ENTITY aring  CDATA "&#229;" -- small a, ring -->
     <!ENTITY atilde CDATA "&#227;" -- small a, tilde -->
     <!ENTITY auml   CDATA "&#228;" -- small a, dieresis or glossary umlaut mark -->
<!-- <DL COMPACT>       Compact style list
 50  <!ENTITY ccedil CDATA "&#231;" -- small c, cedilla -->
<!-- <DT>               Term in definition list
     <!ENTITY eacute CDATA "&#233;" -- small e, acute accent -->
<!-- <DD>               Definition of term
     <!ENTITY ecirc  CDATA "&#234;" -- small e, circumflex accent -->

<!ELEMENT (OL|UL) - -  (LI)+>
<!ATTLIST OL
        COMPACT (COMPACT) #IMPLIED
        %SDAFORM; "List"
        >
<!ATTLIST UL
        COMPACT (COMPACT) #IMPLIED
        %SDAFORM; "List"
        >
<!-- <UL>               Unordered list
     <!ENTITY egrave CDATA "&#232;" -- small e, grave accent -->
<!-- <UL COMPACT>       Compact list style
     <!ENTITY eth    CDATA "&#240;" -- small eth, Icelandic -->
<!-- <OL>               Ordered,
 55  <!ENTITY euml   CDATA "&#235;" -- small e, dieresis or numbered list umlaut mark -->
<!-- <OL COMPACT>       Compact list style
     <!ENTITY iacute CDATA "&#237;" -- small i, acute accent -->


<!ELEMENT (DIR|MENU) - -  (LI)+ -(%block)>
<!ATTLIST DIR
        COMPACT (COMPACT) #IMPLIED
        %SDAFORM; "List"
        %SDAPREF; "<LHead>Directory</LHead>"
        >
<!ATTLIST MENU
        COMPACT (COMPACT) #IMPLIED

Berners-Lee, Connolly, et. al.                                  Page 66

                                HTML 2.0                February 8, 1995


        %SDAFORM; "List"
        %SDAPREF; "<LHead>Menu</LHead>"
        >

<!-- <DIR>              Directory list
     <!ENTITY icirc  CDATA "&#238;" -- small i, circumflex accent -->
<!-- <DIR COMPACT>      Compact list style
     <!ENTITY igrave CDATA "&#236;" -- small i, grave accent -->
<!-- <MENU>             Menu list
     <!ENTITY iuml   CDATA "&#239;" -- small i, dieresis or umlaut mark -->
 60  <!ENTITY ntilde CDATA "&#241;" -- small n, tilde -->
<!-- <MENU COMPACT>     Compact list style
     <!ENTITY oacute CDATA "&#243;" -- small o, acute accent -->

<!ELEMENT LI    - O %flow>
<!ATTLIST LI
        %SDAFORM; "LItem"
        >

<!-- <LI>               List item
     <!ENTITY ocirc  CDATA "&#244;" -- small o, circumflex accent -->

<!--========== Document Body ===================-->

<![ %HTML.Recommended [
     <!ENTITY % body.content "(%heading|%block|HR|ADDRESS|IMG)*" ograve CDATA "&#242;" -- <h1>Heading</h1>
	   <p>Text ...
		is preferred to
	   <h1>Heading</h1>
	   Text ... small o, grave accent -->
]]>
     <!ENTITY % body.content "(%heading | %text | %block |
				 HR | ADDRESS)*">

<!ELEMENT BODY O O  %body.content>

<!-- <BODY>     Document body oslash CDATA "&#248;" -- small o, slash -->

<!ELEMENT BLOCKQUOTE - - %body.content>
<!ATTLIST BLOCKQUOTE
        %SDAFORM; "BQ"
        >

<!-- <BLOCKQUOTE>       Quoted passage
 65  <!ENTITY otilde CDATA "&#245;" -- small o, tilde -->

<!ELEMENT ADDRESS - - (%text|P)*>
<!ATTLIST  ADDRESS
        %SDAFORM; "Lit"
        %SDAPREF; "Address:&#RE;"
        >

<!-- <ADDRESS>	Address, signature,
     <!ENTITY ouml   CDATA "&#246;" -- small o, dieresis or byline umlaut mark -->


Berners-Lee, Connolly, et. al.                                  Page 67

                                HTML 2.0                February 8, 1995



<!--======= Forms ====================-->

<![ %HTML.Forms [

<!ELEMENT FORM - - %body.content -(FORM) +(INPUT|SELECT|TEXTAREA)>
<!ATTLIST FORM
        ACTION %URI #IMPLIED
        METHOD (%HTTP-Method) GET
        ENCTYPE %Content-Type; "application/x-www-form-urlencoded"
        %SDAPREF; "<Para>Form:</Para>"
        %SDASUFF; "<Para>Form End.</Para>"
        >

<!-- <FORM>                     Fill-out or data-entry form
     <!ENTITY szlig  CDATA "&#223;" -- small sharp s, German (sz ligature) -->
<!-- <FORM ACTION="...">        Address for completed form
     <!ENTITY thorn  CDATA "&#254;" -- small thorn, Icelandic -->
<!-- <FORM METHOD=...>          Method of submitting form
     <!ENTITY uacute CDATA "&#250;" -- small u, acute accent -->
<!-- <FORM ENCTYPE="...">       Representation of form data
 70  <!ENTITY ucirc  CDATA "&#251;" -- small u, circumflex accent -->
     <!ENTITY ugrave CDATA "&#249;" -- small u, grave accent -->
     <!ENTITY % InputType "(TEXT | PASSWORD | CHECKBOX |
                        RADIO | SUBMIT | RESET |
                        IMAGE | HIDDEN )">
<!ELEMENT INPUT - O EMPTY>
<!ATTLIST INPUT
	TYPE %InputType TEXT
	NAME uuml   CDATA #IMPLIED
	VALUE "&#252;" -- small u, dieresis or umlaut mark -->
     <!ENTITY yacute CDATA #IMPLIED
	SRC %URI #IMPLIED
	CHECKED (CHECKED) #IMPLIED
	SIZE "&#253;" -- small y, acute accent -->
     <!ENTITY yuml   CDATA #IMPLIED
	MAXLENGTH NUMBER #IMPLIED
	ALIGN (top|middle|bottom) #IMPLIED
        %SDAPREF; "Input: "
	>

<!-- <INPUT>			Form input datum "&#255;" -- small y, dieresis or umlaut mark -->
<!-- <INPUT TYPE=...>		Type


12. Glossary 

     character
                    An atom of input interaction	-->
<!-- <INPUT NAME=...>		Name information, for example a letter or a
                    digit. Graphic characters have associated glyphs,
                    where as control characters have associated
                    processing semantics.

     character
     encoding scheme
                    A function whose domain is the set of form datum		-->
<!-- <INPUT VALUE="...">	Default/initial/selected value	-->
<!-- <INPUT SRC="...">		Address sequences of image		-->
<!-- <INPUT CHECKED>		Initial state
                    octets, and whose range is "on"		-->
<!-- <INPUT SIZE=...>		Field size hint			-->
<!-- <INPUT MAXLENGTH=...>	Data length maximum		-->
<!-- <INPUT ALIGN=...>		Image alignment			-->

<!ELEMENT SELECT - - (OPTION+) -(INPUT|SELECT|TEXTAREA)>
<!ATTLIST SELECT
        NAME CDATA #REQUIRED
        SIZE NUMBER #IMPLIED
        MULTIPLE (MULTIPLE) #IMPLIED

Berners-Lee, Connolly, et. al.                                  Page 68

                                HTML 2.0                February 8, 1995


        %SDAFORM; "List"
        %SDAPREF;
        "<LHead>Select #AttVal(Multiple)</LHead>"
	>

<!-- <SELECT>			Selection 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 option(s)		-->
<!-- <SELECT NAME=...>		Name the
                    integers and whose range is a character
                    repertoire. That is, for some set of integers
                    (usually of the form datum		-->
<!-- <SELECT SIZE=...>		Options displayed at {0, 1, 2, ..., N} ), a time	-->
<!-- <SELECT MULTIPLE>		Multiple selections allowed	-->

<!ELEMENT OPTION - O (#PCDATA)*>
<!ATTLIST OPTION
        SELECTED (SELECTED) #IMPLIED
        VALUE CDATA #IMPLIED
        %SDAFORM; "LItem"
        %SDAPREF;
        "Option: #AttVal(Value) #AttVal(Selected)"
	>

<!-- <OPTION> 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 selection option		-->
<!-- <OPTION SELECTED>		Initial state			-->
<!-- <OPTION VALUE="...">	Form datum value for user agent that conforms to this option-->

<!ELEMENT TEXTAREA - - (#PCDATA)* -(INPUT|SELECT|TEXTAREA)>
<!ATTLIST TEXTAREA
        NAME CDATA #REQUIRED
        ROWS NUMBER #REQUIRED
        COLS NUMBER #REQUIRED
        %SDAFORM; "Para"
        %SDAPREF; "Input Text -- #AttVal(Name): "
        >

<!-- <TEXTAREA>			An area for text input		-->
<!-- <TEXTAREA NAME=...>	Name specification
                    in its processing of form datum		-->
<!-- <TEXTAREA ROWS=...>	Height the Internet Media Type
                    `text/html; version=2.0'.

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

     element
                    A component of the hierarchical structure defined
                    by a document type definition; it is identified in
                    a document instance by descriptive markup, sually
                    a start-tag and end-tag. [SGML]

     end-tag
                    Descriptive markup that identifies the end of area			-->
<!-- <TEXTAREA COLS=...>	Width an
                    element. [SGML]

     entity
                    data with an associated notation or
                    interpretation; for example, a sequence of area			-->

]]>


<!--======= Document Head ======================-->

<![ %HTML.Recommended [
	<!ENTITY % head.extra "META* & LINK*">
]]>

<!ENTITY % head.extra "NEXTID? & META* & LINK*">

<!ENTITY % head.content "TITLE & ISINDEX? & BASE? &
			 (%head.extra)">

Berners-Lee, Connolly, et. al.                                  Page 69 octets
                    associated with an Internet Media Type.[SGML]

     HTML 2.0                February 8, 1995



<!ELEMENT HEAD O O  (%head.content)>

<!-- <HEAD>     Document head   -->

<!ELEMENT TITLE - -  (#PCDATA)*>
<!ATTLIST TITLE
        %SDAFORM; "Ti"    >

<!-- <TITLE>    Title document
                    An SGML document conforming to this document type
                    definition.

     markup
                    Syntactically delimited characters added to the
                    data of a document -->

<!ELEMENT LINK - O EMPTY>
<!ATTLIST LINK
        HREF %URI #REQUIRED
        %linkExtraAttributes;
        %SDAPREF; "Linked to : #AttVal (TITLE) (URN) (HREF)>"    >

<!-- <LINK>		Link from represent its structure.
                    There are four different kinds of markup:
                    descriptive markup (tags), references, markup
                    declarations, and processing instructions.[SGML]

     may
                    A document or user interface is conforming whether
                    this statement applies or not.

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

     must
                    Documents or user agents in conflict with this
                    statement are not conforming.

     SGML document			-->
<!-- <LINK HREF="...">	Address
                    A sequence of link destination		-->
<!-- <LINK URN="...">	Lasting name characters organized physically as a
                    set of destination		-->
<!-- <LINK REL=...>	Relationship to destination		-->
<!-- <LINK REV=...>	Relationship entities and logically into a hierarchy of
                    elements. An SGML document consists of destination to this 	-->
<!-- <LINK TITLE="...">	Title data
                    characters and markup; the markup describes the
                    structure of destination (advisory)	 	-->
<!-- <LINK METHODS="..."> Operations allowed (advisory)		-->

<!ELEMENT ISINDEX - O EMPTY>
<!ATTLIST ISINDEX
        %SDAPREF;
   "<Para>[Document is indexed/searchable.]</Para>">

<!-- <ISINDEX>          Document is the information and an instance of
                    that structure.[SGML]

     shall
                    If a searchable index          -->

<!ELEMENT BASE - O EMPTY>
<!ATTLIST BASE
        HREF %URI; #REQUIRED     >

<!-- <BASE>             Base context document                   -->
<!-- <BASE HREF="...">  Address for or user agent conflicts with this document               -->

<!ELEMENT NEXTID - O EMPTY>
<!ATTLIST NEXTID
        N %linkName #REQUIRED     >

<!-- <NEXTID>		Next ID
                    statement, it does not conform to use for link name		-->
<!-- <NEXTID N=...>	Next ID this
                    specification.

     should
                    If a document or user agent conflicts with this
                    statement, undesirable results may occur in
                    practice even though it conforms to use for link name		-->

<!ELEMENT META - O EMPTY>
<!ATTLIST META
        HTTP-EQUIV  NAME    #IMPLIED
        NAME        NAME    #IMPLIED

Berners-Lee, Connolly, et. al.                                  Page 70

                                HTML 2.0                February 8, 1995


        CONTENT     CDATA   #REQUIRED    >

<!-- <META>                     Generic Metainformation         -->
<!-- <META HTTP-EQUIV=...>      HTTP response header name       -->
<!-- <META HTTP-EQUIV=...>      Metainformation name            -->
<!-- <META CONTENT="...">       Associated information          -->

<!--======= Document Structure =================-->

<![ %HTML.Deprecated [
        <!ENTITY % html.content "HEAD, BODY, PLAINTEXT?">
]]>
<!ENTITY % html.content "HEAD, BODY">

<!ELEMENT HTML O O  (%html.content)>
<!ENTITY % version.attr "VERSION CDATA #FIXED '%HTML.Version;'">

<!ATTLIST HTML
        %version.attr;
        %SDAFORM; "Book"
        >

<!-- <HTML>			HTML Document	-->

5.2.1 ISO Latin 1 Definitions for HTML

<!-- (C) International Organization this
                    specification.

     start-tag
                    Descriptive markup that identifies the start of an
                    element and specifies its generic identifier and
                    attributes. [SGML]

     
     syntax-reference
     character set
                    A coded character set whose range includes all
                    characters used for Standardization 1986
     Permission markup; e.g. name characters
                    and delimiter characters.

     tag
                    Markup that delimits an element. A tag includes a
                    name which refers to copy an element declaration in any the
                    DTD, and may include attributes.[SGML]

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

     typical
                    Typical processing is granted described for use with
     conforming SGML systems many elements.
                    This is not a mandatory part of the specification
                    but is given as guidance for designers and applications to help
                    explain the uses for which the elements were
                    intended.

     URI
                    A Universal Resource Identifier is a formatted
                    string that serves as defined an identifier for a
                    resource, typcally on the Internet. URIs are used
                    in
     ISO 8879:1986, provided this notice HTML to identify the destination of hypertext
                    links, the source of in-line images, and the
                    object of form actions. URIs in common use include
                    Uniform Resource Locators (URLs)[URL] and Relative
                    URLs[RELURL].

     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.

     WWW
                    The World-Wide Web is included a hypertext-based,
                    distributed information system created by
                    researchers at CERN in Switzerland. Users may
                    create, edit or browse hypertext documents.
                    `http://www.w3.org/'


13. Bibliography 

     [URI]
                    T. Berners-Lee. ``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.'' RFC 1630, CERN,
                    June 1994.

     [URL]
                    T. Berners-Lee, L. Masinter, and M. McCahill.
                    ``Uniform Resource Locators (URL).'' RFC 1738,
                    CERN, Xerox PARC, University of Minnesota, October
                    1994.

     [HTTP]
                    T. Berners-Lee, R. T. Fielding, and H. Frystyk
                    Nielsen. ``Hypertext Transfer Protocol -
                    HTTP/1.0.'' Work in Progress
                    (draft-ietf-http-v10-spec-00.ps), MIT, UC Irvine,
                    CERN, March 1995.

     [MIME]
                    N. Borenstein and N. Freed. ``MIME (Multipurpose
                    Internet Mail Extensions) Part One: Mechanisms for
                    Specifying and Describing the Format of Internet
                    Message Bodies.'' RFC 1521, Bellcore, Innosoft,
                    September 1993.

     [RELURL]
                    R. T. Fielding. ``Relative Uniform Resource
                    Locators.'' Work in all copies.
-->
<!-- Progress (draft-ietf-uri-
                    relative-url-06.txt), UC Irvine, March 1995.

     [GOLD90]
                    C. F. Goldfarb. ``The SGML Handbook.'' Y.
                    Rubinsky, Ed., Oxford University Press, 1990.

     [IMEDIA]
                    J. Postel. ``Media Type Registration Procedure.''
                    RFC 1590, USC/ISI, March 1994.

     [IANA]
                    J. Reynolds and J. Postel. ``Assigned Numbers.''
                    STD 2, RFC 1700, USC/ISI, October 1994.

     [SQ91]
                    SoftQuad. ``The SGML Primer.'' 3rd ed., SoftQuad
                    Inc., 1991.

     [US-ASCII]
                    US-ASCII. Coded Character entity set. Typical invocation:
     <!ENTITY % ISOlat1 PUBLIC
       "-//IETF//ENTITIES Added Latin 1 for HTML//EN">
     %ISOlat1;
-->
<!-- Modified Set - 7-Bit American
                    Standard Code for use in HTML
   $Id: ISOlat1.sgml,v 1.1 1994/09/24 14:06:34 connolly Exp $ -->
<!ENTITY AElig  CDATA "&#198;" -- capital AE diphthong (ligature) -->
<!ENTITY Aacute CDATA "&#193;" -- capital A, acute accent -->
<!ENTITY Acirc  CDATA "&#194;" -- capital A, circumflex accent -->
<!ENTITY Agrave CDATA "&#192;" -- capital A, grave accent -->
<!ENTITY Aring  CDATA "&#197;" Information Interchange.
                    Standard ANSI X3.4-1986, ANSI, 1986.

     [ISO-8859-1]
                    ISO 8859. International Standard -- capital A, ring -->
<!ENTITY Atilde CDATA "&#195;" Information
                    Processing -- capital A, tilde -->
<!ENTITY Auml   CDATA "&#196;" 8-bit Single-Byte Coded Graphic
                    Character Sets -- capital A, dieresis or umlaut Part 1: Latin Alphabet No. 1,
                    ISO 8859-1:1987. Part 2: Latin alphabet No. 2, ISO
                    8859-2, 1987. Part 3: Latin alphabet No. 3, ISO
                    8859-3, 1988. Part 4: Latin alphabet No. 4, ISO
                    8859-4, 1988. Part 5: Latin/Cyrillic alphabet, ISO
                    8859-5, 1988. Part 6: Latin/Arabic alphabet, ISO
                    8859-6, 1987. Part 7: Latin/Greek alphabet, ISO
                    8859-7, 1987. Part 8: Latin/Hebrew alphabet, ISO
                    8859-8, 1988. Part 9: Latin alphabet No. 5, ISO
                    8859-9, 1990.

     [SGML]
                    ISO 8879. Information Processing - Text and Office
                    Systems - Standard Generalized Markup Language
                    (SGML), 1986.


14. Appendices 

     These appendices are provided for informational reasons only
     - they do not form a part of the HTML specification.


14.1. The ISO-8859-1 Coded Character Set 

     This list, sorted numerically, is derived from ISO-8859-1
     8-bit single-byte coded graphic character set:

     REFERENCE       DESCRIPTION
     &#00; - &#08;   Unused
     &#09;           Horizontal tab
     &#10;           Line feed
     &#11; - &#31;   Unused
     &#32;           Space
     &#33;           Exclamation mark
     &#34;           Quotation mark
     &#35;           Number sign
     &#36;           Dollar sign
     &#37;           Percent sign
     &#38;           Ampersand
     &#39;           Apostrophe
     &#40;           Left parenthesis
     &#41;           Right parenthesis
     &#42;           Asterisk
     &#43;           Plus sign
     &#44;           Comma
     &#45;           Hyphen
     &#46;           Period (fullstop)
     &#47;           Solidus (slash)
     &#48; - &#57;   Digits 0-9
     &#58;           Colon
     &#59;           Semi-colon
     &#60;           Less than
     &#61;           Equals sign
     &#62;           Greater than
     &#63;           Question mark -->
<!ENTITY Ccedil CDATA "&#199;" -- capital C, cedilla -->
<!ENTITY ETH    CDATA "&#208;" -- capital Eth, Icelandic -->
<!ENTITY Eacute CDATA "&#201;" -- capital E, acute accent -->
<!ENTITY Ecirc  CDATA "&#202;" -- capital E, circumflex
     &#64;           Commercial at
     &#65; - &#90;   Letters A-Z
     &#91;           Left square bracket
     &#92;           Reverse solidus (backslash)
     &#93;           Right square bracket
     &#94;           Caret
     &#95;           Horizontal bar (underscore)
     &#96;           Acute accent -->
<!ENTITY Egrave CDATA "&#200;" -- capital E, grave
     &#97; - &#122;  Letters a-z
     &#123;          Left curly brace
     &#124;          Vertical bar
     &#125;          Right curly brace
     &#126;          Tilde
     &#127; - &#160; Unused
     &#161;          Inverted exclamation
     &#162;          Cent sign
     &#163;          Pound sterling
     &#164;          General currency sign
     &#165;          Yen sign
     &#166;          Broken vertical bar
     &#167;          Section sign
     &#168;          Umlaut (dieresis)
     &#169;          Copyright
     &#170;          Feminine ordinal
     &#171;          Left angle quote, guillemotleft
     &#172;          Not sign
     &#173;          Soft hyphen
     &#174;          Registered trademark
     &#175;          Macron accent -->

Berners-Lee, Connolly, et. al.                                  Page 71

                                HTML 2.0                February 8, 1995


<!ENTITY Euml   CDATA "&#203;" -- capital E, dieresis
     &#176;          Degree sign
     &#177;          Plus or umlaut mark -->
<!ENTITY Iacute CDATA "&#205;" -- capital I, acute accent -->
<!ENTITY Icirc  CDATA "&#206;" -- capital I, circumflex minus
     &#178;          Superscript two
     &#179;          Superscript three
     &#180;          Acute accent -->
<!ENTITY Igrave CDATA "&#204;" -- capital I,
     &#181;          Micro sign
     &#182;          Paragraph sign
     &#183;          Middle dot
     &#184;          Cedilla
     &#185;          Superscript one
     &#186;          Masculine ordinal
     &#187;          Right angle quote, guillemotright
     &#188;          Fraction one-fourth
     &#189;          Fraction one-half
     &#190;          Fraction three-fourths
     &#191;          Inverted question mark
     &#192;          Capital A, grave accent -->
<!ENTITY Iuml   CDATA "&#207;" -- capital I, dieresis or umlaut mark -->
<!ENTITY Ntilde CDATA "&#209;" -- capital N, tilde -->
<!ENTITY Oacute CDATA "&#211;" -- capital O,
     &#193;          Capital A, acute accent -->
<!ENTITY Ocirc  CDATA "&#212;" -- capital O,
     &#194;          Capital A, circumflex accent -->
<!ENTITY Ograve CDATA "&#210;" -- capital O, grave accent -->
<!ENTITY Oslash CDATA "&#216;" -- capital O, slash -->
<!ENTITY Otilde CDATA "&#213;" -- capital O,
     &#195;          Capital A, tilde -->
<!ENTITY Ouml   CDATA "&#214;" -- capital O,
     &#196;          Capital A, dieresis or umlaut mark -->
<!ENTITY THORN  CDATA "&#222;" -- capital THORN, Icelandic -->
<!ENTITY Uacute CDATA "&#218;" -- capital U,
     &#197;          Capital A, ring
     &#198;          Capital AE dipthong (ligature)
     &#199;          Capital C, cedilla
     &#200;          Capital E, grave accent
     &#201;          Capital E, acute accent -->
<!ENTITY Ucirc  CDATA "&#219;" -- capital U,
     &#202;          Capital E, circumflex accent -->
<!ENTITY Ugrave CDATA "&#217;" -- capital U, grave accent -->
<!ENTITY Uuml   CDATA "&#220;" -- capital U,
     &#203;          Capital E, dieresis or umlaut mark -->
<!ENTITY Yacute CDATA "&#221;" -- capital Y, acute
     &#204;          Capital I, grave accent -->
<!ENTITY aacute CDATA "&#225;" -- small a,
     &#205;          Capital I, acute accent -->
<!ENTITY acirc  CDATA "&#226;" -- small a, circumflex accent -->
<!ENTITY aelig  CDATA "&#230;" -- small ae diphthong (ligature) -->
<!ENTITY agrave CDATA "&#224;" -- small a, grave accent -->
<!ENTITY aring  CDATA "&#229;" -- small a, ring -->
<!ENTITY atilde CDATA "&#227;" -- small a, tilde -->
<!ENTITY auml   CDATA "&#228;" -- small a,
     &#206;          Capital I, circumflex accent
     &#207;          Capital I, dieresis or umlaut mark -->
<!ENTITY ccedil CDATA "&#231;" -- small c, cedilla -->
<!ENTITY eacute CDATA "&#233;" -- small e,
     &#208;          Capital Eth, Icelandic
     &#209;          Capital N, tilde
     &#210;          Capital O, grave accent
     &#211;          Capital O, acute accent -->
<!ENTITY ecirc  CDATA "&#234;" -- small e,
     &#212;          Capital O, circumflex accent -->
<!ENTITY egrave CDATA "&#232;" -- small e, grave accent -->
<!ENTITY eth    CDATA "&#240;" -- small eth, Icelandic -->
<!ENTITY euml   CDATA "&#235;" -- small e,
     &#213;          Capital O, tilde
     &#214;          Capital O, dieresis or umlaut mark -->
<!ENTITY iacute CDATA "&#237;" -- small i,
     &#215;          Multiply sign
     &#216;          Capital O, slash
     &#217;          Capital U, grave accent
     &#218;          Capital U, acute accent -->
<!ENTITY icirc  CDATA "&#238;" -- small i,
     &#219;          Capital U, circumflex accent -->
<!ENTITY igrave CDATA "&#236;" -- small i, grave accent -->
<!ENTITY iuml   CDATA "&#239;" -- small i,
     &#220;          Capital U, dieresis or umlaut mark -->
<!ENTITY ntilde CDATA "&#241;" -- small n, tilde -->
<!ENTITY oacute CDATA "&#243;" -- small o,
     &#221;          Capital Y, acute accent -->
<!ENTITY ocirc  CDATA "&#244;" -- small o,
     &#222;          Capital THORN, Icelandic
     &#223;          Small sharp s, German (sz ligature)
     &#224;          Small a, grave accent
     &#225;          Small a, acute accent
     &#226;          Small a, circumflex accent -->
<!ENTITY ograve CDATA "&#242;" -- small o,
     &#227;          Small a, tilde
     &#228;          Small a, dieresis or umlaut mark
     &#229;          Small a, ring
     &#230;          Small ae dipthong (ligature)
     &#231;          Small c, cedilla
     &#232;          Small e, grave accent -->
<!ENTITY oslash CDATA "&#248;" -- small o, slash -->
<!ENTITY otilde CDATA "&#245;" -- small o, tilde -->
<!ENTITY ouml   CDATA "&#246;" -- small o,
     &#233;          Small e, acute accent
     &#234;          Small e, circumflex accent
     &#235;          Small e, dieresis or umlaut mark -->
<!ENTITY szlig  CDATA "&#223;" -- small sharp s, German(sz ligature)-->
<!ENTITY thorn  CDATA "&#254;" -- small thorn, Icelandic -->
<!ENTITY uacute CDATA "&#250;" -- small u,
     &#236;          Small i, grave accent
     &#237;          Small i, acute accent -->
<!ENTITY ucirc  CDATA "&#251;" -- small u,
     &#238;          Small i, circumflex accent -->
<!ENTITY ugrave CDATA "&#249;" -- small u, grave accent -->
<!ENTITY uuml   CDATA "&#252;" -- small u,
     &#239;          Small i, dieresis or umlaut mark -->
<!ENTITY yacute CDATA "&#253;" -- small y,
     &#240;          Small eth, Icelandic
     &#241;          Small n, tilde
     &#242;          Small o, grave accent
     &#243;          Small o, acute accent -->
<!ENTITY yuml   CDATA "&#255;" -- small y,
     &#244;          Small o, circumflex accent
     &#245;          Small o, tilde
     &#246;          Small o, dieresis or umlaut mark -->

Berners-Lee, Connolly, et. al.                                  Page 72

                                HTML 2.0                February 8, 1995



   5.3 HTML Level 0 DTD

      This is the Document Type Definition for the HyperText
      Markup Language as used by minimally conforming World Wide
      Web applications (HTML Level 0 DTD):

<!--	html-0.dtd

        Document Type Definition for the HyperText Markup Language
        as used by minimally conforming World Wide Web applications
	(HTML Level 0 DTD).

	$Id: html-0.dtd,v 1.11 1995/01/28 05:59:32 connolly Exp $

	Author: Daniel W. Connolly <connolly@hal.com>
	See Also: http://www.hal.com/%7Econnolly/html-spec/index.html
		  http://info.cern.ch/hypertext/WWW/MarkUp2/MarkUp.html
-->

<!ENTITY % HTML.Version
	"-//IETF//DTD HTML 2.0 Level 0//EN"
	-- public identifier for "minimal conformance" version             -- 

        -- Typical usage:

            <!DOCTYPE HTML PUBLIC
		"-//IETF//DTD HTML Level 0//EN">
	    <html>
	    ...
	    </html>
	--
	>

<!-- Feature Test Entities -->

<!ENTITY % HTML.Highlighting "IGNORE">
<!ENTITY % HTML.Forms "IGNORE">

<!ENTITY % head.extra " ">
<!ENTITY % linkExtraAttributes " ">

<!ENTITY % html PUBLIC "-//IETF//DTD HTML 2.0//EN">
%html;

   5.4 HTML Level 1 DTD
     &#247;          Division sign
     &#248;          Small o, slash
     &#249;          Small u, grave accent
     &#250;          Small u, acute accent
     &#251;          Small u, circumflex accent
     &#252;          Small u, dieresis or umlaut mark
     &#253;          Small y, acute accent
     &#254;          Small thorn, Icelandic
     &#255;          Small y, dieresis or umlaut mark


14.2. Obsolete Features 

     This is the Document Type Definition section describes elements that are no longer part of
     HTML. Client implementors should implement these obsolete
     elements for the HyperText
      Markup Language compatibility with Level 1 Extensions (HTML Level 1 DTD):


Berners-Lee, Connolly, et. al.                                  Page 73

                                HTML 2.0                February 8, 1995


<!--	html-1.dtd

        Document Type Definition for previous versions of the HyperText Markup Language
	with Level 1 Extensions	(HTML Level 1 DTD).

	$Id: html-1.dtd,v 1.6 1994/11/30 23:45:26 connolly Exp $

	Author: Daniel W. Connolly <connolly@hal.com>
	See Also: http://www.hal.com/%7Econnolly/html-spec/index.html
		  http://info.cern.ch/hypertext/WWW/MarkUp2/MarkUp.html
-->

<!ENTITY % HTML.Version
	"-//IETF//DTD HTML 2.0 Level 1//EN"

        -- Typical usage:

            <!DOCTYPE
     HTML PUBLIC
		"-//IETF//DTD specification.


14.2.1. Comment Element 

     The Comment element is used to delimit unneeded text and
     comments. The Comment element has been introduced in some
     HTML Level 1//EN">
	    <html>
	    ...
	    </html>
	--
	>

<!-- Feature Test Entities -->
<!ENTITY % HTML.Forms "IGNORE">

<!ENTITY % html PUBLIC "-//IETF//DTD applications but should be replaced by the SGML comment
     feature in new HTML 2.0//EN">
%html;

7. Glossary interpreters (see Section 2.2.5).


14.2.2. Highlighted Phrase Element 

     <HP>

     The HTML specification uses these words with precise
   meanings:

   attribute

      A syntactical component Highlighted Phrase element should be ignored if not
     implemented. This element has been replaced by more
     meaningful elements (see Section 8).

     Example of use:

     <HP1>first highlighted phrase</HP1>non-
     highlighted text<HP2>second highlighted phrase</HP2> etc.


14.2.3. Plain Text Element 

     <PLAINTEXT>

     The Plain Text element is used to terminates the HTML entity
     and to indicate that what follows is not SGML which does not
     require parsing. Instead, an old HTTP convention specified
     that what followed was an HTML element which ASCII (MIME ``text/plain'') body.
     Its presence is
      often used to specify a characteristic quality of an
      element, other than type or content.

   document type definition (DTD)

      A DTD optimization. There is a collection no closing tag.

     Example of declarations (entity, element,
      attribute, link, map, etc.) in SGML syntax that defines
      the components and structures available for a class
      (type) use:

     <PLAINTEXT>
     0001 This is line one of documents. a long listing
     0002 file from <ANY@HOST.INC.COM> which is sent


14.2.4. Example and Listing Elements 

     <XMP> ... </XMP> and <LISTING> ... </LISTING>

     The Example and Listing elements have been replaced by the
     Preformatted Text element

Berners-Lee, Connolly, et. al.                                  Page 74

                                HTML 2.0                February 8, 1995



      A component (Section 10.2).

     These styles allow text of fixed-width characters to be
     embedded absolutely as is into the hierarchical structure defined by the
      document type definition; it document. The syntax is:

     <LISTING> ... </LISTING>

     or

     <XMP> ... </XMP>

     The text between these tags is identified typically rendered in a document
      instance
     monospaced font so that any formatting done by descriptive markup, usually a start-tag and
      an end-tag.

   HTML

      HyperText Markup Language.

   HTML user agent

      Any tool used with HTML documents.

   HTML document

      A collection of information represented as a sequence of
      characters. An HTML document consists of data characters
      and markup. In particular, the markup describes a
      structure conforming to character
     spacing on successive lines will be maintained.

     Between the HTML document type
      definition.

   HTTP

      A generic stateless object-oriented protocol, which opening and closing tags:

          * The text may
      be used contain any ISO Latin-1 printable
          characters, except for many similar tasks by extending the
      commands, or "methods", used. For example, you might use
      HTTP for name servers end-tag opener. The Example
          and distributed object-oriented
      systems, With HTTP, the negotiation of data
      representation allows systems Listing elements have historically used
          specifications which do not conform to be built independent of SGML.
          Specifically, the development of new representations. For more
      information see:
      http://info.cern.ch/hypertext/WWW/Protocols/HTTP/HTTP2.html

   (document) instance

      The document itself text may contain ISO Latin printable
          characters, including the actual content with
      the actual markup. Can be a single document or part of a
      document instance set that follows tag opener, as long it they
          does not contain the DTD.

   markup

      Text added to closing tag in full.
          * SGML does not support this form. HTML interpreters
          may vary on how they interpret other tags within
          Example and Listing elements.
          * Line boundaries within the data of a document to convey
      information about it. There text are four different kinds of
      markup: descriptive markup (tags), references, markup
      declarations, and processing instructions.

   Multipurpose Internet Mail Extensions (MIME)

      An extension rendered as a
          move to Internet email which provides the

Berners-Lee, Connolly, et. al.                                  Page 75

                                HTML 2.0                February 8, 1995


      ability to transfer non-textual data, such as graphics,
      audio and fax. It is defined in RFC 1341.

   representation

      The encoding beginning of information the next line, except for interchange. For
      example, HTML is a representation of hypertext.

   rendering

      Formatting and presenting information.

   SGML

      Standard Generalized Markup Language is one
          immediately following a data encoding
      that allows the information in documents to be shared -
      either by other document publishing systems start-tag or by
      applications for electronic delivery, configuration
      management, database management, inventory control, etc.
      Defined in ISO 8879:1986 Information Processing Text and
      Office Systems; Standard Generalized Markup Language
      (SGML).

   SGMLS

      An SGML parser by James Clark, jjc@jclark.com, derived
      from the ARCSGML parser materials which were written by
      Charles F. Goldfarb. immediately
          preceding an end-tag.
          * The source is available at
      ftp.ifi.uio.no/pub/SGML/SGMLS.

   tag

      Descriptive markup. There are two kinds horizontal tab character must be interpreted as
          the smallest positive nonzero number of tags; start-
      tags and end-tags.

   URI

      Universal Resource Identifiers (URIs) is spaces which
          will leave the name for a
      generic WWW identifier. The URI specification simply
      defines number of characters so far on the syntax for encoding arbitrary naming or
      addressing schemes, and has line
          as a list multiple of such schemes. See
      also: http://info.cern.ch/hypertext/WWW/Addressing/Addressing.html

   WWW

      A hypertext-based, distributed information system
      created by researchers at CERN in Switzerland. Users may
      create, edit or browse hypertext documents. The clients
      and servers are freely available.See also:
      http://info.cern.ch/hypertext/WWW/TheProject.html

Berners-Lee, Connolly, et. al.                                  Page 76

                                HTML 2.0                February 8, 1995



   7.1 Imperatives

      may

         The implementation 8. Its use is not obliged to follow this in any
         way.

      must

         If this recommended.

     The Listing element is not followed, the implementation does not
         conform to this specification.

      shall

         If this rendered so that at least 132
     characters fit on a line. The Example element is not followed, the implementation does not
         conform rendered to this specification.

      should

         If this
     that at least 80 characters fit on a line but is not followed, though the implementation
         officially conforms otherwise
     identical to the specification, undesirable
         results Listing element.


14.3. Proposed Features 

     This section describes proposed HTML elements and entities
     that are not currently supported under HTML Levels 0, 1, or
     2@@, but may occur be supported in practice. the future.


14.3.1. Additional Character Entities 

     To indicate special characters, HTML uses entity or numeric
     representations. Additional character presentations are
     proposed:

     CHARACTER                       REPRESENTATION
     Non-breaking space              &nbsp;
     Soft-hyphen                     &shy;
     Registered                      &reg;
     Copyright                       &copy;


14.3.2. Defining Instance Element 

     <DFN> ... </DFN>

     The Defining Instance element indicates the defining
     instance of a term. The typical

         Typical rendering is described for many elements. bold or bold
     italic. This element is not widely supported.


14.3.3. Strike Element 

     <STRIKE> ... </STRIKE>

     The Strike element is proposed to indicate strikethrough, a
     font style in which a horizontal line appears through
     characters. This element is not a mandatory part of the specification but widely supported.


14.3.4. Underline Element 

     <U> ... </U>

     The Underline element is
         given as guidance for designers and proposed to help explain the
         uses for which indicate that the elements were intended.

8. References

   The HTML specification cites these works:

   HTTP

      HTTP: A Protocol for Networked Information. text
     should be rendered as underlined. This
      document proposed tag is available at
      http://info.cern.ch/hypertext/WWW/Protocols/HTTP/HTTP2.h
      tml.

   MIME

      N. Borenstein, N. Freed, MIME (Multipurpose Internet
      Mail Extensions) Part One: Mechanisms for Specifying and
      Describing the Format of Internet Message Bodies,
      09/23/1993. (Pages=81) (Format=.txt, .ps) (Obsoletes
      RFC1341) (Updated not
     supported by RFC1590).


Berners-Lee, Connolly, et. al.                                  Page 77 all HTML 2.0                February 8, 1995


   SGML

      ISO Standard 8879:1986 Information Processing Text and
      Office Systems; Standard Generalized Markup Language
      (SGML).

   SGMLS

      An SGML parser by James Clark, jjc@jclark.com, derived
      from the ARCSGML parser materials which were written by
      Charles F. Goldfarb. interpreters.

     Example of use:

     The source text <U>shown here</U> is available at
      ftp.ifi.uio.no/pub/SGML/SGMLS.

   URI

      Universal Resource Identifiers. Available by anonymous
      FTP rendered in the
     document as Postscript (info.cern.ch/pub/www/doc/url.ps) or
      text (info.cern.ch/pub/www/doc/url.txt)

   WWW

      The World Wide Web , a global information initiative.
      For bootstrap information, telnet info.cern.ch or find
      documents by ftp://info.cern.ch/pub/www/doc.

9. underlined.


15. Acknowledgments 

     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 people who have contributed to
     this specification:

   -

     Terry Allen; O'Reilly & Associates; terry@ora.com

   - Allen Marc Andreessen; Netscape Communications Corp;
      marca@mcom.com


Berners-Lee, Connolly, et. al.                                  Page 78

                                HTML 2.0                February 8, 1995


   - Andreessen

     Tim Berners-Lee Paul Burchard; The Geometry Center, University of
      Minnesota; burchard@geom.umn.edu

   - Burchard

     James Clark; jjc@jclark.com

   - Clark Daniel W. Connolly; HaL Computer Systems; connolly@hal.com

   - Connolly

     Roy Fielding; University of California, Irvine;
      fielding@ics.uci.edu

   - T. Fielding Peter Flynn; University College Cork, Ireland; pflynn@www.ucc.ie

   - Flynn

     Jay Glicksman; Enterprise Integration Technology; jay@eit.com

   - Glicksman Paul Grosso; ArborText, Inc.; paul@arbortext.com

   - Grosso

     Eduardo Gutentag; Sun Microsystems; eduardo@Eng.Sun.com

   - Gutentag Bill Hefley; Software Engineering Institute,
      Carnegie Mellon University; weh@sei.cmu.edu

   - Hefley

     Chung-Jen Ho; Xerox Corporation; cho@xsoft.xerox.com

   - Ho Mike Knezovich; Spyglass, Inc.; mike@spyglass.com

   -  Tim Berners-Lee; CERN; timbl@info.cern.ch

   - Knezovich

     Tom Magliery; NCSA; mag@ncsa.uiuc.edu

   - Magliery Murray Maloney; Toronto Development Centre, The
      Santa Cruz Operation (SCO); murray@sco.com

   - Maloney

     Larry Masinter; Xerox Palo Alto Research Center;
      masinter@parc.xerox.com

   - Masinter Karen Olson Muldrow; HaL Computer Systems; karen@hal.com

   - Muldrow

     Bill Perry, Spry, Inc., wmperry@spry.com

   - Perry Dave Raggett, Hewlett Packard, dsr@hplb.hpl.hp.com

   - Raggett

     E. Corprew Reed; Cold Spring Harbor Laboratory; corp@cshl.org

   - Reed Yuri Rubinsky; SoftQuad, Inc.; yuri@sq.com

   - Rubinsky

     Eric Schieler; Spyglass, Inc.; eschieler@spyglass.com

   - Schieler James L. Seidman; Spyglass, Inc.; jim@spyglass.com

   - Seidman

     Eric W. Sink; Spyglass, Inc.; eric@spyglass.com

Berners-Lee, Connolly, et. al.                                  Page 79

                                HTML 2.0                February 8, 1995



   - Sink Stuart Weibel; OCLC Office of Research; weibel@oclc.org

   - Weibel

     Chris Wilson; Spry, Inc.; cwilson@spry.com

10. Author's Wilson Francois Yergeau


15.1. Authors' Addresses 

     Tim Berners-Lee
   timbl@quag.lcs.mit.edu

     Director, W3 Consortium
     MIT Laboratory for Computer Science
     545 Technology Square
     Cambridge, MA 02139, U.S.A.
     Tel: +1 (617) 253 9670
     Fax: +1 (617) 258 8682
     Email: timbl@w3.org

     Daniel W.
     Connolly
   Hal Software Systems
   3006A Longhorn Blvd.
   Austin, TX 78758

   phone: (512) 834-9962 extension 5010
   fax:   (512) 823-9963
   URL:   http://www.hal.com/~connolly
   email: connolly@hal.com

































Berners-Lee, Connolly, et. al.                                  Page 80

     Research Technical Staff, W3 Consortium
     MIT Laboratory for Computer Science
     545 Technology Square
     Cambridge, MA 02139, U.S.A.
     Fax: +1 (617) 258 8682
     Email: connolly@w3.org
     URI: http://www.w3.org/hypertext/WWW/People/Connolly/


----