view Side-By-Side changes

HTML Working Group                                        T. Berners-Lee
INTERNET-DRAFT                                                   MIT/W3C
<draft-ietf-html-spec-03.txt>
<draft-ietf-html-spec-04.txt>                                D. Connolly
Expires: In six months                                       May 31,                                     June 16, 1995


                    Hypertext Markup Language - 2.0


                               CONTENTS


     1.  Introduction
     2.  HTML as an Application of SGML
     3.  HTML as an Internet Media Type
     4.  Document Structure
     5.  Character, Words, and Paragraphs
     6.  Hyperlinks
     7.  Forms
     8.  HTML Public Text
     9.  Glossary
     10.  Bibliography
     11.  Appendices
     12.  Acknowledgments


Status of this Memo

This document is an 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 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 as reference material
or to cite them other than as ``work in progress.''

To learn the current status of any Internet-Draft, please check the
1id-abstracts.txt listing contained in the 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>. Discussions of the group are archived at
<URL:http://www.acl.lanl.gov/HTML_WG/archives.html>.

In this draft, the first three sections are considered essentially
finished. Sections 4 and 5 have been significantly revised and are
open to comments, though I'm fairly happy with those parts. Section 6
is somewhat new: it collects all information about hyperlinking into
one place. Sections 7 (forms elements) has also been revised, and
there are a few points I'm not sure on. The glossary (section 8) has
also been tweaked. Section 8 ``public text'' has been stable for some
time, but as it's critical, I'd appreciate a careful review just the
same.


                            ABSTRACT

    The Hypertext Markup Language (HTML) is a simple markup language
    used to create hypertext documents that are platform
    independent. HTML documents are SGML documents with generic
    semantics that are appropriate for representing information from
    a wide range of domains. HTML markup can represent hypertext
    news, mail, documentation, and hypermedia; menus of options;
    database query results; simple structured documents with
    in-lined graphics; and hypertext views of existing bodies of
    information.

    HTML has been in use by the World Wide Web (WWW) global
    information initiative since 1990. This specification roughly
    corresponds to the capabilities of HTML in common use prior to
    June 1994. HTML is an application of ISO Standard 8879:1986
    Information Processing Text and Office Systems; Standard
    Generalized Markup Language (SGML).

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


1. Introduction 

     The HyperText



Berners-Lee, Connolly                                           [Page 1]

INTERNET-DRAFT      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. - 2.0        June 16, 1995

                                CONTENTS


    1      Introduction .......................................... 3
    1.1    Scope ................................................. 3
    1.2    Conformance ........................................... 3
    2      Terms ................................................. 5
    3      HTML has been in use by the World-Wide Web (WWW) global
     information initiative since 1990. This specification
     corresponds to the capabilities of HTML in common use prior
     to June 1994 and referred to as ``HTML 2.0''.

     HTML is an application Application of ISO Standard 8879:1986
     _Information Processing SGML ........................ 9
    3.1    SGML Documents ........................................ 9
    3.2    HTML Lexical Syntax .................................. 11
    3.3    HTML Public Text and Office Systems; Standard
     Generalized Markup Language_ (SGML). The Identifiers ......................... 15
    3.4    Example HTML Document Type
     Definition (DTD) is a formal definition of the HTML syntax
     in terms of SGML.

     This specification also defines ................................ 16
    4      HTML as an Internet Media
     Type[IMEDIA] and MIME Content Type[MIME] called `text/html',
     or `text/html; version=2.0'. As such, it defines the
     semantics of the Type ....................... 16
    4.1    text/html media type ................................. 16
    4.2    HTML syntax and how that syntax should be
     interpreted by user agents.


1.2. Conformance 

     This specification governs the syntax of Document Representation ......................... 17
    5      Document Structure ................................... 18
    5.1    Document Element: HTML documents ............................... 19
    5.2    Head: HEAD ........................................... 19
    5.3    Body: BODY ........................................... 22
    5.4    Headings: H1 ... H6 .................................. 22
    5.5    Block Structuring Elements ........................... 23
    5.6    List Elements ........................................ 25
    5.7    Phrase Markup ........................................ 28
    5.8    Line Break: BR ....................................... 31
    5.9    Horizontal Rule: HR .................................. 31
    5.10   Image: IMG ........................................... 31
    6      Characters, Words, and
     the behaviour Paragraphs .................... 33
    6.1    The HTML Document Character Set ...................... 33
    7      Hyperlinks ........................................... 34
    7.1    Accessing Resources .................................. 34
    7.2    Activation of Hyperlinks ............................. 34
    7.3    Simultaneous Presentation of Image Resources ......... 35
    7.4    Fragment Identifiers ................................. 35
    7.5    Queries and Indexes .................................. 35
    7.6    Image Maps ........................................... 36
    8      Forms ................................................ 36
    8.1    Form Elements ........................................ 37
    8.2    Form Submission ...................................... 42
    9      HTML user agents.


1.2.1. Documents 

     A document is a conforming Public Text ..................................... 45
    9.1    HTML document only if:

          * It is a conforming SGML document, and it conforms to
          the DTD ............................................. 45
    9.2    Strict HTML DTD (see 8.1, "HTML DTD").

          NOTE ...................................... 56
    9.3    Level 1 HTML DTD ..................................... 57
    9.4    Strict Level 1 HTML DTD .............................. 58
    9.5    SGML Declaration for HTML ............................ 58
    9.6    Sample SGML Open Entity Catalog for HTML ............. 60
    9.7    Character Entity Sets ................................ 61
    10     Security Considerations .............................. 63
    11     References ........................................... 64
    12     Acknowledgments ...................................... 65
    12.1   Authors' Addresses ................................... 66
    13     The HTML Coded Character Set ......................... 66
    14     Proposed Entities .................................... 69



Berners-Lee, Connolly                                           [Page 2]

INTERNET-DRAFT      Hypertext Markup Language - There are 2.0        June 16, 1995

1. Introduction

    The HyperText Markup Language (HTML) is a number of syntactic idioms simple data format
    used to create hypertext documents 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. portable from one
    platform to another. HTML documents should not contain these idioms, at
          least until such time as support are SGML documents with
    generic semantics that are appropriate for them representing
    information from a wide range of domains.

    As HTML is widely
          deployed. an application of SGML, this specification assumes a
    working knowledge of [SGML].


1.1. Scope

    HTML has been in use by the World-Wide Web (WWW) global
    information initiative since 1990. This specification
    corresponds to the capabilities of HTML in common use prior to
    June 1994 and referred to as ``HTML 2.0''.

    HTML is an application of ISO Standard 8879:1986 _Information
    Processing Text and Office Systems; Standard Generalized Markup
    Language_ (SGML). The HTML Document Type Definition (DTD) is a
    formal definition of the HTML syntax in terms of SGML.

    This specification also defines HTML as an Internet Media
    Type[IMEDIA] and MIME Content Type[MIME] called `text/html'. As
    such, it defines the semantics of the HTML syntax and how that
    syntax should be interpreted by user agents.


1.2. Conformance

    This specification governs the syntax of HTML documents and
    aspects of the behavior of HTML user agents.


1.2.1. Documents

    A document is a conforming HTML document if:

        * It is a conforming SGML document, and it conforms to the
        HTML DTD (see 9.1, "HTML DTD").

            NOTE - There are a number of syntactic idioms that
            are not supported or are supported inconsistently in
            some historical user agent implementations. These
            idioms are identified in notes like this throughout
            this specification.

        * It conforms to the application conventions in this
        specification. For example, the value of the HREF attribute
        of the <A> element must conform to the URI syntax.

        * Its document character set includes ANSI/ISO 8859-1 [ISO-8859-1] and

Berners-Lee, Connolly                                           [Page 3]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

        agrees with ISO/IEC 10646-1; [ISO-10646]; that is, each code position listed
        in 11.1, 13, "The ANSI/ISO 8859-1 HTML Coded Character Set" is included, and each
        code position in the document character set is mapped to the
        same character as ISO10646 [ISO-10646] designates for that code
        position.

            NOTE - The document character set is somewhat
            independent of the character encoding scheme used to
            represent a document. For example, the ISO-2022-JP `ISO-2022-JP'
            character encoding scheme can be used for HTML
            documents, since its repertoire is a subset of the
          ISO10646
            [ISO-10646] repertoire. The critical distinction is
            that numeric character references agree with ISO10646
            [ISO-10646] regardless of how the document is
            encoded.


1.2.2. Feature Test Entities

    The HTML DTD defines a standard HTML document type and several
    variations, based on by way of feature test entities:

     
     HTML.Recommended
                    Certain features of the language are necessary for entities. Feature test
    entities are declarations in the HTML DTD that control the
    inclusion or exclusion of portions of the DTD.

    HTML.Recommended
            Certain features of the language are necessary for
            compatibility with widespread usage, but they may
            compromise the structural integrity of a document. This
            feature test entity enables selects a more prescriptive document
            type definition that eliminates those features. It is
            set to `IGNORE' by default.

            For example, in order to preserve the structure of a
            document, an editing user agent may translate HTML
            documents to the recommended subset, or it may require
            that the documents be in the recommended subset for
            import.

    HTML.Deprecated
            Certain features of the language are necessary for
            compatibility with earlier versions of the
            specification, but they tend to be used and implemented
            inconsistently, and their use is deprecated. This
            feature test entity enables a document type definition
            that eliminates allows these features. It is set to `INCLUDE' by
            default.

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


1.2.2.


1.2.3. User Agents

    An HTML user agent conforms to this specification if:

Berners-Lee, Connolly                                           [Page 4]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995


        * It parses the characters of an HTML document into data
        characters and markup according to [SGML].

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

        * It supports the `ISO-8859-1' character encoding scheme and
        processes each character in the ISO Latin Alphabet No. 1 as
        specified in 5.1, 6.1, "The ISO Latin 1 HTML Document Character Repertoire". Set".

            NOTE - To support non-western writing systems, HTML
            user agents should are encouraged to support ISO-10646-UCS-2
            `ISO-10646-UCS-2' or similar character encoding
            schemes and as much of the character repertoire of ISO10646
            [ISO-10646] as is practical.

        * It behaves identically for documents whose parsed token
        sequences are identical.

        For example, comments and the whitespace in tags disappear
        during tokenization, and hence they do not influence the behaviour
        behavior of conforming user agents.

        * It allows the user to traverse (or at least attempt to
        traverse, resources permitting) all hyperlinks from <A>
        elements in an HTML document.

    An HTML user agent is a level 2 user agent if, additionally:

        * It allows the user to express all form field values
        specified in an HTML document and to (attempt to) submit the
        values as requests to information services.


2. HTML Terms

    absolute URI
            a URI in absolute form, as per [URL]

    anchor
            one of two ends of a hyperlink; typically, a phrase
            marked as an Application <A> element.

    base URI
            URI used as the base of SGML 

     HTML is an application HTML document for the purpose
            of ISO 8879:1986 -- Standard
     Generalized resolving hyperlink destinations.

    character
            An atom of information, for example a letter or a digit.
            Graphic characters have associated glyphs, where as

Berners-Lee, Connolly                                           [Page 5]

INTERNET-DRAFT      Hypertext Markup Language (SGML). SGML - 2.0        June 16, 1995

            control characters have associated processing semantics.

    character encoding
    scheme
            A function whose domain is a system for
     defining structured document types and markup languages to
     represent instances the set of those document types[SGML]. The
     public text -- DTD and SGML declaration -- sequences of the HTML
     document type definition are provided in 8, "HTML Public
     Text".

     The term _HTML_ refers to both the document type defined
     here
            octets, and whose range is the markup language for representing instances set of
     this document type.


2.1. SGML Documents 

     An HTML document is an SGML document; sequences of
            characters from a character repertoire; that is, a
            sequence of
     characters organized physically into octets and a set of entities, and
     logically as character encoding scheme
            determines a hierarchy sequence of elements.

     The first production characters.

    character repertoire
            A finite set of characters; e.g. the SGML grammar separates an SGML
     document into three parts: an SGML declaration, range of a prologue, coded
            character set.

    code position
            An integer. A coded character set and an instance. For the purposes of this specification, the
     prologue a code position
            from its domain determine a character.

    coded character set
            A function whose domain is a DTD. This DTD describes another grammar: subset of the
     start symbol integers and
            whose range is given in the doctype declaration, a character repertoire. That is, for some
            set of integers (usually of the
     terminals are data characters form {0, 1, 2, ..., N}
            ), a coded character set and tags, an integer in that set
            determine a character. Conversely, a character and a
            coded character set determine the productions
     are determined by the element declarations. The instance
     must conform to the DTD, that is, it must be character's code
            position (or, in the language
     defined by rare cases, a few code positions).

    conforming HTML user
    agent
            A user agent that conforms to this grammar.

     The SGML declaration determines the lexicon specification in its
            processing of the grammar.
     It specifies Internet Media Type `text/html'.

    data character
            Characters other than markup, which make up the content
            of elements.

    document character set, which determines set
            a coded character repertoire that contains set whose range includes all
            characters that occur
     in all text entities used in the document, and the code positions
     associated with those characters.

     The a document. Every SGML declaration also specifies the syntax-reference document has
            exactly one document character set of set. Numeric character
            references are resolved via the document, and a few other parameters document character set.

    DTD
            document type definition. Rules that bind the abstract syntax of apply SGML to a concrete syntax.
     This concrete syntax determines how the sequence
            markup of
     characters 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 mapped to a sequence of
     terminals identified in a document
            instance by descriptive markup, usually a start-tag and
            end-tag. [SGML]

    end-tag

Berners-Lee, Connolly                                           [Page 6]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

            Descriptive markup that identifies the grammar end of the prologue.

     For an
            element. [SGML]

    entity
            data with an associated notation or interpretation; for
            example, consider a sequence of octets associated with an
            Internet Media Type. [SGML]

    fragment identifier
            the portion of an HREF attribute value 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 SGML declaration that is
     given in 8.2, "SGML Declaration for HTML". According to its
     document `#'
            character set, `&#42;' refers to an asterisk
     character.

     The instance above is regarded as which modifies the following sequence presentation of
     terminals:

          1. TITLE start-tag

          2. data characters: ``Parsing Example''

          3. TITLE end-tag

          4. P start-tag

          5. the
            destination of a hyperlink.

    form data characters ``Some text. ''

          6. EM start-tag

          7. ``*wow*''

          8. EM end-tag

          9. P end-tag

     The start symbol set
            a sequence of name/value pairs; the DTD grammar is HTML, names are given by
            an HTML document and the
     productions values are given in the public text identified by
     `-//IETF//DTD a user.

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

        HTML
         |
         \-HEAD
         |  |
         |  \-TITLE
         |      |
         |      \-<TITLE>
         |      |
         |      \-"Parsing Example"
         |      |
         |      \-</TITLE>
         |
         \-BODY
           |
           \-P
             |
             \-<P>
             |
             \-"Some text. "
             |
             \-EM
             |  |
             |  \-<EM>
             |  |
             |  \-"*wow*"
             |  |
             |  \-</EM>
             |
             \-</P>


2.2. HTML Lexical Syntax document
            An SGML specifies an abstract syntax and document conforming to this document type
            definition.

    hyperlink
            a reference concrete
     syntax. Aside from certain quantities and capacities (e.g.
     the limit on relationship between two anchors, called the length of a name), all HTML documents use tail and
            the reference concrete syntax. In particular, all head.

    markup
            Syntactically delimited characters are in added to the repertoire data of ISO 646 IRV. Data
     characters are drawn from the
            a document character set (see 5,
     "Character, Words, to represent its structure. There are four
            different kinds of markup: descriptive markup (tags),
            references, markup declarations, and Paragraphs"). processing
            instructions. [SGML]

    may
            A complete discussion of SGML parsing, e.g. the mapping of document or user interface is conforming whether this
            statement applies or not.

    media type
            an Internet Media Type, as per [IMEDIA].

    message entity
            a
     sequence of characters to head and body. The head is a sequence collection of tags name/value
            fields, and data, is
     left to the SGML standard[SGML]. This section body 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 octets. The head
            defines the document
     character set. Each reference to one content type and content transfer encoding
            of the general entities
     defined in the body. [MIME]

    minimally conforming
    HTML DTD also maps to a single-character
     string.

     For example,

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

     Note user agent
            A user agent that the terminating semicolon is conforms to this specification except
            for form processing. It may only necessary when
     the process level 1 HTML
            documents.

    must
            Documents or user agents in conflict with this statement
            are not conforming.

Berners-Lee, Connolly                                           [Page 7]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995


    numeric character following the
    reference would otherwise be
     recognized as markup:

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

     And note that an ampersand is only recognized as
            markup when
     it is followed by a letter or digit:

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

     A useful technique for translating plain text to HTML is that refers to
     replace each '<', '&', and '>' a character by an entity reference or
     numeric its code position
            in the document character reference as follows:

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

          NOTE - There are set.

    SGML mechanisms, CDATA and RCDATA, to
          allow most `<', `>', document
            A sequence of characters organized physically as a set
            of entities and `&' logically into a hierarchy of elements.
            An SGML document consists of data characters to be entered
          without and markup;
            the use markup describes the structure of entity references. Because these
          features tend to be used and implemented
          inconsistently, the information
            and because they conflict with
          techniques for reducing HTML to 7 bit ASCII for
          transport, they are not used in this version an instance of the
          HTML DTD.


2.2.2. Tags 

     Tags delimit elements such as headings, paragraphs, lists,
     character highlighting, and links. Most HTML elements are
     identified in that structure. [SGML]

    shall
            If a document as or user agent conflicts with this
            statement, it does not conform to this specification.

    should
            If a start-tag, which gives document or user agent conflicts with this
            statement, undesirable results may occur in practice
            even though it conforms to this specification.

    start-tag
            Descriptive markup that identifies the start of an
            element name and attributes, followed by the content,
     followed by the end tag. Start-tags are delimited by `<' specifies its generic identifier and
     `>'; end tags are delimited by `</'
            attributes. [SGML]

    syntax-reference
    character set
            A coded character set whose range includes all
            characters used for markup; e.g. name characters and `>'. An example is:

     <H1>This is a Heading</H1>

     Some elements only have a start-tag without
            delimiter characters.

    tag
            Markup that delimits an end-tag. For
     example, to create element. A tag includes a line break, you use the `<BR>' tag.
     Additionally, name
            which refers to an element declaration in the end tags of some other elements, such as
     Paragraph (`</P>'), List Item (`</LI>'), Definition Term
     (`</DT>'), DTD, and Definition Description (`<DD>') elements,
            may
     be omitted.

     The content include attributes. [SGML]

    text entity
            A finite sequence of characters. A text entity typically
            takes the form of an element is a sequence of data character
     strings and nested elements. Some elements, such as anchors,
     cannot be nested. Anchors and octets with some
            associated character highlighting may be
     put inside other constructs. See encoding scheme, transmitted over
            the HTML DTD, 8.1, "HTML
     DTD" for full details.

          NOTE - The SGML declaration for HTML specifies SHORTTAG
          YES, which means that there are other valid syntaxes
          for tags, such as NET tags, `<EM/.../'; empty start
          tags, `<>'; and empty end-tags, `</>'. Until support
          for these idioms network or stored in a file. [SGML]

    typical
            Typical processing is widely deployed, their use described for many elements. This
            is
          strongly discouraged.


2.2.3. Names 

     A name consists of a letter followed by up to 71 letters,
     digits, periods, or hyphens. Element names are not case
     sensitive, a mandatory part of the specification but entity names are. For example,
     `<BLOCKQUOTE>', `<BlockQuote>', and `<blockquote>' are
     equivalent, whereas `&amp;' is different from `&AMP;'.

     In a start-tag,
            given as guidance for designers and to help explain the element name must immediately follow
            uses for which the
     tag open delimiter `<'.


2.2.4. Attributes 

     In elements were intended.

    URI
            A Universal Resource Identifier is a start-tag, white space and attributes formatted string
            that serves as an identifier for a resource, typically
            on the Internet. URIs are allowed
     between used in HTML to identify the element name

Berners-Lee, Connolly                                           [Page 8]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

            destination of hyperlinks. URIs in common practice
            include Uniform Resource Locators (URLs)[URL] and the closing delimiter. An
     attribute typically consists
            Relative URLs [RELURL].

    user agent
            A component of a distributed system that presents an attribute name, an equal
     sign,
            interface and processes requests on behalf of a value, though some attributes may be just user;
            for example, a
     value. White space www browser or a mail user agent.

    WWW
            The World-Wide Web is allowed around the equal sign.

     The value of the attribute may be either:

          * A string literal, delimited a hypertext-based, distributed
            information system created by single quotes or
          double quotes researchers at CERN in
            Switzerland. <URL:http://www.w3.org/>


3. HTML as an Application of SGML

    HTML is an application of ISO 8879:1986 -- Standard Generalized
    Markup Language (SGML). SGML is a system for defining structured
    document types and not containing any occurrences markup languages to represent instances of the
          delimiting character.

          NOTE - Some historical implementations consider any
          occurrence
    those document types[SGML]. The public text -- DTD and SGML
    declaration -- of the `>' character HTML document type definition are provided
    in 9, "HTML Public Text".

    The term _HTML_ refers to signal both the end document type defined here
    and the markup language for representing instances of a
          tag. For compatibility with such implementations, when
          `>' appears in this
    document type.


3.1. SGML Documents

    An HTML document is an attribute value, it should be
          represented with SGML document; that is, a numeric character reference. For
          example, `<IMG SRC="eq1.jpg" alt="a>b">' should be
          written `<IMG SRC="eq1.jpg" alt="a&#62;b">' or `<IMG
          SRC="eq1.jpg" alt="a&gt;b">'.

          * A name token (a sequence of letters, digits, periods,
          or hyphens).

          NOTE - Some historical implementations allow any
          character except space or `>' in
    characters organized physically into a name token. set of entities, and
    logically as a hierarchy of elements.

    In this example, <img> is the element name, src is SGML specification, the
     attribute name, and `http://host/dir/file.gif' is first production of the
     attribute value:

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

     A useful technique for computing SGML
    syntax grammar separates an attribute value literal
     for a given string is to replace each quote SGML document into three parts: an
    SGML declaration, a prologue, and 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 instance. For example:

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

     Note that the SGML declaration in section 13.3 limits the
     length purposes
    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 this specification, the prologue is a minimized syntax:

     <UL COMPACT>

          NOTE - Some historical implementations only understand DTD. This DTD describes
    another grammar: the minimized syntax.


2.2.5. Comments 

     To include comments start symbol is given in an HTML document, use a comment
     declaration. A comment declaration consists of `<!' followed
     by zero or more comments followed by `>'. Each comment
     starts with `--' the doctype
    declaration, the terminals are data characters and includes all text up to tags, and including the next occurrence of `--'. In a comment declaration, white
     space is allowed after each comment, but not before
    productions are determined by the
     first comment. element declarations. The entire comment declaration is ignored.

          NOTE - Some historical HTML implementations incorrectly
          consider any `>' character
    instance must conform to the DTD, that is, it must be in the termination
    language defined by this grammar.

    The SGML declaration determines the lexicon of the grammar. It
    specifies the document character set, which determines a
          comment.

     For example:

     <HEAD>
     <TITLE>HTML Comment Example</TITLE>
     <!-- Id: html-sgml.sgm,v 1.5 1995/05/26 21:29:50 connolly Exp  -->
     <!-- another -- -- comment -->
     <!>
     </HEAD>
     <BODY>
     <p> <!- not a comment, just regular old data
    character repertoire that contains all characters ->


2.2.6. Example HTML Document 

     <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
     <HTML>
     <!-- Here's a good place to put a comment. -->
     <HEAD>
     <TITLE>Structural Example</TITLE>
     </HEAD><BODY>
     <H1>First Header</H1>
     <P>This is a paragraph that occur in the example HTML file. Keep
    all text entities in mind
     that the title does not appear in document, and the document text, but that code positions
    associated with those characters.

    The SGML declaration also specifies the header (defined by H1) does.</P>
     <OL>
     <LI>First item in an ordered list.
     <LI>Second item in an ordered list.
       <UL COMPACT>
       <LI> Note syntax-reference
    character set of the document, and a few other parameters that lists can be nested;
       <LI> Whitespace may be used
    bind the abstract syntax of SGML to assist in reading a concrete syntax. This

Berners-Lee, Connolly                                           [Page 9]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    concrete syntax determines how the
            HTML source.
       </UL>
     <LI>Third item in an ordered list.
     </OL>
     <P>This sequence of characters of the
    document is an additional paragraph. Technically, end tags are
     not required for paragraphs, although they are allowed. You can
     include character highlighting in mapped to a paragraph. <EM>This sentence sequence of terminals in the paragraph is emphasized.</EM> Note that grammar of
    the &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. prologue.

    For example, consider the following document:

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

    An HTML user agent allows users to interact with resources
     which have HTML representations. At a minimum, it must allow
     users to examine and navigate the content of HTML level 1
     documents. HTML user agents should be able to preserve all
     formatting distinctions represented use the SGML declaration that is given
    in an HTML document, and
     be able to simultaneously present resources referred 9.5, "SGML Declaration for HTML". According to by
     IMG elements (they may ignore some formatting distinctions
     or IMG resources at the request of the user). Conforming
     HTML user agents should support form entry and submission.


3.1. text/html media type 

     This specification defines the Internet Media Type[IMEDIA]
     (formerly referred its document
    character set, `&#42;' refers to as the Content Type[MIME]) called
     `text/html'. an asterisk character, `*'.

    The following is to be registered with [IANA].

     Media Type name
                    text

     Media subtype
     name
                    html

     Required
     parameters
                    none

     Optional
     parameters
                    level, charset

     Encoding
     considerations
                    any encoding instance above is allowed

     Security
     considerations
                    see 3.3, "Security Considerations"

     The optional parameters are defined regarded as follows:

     Level
                    The level parameter specifies the feature set used
                    in the document. following sequence of
    terminals:

        1. start-tag: TITLE

        2. data characters: ``Parsing Example''

        3. end-tag: TITLE

        4. start-tag: P

        5. data characters ``Some text. ''

        6. start-tag: EM

        7. data characters: ``*wow*''

        8. end-tag: EM

        9. end-tag: P

    The level is an integer number,
                    implying that any features start symbol of same or lower level
                    may be present in the document. Level 1 DTD grammar is all
                    features defined in this specification except
                    those that require HTML, and the <FORM> element. Level 2
                    includes form processing. Level 2 is productions
    are given in the default.

     Charset
                    The charset parameter (as defined in section 7.1.1 public text identified by `-//IETF//DTD HTML
    2.0//EN' (9.1, "HTML DTD"). The terminals above parse as:

       HTML
        |
        \-HEAD
        |  |
        |  \-TITLE
        |      |
        |      \-<TITLE>
        |      |
        |      \-"Parsing Example"
        |      |
        |      \-</TITLE>
        |
        \-BODY
          |
          \-P

Berners-Lee, Connolly                                          [Page 10]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

            |
            \-<P>
            |
            \-"Some text. "
            |
            \-EM
            |  |
            |  \-<EM>
            |  |
            |  \-"*wow*"
            |  |
            |  \-</EM>
            |
            \-</P>

    Some of RFC 1521[MIME]) may be given to specify the
                    character encoding scheme used to represent elements are delimited explicity by tags, while the
                    HTML document as a sequence
    boundaries of octets. others are inferred. The default
                    value <HTML> element contains a
    <HEAD> element and a <BODY> element. The <HEAD> contains
    <TITLE>, which is outside explicitly delimited by start- and end-tags.


3.2. HTML Lexical Syntax

    SGML specifies an abstract syntax and a reference concrete
    syntax. Aside from certain quantities and capacities (e.g. the scope
    limit on the length of this specification;
                    but for example, a name), all HTML documents use the default is `US-ASCII'
    reference concrete syntax. In particular, all markup characters
    are in the
                    context repertoire of MIME mail, and `ISO-8859-1' in [ISO-646]. Data characters are drawn
    from the
                    context of HTTP.


3.2. HTML Document Representation document character set (see 6, "Characters, Words, and
    Paragraphs").

    A message entity with a content type complete discussion of `text/html'
     represents an HTML document, consisting SGML parsing, e.g. the mapping of a single text
     entity. The `charset' parameter (whether implicit or
     explicit) identifies a character encoding scheme. The text
     entity consists
    sequence of the characters determined by this
     character encoding scheme and the octets to a sequence of tags and data, is left
    to the body of the
     message entity. SGML standard[SGML]. This section is only a summary.


3.2.1. Undeclared Markup Error Handling 

     To facilitate experimentation and interoperability between
     implementations of various versions Data Characters

    Any sequence of HTML, the installed
     base characters that do not constitute markup (see
    9.6 ``Delimiter Recognition'' of HTML user agents supports a superset [SGML]) are mapped directly to
    strings of data characters. Some markup also maps to data
    character strings. Numeric character references map to
    single-character strings, via the HTML 2.0
     language by reducing it document character set. Each
    reference to HTML 2.0: markup one of the general entities defined in the form of HTML DTD
    maps to a
     start-tag single-character string.

    For example,

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

    The terminating semicolon on entity or end-tag whose generic identifier is not
     declared numeric character
    references is mapped to nothing during tokenization.
     Undeclared attributes are treated similarly. The entire
     attribute specification of an unknown attribute (i.e., only necessary when the
     unknown attribute and its value, if any) should be ignored.
     On character following the other hand, references to undeclared entities should
    reference would otherwise be treated recognized as data characters.

     For example:

     <div class=chapter><h1>foo</h1><p>...</div>
       => <H1>,"foo",</H1>,<P>,"..."
     xxx <P ID=z23> yyy part of the name (see

Berners-Lee, Connolly                                          [Page 11]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    9.4.5 ``Reference End'' in [SGML]).

    abc &lt def     => "xxx ",<P>," yyy
     Let &alpha; and &beta; be finite sets. "abc ","<"," def"
    abc &#60 def    => "Let &alpha; and &beta; be finite sets."

     Support for notifying the user of such errors "abc ","<"," def"

    An ampersand is encouraged.

     Information providers are warned that this convention only recognized as markup when it is not
     binding: unspecified behavior may result, as such markup is
     not conforming to this specification.


3.2.2. Conventional Representation of Newlines 

     SGML specifies that a text entity is a sequence of records,
     each beginning with followed by
    a record start character and ending with letter or a record end character (code positions 10 `#' and 13
     respectively) (section 7.6.1, ``Record Boundaries'' in
     [SGML]).

     [MIME] specifies that a body of type `text/*' digit:

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

    A useful technique for translating plain text to HTML is a sequence
     of lines, to
    replace each terminated '<', '&', and '>' by CRLF, that is, octets 10, 13.

     In practice, HTML documents 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 - There are frequently represented SGML mechanisms, CDATA and
     transmitted using an end of line convention that depends on
     the conventions of the source of the document; frequently, RCDATA
        declared content, that representation consists of CR only, LF only, or a CR LF
     sequence. Hence allow most `<', `>', and `&'
        characters to be entered without the decoding use of the octets will often result
     in a text entity with some missing record start and record
     end characters.

     Since there is no ambiguity, HTML user agents are encouraged
        references. Because these mechanisms tend to infer the missing record start be used and end characters.

     An
        implemented inconsistently, and because they conflict
        with techniques for reducing HTML user agent should treat end of line to 7 bit ASCII for
        transport, they are deprecated in any this version of its
     variations HTML.
        See 5.5.2.1, "Example and Listing: XMP, LISTING".


3.2.2. Tags

    Tags delimit elements such as a word space in all contexts except
     preformatted text. Within preformatted text, an headings, paragraphs, lists,
    character highlighting, and links. Most HTML user
     agent should treat any of the three common representations
     of end-of-line elements are
    identified in a document as starting a new line.


3.3. Security Considerations 

     Anchors, embedded images, and all other elements start-tag, which
     contain URIs as parameters may cause gives the URI to be
     dereferenced in response to user input. In this case, element
    name and attributes, followed by the
     security considerations of content, followed by the URI specification apply.

     The widely deployed methods for submitting forms requests --
     HTTP
    end tag. Start-tags are delimited by `<' and SMTP -- provide little assurance of
     confidentiality. Information providers who request sensitive
     information via forms -- especially `>'; end tags are
    delimited by way of the `PASSWORD'
     type input field (see 7.1.2, "Input Field: INPUT") -- should
     be aware `</' and make their users aware of the lack of
     confidentiality.


4. Document Structure 

     To identify information as an HTML document conforming to
     this specification, each document should start with the
     following prologue:

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

          NOTE - If the body of `>'. An example is:

    <H1>This is a `text/html' message entity does
          not begin with Heading</H1>

    Some elements only have a document type declaration, start-tag without an HTML
          user agent should infer the above document type
          declaration.

     HTML user agents are required end-tag. For
    example, to support create a line break, you use the above document
     type declaration and `<BR>' tag.
    Additionally, the following document type
     declarations:

     <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Level 2//EN">
     <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Level 1//EN">
     <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Strict//EN">
     <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">

     They are not required to support other document types, but
     they may. In particular, they may support other formal
     public identifiers, or end tags of some other document types altogether. They
     may support an internal declaration subset with supplemental
     entity, element, elements, such as
    Paragraph (`</P>'), List Item (`</LI>'), Definition Term
    (`</DT>'), and other markup declarations, or they Definition Description (`<DD>') elements, may
     not.


4.1. Document Element: <HTML> be
    omitted.

    The HTML document element consists content of a head and a body,
     much like a memo or a mail message. The head contains the
     title and other optional elements. The body an element is a text flow
     consisting sequence of paragraphs, lists, data character
    strings and other nested elements.


4.2. Head: <HEAD> 

     The head of an HTML document is an unordered collection of
     information about the document. For example:

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


4.2.1. Title: <TITLE> 

     Every HTML document must contain a <TITLE> element.

     The title should identify the contents of the document in a
     global context. A short title, Some elements, such as ``Introduction'' anchors,
    cannot be nested. Anchors and character highlighting may be meaningless out of context. A title such as
     ``Introduction to put
    inside other constructs. See the HTML Elements'' is more appropriate. DTD, 9.1, "HTML DTD" for

Berners-Lee, Connolly                                          [Page 12]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    full details.

        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. SGML declaration for HTML specifies SHORTTAG
        YES, which means that there are other valid syntaxes for
        tags, such as NET tags, `<EM/.../'; empty start tags,
        `<>'; and empty end-tags, `</>'. Until support for these
        idioms is widely deployed, their use is strongly
        discouraged.


3.2.3. Names

    A user agent may display the title name consists of a document in a
     history list letter followed by letters, digits,
    periods, or as hyphens. The length of a label for name is limited to 72
    characters by the window displaying `NAMELEN' parameter in the
     document. Contrast with headings (4.4, "Headings: H1 ...
     H6"), which SGML delcaration
    for HTML, 9.5, "SGML Declaration for HTML". Element and
    attribute names are typically displayed with 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, the body text flow.


4.2.2. Base URI: <BASE> 

     The optional <BASE> element specifies name must immediately follow the URI of tag
    open delimiter `<'.


3.2.4. Attributes

    In a start-tag, white space and attributes are allowed between
    the
     document, overriding any context otherwise known to element name and the user
     agent. The required HREF closing delimiter. An attribute specifies the URI for
     navigating
    specification typically consists of an attribute name, an equal
    sign, and a value, though some attribute specifications may be
    just a name token. White space is allowed around the document (see 6, "Hyperlinks"). equal sign.

    The value of the HREF attribute must may be an absolute URI.


4.2.3. Keyword Index: <ISINDEX> 

     The <ISINDEX> element indicates that the user agent should
     allow the user to search an index either:

        * A string literal, delimited by giving keywords. See
     6.3, "Queries and Indexes" for details.


4.2.4. Link: <LINK> 

     The <LINK> element represents a hyperlink. It is typically
     used to indicate authorship, related indexes and glossaries,
     older single quotes or more recent versions, stylesheets, document
     hierarchy etc.


4.2.5. Associated Metainformation: <META> 

     The <META> element is an extensible container for use in
     identifying, indexing, double
        quotes and cataloging specialized document
     metainformation. Metainformation has two main functions:

          * to provide a means to discover that not containing any occurrences of the data set
          exists and how it might be obtained or accessed; and

          * delimiting
        character.

            NOTE - Some historical implementations consider any
            occurrence of the `>' character to document signal the content, quality, and features of a
          data set and so give an indication end of its fitness for
          use.

     Each <META> element specifies a name/value pair. If multiple
     META elements are provided with the same name, their
     combined contents--concatenated as
            a comma-separated
     list--is the value associated tag. For compatibility with that name.

          NOTE - The <META> element such implementations,
            when `>' appears in an attribute value, it should not be used where
            represented with a
          specific element such as <TITLE> would be appropriate.

     HTTP servers numeric character reference. For
            example, `<IMG SRC="eq1.jpg" alt="a>b">' should read the content be
            written `<IMG SRC="eq1.jpg" alt="a&#62;b">' or `<IMG
            SRC="eq1.jpg" alt="a&gt;b">'.

        * A name token (a sequence of the document <HEAD>
     to generate header fields corresponding to letters, digits, periods, or
        hyphens). Name tokens are not case sensitive.

            NOTE - Some historical implementations allow any elements
     defining
            character except space or `>' in a value for name token.

    In this example, <img> is the element name, src is the attribute HTTP-EQUIV.

          NOTE

Berners-Lee, Connolly                                          [Page 13]

INTERNET-DRAFT      Hypertext Markup Language - The method by which the server extracts document
          metainformation is unspecified 2.0        June 16, 1995

    name, and not mandatory. The
          META element only provides `http://host/dir/file.gif' is the attribute value:

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

    A useful technique for computing an extensible mechanism attribute value literal for
          identifying and embedding document metainformation -
          how it may be used
    a given string is up to the individual server
          implementation replace each quote and white space
    character by an entity reference or numeric character reference
    as follows:

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

    For example:

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

    The `NAMELEN' parameter in the HTML user agent.

     Attributes of SGML declaration (9.5, "SGML
    Declaration for HTML") limits the META element:

     HTTP-EQUIV
                    This length of an attribute binds the element value
    to an HTTP header
                    field. An HTTP server 1024 characters.

    Attributes such as ISMAP and COMPACT may use this information to
                    process the doducment. In particular, it should
                    include be written using a header field
    minimized syntax (see 7.9.1.2 ``Omitted Attribute Name'' in
    [SGML]). The markup:

    <UL COMPACT="compact">

    can be written using a minimized syntax:

    <UL COMPACT>

        NOTE - Some historical implementations only understand
        the responses minimized syntax.


3.2.5. Comments

    To include comments in an HTML document, use a comment
    declaration. A comment declaration consists of `<!' followed by
    zero or more comments followed by `>'. Each comment starts with
    `--' and includes all text up to GET
                    requests for this document: the header name is
                    taken from the HTTP-EQUIV attribute value, and including the
                    header value is taken from the value of the
                    CONTENT attribute. HTTP header names are not case
                    sensitive.

     NAME
                    name next
    occurrence of the name/value pair. If `--'. In a comment declaration, white space is
    allowed after each comment, but not present,
                    HTTP-EQUIV gives before the name.

     CONTENT first comment.
    The value of the name/value pair.

     Examples

     If entire comment declaration is ignored.

        NOTE - Some historical HTML implementations incorrectly
        consider any `>' character to be the termination of a
        comment.

Berners-Lee, Connolly                                          [Page 14]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995


    For example:

    <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    <HEAD>
    <TITLE>HTML Comment Example</TITLE>
    <!-- Id: html-sgml.sgm,v 1.5 1995/05/26 21:29:50 connolly Exp  -->
    <!-- another -- -- comment -->
    <!>
    </HEAD>
    <BODY>
    <p> <!- not a comment, just regular old data characters ->


3.3. HTML Public Text Identifiers

    To identify information as an HTML document conforming to this
    specification, each 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)">

     then the server should include the following header fields:

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

     as part start with one of the HTTP response
    following document type declarations.

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

    This document type declaration refers to a `GET' or `HEAD' request
     for that document.

     When the HTTP-EQUIV attribute is not present, the server
     should not generate an HTTP response header for HTML DTD in 9.1,
    "HTML DTD".

        NOTE - If the
     metainformation; e.g.,

     Do body of a `text/html' message entity does
        not name an HTTP-EQUIV equal to begin with a response header that document type declaration, an HTML user
        agent should normally only be generated by infer the HTTP server.
     Example names that are inappropriate include `Server',
     `Date', above document type declaration.

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

    This document type declaration also refers to the HTML DTD which
    appears in 9.1, "HTML DTD".

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

    This document type declaration refers to the level 1 HTML DTD in
    9.3, "Level 1 HTML DTD". Form elements must not occur in level 1
    documents.

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

    These two document type declarations refer to the HTML DTD in
    9.2, "Strict HTML DTD" and `Last-modified' -- 9.4, "Strict Level 1 HTML DTD". They
    refer to the exact list more structurally rigid definition of
     inappropriate names is dependent on the particular server
     implementation.


4.2.6. Next Id: <NEXTID> HTML.

    HTML user agents may support other document types. In
    particular, they may support other formal public identifiers, or
    other document types altogether. They <NEXTID> element gives may support an internal
    declaration subset with supplemental entity, element, and other
    markup declarations.



Berners-Lee, Connolly                                          [Page 15]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

3.4. Example HTML Document

    <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    <HTML>
    <!-- Here's a hint for the name good place to use for
     an <A> element when editing an put a comment. -->
    <HEAD>
    <TITLE>Structural Example</TITLE>
    </HEAD><BODY>
    <H1>First Header</H1>
    <P>This is a paragraph in the example HTML document. It should be
     distinct from all NAME attribute values on <A> elements. For
     example:

     <NEXTID N=Z27>


4.3. Body: <BODY> 

     The <BODY> element contains file. Keep in mind
    that the text flow of title does not appear in the document,
     including headings, paragraphs, lists, etc.

     For example:

     <BODY>
     <h1>Important Stuff</h1>
     <p>Explanation about important stuff...
     </BODY>


4.4. Headings: <H1> ... <H6> 

     The six heading elements, <H1> through <H6>, denote section
     headings. Although document text, but that
    the order and occurence of headings is
     not constrained header (defined by H1) does.</P>
    <OL>
    <LI>First item in an ordered list.
    <LI>Second item in an ordered list.
      <UL COMPACT>
      <LI> Note that lists can be nested;
      <LI> Whitespace may be used to assist in reading the
           HTML DTD, documents should source.
      </UL>
    <LI>Third item in an ordered list.
    </OL>
    <P>This is an additional paragraph. Technically, end tags are
    not skip
     levels (for example, from H1 required for paragraphs, although they are allowed. You can
    include character highlighting in a paragraph. <EM>This sentence
    of the paragraph is emphasized.</EM> Note that the &lt;/P&gt;
    end tag has been omitted.
    <P>
    <IMG SRC ="triangle.xbm" alt="Warning: ">
    Be sure to H3), read these <b>bold instructions</b>.
    </BODY></HTML>


4. HTML as converting such
     documents an Internet Media Type

    An HTML user agent allows users to other representations is often problematic.

     Example of use:

     <H1>This is interact with resources which
    have HTML representations. At a heading</H1>
     Here is some text
     <H2>Second minimum, it must allow users to
    examine and navigate the content of HTML level heading</H2>
     Here is some more text.

     Typical renderings are:

     H1
                    Bold, very-large font, centered. One or two blank
                    lines above 1 documents. HTML
    user agents should be able to preserve all formatting
    distinctions represented in an HTML document, and below.

     H2
                    Bold, large font, flush-left. One be able to
    simultaneously present resources referred to by IMG elements
    (they may ignore some formatting distinctions or two blank
                    lines above and below.

     H3
                    Italic, large font, slightly indented from IMG resources
    at the
                    left margin. One or two blank lines above and
                    below.

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

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

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


4.5. Block Structuring Elements 

     Each request of the following elements defines a block structure;
     that is, they indicate a paragraph break before user). Level 2 HTML user agents should
    support form entry and after.


4.5.1. Paragraph: <P> 

     The <P> element indicates a paragraph. submission.


4.1. text/html media type

    This specification defines the Internet Media Type[IMEDIA]
    (formerly referred to as the Content Type[MIME]) called
    `text/html'. The exact
     indentation, leading space, etc. of a paragraph following is not
     specified and may to be a function of other tags, style sheets,
     etc.

     Typically, paragraphs registered with [IANA].

    Media Type name
            text

Berners-Lee, Connolly                                          [Page 16]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995


    Media subtype name
            html

    Required parameters
            none

    Optional parameters
            level, charset

    Encoding considerations
            any encoding is allowed

    Security considerations
            see 10, "Security Considerations"

    The optional parameters are surrounded by a vertical space of
     one line or half a line. defined as follows:

    Level
            The first line in a paragraph is
     indented level parameter specifies the feature set used in some cases.

     Example of use:

     <H1>This Heading Precedes
            the Paragraph</H1>
     <P>This document. The level is the text an integer number, implying
            that any features of same or lower level may be present
            in the first paragraph.
     <P>This document. Level 1 is the text of the second paragraph. Although you do not
     need to start paragraphs on new lines, maintaining all features defined in this
     convention facilitates document maintenance.</P>
     <P>This
            specification except those that require the <FORM>
            element. Level 2 includes form processing. Level 2 is
            the text of a third paragraph.</P>


4.5.2. Preformatted Text: <PRE> default.

    Charset
            The <PRE> element represents a character cell block charset parameter (as defined in section 7.1.1 of
     textand so is suitable for text that has been formatted on
     screen.

     The <PRE> tag
            RFC 1521[MIME]) may be given to specify the character
            encoding scheme used with to represent the optional WIDTH attribute. HTML document as a
            sequence of octets. The WIDTH attribute specifies default value is outside the maximum number
            scope of
     characters this specification; but for a line and allows example, the HTML user agent to
     select a suitable font
            default is `US-ASCII' in the context of MIME mail, and indentation.

     Within preformatted text:

          * Line breaks within
            `ISO-8859-1' in the text are rendered as context of HTTP.


4.2. HTML Document Representation

    A message entity with a move to
          the beginning content type of the next line.

          NOTE - References to the ``beginning `text/html' represents
    an HTML document, consisting of a new line'' do
          not imply that the renderer is forbidden from using single text entity. The
    `charset' parameter (whether implicit or explicit) identifies a
          constant left indent for rendering preformatted text.
    character encoding scheme. The left indent may be constrained by text entity consists of the width
          required.

          * Anchor elements
    characters determined by this character encoding scheme and phrase markup may be used.

          NOTE - Within a Preformatted Text element, the
          constraint that
    octets of the rendering must be on a fixed
          horizontal character pitch may limit or prevent body of the
          ability message entity.


4.2.1. Undeclared Markup Error Handling

    To facilitate experimentation and interoperability between
    implementations of various versions of HTML, the installed base
    of HTML user agent to faithfully render
          phrase markup.

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

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

          * The horizontal tab character (encoded reducing it to HTML 2.0: markup 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 form of characters so far on the line
          as a multiple of 8.

     Example of use:

     <PRE>
     This start-tag or
    end-tag, whose generic identifier is an example line.
     </PRE>


4.5.3. Address: <ADDRESS> not declared is mapped to

Berners-Lee, Connolly                                          [Page 17]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    nothing during tokenization. Undeclared attributes are treated
    similarly. The <ADDRESS> element specifies such information as address,
     signature and authorship, often at the beginning or end of
     the body entire attribute specification of a document.

     Typically, the <ADDRESS> element is rendered in an italic
     typeface unknown
    attribute (i.e., the unknown attribute and may be indented.

     Example of use:

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


4.5.4. Block Quote: <BLOCKQUOTE> 

     The <BLOCKQUOTE> element contains text quoted from another
     source.

     A typical rendering might its value, if any)
    should be a slight extra left and right
     indent, and/or italic font. The <BLOCKQUOTE> typically
     provides space above and below the quote.

     Single-font rendition may reflect ignored. On the quotation style of
     Internet mail by putting a vertical line of graphic
     characters, such other hand, references to undeclared
    entities should be treated as the greater than symbol (>), in the left
     margin.

     Example of use:

     I think the poem ends
     <BLOCKQUOTE>
     <P>Soft you now, the fair Ophelia. Nymph, in thy orisons, data characters.

    For example:

    <div class=chapter><h1>foo</h1><p>...</div>
      => <H1>,"foo",</H1>,<P>,"..."
    xxx <P ID=z23> yyy
      => "xxx ",<P>," yyy
    Let &alpha; &amp; &beta; be all
     my sins remembered.
     </BLOCKQUOTE>
     but I am not sure.


4.6. List Elements 

     HTML includes a number of list elements. They may finite sets.
      => "Let &alpha; & &beta; be used in
     combination; finite sets."

    Support for example, a <OL> notifying the user of such errors is encouraged.

    Information providers are warned that this convention is not
    binding: unspecified behavior may be nested in an <LI>
     element result, as such markup does
    not conform to this specification.


4.2.2. Conventional Representation of Newlines

    SGML specifies that a <UL>.


4.6.1. Unordered List: <UL>, <LI> 

     The <UL> represents text entity is a list sequence of items records, each
    beginning with no inherent
     ordering -- typically a bulleted list.

     The content of record start character and ending with a <UL> element record
    end character (code positions 10 and 13 respectively) (section
    7.6.1, ``Record Boundaries'' in [SGML]).

    [MIME] specifies that a body of type `text/*' is a sequence of <LI>
     elements. For example:

     <UL>
     <LI>First list item
     <LI>Second list item
      <p>second paragraph of second item
     <LI>Third list item
     </UL>


4.6.2. Ordered List: <OL> 

     The <UL> element represents an ordered list of items, sorted
    lines, each terminated by sequence or order of importance.

     The content of a <OL> element is a sequence CRLF, that is, octets 13, 10.

    In practice, HTML documents are frequently represented and
    transmitted using an end of <LI>
     elements. For example:

     <OL>
     <LI>Click the Web button to open line convention that depends on the Open
    conventions of the URI window.
     <LI>Enter source of the URI number in document; frequently, that
    representation consists of CR only, LF only, or a CR LF
    sequence. Hence the text field decoding of the Open URI
     window. The Web document you specified is displayed.
       <ol>
        <li>substep 1
        <li>substep 2
       </ol>
     <LI>Click highlighted text to move from one link to another.
     </OL>

     The COMPACT attribute suggests that octets will often result in
    a compact rendering be
     used.


4.6.3. Directory List: <DIR> 

     The <DIR> element text entity with some missing record start and record end
    characters.

    Since there is similar no ambiguity, HTML user agents are encouraged to
    infer the <UL> element. It
     represents a list missing record start and end characters.

    An HTML user agent should treat end of short items, typically up to 20
     characters each. Items line in any of its
    variations as a directory list may be arranged word space in columns, typically 24 characters wide.

     The content all contexts except preformatted
    text. Within preformatted text, an HTML user agent should treat
    any of the three common representations of end-of-line as
    starting a <OL> element new line.


5. Document Structure

    An HTML document is a sequence tree of <LI>
     elements. Nested block elements, including a head and
    body, headings, paragraphs, lists, etc. Form elements are not allowed

Berners-Lee, Connolly                                          [Page 18]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    discussed in the
     content 8, "Forms".


5.1. Document Element: HTML

    The HTML document element consists of <DIR> a head and a body, much
    like a memo or a mail message. The head contains the title and
    optional elements. For example:

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


4.6.4. Menu List: <MENU> The <MENU> element body is a list text flow consisting of items with typically one
     line per item.
    paragraphs, lists, and other elements.


5.2. Head: HEAD

    The menu list style is typically more compact
     than the style head of an unordered list.

     The content of a <MENU> element HTML document is a sequence an unordered collection of <LI>
     elements. Nested block elements are not allowed in
    information about the
     content of <MENU> elements. document. For example:

     <MENU>
     <LI>First item in

    <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    <HEAD>
    <TITLE>Introduction to HTML</TITLE>
    </HEAD>
    ...


5.2.1. Title: TITLE

    Every HTML document must contain a <TITLE> element.

    The title should identify the list.
     <LI>Second item in contents of the list.
     <LI>Third item document in the list.
     </MENU>


4.6.5. Definition List: <DL>, <DT>, <DD> 

     A definition list is a list of terms and corresponding
     definitions. Definition lists are typically formatted with
     the term flush-left and the definition, formatted paragraph
     style, indented after the term.

     Example
    global context. A short title, such as ``Introduction'' may be
    meaningless out of use:

     <DL>
     <DT>Term<DD>This context. A title such as ``Introduction to
    HTML Elements'' is the definition more appropriate.

        NOTE - The length of the first term.
     <DT>Term<DD>This a title is the definition of the second term.
     </DL>

     If the DT term does not fit in the DT column (one third of
     the display area), it limited; however,
        long titles may be extended across truncated in some applications. To
        minimize this possibility, titles should be fewer than
        64 characters.

    A user agent may display the page with title of a document in a history
    list or as a label for the DD section moved to window displaying the next line, or it may be wrapped
     onto successive lines of document. This
    differs from headings (5.4, "Headings: H1 ... H6"), which are
    typically displayed within the left hand column. body text flow.


5.2.2. Base Address: BASE

    The optional COMPACT attribute suggests that a compact
     rendering be used, because <BASE> element specifies the list items are small and/or base address for
    resolving relative links from the entire list is large.

     Unless document, overriding any
    context otherwise known to the COMPACT attribute is present, an HTML user agent
     may leave white space between successive DT, DD pairs. agent. The
     COMPACT required HREF
    attribute may also reduce specifies the width URI for navigating the document (see 7,
    "Hyperlinks"). The value of the left-hand
     (DT) column.

     <DL COMPACT>
     <DT>Term<DD>This is HREF attribute must be an
    absolute URI.




Berners-Lee, Connolly                                          [Page 19]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

5.2.3. Keyword Index: ISINDEX

    The <ISINDEX> element indicates that the first definition in compact format.
     <DT>Term<DD>This is user agent should allow
    the second definition in compact format.
     </DL>


4.7. Phrase Markup 

     Phrases may be marked up according user to idiomatic usage,
     typographic appearance, or search an index by giving keywords. See 7.5,
    "Queries and Indexes" for use as details.


5.2.4. Link: LINK

    The <LINK> element represents a hyperlink anchors.

     User agents must render highlighted phrases distinctly from
     plain text. Additionally, <EM> content must be rendered (see 7, "Hyperlinks").
    It has the same attributes as
     distinct from <STRONG> content, and <B> content must
     rendered as distinct from <I> content.

     Phrase elements may be nested within the content of other
     phrase elements; however, HTML user agents may render nested
     phrase elements indistinctly from non-nested elements:

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


4.7.1. Idiomatic Elements 


4.7.1.1. Citation: <CITE> <A> element (see 5.7.3,
    "Anchor: A").

    The <CITE> <LINK> element is typically used to indicate the title of a book authorship,
    related indexes and glossaries, older or other citation. It is typically typeset as italics. For
     example:

     He just couldn't get enough of <cite>The Grapes of Wrath</cite>.


4.7.1.2. Code: <CODE> more recent versions,
    style sheets, document hierarchy etc.


5.2.5. Associated Meta-information: META

    The <CODE> <META> element indicates is an example of code, typically
     rendered extensible container for use in
    identifying specialized document meta-information.
    Meta-information has two main functions:

        * to provide a monospaced font. Contrast with means to discover that the <PRE> block
     structuring element in 4.5.2, "Preformatted Text: PRE". For
     example:

     The expression <code>x += 1</code> is short data set exists
        and how it might be obtained or accessed; and

        * to document the content, quality, and features of a data
        set, indicating its fitness for <code>x = x + 1</code>.


4.7.1.3. Emphasis: <EM> 

     The <EM> use.

    Each <META> element indicates an emphasized phrase, typically
     rendered specifies a name/value pair. If multiple
    META elements are provided with the same name, their combined
    contents--concatenated as italics. For example:

     A singular subject <em>always</em> takes a singular verb.


4.7.1.4. Keyboard: <KBD> comma-separated list--is the value
    associated with that name.

        NOTE - The Keyboard <META> element indicates text typed by a user,
     typically rendered in a monospaced font. This is commonly should not be used in instruction manuals. For example:

     Enter <kbd>FIND IT</kbd> to search the database.


4.7.1.5. Sample: <SAMP> 

     The <SAMP> element indicates a sequence of literal
     characters, typically rendered in a monospaced font. For
     example:

     The only word containing the letters <samp>mt</samp> is dreamt.


4.7.1.6. Strong Empasis: <STRONG> 

     The <STRONG> element indicates strong emphasis, typically
     rendered in bold. For example:

     <strong>STOP</strong>, or I'll say "<strong>STOP</strong>" again!.


4.7.1.7. Variable: <VAR> 

     The <VAR> element indicates where a placeholder, typically
     rendered
        specific element, such as italic. For example:

     Take a guess: Roses are <var>blank</var>.


4.7.2. Typographic Elements 

     Typographic elements are used to specify <TITLE>, would be more
        appropriate.

    HTTP servers may read the format content of
     marked text.

     Typical renderings for idomatic the document <HEAD> to
    generate header fields corresponding to any elements vary between user
     agents. If defining a specific rendering is necessary --
    value for example,
     when referring to a specific text attribute as in ``The
     italic parts are mandatory'' -- a typographic element can be
     used to ensure that the intended typography is used where
     possible.


4.7.2.1. Bold: <B> attribute HTTP-EQUIV.

        NOTE - The <B> element indicated bold text. Where bold typography method by which the server extracts document
        meta-information is unavailable, an alternative representation may be used.


4.7.2.2. Italic: <I> unspecified and not mandatory. The <I>
        <META> element indicated italic text. Where italic
     typography is unavailable, only provides an alternative representation extensible mechanism for
        identifying and embedding document meta-information --
        how it may be used.


4.7.2.3. Typewriter: <TT> 

     The <TT> element indicates typewriter text. Where a
     typewriter font used is unavailable, an alternative
     representation may be used.


4.7.3. Anchor: <A> 

     The <A> element indicates the source and/or destination of a
     hyperlink (see 6, "Hyperlinks"). At least one of up to the NAME individual server
        implementation and HREF attributes should be given. the HTML user agent.

    Attributes of the <A> META element:

     HREF
                    gives the destination of a hyperlink.

     NAME
                    gives

    HTTP-EQUIV
            binds the name of element to an HTTP header field. An HTTP

Berners-Lee, Connolly                                          [Page 20]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

            server may use this information to process the anchor, and makes document.
            In particular, it
                    available as a navigation destination.

     TITLE
                    suggests may include a title for header field in the destination resource --
                    advisory only. The TITLE attribute may be used:

          * for display prior
            responses to accessing the destination
          resource, requests for example, as a margin note or on a small
          box while this document: the mouse header name
            is over the anchor, or while taken from the
          document is being loaded;

          * for resources that do not specify a title such as
          graphics, plain text and Gopher menus, for use as a
          window title.

     REL
                    The REL HTTP-EQUIV attribute gives the relationship(s)
                    described by value, and the hyperlink. The
            header value is a
                    whitespace separated list of relationship names.

     REV
                    same as the REL attribute, but taken from the semantics value of the relationship CONTENT
            attribute. HTTP header names are in the reverse direction. A
                    link from A to B with REL=``X'' expresses the same
                    relationship as a link from B to A with REV=``X''.
                    An anchor may have both REL and REV attributes.

     URN not case sensitive.

    NAME
            specifies a preferred, more persistent identifier
                    for the destination. The format of URNs is under
                    discussion (1995) by various working groups name of the
                    Internet Engineering Task Force.

     METHODS name/value pair. If not
            present, HTTP-EQUIV gives the name.

    CONTENT
            specifies methods to be used in accessing the
                    destination, as a whitespace-separated list value of
                    names. For similar reasons as for the TITLE
                    attribute, it may be useful to include the
                    information in advance in name/value pair.

    Examples

    If the link. For example, document contains:

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

    then the HTML user agent server may chose a different
                    rendering include the following header fields:

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

    as a function part of the methods allowed; HTTP response to a `GET' or `HEAD' request for example, something
    that is searchable may get
                    a different icon.


4.8. Line Break: <BR> 

     The <BR> element specifies a line break between words (see
     5, "Character, Words, and Paragraphs"). For example:

     <P> Pease porridge hot<BR>
     Pease porridge cold<BR>
     Pease porridge in document.

    An HTTP server must not use the pot<BR>
     Nine days old.


4.9. Horizontal Rule: <HR> 

     The <HR> element is a divider between sections of text;
     typcially a full width horizontal rule or equivalent
     graphic. For example:

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


4.10. Image: <IMG> 

     The <IMG> <META> element refers to form an image or icon.

     HTML user agents that cannot process images ignore the <IMG>
     element HTTP
    response header unless it the ALT HTTP-EQUIV attribute is present.

          NOTE - Some

    An HTTP server may disregard any <META> elements that specify
    information controlled by the HTTP server, for example `Server',
    `Date', and `Last-modified'.


5.2.6. Next Id: NEXTID

    The <NEXTID> element is included for historical reasons only.
    HTML user agents can process graphics
          linked via anchors , but document should not <IMG> graphics. If contain <NEXTID> elements.

    The <NEXTID> element gives a
          graphic is essential, it should be referenced from an hint for the name to use for a new
    <A> element rather than in <IMG> element.If the graphic
          is not essential, then the <IMG> when editing an HTML document. It should be distinct
    from all NAME attribute values on <A> elements. For example:

    <NEXTID N=Z27>



Berners-Lee, Connolly                                          [Page 21]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

5.3. Body: BODY

    The <BODY> element is
          appropriate.

     Attributes of the <IMG> element:

     ALIGN
          alignment of the image with respect to contains the text
          baseline. * `TOP' specifies that the top of the image
          aligns with the tallest item on the line contianing the
          image.

          * `MIDDLE' specifies that the center of the image
          aligns with the baseline of the line containing the
          image.

          * `BOTTOM' specifies that the bottom of the image
          aligns with the baseline flow of the line containing the
          image.

     ALT
                    Optional alternative text, for use in
                    non-graphical environments.

     ISMAP
                    indicates an image map (see 6.4, "Image Maps").

     SRC
                    specifies document,
    including headings, paragraphs, lists, etc.

    For example:

    <BODY>
    <h1>Important Stuff</h1>
    <p>Explanation about important stuff...
    </BODY>


5.4. Headings: H1 ... H6

    The six heading elements, <H1> through <H6>, denote section
    headings. Although the URI order and occurrence of headings is not
    constrained by the image resource.

          NOTE - In practice, the media types of image resources
          are limited to a few raster graphic formats: typically
          `image/gif', `image/jpeg'. In particular, `text/html'
          resources are HTML DTD, documents should not intended skip levels
    (for example, from H1 to be used H3), as image
          resources.

     Examples converting such documents to
    other representations is often problematic.

    Example of use:

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

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

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


5. Character, Words, and Paragraphs 

     An HTML user agent should present the body of an HTML
     document as

    <H1>This is a collection of typeset paragraphs and
     preformatted heading</H1>
    Here is some text
    <H2>Second level heading</H2>
    Here is some more text. Except for

    Typical renderings are:

    H1
            Bold, very-large font, centered. One or two blank lines
            above and below.

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

    H3
            Italic, large font, slightly indented from the <PRE> element, each block left
            margin. One or two blank lines above and below.

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

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

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


Berners-Lee, Connolly                                          [Page 22]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

5.5. Block Structuring Elements

    Block structuring elements include paragraphs, lists, and block
    quotes. They must not contain heading elements, but they may
    contain phrase markup, and in some cases, they may be nested.


5.5.1. Paragraph: P

    The <P> element is regarded as indicates a paragraph. The exact indentation,
    leading space, etc. of a paragraph by taking the
     data characters in its content is not specified and the content may be a
    function of its
     descendant elements, concatenating them, and splitting the
     result into words, separated other tags, style sheets, etc.

    Typically, paragraphs are surrounded by space, tab, a vertical space of one
    line or record end
     characters (and perhaps hyphen characters). half a line. The sequence of
     words is typeset as first line in a paragraph by 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 number indented
    in some cases.

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

          NOTE - Use use:

    <H1>This Heading Precedes the non-breaking space and soft hyphen
          indicator characters Paragraph</H1>
    <P>This is discouraged because support for
          them the text of the first paragraph.
    <P>This is the text of the second paragraph. Although you do not widely deployed.

          NOTE - To support non-western writing systems,
    need to start paragraphs on new lines, maintaining this
    convention facilitates document maintenance.</P>
    <P>This is the text of a larger
          character repertoire will be specified in third paragraph.</P>


5.5.2. Preformatted Text: PRE

    The <PRE> element represents a future
          version character cell block of HTML. text and
    is suitable for text that has been formatted for a monospaced
    font.

    The document character set will <PRE> tag may be
          ISO/IEC 10646-1, or some subset that agrees used with
          ISO/IEC 10646-1; in particular, all numeric character
          references must use code positions assigned by ISO/IEC
          10646-1.

     In SGML applications, the use of control characters is
     limited in order to maximize optional WIDTH attribute. The
    WIDTH attribute specifies the chance maximum number 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 `US-ASCII' for a
    line and
     `ISO-8859-1'), Carriage Return, allows the HTML user agent to select a suitable font
    and indentation.

    Within preformatted text:

        * Line Feed.

     The HTML DTD references breaks within the Added Latin 1 entity set, to
     allow mnemonic representation of Latin 1 characters using
     only the widely supported ASCII character repertoire. For
     example:

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

     See 8.4.2, "ISO Latin 1 Character Entity Set" for text are rendered as a table of move to the ``Added Latin 1'' entities, and 11.1, "The ANSI/ISO
     8859-1 Coded Character Set" for a table
        beginning of the code
     positions of ANSI/ISO 8859-1.


6. Hyperlinks 

     In addition next line.

            NOTE - References to general purpose elements such as paragraphs
     and lists, HTML documents can express hyperlinks. A
     hyperlink is a relationship between two resources, called the source and the destination ``beginning of the hyperlink. Each
     resource has a Uniform Resource Identifier (URI).

     An HTML user agent allows navigating a collection of these
     resources. In the following interactions, the URI of the
     source document is called the base URI.


6.1. Accessing Resources 

     Each of new line''
            do not imply that the following markup constructs renderer is the source of forbidden from
            using a
     hyperlink; these hyperlinks are references to resources to constant left indent for rendering
            preformatted text. The left indent may be processed in conjunction with
            constrained by the source documents:

          * <IMG> elements width required.

        * <INPUT> Anchor elements with the SRC attribute present

          * <LINK> element

     To access the destination of a hyperlink, the base URI of
     the source document is combined with and phrase markup may be used.

            NOTE - Constraints on the value processing of the HREF <PRE>
            content may may limit or SRC attribute prevent the ability of the hyperlink element according to
     [RELURL]. The
            HTML user agent disregards any fragment identifer,
     and uses the resulting URI to access the destination
     resource. For example, if a document identified as
     `http://host/x/y.html' contains:

     <img src="../icons/abc.gif">

     then the user agent must use the URI
     `http://host/icons/abc.gif' to access the resource linked
     from the <IMG> element.


6.2. Traversing Hyperlinks 

     An <A> element with the HREF attribute present is an anchor;
     that is, the source of a hyperlink faithfully render phrase markup.

Berners-Lee, Connolly                                          [Page 23]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995


        * Elements that is an option to
     navigate to another resource. The <LINK> element may also define paragraph formatting (headings,
        address, etc.) must not be
     an anchor.

     In addition to the base URI, the state of an HTML user agent
     includes a list of the anchors used.

            NOTE - Some historical documents contain <P> tags in the document. The user can
     traverse
            <PRE> elements. User agents are encouraged to treat
            this as a hyperlink line break. A <P> tag followed by choosing an anchor. a
            newline character should produce only one line
            break, not a line break plus a blank line.

        * The user agent
     then accesses horizontal tab character (code position 9 in the destination HTML
        document character set) must be interpreted as above and presents
     it.


6.2.1. Fragment Identifiers 

     If the value smallest
        positive nonzero number of spaces which will leave the <HREF> attribute
        number of an anchor element
     contains a `#' character, then the characters after so far on the `#'
     are line as a fragment identifier, multiple of 8.
        Documents should not a part contain tab characters, as they are not
        supported consistently.

    Example of the destination
     URI. As a degenerate case, `HREF="#fragment"' refers use:

    <PRE>
    Line 1.
           Line 2 is to an
     anchor in the same document: the source right of line 1.     <a href="abc">abc</a>
           Line 3 aligns with line 2.            <a href="def">def</a>
    </PRE>


5.5.2.1. Example and destination URIs
     are the same.

     After accessing the destination resource, the navigation
     state (the scrollbar, for example) may be modified by a
     fragment identifer in the hyperlink source markup. Listing: XMP, LISTING

    The
     meaning of fragment identifiers depends on the media type of
     the destination resource. For `text/html' resources, it
     instructs the user agent <XMP> and <LISTING> elements are similar to locate the <A> element with <PRE>
    element, but they have a
     NAME attribute whose value different syntax. Their content is the same
    declared as CDATA, which means that no markup except the fragment
     identifier. The matching end-tag
    open delimiter-in-context is case sensitive.

     For example, if recognized (see 9.6 ``Delimiter
    Recognition'' of [SGML]).

        NOTE - In a user agent was processing the above
     document and the user indicated the following anchor:

     <p> See: <a href="app1.html#bannanas">appendix 1</a> for more detail
     on bannanas.</a>

     then the user agent URI must access the resource
     `http://host/x/app1.html'. Assuming the resource is
     represented using the `text/html' media type, previous draft of the user agent
     must locate HTML specification,
        the anchor named `bannanas' syntax of <XMP> and begin navigation
     there.

     The base URI for navigating the destination document may <LISTING> elements allowed
        closing tags to be
     different from treated as data characters, as long
        as the URI used tag name was not <XMP> or <LISTING>,
        respectively.

    Since CDATA declared content has a number of unfortunate
    interactions with processing techniques and tends to access it. For example, it
     may be replaced by by a <BASE> tag in used and
    implemented inconsistently, HTML documents should not contain
    <XMP> nor <LISTING> elements -- the destination
     document or by an HTTP redirection transaction.


6.3. Queries <PRE> tag is more expressive
    and Indexes more consistently supported.

    The <ISINDEX> <LISTING> element represents should be rendered so that at least 132
    characters fit on a set of hyperlinks. line. The
     user can choose from the set by providing keywords to the
     user agent. The user agent computes the destination URI by
     appending `?' and the keywords <XMP> element should be rendered
    so that at least 80 characters fit on a line but is otherwise
    identical to the base URI. The keywords
     are escaped according to [URL] and joined by `+'. For
     example, if <LISTING> element.

        NOTE - In a document contains:

     <BASE HREF="http://host/index">
     <ISINDEX>

     and previous draft, HTML included a <PLAINTEXT>
        element that is similar to the user provides <LISTING> element, except
        that there is no closing tag: all characters after the keywords `apple'

Berners-Lee, Connolly                                          [Page 24]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

        <PLAINTEXT> start-tag are data.


5.5.3. Address: ADDRESS

    The <ADDRESS> element contains such information as address,
    signature and `berry', then authorship, often at the user agent must access beginning or end of the resource
     `http://host/index?apple+berry'.

     <FORM> elements with `METHOD=GET' also represent sets
    body of
     hyperlinks. See 7.2.2, "Query Forms: METHOD=GET" for
     details.


6.4. Image Maps 

     The ISMAP attribute in combination with a document.

    Typically, the <A> <ADDRESS> element is rendered in an italic
    typeface and <IMG>
     elements, represents a set may be indented.

    Example of hyperlinks. use:

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


5.5.4. Block Quote: BLOCKQUOTE

    The user can
     choose <BLOCKQUOTE> element contains text quoted from the set by choosing another
    source.

    A typical rendering might be a pixel of the image. slight extra left and right
    indent, and/or italic font. The
     user agent computes the destination URI by appending `?' <BLOCKQUOTE> typically provides
    space above and below the coordinates of the pixel to quote.

    Single-font rendition may reflect the URI given in the <A>
     element. For example, if a document contains:

     <head><title>ImageMap Example</title>
     <BASE HREF="http://host/index"></head>
     <body>
     <p> Choose any quotation style of these icons:<br>
     <a href="/cgi-bin/imagemap"><img ismap src="icons.gif"></a>

     and the user chooses the upper-leftmost pixel, then chosen
     hyperlink is the one with the URI
     `http://host/cgi-bin/image?0,0'.


7. Forms 

     A form is a template for
    Internet mail by putting a form data set -- sequence vertical line of
     name/value pair fields -- with an associated method and
     action URI. The names are specified on graphic characters,
    such as the NAME attributes greater than symbol (>), in the left margin.

    Example of form input elements, and use:

    I think the values are given by poem ends
    <BLOCKQUOTE>
    <P>Soft you now, the
     user. The resulting form data set is used to access an
     information service as fair Ophelia. Nymph, in thy orisons, be all
    my sins remembered.
    </BLOCKQUOTE>
    but I am not sure.


5.6. List Elements

    HTML includes a function number of the action and method.

     Forms elements can list elements. They may be mixed used in with document structuring
     elements. For
    combination; for example, a <PRE> element <OL> may contain be nested in an <LI>
    element of a <FORM>
     element, or <UL>.

    The COMPACT attribute suggests that a <FORM> element may contain lists which contain
     <INPUT> elements. This gives considerable flexibility in
     designing the layout compact rendering be used.



Berners-Lee, Connolly                                          [Page 25]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

5.6.1. Unordered List: UL, LI

    The <UL> represents a list of forms.

     Form processing is items -- typically a level 2 feature.


7.1. Form Elements 


7.1.1. Form: <FORM> bulleted
    list.

    The <FORM> content of a <UL> element contains is a sequence of input elements,
     along with document structuring <LI> elements.
    For example:

    <UL>
    <LI>First list item
    <LI>Second list item
     <p>second paragraph of second item
    <LI>Third list item
    </UL>


5.6.2. Ordered List: OL

    The attributes
     are:

     ACTION
                    specifies the action URI for the form. <OL> element represents an ordered list of items, sorted by
    sequence or order of importance. It is typically rendered as a
    numbered list.

    The ACTION
                    attribute defaults to the base URI content of the document
                    (see 6, "Hyperlinks").

     METHOD
                    selects a method <OL> element is a sequence of accessing the action URI.

     ENCTYPE
                    specifies <LI> elements.
    For example:

    <OL>
    <LI>Click the media type used Web button to encode open URI window.
    <LI>Enter the
                    name/value pairs for transport, URI number in case the
                    protocol does not itself impose a format.


7.1.2. Input Field: <INPUT> 

     The <INPUT> element represents a text field for user input.
     Attributes are:

     ALIGN
                    vertical alignment of the image. For use only with
                    `TYPE=IMAGE'. Open URI
    window. The possible values are as for the
                    ALIGN attribute of the <IMG> Web document you specified is displayed.
      <ol>
       <li>substep 1
       <li>substep 2
      </ol>
    <LI>Click highlighted text to move from one link to another.
    </OL>


5.6.3. Directory List: DIR

    The <DIR> element (see 4.10,
                    "Image: IMG").

     CHECKED
                    indicates that the initial state of a checkbox or
                    radio button is selected.

     MAXLENGTH
                    constrains similar to the number <UL> element. It represents
    a list of short items, typically up to 20 characters that can be
                    entered into each. Items
    in a text input field. If the value directory list may be arranged in columns, typically 24
    characters wide.

    The content of
                    MAXLENGTH a <DIR> element is greater the the value a sequence of <LI> elements.
    Nested block elements are not allowed in the SIZE
                    attribute, the field should scroll appropriately. content of <DIR>
    elements. For example:

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



Berners-Lee, Connolly                                          [Page 26]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

5.6.4. Menu List: MENU

    The default number <MENU> element is a list of characters items with typically one line
    per item. The menu list style is unlimited.

     NAME
                    symbolic name for typically more compact than the form field corresponding to
                    this
    style of an unordered list.

    The content of a <MENU> element or group is a sequence of <LI> elements.

     SIZE
                    specifies
    Nested block elements are not allowed in the amount content of display space allocated to
                    this input field according to its type.

     SRC
                    A URI specifying an image resource. <MENU>
    elements. For use only
                    with `TYPE=IMAGE'.

     TYPE
                    indicates type of example:

    <MENU>
    <LI>First item in the field. Defaults to `TEXT'.
                    Values are:

     CHECKBOX
                    an independent boolean value.

     HIDDEN
                    a hidden field. The user does not interact with
                    this field; instead, list.
    <LI>Second item in the VALUE attribute can be
                    used to specify list.
    <LI>Third item in the list.
    </MENU>


5.6.5. Definition List: DL, DT, DD

    A definition list is a value.

     IMAGE
                    specifies an image resource to display, and allows
                    input list of two form data: terms and corresponding
    definitions. Definition lists are typically formatted with the x
    term flush-left and y coordinate the definition, formatted paragraph style,
    indented after the term.

    The content of a pixel chosen from <DL> element is a sequence of <DT> elements
    and/or <DD> elements, usually in pairs. Multiple <DT> may be
    paired with a single <DD> element. Documents should not contain
    multiple consecutive <DD> elements.

    Example of use:

    <DL>
    <DT>Term<DD>This is the image. The names definition of the
                    data are first term.
    <DT>Term<DD>This is the name definition of this element with `.x' and
                    `.y' appended. `TYPE=IMAGE' implies `TYPE=SUBMIT'
                    processing; that is, when a pixel is chosen, the
                    form as a whole is submitted.

     PASSWORD
                    Similar to the TEXT attribute, except that second term.
    </DL>

    If the
                    value is obscured as it is entered.

     RADIO
                    a 1-of-many choice. All <INPUT> elements with
                    `TYPE=RADIO' and DT term does not fit in the same NAME combine into DT column (typically one
                    form field. The value
    third of the form field is display area), it may be extended across the
                    VALUE of page
    with the element chosen by DD section moved to the user. The
                    initial state next line, or it may be indicated with wrapped
    onto successive lines of the CHECKED
                    attribute. left hand column.

    The VALUE attribute is required for
                    radio inputs.

     RESET
                    an input option, typically a button, that
                    instructs the user agent to reset the form's
                    fields to their initial states. Any VALUE optional COMPACT attribute indicates a label for the input
                    (button).

     SUBMIT
                    an input option, typically a button, suggests that
                    instructs the user agent to submit the form. Any
                    VALUE attribute indicates a label for compact rendering
    be used, because the input
                    (button). If list items are small and/or the NAME attribute is present, this
                    element contributes a form field whose value entire list
    is
                    given by the VALUE attribute. If large.

    Unless the NAME COMPACT attribute is not present, this element does not
                    contribute a form field.

     TEXT
                    a single line text entry fields. an HTML user agent may
    leave white space between successive DT, DD pairs. The SIZE and
                    MAXLENGTH attributes COMPACT
    attribute may be used to constrain also reduce the
                    input or layout width of the field. Use the <TEXTAREA>
                    element for mulit-line text fields.

     VALUE
                    The initial value of left-hand (DT)
    column.

    <DL COMPACT>
    <DT>Term<DD>This is the field.


7.1.3. Selection: <SELECT> 

     The <SELECT> element constrains first definition in compact format.
    <DT>Term<DD>This is the form field second definition in compact format.
    </DL>

Berners-Lee, Connolly                                          [Page 27]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995



5.7. Phrase Markup

    Phrases may be marked up according to an
     enumerated list idiomatic usage,
    typographic appearance, or for use as hyperlink anchors.

    User agents must render highlighted phrases distinctly from
    plain text. Additionally, <EM> content must be rendered as
    distinct from <STRONG> content, and <B> content must rendered as
    distinct from <I> content.

    Phrase elements may be nested within the content of values. The values are given in <OPTION>
     elements. Attributes are:

     MULTIPLE
                    indicates that more than one option other phrase
    elements; however, HTML user agents may render nested phrase
    elements indistinctly from non-nested elements:

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


5.7.1. Idiomatic Elements

    Phrases may be marked up to indicate certain idioms.

        NOTE - User agents may support the <DFN> element, not
        included in this specification, as it has been deployed
        to some extent. It is used to indicate the value.

     NAME
                    specifies the name defining
        instance of a term, and it is typically rendered in
        italic or bold italic.


5.7.1.1. Citation: CITE

    The <CITE> element is used to indicate the form field.

     SIZE
                    specifies the number of visible items. Select
                    fields title of size one are typically pop-down menus,
                    whereas select fields with size greater than one
                    are a book or
    other citation. It is typically lists. rendered as italics. For
    example:

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

     The initial state has the first option selected, unless a
     SELECTED attribute is present on any

    He just couldn't get enough of the <OPTION>
     elements.


7.1.3.1. Option: <OPTION> <cite>The Grapes of Wrath</cite>.


5.7.1.2. Code: CODE

    The Option <CODE> element can only occur within a Select element.
     It represents one choice, and has the following attributes:

     SELECTED
                    Indicates that this option is initially selected.

     VALUE indicates the value to be returned if this option
                    is chosen. The field value defaults to the content an example of the <OPTION> element. code, typically
    rendered in a mono-spaced font. The content <CODE> element is intended
    for short words or phrases of code; the <OPTION> <PRE> block structuring
    element (5.5.2, "Preformatted Text: PRE") is presented to the user
     to represent the option. It more apropriate for
    multiple-line listings. For example:

    The expression <code>x += 1</code>
    is used short for <code>x = x + 1</code>.





Berners-Lee, Connolly                                          [Page 28]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

5.7.1.3. Emphasis: EM

    The <EM> element indicates an emphasized phrase, typically
    rendered as italics. For example:

    A singular subject <em>always</em> takes a returned value if
     the VALUE attribute is not present.


7.1.4. Text Area: <TEXTAREA> singular verb.


5.7.1.4. Keyboard: KBD

    The <TEXTAREA> <KBD> element represents a multi-line indicates text field. typed by a user, typically
    rendered in a mono-spaced font. This is commonly used in
    instruction manuals. For example:

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

     The content of

    Enter <kbd>FIND IT</kbd> to search the <TEXTAREA> database.


5.7.1.5. Sample: SAMP

    The <SAMP> element is the field's initial
     value.

     Typically, the ROWS and COLS attributes determine the
     visible dimension indicates a sequence of the field in characters. The field is literal characters,
    typically rendered in a fixed-width mono-spaced font. HTML user agents should
     allow text to extend beyond these limits by scrolling as
     needed.


7.2. Form Submission 

     An HTML user agent begins processing a form by presenting
     the document with For example:

    The only word containing the fields letters <samp>mt</samp> is dreamt.


5.7.1.6. Strong Emphasis: STRONG

    The <STRONG> element indicates strong emphasis, typically
    rendered in their initial state. bold. For example:

    <strong>STOP</strong>, or I'll say "<strong>STOP</strong>" again!.


5.7.1.7. Variable: VAR

    The
     user is allowed <VAR> element indicates a placeholder variable, typically
    rendered as italic. For example:

    Type <SAMP>html-check <VAR>file</VAR> | more</SAMP>
    to modify the fields, constrained by the
     field type etc. When check <VAR>file</VAR> for markup errors.


5.7.2. Typographic Elements

    Typographic elements are used to specify the format of marked
    text.

    Typical renderings for idiomatic elements may vary between user indicates that the form should
     be submitted (using
    agents. If a submit button or image input), the
     form data set specific rendering is processed according necessary -- for example,
    when referring to its method, action
     URI and enctype.

     When there is only one single-line text input field in a
     form, the user agent should accept Enter in that field specific text attribute as in ``The italic
    parts are mandatory'' -- a
     request typographic element can be used to submit
    ensure that the form.


7.2.1. The `application/x-www-form-urlencoded' Media Type 

     The default encoding for all forms is
     `application/x-www-form-urlencoded'. A form data set intended typography is
     represented used where possible.

        NOTE - User agents may support some typographic elements

Berners-Lee, Connolly                                          [Page 29]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

        not included in this media type specification, as follows:

          1. they have been
        deployed to some extent. The form field names <STRIKE> element indicates
        horizontal line through the characters, and values are escaped: space
          characterss are replaced by `+', and then reserved
          characters are escaped as per [URL]; that is,
          non-alphanumeric characters are replaced by `%HH', a
          percent sign and two hexadecimal digits representing
          the ASCII code of the character. Line breaks, as in
          multi-line textfield values, are represented as CR LF
          pairs, i.e. `%0D0A'.

          2. <U>
        element indicates an underline.


5.7.2.1. Bold: B

    The fields are listed in the order they appear in
          the document with the name separated from the value by
          `=' and the pairs separated from each other by `&'.
          Fields with null values <B> element indicates bold text. Where bold typography is
    unavailable, an alternative representation may be omitted. In particular,
          unselected radio buttons and checkboxes should not
          appear in the encoded data, but hidden fields with
          VALUE attributes present should.

          NOTE - used.


5.7.2.2. Italic: I

    The URI from <I> element indicates italic text. Where italic typography
    is unavailable, an alternative representation may be used.


5.7.2.3. Teletype: TT

    The <TT> element indicates teletype (monospaced )text. Where a query form submission can
    teletype font is unavailable, an alternative representation may
    be used
          in used.


5.7.3. Anchor: A

    The <A> element indicates a normal hyperlink anchor style hyperlink. Unfortunately, (see 7,
    "Hyperlinks"). At least one of the
          use NAME and HREF attributes
    should be present. Attributes of the `&' character to separate form fields
          interacts with its use in SGML attribute values as an
          entity reference delimiter. For example, <A> element:

    HREF
            gives the URI
          `http://host/?x=1&y=2' must be written `<a
          href="http://host/?x=1&#38;y=2"' or `<a
          href="http://host/?x=1&#amp;y=2">'.
          HTTP server implementors, and in particular, CGI
          implementors are encouraged to support the use of `;'
          in place the head anchor of `&' to save users a hyperlink.

    NAME
            gives the trouble name of escaping
          `&' characters this way.


7.2.2. Query Forms: `METHOD=GET' 

     If the processing anchor, and makes it available as
            a head of a form is idempotent (i.e. it has no
     lasting observable effect hyperlink.

    TITLE
            suggests a title for the destination resource --
            advisory only. The TITLE attribute may be used:

                * for display prior to accessing the destination
                resource, for example, as a margin note or on a
                small box while the state of mouse is over the world), then anchor, or
                while the form method should be `GET'. Many database searches have
     no visible side-effects and make ideal applications of query
     forms.

     To process a form whose action URL document is an HTTP URL being loaded;

                * for resources that do not include a title, such as
                graphics, plain text and whose
     method is `GET', Gopher menus, for use as a
                window title.

    REL
            The REL attribute gives the user agent starts with relationship(s) described by
            the action URI
     and appends hyperlink. The value is a `?' and whitespace separated list

Berners-Lee, Connolly                                          [Page 30]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

            of relationship names.

    REV
            same as the form data set, REL attribute, but the semantics of the
            relationship are in
     `application/x-www-form-urlencoded' format as above. The
     user agent then traverses the reverse direction. A link from A
            to this URI just B with REL=``X'' expresses the same relationship as if it
     were an a
            link from B to A with REV=``X''. An anchor (see 6.2, "Traversing Hyperlinks").

          NOTE - The URL encoding may result in vary long URIs,
          which cause some historical HTTP server implementations
          to exhibit defective behavior. As have both
            REL and REV attributes.

    URN
            specifies a result, some HTML
          forms are written using `METHOD=POST' even though the
          form submission has no side-effects.


7.2.3. Forms with Side-Effects: `METHOD=POST' 

     If the service associated with preferred, more persistent identifier for
            the processing of a form has
     side effects (for example, modification head anchor of a database or
     subscription to a service), the method should be `POST'.

     To process a form whose action URL is an HTTP URL hyperlink. The syntax and whose
     method is `POST',
            semantics of the user agent conducts an HTTP POST
     transaction using URN attribute are not yet specified.

    METHODS
            specifies methods to be used in accessing the action URI, and
            destination, as a message body whitespace-separated list of type
     `application/x-www-form-urlencoded' format as above. names.
            The
     user agent should display set of applicable names is a function of the response from scheme
            of the HTTP POST
     interaction just URI in the HREF attribute. For similar reasons as it would display
            for the response from an
     HTTP GET above.


7.2.4. Example Form Submission: Questionnaire Form 

     Consider TITLE attribute, it may be useful to include the following document:

     <title>Sample of HTML Form Submission</title>
     <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
            information in family: <INPUT NAME="family" TYPE=text>
     <P>Cities advance in which you maintain the link. For example, the
            HTML user agent may chose 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>

     The inital state different rendering as a
            function of the form data set is:

     name
                    ``''

     gender
                    ``male''

     family
                    ``''

     other
                    ``''

     nickname
                    ``''

     Note methods allowed; for example, something
            that the radio input has an initial value, while the
     checkbox has none. is searchable may get a different icon.


5.8. Line Break: BR

    The user might edit the fields <BR> element specifies a line break between words (see 6,
    "Characters, Words, and request that the form be
     submitted. At that point, suppose Paragraphs"). For example:

    <P> Pease porridge hot<BR>
    Pease porridge cold<BR>
    Pease porridge in the values are:

     name
                    ``John Doe''

     gender
                    ``male''

     family
                    ``5''

     city
                    ``kent,miami''

     other
                    ``abc\ndef''

     nickname
                    ``J&D'' pot<BR>
    Nine days old.


5.9. Horizontal Rule: HR

    The <HR> element is a divider between sections of text;
    typically a full width horizontal rule or equivalent graphic.
    For example:

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


5.10. Image: IMG

    The <IMG> element refers to an image or icon via a hyperlink
    (see 7.3, "Simultaneous Presentation of Image Resources").

    HTML user agent then conducts agents may process the value of the ALT attribute as

Berners-Lee, Connolly                                          [Page 31]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    an HTTP POST transaction using alternative to processing the URI `http://www.w3.org/sample'. The message body would
     be (ignore image resource indicated by the linebreak):

     name=John+Doe&gender=male&family=5&city=kent%2Cmiami&
     other=abc%0D0Adef&nickname=J%26D


8. HTML Public Text 


8.1.
    SRC attribute.

        NOTE - Some HTML DTD 

     This user agents can process graphics linked
        via anchors, but not <IMG> graphics. If a graphic is
        essential, it should be referenced from an <A> element
        rather than an <IMG> element. If the Document Type Definition for graphic is not
        essential, then the HyperText
     Markup Language.

<!--    html.dtd

        Document Type Definition for <IMG> element is appropriate.

    Attributes of the HyperText Markup Language
                 (HTML DTD)

        $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
          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 <IMG> element:

    ALIGN
            alignment of the language are necessary for
           compatibility image with widespread usage, but they may
           compromise respect to the structural integrity text
            baseline.

                * `TOP' specifies that the top of a document.
           This feature test entity enables a more prescriptive
           document type definition the image aligns
                with the tallest item on the line containing the
                image.

                * `MIDDLE' specifies that eliminates
           those features.
        -->

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

<!ENTITY % HTML.Deprecated "INCLUDE"
        -- Certain features the center of the language are necessary for
           compatibility image
                aligns with earlier versions the baseline of the specification,
           but they tend line containing the
                image.

                * `BOTTOM' specifies that the bottom of the image
                aligns with the baseline of the line containing the
                image.

    ALT
            text to be used an implemented inconsistently,
           and their use is deprecated. This feature test entity
           enables a document type definition that eliminates
           these features.
        -->

<!ENTITY % HTML.Highlighting "INCLUDE"
        -- Use this feature test entity in place of the referenced image resource,
            for example due to processing constraints or user
            preference.

    ISMAP
            indicates an image map (see 7.6, "Image Maps").

    SRC
            specifies the URI of the image resource.

                NOTE - In practice, the media types of image
                resources are limited to validate that a
           document uses no highlighting tags, which may be
           ignored on minimal implementations.
        -->

<!ENTITY % HTML.Forms "INCLUDE"
        -- Use this feature test entity to validate that a document
           contains no forms, which may few raster graphic
                formats: typically `image/gif', `image/jpeg'. In
                particular, `text/html' resources are not
                intended to be supported in minimal
           implementations
        -->

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

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

<!ENTITY % HTTP-Method "GET | POST"
        -- image resources.

    Examples of use:

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

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



Berners-Lee, Connolly                                          [Page 32]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

6. Characters, Words, and Paragraphs

    An HTML user agent should present the body of an HTML document
    as per HTTP specification, in progress
        -->

<!ENTITY % URI "CDATA"
        -- The term URI means a CDATA attribute
           whose value collection of typeset paragraphs and preformatted text.
    Except for preformatted elements (<PRE>, <XMP>, <LISTING>,
    <TEXTAREA>), each block structuring element is a Uniform Resource Identifier, regarded as defined by 
        "Universal Resource Identifiers" by Tim Berners-Lee
        aka RFC 1630

        Note that CDATA attributes are limited a
    paragraph by taking the LITLEN
        capacity (1024 data characters in its content and the current version
    content of html.decl),
        so that URIs in HTML have its descendant elements, concatenating them, and
    splitting the result into words, separated by space, tab, or
    record end characters (and perhaps hyphen characters). The
    sequence of words is typeset as a bounded length.

        -->


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

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

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


<!--======= paragraph by breaking it into
    lines.


6.1. The HTML Document Character mnemonic entities =================-->

<!ENTITY % ISOlat1 PUBLIC
  "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML">
%ISOlat1;

<!ENTITY amp CDATA "&#38;"     -- ampersand          -->
<!ENTITY gt CDATA "&#62;"      -- greater than       -->
<!ENTITY lt CDATA "&#60;"      -- less than          -->
<!ENTITY quot CDATA "&#34;"    -- double quote       -->


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

<!-- HTML 2.0 contains SGML Document Access (SDA) fixed attributes Set

    The document character set specified in support of easy transformation to the International Committee 9.5, "SGML Declaration
    for Accessible Document Design (ICADD) DTD
         "-//EC-USA-CDA/ICADD//DTD ICADD22//EN".
ICADD applications are designed to support usable access to
structured information HTML" must be supported by print-impaired individuals through
Braille, large print and voice synthesis.  For more information on
SDA & ICADD: HTML user agents. It includes the
    graphic characters of Latin Alphabet No. 1, or simply Latin-1.
    Latin-1 comprises 191 graphic characters, including the
    alphabets of most Western European languages.

        NOTE - ISO 12083:1993, Annex A.8, Facilities for Braille,
          large print Use the non-breaking space and computer voice
        - ICADD ListServ
          <ICADD%ASUACAD.BITNET@ARIZVM1.ccit.arizona.edu>
        - Usenet news group bit.listserv.easi
        - Recording soft hyphen
        indicator characters is discouraged because support for
        them is not widely deployed.

        NOTE - To support non-western writing systems, a larger
        character repertoire will be specified in a future
        version of HTML. The document character set will be
        [ISO-10646], or some subset that agrees with
        [ISO-10646]; in particular, all numeric character
        references must use code positions assigned by
        [ISO-10646].

    In SGML applications, the Blind, +1 800 221 4792
-->

<!ENTITY % SDAFORM  "SDAFORM  CDATA  #FIXED"
          -- one use of control characters is limited
    in order to one mapping        -->
<!ENTITY % SDARULE  "SDARULE  CDATA  #FIXED"
          -- context-sensitive mapping -->
<!ENTITY % SDAPREF  "SDAPREF  CDATA  #FIXED"
          -- generated text prefix     -->
<!ENTITY % SDASUFF  "SDASUFF  CDATA  #FIXED"
          -- generated text suffix     -->
<!ENTITY % SDASUSP  "SDASUSP  NAME   #FIXED"
          -- 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"
        >
<!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 maximize the chance 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> successful interchange over
    heterogeneous networks and operating systems. In the HTML
    document character set only three control characters are
    allowed: Horizontal Tab, Carriage Return, and Line break      -->


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

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

<!ENTITY % linkName "CDATA">

<!ENTITY % linkType "NAME"
        -- Feed (code
    positions 9, 13, and 10).

    The HTML DTD references the Added Latin 1 entity set, to allow
    mnemonic representation of selected Latin 1 characters using
    only the widely supported ASCII character repertoire. For
    example:

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

    See 9.7.2, "ISO Latin 1 Character Entity Set" for a table of these will be specified at the
    ``Added Latin 1'' entities, and 13, "The HTML Coded Character
    Set" for a later date -->

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

<![ %HTML.Recommended [
        <!ENTITY % A.content   "(%text)*"
        -- <H1><a name="xxx">Heading</a></H1>
                is preferred to
           <a name="xxx"><H1>Heading</H1></a>
        -->
]]>

<!ENTITY % A.content   "(%heading|%text)*">

<!ELEMENT A     - table of the code positions of [ISO 8859-1] and the
    control characters in the HTML document character set.



Berners-Lee, Connolly                                          [Page 33]

INTERNET-DRAFT      Hypertext Markup Language - %A.content -(A)>
<!ATTLIST 2.0        June 16, 1995

7. Hyperlinks

    In addition to general purpose elements such as paragraphs and
    lists, HTML documents can express hyperlinks. A
        HREF %URI #IMPLIED
        NAME %linkName #IMPLIED
        %linkExtraAttributes;
        %SDAPREF; "<Anchor: #AttList>"
        >
<!-- <A>                Anchor; source/destination of link      -->
<!-- <A NAME="...">     Name hyperlink is a
    relationship between two anchors, called the head and the tail
    of this the hyperlink[DEXTER]. An anchor                     -->
<!-- <A HREF="...">     Address is a resource such as an
    HTML document, or some fragment of, i.e. view on or portion of a
    resource. Typically, the user activates a link destination             -->
<!-- <A URN="...">      Permanent address of destination        -->
<!-- <A REL=...>        Relationship to destination             -->
<!-- <A REV=...>        Relationship by indicating the
    tail of destination to this     -->
<!-- <A TITLE="...">    Title the link; the head of destination (advisory)         -->
<!-- <A METHODS="...">  Operations on destination (advisory)    -->


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

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

<!-- <IMG>              Image; icon, glyph the link is presented as a result.

    Anchors are addressed by Uniform Resource Identifiers (URI).
    URIs either refer directly to an anchor in absolute form for
    example as in [URL], or illustration      -->
<!-- <IMG SRC="...">    Address of image object                 -->
<!-- <IMG ALT="...">    Textual alternative                     -->
<!-- <IMG ALIGN=...>    Position they refer to an anchor relative to text               -->
<!-- <IMG ISMAP> a
    base URI which is absolute, as in [RELURL].

    Each pixel can be of the following markup constructs indicates the tail
    anchor of a link                -->

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

<!ELEMENT P     - O (%text)*>
<!ATTLIST P
        %SDAFORM; "Para"
        >

<!-- <P>        Paragraph       -->


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

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

<!-- <HR>       Horizontal rule -->

<!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 -->
<!-- <H2>       Heading, level 2 -->
<!-- <H3>       Heading, level 3 -->
<!-- <H4>       Heading, level 4 -->
<!-- <H5>       Heading, level 5 -->
<!-- <H6>       Heading, level 6 -->


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

<![ %HTML.Forms [
        <!ENTITY % block.forms "BLOCKQUOTE | FORM | ISINDEX">
]]>

<!ENTITY % block.forms "BLOCKQUOTE">

<![ %HTML.Deprecated [
        <!ENTITY % preformatted "PRE | XMP | LISTING">
]]>

<!ENTITY % preformatted "PRE">

<!ENTITY % block "P | %list | DL
        | %preformatted
        | %block.forms">

<!ENTITY % flow "(%text|%block)*">

<!ENTITY % pre.content "#PCDATA | A | HR | BR">
<!ELEMENT PRE - - (%pre.content)*>
<!ATTLIST PRE
        WIDTH NUMBER #implied
        %SDAFORM; "Lit"
        >

<!-- <PRE>              Preformatted text               -->
<!-- <PRE WIDTH=...>    Maximum characters per line     -->

<![ %HTML.Deprecated [

<!ENTITY % literal "CDATA"
        -- historical, non-conforming parsing mode where hyperlink or set of hyperlinks:

        * <A> elements with HREF present.

        * <LINK> elements.

        * <IMG> elements.

        * <INPUT> elements with the only markup signal SRC attribute present.

        * <ISINDEX> elements.

        * <FORM> elements with `METHOD=GET'.


7.1. Accessing Resources

    To access the head anchor of a hyperlink, the user agent
    determines its URI from the URI given in the tail anchor, using
    the base URI of the document containing the tail anchor if
    necessary. Any fragment identifier is discarded, and the end tag result
    is used to access a resource, for example as in full
        -->

<!ELEMENT (XMP|LISTING) - [URL].

    For example, if a document identified as `http://host/x/y.html'
    contains:

    <img src="../icons/abc.gif">

    then the user agent must use the URI `http://host/icons/abc.gif'
    to access the resource linked from the <IMG> element.


7.2. Activation of Hyperlinks

    An HTML user agent allows the user to navigate the content of
    the document and request activation of <A> element hyperlinks. A
    request to activate a link is essentially a request to process
    the resource indicated by the head anchor of the link, for

Berners-Lee, Connolly                                          [Page 34]

INTERNET-DRAFT      Hypertext Markup Language -  %literal>
<!ATTLIST XMP
        %SDAFORM; "Lit"
        %SDAPREF; "Example:&#RE;"
        >
<!ATTLIST LISTING
        %SDAFORM; "Lit"
        %SDAPREF; "Listing:&#RE;"
        >

<!-- <XMP>              Example section         -->
<!-- <LISTING>          Computer listing        -->

<!ELEMENT PLAINTEXT - O %literal>
<!-- <PLAINTEXT>        Plain text passage      -->

<!ATTLIST PLAINTEXT
        %SDAFORM; "Lit"
        >
]]>


<!--========== 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, 2.0        June 16, 1995

    example to display the indicated HTML document. HTML user agents
    should also allow activation of <LINK> element hyperlinks.

    The base URI for navigating the head anchor may be different
    from the URI used to access it. For example, it may be replaced
    by a <BASE> tag in the destination document or glossary    -->
<!-- <DL COMPACT>       Compact style list              -->
<!-- <DT>               Term by an HTTP
    redirection transaction.


7.3. Simultaneous Presentation of Image Resources

    An HTML user agent may activate hyperlinks indicated by <IMG>
    and <INPUT> elements concurrently with processing the document;
    that is, image hyperlinks may be processed without explicit
    request by the user. Image resources should be embedded in definition list         -->
<!-- <DD>               Definition the
    presentation at the point of term              -->

<!ELEMENT (OL|UL) - -  (LI)+>
<!ATTLIST OL
        COMPACT (COMPACT) #IMPLIED
        %SDAFORM; "List"
        >
<!ATTLIST UL
        COMPACT (COMPACT) #IMPLIED
        %SDAFORM; "List"
        >
<!-- <UL>               Unordered list                  -->
<!-- <UL COMPACT>       Compact list style              -->
<!-- <OL>               Ordered, the tail anchor, that is the <IMG>
    or numbered list       -->
<!-- <OL COMPACT>       Compact list style              -->


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

<!-- <DIR>              Directory list                  -->
<!-- <DIR COMPACT>      Compact list style              -->
<!-- <MENU>             Menu list                       -->
<!-- <MENU COMPACT>     Compact list <INPUT> element.

    <LINK> hyperlinks may also be processed without explicit user
    request; for example, style              -->

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

<!-- <LI>               List item                       -->

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

<![ %HTML.Recommended [
        <!ENTITY % body.content "(%heading|%block|HR|ADDRESS|IMG)*"
        -- <h1>Heading</h1>
           <p>Text ...
                is preferred to
           <h1>Heading</h1>
           Text ...
        -->
]]>

<!ENTITY % body.content "(%heading | %text | %block |
                                 HR | ADDRESS)*">

<!ELEMENT BODY O O  %body.content>

<!-- <BODY>     Document body   -->

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

<!-- <BLOCKQUOTE>       Quoted passage  -->

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

<!-- <ADDRESS>  Address, signature, or byline   -->


<!--======= 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 sheet resources may be processed
    before or data-entry form     -->
<!-- <FORM ACTION="...">        Address for completed form      -->
<!-- <FORM METHOD=...>          Method during the processing of submitting form       -->
<!-- <FORM ENCTYPE="...">       Representation the document.


7.4. Fragment Identifiers

    Any characters following a `#' character in a URI constitute a
    fragment identifier. As a degenerate case, a URI of the form data     -->

<!ENTITY % InputType "(TEXT | PASSWORD | CHECKBOX |
                        RADIO | SUBMIT | RESET |
                        IMAGE | HIDDEN )">
<!ELEMENT INPUT - O EMPTY>
<!ATTLIST INPUT
        TYPE %InputType TEXT
        NAME CDATA #IMPLIED
        VALUE CDATA #IMPLIED
        SRC %URI #IMPLIED
        CHECKED (CHECKED) #IMPLIED
        SIZE CDATA #IMPLIED
        MAXLENGTH NUMBER #IMPLIED
        ALIGN (top|middle|bottom) #IMPLIED
        %SDAPREF; "Input: "
        >

<!-- <INPUT>                    Form input datum                -->
<!-- <INPUT TYPE=...>           Type of input interaction       -->
<!-- <INPUT NAME=...>           Name of form datum              -->
<!-- <INPUT VALUE="...">        Default/initial/selected value  -->
<!-- <INPUT SRC="...">          Address of image                -->
<!-- <INPUT CHECKED>            Initial state 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
        %SDAFORM; "List"
        %SDAPREF;
        "<LHead>Select #AttVal(Multiple)</LHead>"
        >

<!-- <SELECT>                   Selection
    `#fragment' refers to an anchor in the same document.

    The meaning of option(s)          -->
<!-- <SELECT NAME=...>          Name fragment identifiers depends on the media type of form datum              -->
<!-- <SELECT SIZE=...>          Options displayed at
    the resource containing the head anchor. For `text/html'
    resources, it refers to the <A> element with 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>                   A selection option              -->
<!-- <OPTION SELECTED>          Initial state                   -->
<!-- <OPTION VALUE="...">       Form datum NAME attribute
    whose value is the same as the fragment identifier. The matching
    is case sensitive. The document should have exactly one such
    element. The user agent should indicate the anchor element, for 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 of form datum              -->
<!-- <TEXTAREA ROWS=...>        Height of area                  -->
<!-- <TEXTAREA COLS=...>        Width 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)">

<!ELEMENT HEAD O O  (%head.content)>

<!-- <HEAD>     Document head   -->

<!ELEMENT TITLE - -  (#PCDATA)*>
<!ATTLIST TITLE
        %SDAFORM; "Ti"    >

<!-- <TITLE>    Title of document -->

<!ELEMENT LINK - O EMPTY>
<!ATTLIST LINK
        HREF %URI #REQUIRED
        %linkExtraAttributes;
        %SDAPREF; "Linked to : #AttVal (TITLE) (URN) (HREF)>"    >

<!-- <LINK>             Link from this document                 -->
<!-- <LINK HREF="...">  Address of link destination             -->
<!-- <LINK URN="...">   Lasting name of destination             -->
<!-- <LINK REL=...>     Relationship to destination             -->
<!-- <LINK REV=...>     Relationship of destination
    example by scrolling to this     -->
<!-- <LINK TITLE="..."> Title of destination (advisory)         -->
<!-- <LINK METHODS="..."> Operations allowed (advisory)         -->

<!ELEMENT ISINDEX - O EMPTY>
<!ATTLIST ISINDEX
        %SDAPREF;
   "<Para>[Document is indexed/searchable.]</Para>">

<!-- <ISINDEX>          Document is and/or highlighting the phrase.

    For example, if a user agent was processing a searchable index          -->

<!ELEMENT BASE - O EMPTY>
<!ATTLIST BASE
        HREF %URI; #REQUIRED     >

<!-- <BASE>             Base context document                   -->
<!-- <BASE HREF="...">  Address
    identified as `http://host/x/y.html' and the user indicated the
    following anchor:

    <p> See: <a href="app1.html#bananas">appendix 1</a>
    for this document               -->

<!ELEMENT NEXTID - O EMPTY>
<!ATTLIST NEXTID
        N %linkName #REQUIRED     >

<!-- <NEXTID>           Next ID to use for link name            -->
<!-- <NEXTID N=...>     Next ID to use for link name            -->

<!ELEMENT META - O EMPTY>
<!ATTLIST META
        HTTP-EQUIV  NAME    #IMPLIED
        NAME        NAME    #IMPLIED
        CONTENT     CDATA   #REQUIRED    >

<!-- <META>                     Generic Metainformation         -->
<!-- <META HTTP-EQUIV=...>      HTTP response header name       -->
<!-- <META NAME=...>            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   -->


8.2. SGML Declaration for HTML 

     This more detail on bananas.

    then the user agent URI must access the resource
    `http://host/x/app1.html'. Assuming the resource is represented
    using the SGML Declaration for HyperText Markup Language
     (HTML) as used `text/html' media type, the user agent must locate the
    anchor named `bananas' and begin navigation there.


7.5. Queries and Indexes

    The <ISINDEX> element represents a set of hyperlinks. The user
    can choose from the set by providing keywords to the World Wide Web (WWW) application:

<!SGML  "ISO 8879:1986"
--
        SGML Declaration for HyperText user agent.

Berners-Lee, Connolly                                          [Page 35]

INTERNET-DRAFT      Hypertext Markup Language (HTML).

--

CHARSET
         BASESET  "ISO 646:1983//CHARSET
                   International Reference Version
                   (IRV)//ESC 2/5 4/0"
         DESCSET  0   9   UNUSED
                  9   2   9
                  11  2   UNUSED
                  13  1   13
                  14  18  UNUSED
                  32  95  32
                  127 1   UNUSED
     BASESET   "ISO Registration Number 100//CHARSET
                ECMA-94 Right Part of
                Latin Alphabet Nr. 1//ESC 2/13 4/1"

         DESCSET  128  32   UNUSED
                  160  96    32

CAPACITY        SGMLREF
                TOTALCAP        150000
                GRPCAP          150000
                ENTCAP          150000
  
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
                   International Reference Version
                   (IRV)//ESC 2/5 4/0"
         DESCSET  0 128 0
         FUNCTION
                  RE          13
                  RS          10
                  SPACE       32
                  TAB SEPCHAR  9
        

         NAMING   LCNMSTRT ""
                  UCNMSTRT ""
                  LCNMCHAR ".-"
                  UCNMCHAR ".-"
                  NAMECASE GENERAL YES
                           ENTITY  NO
         DELIM    GENERAL  SGMLREF
                  SHORTREF SGMLREF
         NAMES    SGMLREF
         QUANTITY SGMLREF
                  ATTSPLEN 2100
                  LITLEN   1024
                  NAMELEN  72    -- somewhat arbitrary; taken from
                                internet line length conventions --
                  PILEN    1024
                  TAGLEN   2100
                  GRPGTCNT 150
                  GRPCNT   64                   

FEATURES
  MINIMIZE
    DATATAG  NO
    OMITTAG  YES
    RANK     NO
    SHORTTAG YES
  LINK
    SIMPLE   NO
    IMPLICIT NO
    EXPLICIT NO
  OTHER
    CONCUR   NO
    SUBDOC   NO
    FORMAL   YES
  APPINFO    "SDA"  -- conforming SGML Document Access application
                    --
>
<!-- 
        $Id: html.decl,v 1.15 1995/05/06 01:44:47 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
 -->


8.3. Sample SGML Open Entity Catalog for HTML - 2.0        June 16, 1995

    The SGML standard describes an ``entity manager'' as user agent computes the
     portion or component of an SGML system that maps SGML
     entities into head URI by appending `?' and the actual storage model (e.g.,
    keywords to the file
     system). base URI. The standard itself does not define keywords are escaped according to
    [URL] and joined by `+'. For example, if a particular
     mapping methodology or notation.

     To assist document contains:

    <BASE HREF="http://host/index">
    <ISINDEX>

    and the interoperability among various SGML tools user provides the keywords `apple' and
     systems, `berry', then the SGML Open consortium has passed a technical
     resolution that defines a format
    user agent must access the resource
    `http://host/index?apple+berry'.

    <FORM> elements with `METHOD=GET' also represent sets of
    hyperlinks. See 8.2.2, "Query Forms: METHOD=GET" for details.


7.6. Image Maps

    If the ISMAP attribute is present on an application-
     independent entity catalog that maps external identifiers
     and/or entity names to file names.

     Each entry in <IMG> element, the catalog associates <IMG>
    element must be contained in an <A> element with an HREF
    present. This construct represents a storage object
     identifier (such as set of hyperlinks. The user
    can choose from the set by choosing a file name) with information about pixel of the
     external entity that appears in image. The
    user agent computes the SGML document. In
     addition head URI by appending `?' and the x and
    y coordinates of the pixel to entries that associate public identifiers, a
     catalog entry can associate an entity name with a storage
     object indentifier. the URI given in the <A> element.
    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 --
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  "-//IETF//DTD HTML 2.0 Level 2//EN"     html.dtd

        -- Ways to refer to Level 1: most general to most specific --
PUBLIC  "-//IETF//DTD HTML Level 1//EN"         html-1.dtd
PUBLIC  "-//IETF//DTD if a document contains:

    <!DOCTYPE HTML 2.0 Level 1//EN"     html-1.dtd

        -- Ways to refer to Level 0: most general to most specific -- PUBLIC "-//IETF//DTD HTML Level 0//EN"         html-0.dtd
PUBLIC  "-//IETF//DTD HTML 2.0 Level 0//EN"     html-0.dtd


        -- Ways to refer to Strict Level 2: most general to most specific --
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

        -- Ways to refer to Strict Level 1: most general to most specific --
PUBLIC  "-//IETF//DTD HTML Strict Level 1//EN"          html-1s.dtd
PUBLIC  "-//IETF//DTD HTML 2.0 Strict Level 1//EN"      html-1s.dtd

        -- Ways to refer to Strict Level 0: most general to most specific --
PUBLIC  "-//IETF//DTD HTML Strict Level 0//EN"          html-0s.dtd
PUBLIC  "-//IETF//DTD HTML 2.0 Strict Level 0//EN"      html-0s.dtd

        -- ISO latin 1 entity set for HTML -- 
PUBLIC  "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML"       ISOlat1.sgml


8.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 2.0//EN">
    <head><title>ImageMap Example</title>
    <BASE HREF="http://host/index"></head>
    <body>
    <p> Choose any of these icons:<br>
    <a href="/cgi-bin/imagemap"><img ismap src="icons.gif"></a>

    and the character
     set available to user chooses the writer.


8.4.1. Numeric and Special Graphic Entity Set 

     The following table lists each of upper-leftmost pixel, the characters included
     from chosen
    hyperlink is the Numeric and Special Graphic entity set, along one with
     its name, syntax the URI
    `http://host/cgi-bin/imagemap?0,0'.


8. Forms

    A form is a template for use, a form data set and description. This list is
     derived from `ISO Standard 8879:1986//ENTITIES Numeric an associated
    method and
     Special Graphic//EN'. However, HTML does not include for the
     entire entity action URI. A form data set -- only the entities listed below are
     included.

     GLYPH is a sequence of
    name/value pair fields. The names are specified on the NAME    SYNTAX  DESCRIPTION
     <       lt      &lt;    Less than sign
     >       gt      &gt;    Greater than sign
     &       amp     &amp;   Ampersand
     "       quot    &quot;  Double quote sign


8.4.2. ISO Latin 1 Character Entity Set
    attributes of form input elements, and the values are given
    initial values by various forms of markup and edited by the
    user. The following public text lists each resulting form data set is used to access an
    information service as a function of the characters
     specified action and method.

    Forms elements can be mixed in the Added Latin 1 entity set, along with its
     name, syntax for use, and description. document structuring
    elements. For example, a <PRE> element may contain a <FORM>
    element, or a <FORM> element may contain lists which contain
    <INPUT> elements. This list gives considerable flexibility in
    designing the layout of forms.

    Form processing is derived
     from ISO Standard 8879:1986//ENTITIES Added Latin 1//EN.
     HTML includes a level 2 feature.

Berners-Lee, Connolly                                          [Page 36]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995



8.1. Form Elements


8.1.1. Form: FORM

    The <FORM> element contains a sequence of input elements, along
    with document structuring elements. The attributes are:

    ACTION
            specifies the entire entity set.

<!-- (C) International Organization action URI for Standardization 1986
     Permission to copy in any the form. The action URI of
            a form defaults to the base URI of the document (see 7,
            "Hyperlinks").

    METHOD
            selects a method of accessing the action URI. The set of
            applicable methods is granted for use with
     conforming SGML systems and applications as defined in
     ISO 8879, provided this notice is included in all copies.
-->
<!-- Character entity set. Typical invocation:
     <!ENTITY % ISOlat1 PUBLIC
       "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML">
     %ISOlat1;
-->
<!--    Modified a function of the scheme of the
            action URI of the form. See 8.2.2, "Query Forms:
            METHOD=GET" and 8.2.3, "Forms with Side-Effects:
            METHOD=POST".

    ENCTYPE
            specifies the media type used to encode the name/value
            pairs for use transport, in HTML
        $Id: ISOlat1.sgml,v 1.2 1994/11/30 23:45:12 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;" -- capital A, ring -->
<!ENTITY Atilde CDATA "&#195;" -- capital A, tilde -->
<!ENTITY Auml   CDATA "&#196;" -- capital A, dieresis or umlaut 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 accent -->
<!ENTITY Egrave CDATA "&#200;" -- capital E, grave accent -->
<!ENTITY Euml   CDATA "&#203;" -- capital E, dieresis or umlaut mark -->
<!ENTITY Iacute CDATA "&#205;" -- capital I, acute accent -->
<!ENTITY Icirc  CDATA "&#206;" -- capital I, circumflex accent -->
<!ENTITY Igrave CDATA "&#204;" -- capital I, 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, acute accent case the protocol does not
            itself impose a format. See 8.2.1, "The form-urlencoded
            Media Type".


8.1.2. Input Field: INPUT

    The <INPUT> element represents a field for user input. The TYPE
    attribute discriminates between several variations of fields.

    The <INPUT> element has a number of attributes. The set of
    applicable attributes depends on the value of the TYPE
    attribute.


8.1.2.1. Text Field: INPUT TYPE=TEXT

    The default vaule of the TYPE attribute is `TEXT', indicating a
    single line text entry fields. (Use the <TEXTAREA> element for
    multi-line text fields.)

    Required attributes are:

    NAME
            name for the form field corresponding to this element.

    The optional attriubtes are:

    MAXLENGTH
            constrains the number of characters that can be entered

Berners-Lee, Connolly                                          [Page 37]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

            into a text input field. If the value of MAXLENGTH is
            greater the the value of the SIZE attribute, the field
            should scroll appropriately. The default number of
            characters is unlimited.

    SIZE
            specifies the amount of display space allocated to this
            input field according to its type. The default depends
            on the user agent.

    VALUE
            The initial value of the field.

    For example:

    <p>Street Address: <input name=street><br>
    Postal City code: <input name=city size=16 maxlength=16><br>
    Zip Code: <input name=zip size=10 maxlength=10 value="99999-9999"><br>


8.1.2.2. Password Field: INPUT TYPE=PASSWORD

    An <INPUT> element with `TYPE=PASSWORD' is a text field as
    above, except that the value is obscured as it is entered. (see
    also: 10, "Security Considerations").

    For example:

    <p>Name: <input name=login> Password: <input type=password name=passwd>


8.1.2.3. Check Box: INPUT TYPE=CHECKBOX

    An <INPUT> element with `TYPE=CHECKBOX' represents a boolean
    choice. A set of such elements with the same name represents an
    n-of-many choice field. Required attributes are:

    NAME
            symbolic name for the form field corresponding to this
            element or group of elements.

    VALUE
            The portion of the value of the field contributed by
            this element.

    Optional attributes are:

    CHECKED
            indicates that the initial state is on.

    For example:




Berners-Lee, Connolly                                          [Page 38]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    <p>What flavors do you like?
    <input type=checkbox name=flavor value=vanilla>Vanilla<br>
    <input type=checkbox name=flavor value=strawberry>Strawberry<br>
    <input type=checkbox name=flavor value=chocolate checked>Chocolate<br>


8.1.2.4. Radio Button: INPUT TYPE=RADIO

    An <INPUT> element with `TYPE=RADIO' represents a boolean
    choice. A set of such elements with the same name represents a
    1-of-many choice field. The NAME and VALUE attributes are
    required as for check boxes. Optional attributes are:

    CHECKED
            indicates that the initial state is on.

    At all times, exactly one of the radio buttons in a set is
    checked. If none of the <INPUT> elements of a set of radio
    buttons specifies `CHECKED', then the user agent must check the
    first radio button of the set initially.

    For example:

    <p>Which is your favorite?
    <input type=radio name=flavor value=vanilla>Vanilla<br>
    <input type=radio name=flavor value=strawberry>Strawberry<br>
    <input type=radio name=flavor value=chocolate>Chocolate<br>


8.1.2.5. Image Pixel: INPUT TYPE=IMAGE

    An <INPUT> element with `TYPE=IMAGE' specifies an image resource
    to display, and allows input of two form fields: the x and y
    coordinate of a pixel chosen from the image. The names of the
    fields are the name of the field with `.x' and `.y' appended.
    `TYPE=IMAGE' implies `TYPE=SUBMIT' processing; that is, when a
    pixel is chosen, the form as a whole is submitted.

    The NAME attribute is required as for other input fields. The
    SRC attribute is required and the ALIGN is optional as for the
    <IMG> element (see 5.10, "Image: IMG").

    For example:

    <p>Choose a point on the map:
    <input type=image name=point src="map.gif">


8.1.2.6. Hidden Field: INPUT TYPE=HIDDEN

    An <INPUT> element with `TYPE=HIDDEN' represents a hidden
    field.The user does not interact with this field; instead, the
    VALUE attribute specifies the value of the field. The NAME and
    VALUE attributes are required.

Berners-Lee, Connolly                                          [Page 39]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995


    For example:

    <input type=hidden name=context value="l2k3j4l2k3j4l2k3j4lk23">


8.1.2.7. Submit Button: INPUT TYPE=SUBMIT

    An <INPUT> element with `TYPE=SUBMIT' represents an input
    option, typically a button, that instructs the user agent to
    submit the form. Optional attributes are:

    NAME
            indicates that this element contributes a form field
            whose value is given by the VALUE attribute. If the NAME
            attribute is not present, this element does not
            contribute a form field.

    VALUE
            indicates a label for the input (button).

    You may submit this request internally:
    <input type=submit name=recipient value=internal><br>
    or to the external world:
    <input type=submit name=recipient value=world>


8.1.2.8. Reset Button: INPUT TYPE=RESET

    An <INPUT> element with `TYPE=RESET' represents an input option,
    typically a button, that instructs the user agent to reset the
    form's fields to their initial states. The VALUE attribute, if
    present, indicates a label for the input (button).

    When you are finished, you may submit this request:
    <input type=submit><br>
    You may clear the form and start over at any time: <input type=reset>


8.1.3. Selection: SELECT

    The <SELECT> element constrains the form field to an enumerated
    list of values. The values are given in <OPTION> elements.
    Attributes are:

    MULTIPLE
            indicates that more than one option may be included in
            the value.

    NAME
            specifies the name of the form field.

    SIZE
            specifies the number of visible items. Select fields of

Berners-Lee, Connolly                                          [Page 40]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

            size one are typically pop-down menus, whereas select
            fields with size greater than one are typically lists.

    For example:

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

    The initial state has the first option selected, unless a
    SELECTED attribute is present on any of the <OPTION> elements.


8.1.3.1. Option: OPTION

    The Option element can only occur within a Select element. It
    represents one choice, and has the following attributes:

    SELECTED
            Indicates that this option is initially selected.

    VALUE
            indicates the value to be returned if this option is
            chosen. The field value defaults to the content of the
            <OPTION> element.

    The content of the <OPTION> element is presented to the user to
    represent the option. It is used as a returned value if the
    VALUE attribute is not present.


8.1.4. Text Area: TEXTAREA

    The <TEXTAREA> element represents a multi-line text field.
    Attributes are:

    COLS
            the number of visible columns to display for the text
            area, in characters.

    NAME
            Specifies the name of the form field.

    ROWS
            The number of visible rows to display for the text area,
            in characters.

    For example:




Berners-Lee, Connolly                                          [Page 41]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

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

    The content of the <TEXTAREA> element is the field's initial
    value.

    Typically, the ROWS and COLS attributes determine the visible
    dimension of the field in characters. The field is typically
    rendered in a fixed-width font. HTML user agents should allow
    text to extend beyond these limits by scrolling as needed.


8.2. Form Submission

    An HTML user agent begins processing a form by presenting the
    document with the fields in their initial state. The user is
    allowed to modify the fields, constrained by the field type etc.
    When the user indicates that the form should be submitted (using
    a submit button or image input), the form data set is processed
    according to its method, action URI and enctype.

    When there is only one single-line text input field in a form,
    the user agent should accept Enter in that field as a request to
    submit the form.


8.2.1. The form-urlencoded Media Type

    The default encoding for all forms is
    `application/x-www-form-urlencoded'. A form data set is
    represented in this media type as follows:

        1. The form field names and values are escaped: space
        characters are replaced by `+', and then reserved characters
        are escaped as per [URL]; that is, non-alphanumeric
        characters are replaced by `%HH', a percent sign and two
        hexadecimal digits representing the ASCII code of the
        character. Line breaks, as in multi-line text field values,
        are represented as CR LF pairs, i.e. `%0D%0A'.

        2. The fields are listed in the order they appear in the
        document with the name separated from the value by `=' and
        the pairs separated from each other by `&'. Fields with null
        values may be omitted. In particular, unselected radio
        buttons and checkboxes should not appear in the encoded
        data, but hidden fields with VALUE attributes present
        should.

            NOTE - The URI from a query form submission can be
            used in a normal anchor style hyperlink.
            Unfortunately, the use of the `&' character to

Berners-Lee, Connolly                                          [Page 42]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

            separate form fields interacts with its use in SGML
            attribute values as an entity reference delimiter.
            For example, the URI `http://host/?x=1&y=2' must be
            written `<a href="http://host/?x=1&#38;y=2"' or `<a
            href="http://host/?x=1&#amp;y=2">'.

            HTTP server implementors, and in particular, CGI
            implementors are encouraged to support the use of
            `;' in place of `&' to save users the trouble of
            escaping `&' characters this way.


8.2.2. Query Forms: METHOD=GET

    If the processing of a form is idempotent (i.e. it has no
    lasting observable effect on the state of the world), then the
    form method should be `GET'. Many database searches have no
    visible side-effects and make ideal applications of query forms.

    To process a form whose action URL is an HTTP URL and whose
    method is `GET', the user agent starts with the action URI and
    appends a `?' and the form data set, in
    `application/x-www-form-urlencoded' format as above. The user
    agent then traverses the link to this URI just as if it were an
    anchor (see 7.2, "Activation of Hyperlinks").

        NOTE - The URL encoding may result in very long URIs,
        which cause some historical HTTP server implementations
        to exhibit defective behavior. As a result, some HTML
        forms are written using `METHOD=POST' even though the
        form submission has no side-effects.


8.2.3. Forms with Side-Effects: METHOD=POST

    If the service associated with the processing of a form has side
    effects (for example, modification of a database or subscription
    to a service), the method should be `POST'.

    To process a form whose action URL is an HTTP URL and whose
    method is `POST', the user agent conducts an HTTP POST
    transaction using the action URI, and a message body of type
    `application/x-www-form-urlencoded' format as above. The user
    agent should display the response from the HTTP POST interaction
    just as it would display the response from an HTTP GET above.


8.2.4. Example Form Submission: Questionnaire Form

    Consider the following document:

    <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    <title>Sample of HTML Form Submission</title>
    <H1>Sample Questionnaire</H1>

Berners-Lee, Connolly                                          [Page 43]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

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

    The initial state of the form data set is:

    name
            ``''

    gender
            ``male''

    family
            ``''

    other
            ``''

    nickname
            ``''

    Note that the radio input has an initial value, while the
    checkbox has none.

    The user might edit the fields and request that the form be
    submitted. At that point, suppose the values are:

    name
            ``John Doe''

    gender
            ``male''

    family
            ``5''

    city
            ``kent,miami''

    other
            ``abc\ndef''

Berners-Lee, Connolly                                          [Page 44]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995


    nickname
            ``J&D''

    The user agent then conducts an HTTP POST transaction using the
    URI `http://www.w3.org/sample'. The message body would be
    (ignore the line break):

    name=John+Doe&gender=male&family=5&city=kent%2Cmiami&
    other=abc%0D%0Adef&nickname=J%26D


9. HTML Public Text


9.1. HTML DTD

    This is the Document Type Definition for the HyperText Markup
    Language, level 2.

<!--    html.dtd

        Document Type Definition for the HyperText Markup Language
                 (HTML DTD)

        $Id: html.dtd,v 1.28 1995/06/16 18:54:22 connolly Exp $

        Author: Daniel W. Connolly <connolly@w3.org>
        See Also: html.decl, html-1.dtd
          http://www.w3.org/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 for
           compatibility with widespread usage, but they may
           compromise the structural integrity of a document.
           This feature test entity enables a more prescriptive
           document type definition that eliminates
           those features.

Berners-Lee, Connolly                                          [Page 45]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

        -->

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

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

<!ENTITY % HTML.Highlighting "INCLUDE"
        -- Use this feature test entity to validate that a
           document uses no highlighting tags, which may be
           ignored on minimal implementations.
        -->

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

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

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

<!ENTITY % HTTP-Method "GET | POST"
        -- as per HTTP specification, in progress
        -->

<!ENTITY % URI "CDATA"
        -- The term URI means a CDATA attribute
           whose value is a Uniform Resource Identifier,
           as defined by 
        "Universal Resource Identifiers" by Tim Berners-Lee
        aka RFC 1630

        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 bounded length.

        -->


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


Berners-Lee, Connolly                                          [Page 46]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

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

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


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

<!ENTITY % ISOlat1 PUBLIC
  "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML">
%ISOlat1;

<!ENTITY amp CDATA "&#38;"     -- ampersand          -->
<!ENTITY gt CDATA "&#62;"      -- greater than       -->
<!ENTITY lt CDATA "&#60;"      -- less than          -->
<!ENTITY quot CDATA "&#34;"    -- double quote       -->


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

<!-- HTML 2.0 contains SGML Document Access (SDA) fixed attributes
in support of easy transformation to the International Committee
for Accessible Document Design (ICADD) DTD
         "-//EC-USA-CDA/ICADD//DTD ICADD22//EN".
ICADD applications are designed to support usable access to
structured information by print-impaired individuals through
Braille, large print and voice synthesis.  For more information on
SDA & 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"
          -- generated text suffix     -->
<!ENTITY % SDASUSP  "SDASUSP  NAME   #FIXED"
          -- suspend transform process -->


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

<![ %HTML.Highlighting [

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

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

Berners-Lee, Connolly                                          [Page 47]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995


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

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

<!ENTITY % linkType "NAME">

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

<![ %HTML.Recommended [
        <!ENTITY % A.content   "(%text)*"

Berners-Lee, Connolly                                          [Page 48]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

        -- <H1><a name="xxx">Heading</a></H1>
                is preferred to
           <a name="xxx"><H1>Heading</H1></a>
        -->
]]>

<!ENTITY % A.content   "(%heading|%text)*">

<!ELEMENT A     - - %A.content -(A)>
<!ATTLIST A
        HREF %URI #IMPLIED
        NAME CDATA #IMPLIED
        %linkExtraAttributes;
        %SDAPREF; "<Anchor: #AttList>"
        >
<!-- <A>                Anchor; source/destination of link      -->
<!-- <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     -->
<!-- <A TITLE="...">    Title of destination (advisory)         -->
<!-- <A METHODS="...">  Operations on destination (advisory)    -->


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

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

<!-- <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                -->

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

<!ELEMENT P     - O (%text)*>
<!ATTLIST P
        %SDAFORM; "Para"
        >

<!-- <P>        Paragraph       -->


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


Berners-Lee, Connolly                                          [Page 49]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

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

<!-- <HR>       Horizontal rule -->

<!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 -->
<!-- <H2>       Heading, level 2 -->
<!-- <H3>       Heading, level 3 -->
<!-- <H4>       Heading, level 4 -->
<!-- <H5>       Heading, level 5 -->
<!-- <H6>       Heading, level 6 -->


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

<![ %HTML.Forms [
        <!ENTITY % block.forms "BLOCKQUOTE | FORM | ISINDEX">
]]>

<!ENTITY % block.forms "BLOCKQUOTE">

<![ %HTML.Deprecated [
        <!ENTITY % preformatted "PRE | XMP | LISTING">
]]>

<!ENTITY % preformatted "PRE">

<!ENTITY % block "P | %list | DL
        | %preformatted
        | %block.forms">

<!ENTITY % flow "(%text|%block)*">

Berners-Lee, Connolly                                          [Page 50]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995


<!ENTITY % pre.content "#PCDATA | A | HR | BR">
<!ELEMENT PRE - - (%pre.content)*>
<!ATTLIST PRE
        WIDTH NUMBER #implied
        %SDAFORM; "Lit"
        >

<!-- <PRE>              Preformatted text               -->
<!-- <PRE WIDTH=...>    Maximum characters per line     -->

<![ %HTML.Deprecated [

<!ENTITY % literal "CDATA"
        -- historical, non-conforming parsing mode where
           the only markup signal is the end tag
           in full
        -->

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

<!-- <XMP>              Example section         -->
<!-- <LISTING>          Computer listing        -->

<!ELEMENT PLAINTEXT - O %literal>
<!-- <PLAINTEXT>        Plain text passage      -->

<!ATTLIST PLAINTEXT
        %SDAFORM; "Lit"
        >
]]>


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

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

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

Berners-Lee, Connolly                                          [Page 51]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995


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

<!-- <DL>               Definition list, or glossary    -->
<!-- <DL COMPACT>       Compact style list              -->
<!-- <DT>               Term in definition list         -->
<!-- <DD>               Definition of term              -->

<!ELEMENT (OL|UL) - -  (LI)+>
<!ATTLIST OL
        COMPACT (COMPACT) #IMPLIED
        %SDAFORM; "List"
        >
<!ATTLIST UL
        COMPACT (COMPACT) #IMPLIED
        %SDAFORM; "List"
        >
<!-- <UL>               Unordered list                  -->
<!-- <UL COMPACT>       Compact list style              -->
<!-- <OL>               Ordered, or numbered list       -->
<!-- <OL COMPACT>       Compact list style              -->


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

<!-- <DIR>              Directory list                  -->
<!-- <DIR COMPACT>      Compact list style              -->
<!-- <MENU>             Menu list                       -->
<!-- <MENU COMPACT>     Compact list style              -->

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

<!-- <LI>               List item                       -->

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

<![ %HTML.Recommended [
        <!ENTITY % body.content "(%heading|%block|HR|ADDRESS|IMG)*"

Berners-Lee, Connolly                                          [Page 52]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

        -- <h1>Heading</h1>
           <p>Text ...
                is preferred to
           <h1>Heading</h1>
           Text ...
        -->
]]>

<!ENTITY % body.content "(%heading | %text | %block |
                                 HR | ADDRESS)*">

<!ELEMENT BODY O O  %body.content>

<!-- <BODY>     Document body   -->

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

<!-- <BLOCKQUOTE>       Quoted passage  -->

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

<!-- <ADDRESS>  Address, signature, or byline   -->


<!--======= 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     -->
<!-- <FORM ACTION="...">        Address for completed form      -->
<!-- <FORM METHOD=...>          Method of submitting form       -->
<!-- <FORM ENCTYPE="...">       Representation of form data     -->

<!ENTITY % InputType "(TEXT | PASSWORD | CHECKBOX |
                        RADIO | SUBMIT | RESET |
                        IMAGE | HIDDEN )">
<!ELEMENT INPUT - O EMPTY>
<!ATTLIST INPUT

Berners-Lee, Connolly                                          [Page 53]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

        TYPE %InputType TEXT
        NAME CDATA #IMPLIED
        VALUE CDATA #IMPLIED
        SRC %URI #IMPLIED
        CHECKED (CHECKED) #IMPLIED
        SIZE CDATA #IMPLIED
        MAXLENGTH NUMBER #IMPLIED
        ALIGN (top|middle|bottom) #IMPLIED
        %SDAPREF; "Input: "
        >

<!-- <INPUT>                    Form input datum                -->
<!ENTITY Ocirc
<!-- <INPUT TYPE=...>           Type of input interaction       -->
<!-- <INPUT NAME=...>           Name of form datum              -->
<!-- <INPUT VALUE="...">        Default/initial/selected value  -->
<!-- <INPUT SRC="...">          Address of image                -->
<!-- <INPUT CHECKED>            Initial state 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 "&#212;" -- capital O, circumflex accent #REQUIRED
        SIZE NUMBER #IMPLIED
        MULTIPLE (MULTIPLE) #IMPLIED
        %SDAFORM; "List"
        %SDAPREF;
        "<LHead>Select #AttVal(Multiple)</LHead>"
        >

<!-- <SELECT>                   Selection of option(s)          -->
<!ENTITY Ograve
<!-- <SELECT NAME=...>          Name of form datum              -->
<!-- <SELECT SIZE=...>          Options displayed at a time     -->
<!-- <SELECT MULTIPLE>          Multiple selections allowed     -->

<!ELEMENT OPTION - O (#PCDATA)*>
<!ATTLIST OPTION
        SELECTED (SELECTED) #IMPLIED
        VALUE CDATA "&#210;" #IMPLIED
        %SDAFORM; "LItem"
        %SDAPREF;
        "Option: #AttVal(Value) #AttVal(Selected)"
        >

<!-- <OPTION>                   A selection option              -->
<!-- <OPTION SELECTED>          Initial state                   -->
<!-- <OPTION VALUE="...">       Form datum value for this option-->

<!ELEMENT TEXTAREA - - (#PCDATA)* -(INPUT|SELECT|TEXTAREA)>
<!ATTLIST TEXTAREA
        NAME CDATA #REQUIRED
        ROWS NUMBER #REQUIRED
        COLS NUMBER #REQUIRED

Berners-Lee, Connolly                                          [Page 54]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

        %SDAFORM; "Para"
        %SDAPREF; "Input Text -- capital O, grave accent #AttVal(Name): "
        >

<!-- <TEXTAREA>                 An area for text input          -->
<!-- <TEXTAREA NAME=...>        Name of form datum              -->
<!-- <TEXTAREA ROWS=...>        Height of area                  -->
<!-- <TEXTAREA COLS=...>        Width of area                   -->

]]>


<!--======= Document Head ======================-->

<![ %HTML.Recommended [
        <!ENTITY Oslash CDATA "&#216;" -- capital O, slash --> % head.extra "">
]]>
<!ENTITY Otilde CDATA "&#213;" -- capital O, tilde --> % head.extra "& NEXTID?">

<!ENTITY Ouml   CDATA "&#214;" -- capital O, dieresis or umlaut mark % head.content "TITLE & ISINDEX? & BASE? %head.extra">

<!ELEMENT HEAD O O  (%head.content) +(META|LINK)>

<!-- <HEAD>     Document head   -->
<!ENTITY THORN  CDATA "&#222;" -- capital THORN, Icelandic

<!ELEMENT TITLE - -  (#PCDATA)*>
<!ATTLIST TITLE
        %SDAFORM; "Ti"    >

<!-- <TITLE>    Title of document -->
<!ENTITY Uacute CDATA "&#218;" -- capital U, acute accent

<!ELEMENT LINK - O EMPTY>
<!ATTLIST LINK
        HREF %URI #REQUIRED
        %linkExtraAttributes;
        %SDAPREF; "Linked to : #AttVal (TITLE) (URN) (HREF)>"    >

<!-- <LINK>             Link from this document                 -->
<!ENTITY Ucirc  CDATA "&#219;" -- capital U, circumflex accent
<!-- <LINK HREF="...">  Address of link destination             -->
<!ENTITY Ugrave CDATA "&#217;" -- capital U, grave accent
<!-- <LINK URN="...">   Lasting name of destination             -->
<!ENTITY Uuml   CDATA "&#220;" -- capital U, dieresis or umlaut mark
<!-- <LINK REL=...>     Relationship to destination             -->
<!ENTITY Yacute CDATA "&#221;" -- capital Y, acute accent
<!-- <LINK REV=...>     Relationship of destination to this     -->
<!ENTITY aacute CDATA "&#225;" -- small a, acute accent
<!-- <LINK TITLE="..."> Title of destination (advisory)         -->
<!ENTITY acirc  CDATA "&#226;" -- small a, circumflex accent
<!-- <LINK METHODS="..."> Operations allowed (advisory)         -->
<!ENTITY aelig  CDATA "&#230;" -- small ae diphthong (ligature)

<!ELEMENT ISINDEX - O EMPTY>
<!ATTLIST ISINDEX
        %SDAPREF;
   "<Para>[Document is indexed/searchable.]</Para>">

<!-- <ISINDEX>          Document is a searchable index          -->
<!ENTITY agrave CDATA "&#224;" -- small a, grave accent

<!ELEMENT BASE - O EMPTY>
<!ATTLIST BASE

Berners-Lee, Connolly                                          [Page 55]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

        HREF %URI; #REQUIRED     >

<!-- <BASE>             Base context document                   -->
<!ENTITY aring  CDATA "&#229;" -- small a, ring
<!-- <BASE HREF="...">  Address for this document               -->
<!ENTITY atilde

<!ELEMENT NEXTID - O EMPTY>
<!ATTLIST NEXTID
        N CDATA "&#227;" -- small a, tilde #REQUIRED     >

<!-- <NEXTID>           Next ID to use for link name            -->
<!ENTITY auml   CDATA "&#228;" -- small a, dieresis or umlaut mark
<!-- <NEXTID N=...>     Next ID to use for link name            -->
<!ENTITY ccedil

<!ELEMENT META - O EMPTY>
<!ATTLIST META
        HTTP-EQUIV  NAME    #IMPLIED
        NAME        NAME    #IMPLIED
        CONTENT     CDATA "&#231;" -- small c, cedilla   #REQUIRED    >

<!-- <META>                     Generic Metainformation         -->
<!ENTITY eacute CDATA "&#233;" -- small e, acute accent
<!-- <META HTTP-EQUIV=...>      HTTP response header name       -->
<!ENTITY ecirc  CDATA "&#234;" -- small e, circumflex accent
<!-- <META NAME=...>            Metainformation name            -->
<!ENTITY egrave CDATA "&#232;" -- small e, grave accent
<!-- <META CONTENT="...">       Associated information          -->

<!--======= Document Structure =================-->

<![ %HTML.Deprecated [
        <!ENTITY eth    CDATA "&#240;" -- small eth, Icelandic --> % html.content "HEAD, BODY, PLAINTEXT?">
]]>
<!ENTITY euml   CDATA "&#235;" -- small e, dieresis or umlaut mark --> % html.content "HEAD, BODY">

<!ELEMENT HTML O O  (%html.content)>
<!ENTITY iacute % version.attr "VERSION CDATA "&#237;" -- small i, acute accent #FIXED '%HTML.Version;'">

<!ATTLIST HTML
        %version.attr;
        %SDAFORM; "Book"
        >

<!-- <HTML>                     HTML Document   -->
<!ENTITY icirc  CDATA "&#238;" -- small i, circumflex accent


9.2. Strict HTML DTD

    This document type declaration refers to the HTML DTD with the
    `HTML.Recommended' entity defined as `INCLUDE' rather than
    IGNORE; that is, it refers to the more structurally rigid
    definition of HTML.

<!--    html-s.dtd

        Document Type Definition for the HyperText Markup Language
        with strict validation (HTML Strict DTD).

        $Id: html-s.dtd,v 1.3 1995/06/02 18:55:46 connolly Exp $

Berners-Lee, Connolly                                          [Page 56]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995


        Author: Daniel W. Connolly <connolly@w3.org>
        See Also: http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html
- -->

<!ENTITY igrave CDATA "&#236;" % HTML.Version
        "-//IETF//DTD HTML 2.0 Strict//EN"

        -- small i, grave accent -->
<!ENTITY iuml   CDATA "&#239;" Typical usage:

            <!DOCTYPE HTML PUBLIC
                "-//IETF//DTD HTML Strict//EN">
            <html>
            ...
            </html>
        -- small i, dieresis or umlaut mark
        >

<!-- Feature Test Entities -->
<!ENTITY ntilde CDATA "&#241;" -- small n, tilde --> % HTML.Recommended "INCLUDE">

<!ENTITY oacute CDATA "&#243;" -- small o, acute accent % html PUBLIC "-//IETF//DTD HTML 2.0//EN">
%html;


9.3. Level 1 HTML DTD

    This document type declaration refers to the HTML DTD with the
    `HTML.Forms' entity defined as `IGNORE' rather than `INCLUDE'.
    Documents which contain <FORM> elements do not conform to this
    DTD, and must use the level 2 DTD.

<!--    html-1.dtd

        Document Type Definition for the HyperText Markup Language
        with Level 1 Extensions (HTML Level 1 DTD).

        $Id: html-1.dtd,v 1.2 1995/03/29 18:53:10 connolly Exp $

        Author: Daniel W. Connolly <connolly@w3.org>
        See Also: http://info.cern.ch/hypertext/WWW/MarkUp/MarkUp.html
- -->

<!ENTITY ocirc  CDATA "&#244;" % HTML.Version
        "-//IETF//DTD HTML 2.0 Level 1//EN"

        -- small o, circumflex accent -->
<!ENTITY ograve CDATA "&#242;" Typical usage:

            <!DOCTYPE HTML PUBLIC
                "-//IETF//DTD HTML Level 1//EN">
            <html>
            ...
            </html>
        -- small o, grave accent

Berners-Lee, Connolly                                          [Page 57]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

        >

<!-- Feature Test Entities -->
<!ENTITY oslash CDATA "&#248;" -- small o, slash --> % HTML.Forms "IGNORE">

<!ENTITY otilde CDATA "&#245;" -- small o, tilde % html PUBLIC "-//IETF//DTD HTML 2.0//EN">
%html;


9.4. Strict Level 1 HTML DTD

    This document type declaration refers to the level 1 HTML DTD
    with the `HTML.Recommended' entity defined as `INCLUDE' rather
    than IGNORE; that is, it refers to the more structurally rigid
    definition of HTML.

<!--    html-1s.dtd

        Document Type Definition for the HyperText Markup Language
        Struct Level 1

        $Id: html-1s.dtd,v 1.3 1995/06/02 18:55:43 connolly Exp $

        Author: Daniel W. Connolly <connolly@w3.org>
        See Also: http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html
- -->

<!ENTITY ouml   CDATA "&#246;" % HTML.Version
        "-//IETF//DTD HTML 2.0 Strict Level 1//EN"

        -- small o, dieresis or umlaut mark -->
<!ENTITY szlig  CDATA "&#223;" Typical usage:

            <!DOCTYPE HTML PUBLIC
                "-//IETF//DTD HTML Strict Level 1//EN">
            <html>
            ...
            </html>
        -- small sharp s, German (sz ligature)
        >

<!-- Feature Test Entities -->
<!ENTITY thorn  CDATA "&#254;" -- small thorn, Icelandic --> % HTML.Recommended "INCLUDE">

<!ENTITY uacute CDATA "&#250;" % html-1 PUBLIC "-//IETF//DTD HTML 2.0 Level 1//EN">
%html-1;


9.5. SGML Declaration for HTML

    This is the SGML Declaration for HyperText Markup Language.

<!SGML  "ISO 8879:1986"
- -- small u, acute accent -->
<!ENTITY ucirc  CDATA "&#251;"
        SGML Declaration for HyperText Markup Language (HTML).

Berners-Lee, Connolly                                          [Page 58]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995


- -- small u, circumflex accent -->
<!ENTITY ugrave CDATA "&#249;"

CHARSET
         BASESET  "ISO 646:1983//CHARSET
                   International Reference Version
                   (IRV)//ESC 2/5 4/0"
         DESCSET  0   9   UNUSED
                  9   2   9
                  11  2   UNUSED
                  13  1   13
                  14  18  UNUSED
                  32  95  32
                  127 1   UNUSED
     BASESET   "ISO Registration Number 100//CHARSET
                ECMA-94 Right Part of
                Latin Alphabet Nr. 1//ESC 2/13 4/1"

         DESCSET  128  32   UNUSED
                  160  96    32

CAPACITY        SGMLREF
                TOTALCAP        150000
                GRPCAP          150000
                ENTCAP          150000
  
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
                   International Reference Version
                   (IRV)//ESC 2/5 4/0"
         DESCSET  0 128 0
         FUNCTION
                  RE          13
                  RS          10
                  SPACE       32
                  TAB SEPCHAR  9
        

         NAMING   LCNMSTRT ""
                  UCNMSTRT ""
                  LCNMCHAR ".-"
                  UCNMCHAR ".-"
                  NAMECASE GENERAL YES
                           ENTITY  NO
         DELIM    GENERAL  SGMLREF
                  SHORTREF SGMLREF
         NAMES    SGMLREF
         QUANTITY SGMLREF
                  ATTSPLEN 2100
                  LITLEN   1024
                  NAMELEN  72    -- small u, grave accent -->
<!ENTITY uuml   CDATA "&#252;" somewhat arbitrary; taken from

Berners-Lee, Connolly                                          [Page 59]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

                                internet line length conventions -- small u, dieresis or umlaut mark -->
<!ENTITY yacute CDATA "&#253;"
                  PILEN    1024
                  TAGLVL   100
                  TAGLEN   2100
                  GRPGTCNT 150
                  GRPCNT   64                   

FEATURES
  MINIMIZE
    DATATAG  NO
    OMITTAG  YES
    RANK     NO
    SHORTTAG YES
  LINK
    SIMPLE   NO
    IMPLICIT NO
    EXPLICIT NO
  OTHER
    CONCUR   NO
    SUBDOC   NO
    FORMAL   YES
  APPINFO    "SDA"  -- small y, acute accent -->
<!ENTITY yuml   CDATA "&#255;" conforming SGML Document Access application
                    -- small y, dieresis or umlaut mark
>
<!-- 
        $Id: html.decl,v 1.17 1995/06/08 14:59:32 connolly Exp $

        Author: Daniel W. Connolly <connolly@w3.org>

        See also: http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html
 -->


9. Glossary 

     absolute URI
                    a URI in absolute form, as per [URL]

     anchor
                    a hyperlink navigation option; typically, a
                    highlighted phrase marked as


9.6. Sample SGML Open Entity Catalog for HTML

    The SGML standard describes an <A> element.

     base URI
                    URI used ``entity manager'' as the base of an HTML document for the
                    purpose of resolving hyperlink destinations.

     character
                    An atom of information, for example a letter portion
    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 sequences of
                    octets, and whose range is the set of sequences component of
                    characters from a character repertoire; an SGML system 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. maps SGML entities into 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
    actual storage model (e.g., the file system). The standard
    itself does not define a subset of particular mapping methodology or
    notation.

    To assist the
                    integers interoperability among various SGML tools and whose range is a character
                    repertoire. That is, for some set of integers
                    (usually of
    systems, the form {0, 1, 2, ..., N} ), SGML Open consortium has passed a coded
                    character set and an integer in technical
    resolution that set determine defines a character. Conversely, 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 character and storage object identifier
    (such as a coded
                    character set determine file name) with information about the character's code
                    position (or, external entity
    that appears in rare cases, the SGML document. In addition to entries that
    associate public identifiers, a few code
                    positions).

     conforming catalog entry can associate an
    entity name with a storage object identifier. For example, the
    following are possible catalog entries:


Berners-Lee, Connolly                                          [Page 60]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

        -- 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 --
PUBLIC  "-//IETF//DTD HTML//EN"                 html.dtd
PUBLIC  "-//IETF//DTD HTML
     user agent
                    A user agent that conforms 2.0//EN"             html.dtd
PUBLIC  "-//IETF//DTD HTML Level 2//EN"         html.dtd
PUBLIC  "-//IETF//DTD HTML 2.0 Level 2//EN"     html.dtd

        -- Ways to this specification
                    in its processing of 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 refer to Level 1: most general to most specific --
PUBLIC  "-//IETF//DTD HTML Level 1//EN"         html-1.dtd
PUBLIC  "-//IETF//DTD HTML 2.0 Level 1//EN"     html-1.dtd

        -- Ways to refer to Level 0: most general to most specific --
PUBLIC  "-//IETF//DTD HTML Level 0//EN"         html-0.dtd
PUBLIC  "-//IETF//DTD HTML 2.0 Level 0//EN"     html-0.dtd


        -- Ways to refer to Strict Level 2: most general to most specif\
c --
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

        -- Ways to refer to Strict Level 1: most general to most specif\
c --
PUBLIC  "-//IETF//DTD HTML Strict Level 1//EN"          html-1s.dtd
PUBLIC  "-//IETF//DTD HTML 2.0 Strict Level 1//EN"      html-1s.dtd

        -- Ways to refer to Strict Level 0: most general to most specif\
c --
PUBLIC  "-//IETF//DTD HTML Strict Level 0//EN"          html-0s.dtd
PUBLIC  "-//IETF//DTD HTML 2.0 Strict Level 0//EN"      html-0s.dtd

        -- ISO latin 1 entity 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. for HTML -- 
PUBLIC  "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML"       ISOlat1\
sgml


9.7. Character Entity Sets

    The HTML DTD
                    document type definition. Rules that apply SGML to defines the markup of documents of a following entities. They represent
    particular type,
                    including a graphic characters which have special meanings in
    places in the markup, or may not be part of the character set
    available to the writer.


9.7.1. Numeric and Special Graphic Entity Set

    The following table lists each of element the characters included from
    the Numeric and Special Graphic entity
                    declarations. [SGML]

     element
                    A component 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'.

Berners-Lee, Connolly                                          [Page 61]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    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


9.7.2. ISO Latin 1 Character Entity Set

    The following public text lists each of the hierarchical structure defined
                    by a document type definition; it is identified characters specified
    in
                    a document instance by descriptive markup, sually
                    a start-tag the Added Latin 1 entity set, along with its name, syntax for
    use, and end-tag. [SGML]

     end-tag
                    Descriptive markup that identifies description. This list is derived from ISO Standard
    8879:1986//ENTITIES Added Latin 1//EN. HTML includes the end of an
                    element. [SGML] 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 included in all copies.
- -->
<!-- Character entity
                    data with an associated notation set. Typical invocation:
     <!ENTITY % ISOlat1 PUBLIC
       "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML">
     %ISOlat1;
- -->
<!--    Modified for use in HTML
        $Id: ISOlat1.sgml,v 1.2 1994/11/30 23:45:12 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;" -- capital A, ring -->
<!ENTITY Atilde CDATA "&#195;" -- capital A, tilde -->
<!ENTITY Auml   CDATA "&#196;" -- capital A, dieresis or umlaut 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 accent -->
<!ENTITY Egrave CDATA "&#200;" -- capital E, grave accent -->
<!ENTITY Euml   CDATA "&#203;" -- capital E, dieresis or umlaut mark -->
<!ENTITY Iacute CDATA "&#205;" -- capital I, acute accent -->
<!ENTITY Icirc  CDATA "&#206;" -- capital I, circumflex accent -->
<!ENTITY Igrave CDATA "&#204;" -- capital I, 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, acute accent -->
<!ENTITY Ocirc  CDATA "&#212;" -- capital O, circumflex accent -->
<!ENTITY Ograve CDATA "&#210;" -- capital O, grave accent -->
<!ENTITY Oslash CDATA "&#216;" -- capital O, slash -->
<!ENTITY Otilde CDATA "&#213;" -- capital O, tilde -->
<!ENTITY Ouml   CDATA "&#214;" -- capital O, dieresis or
                    interpretation; for example, a sequence of octets
                    associated with an Internet Media Type.[SGML]

     fragment
     identifier
                    the portion of an HREF attribute value following
                    the `#' character which modifies the prenentation
                    of the destination of a hyperlink.

     form data set
                    a sequence of name/value pairs; the names are
                    given by an HTML document and the values are given
                    by a user.

     HTML document
                    An SGML document conforming to this document type
                    definition.

     hyperlink
                    a relationship between to resources, called the
                    source and the destination.

     markup
                    Syntactically delimited characters added to the
                    data of a document to represent its structure.
                    There are four different kinds of markup:
                    descriptive markup (tags), references, markup
                    declarations, and processing instructions.[SGML]

     may
                    A document umlaut mark -->

Berners-Lee, Connolly                                          [Page 62]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

<!ENTITY THORN  CDATA "&#222;" -- capital THORN, Icelandic -->
<!ENTITY Uacute CDATA "&#218;" -- capital U, acute accent -->
<!ENTITY Ucirc  CDATA "&#219;" -- capital U, circumflex accent -->
<!ENTITY Ugrave CDATA "&#217;" -- capital U, grave accent -->
<!ENTITY Uuml   CDATA "&#220;" -- capital U, dieresis or user interface is conforming whether
                    this statement applies umlaut mark -->
<!ENTITY Yacute CDATA "&#221;" -- capital Y, acute accent -->
<!ENTITY aacute CDATA "&#225;" -- small a, 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, dieresis or not.

     media type
                    an Internet Media Type, as per [IMEDIA].

     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]

     minimally
     conforming HTML
     user agent
                    A user agent that conforms to this specification
                    except for form processing. It may only process
                    level 1 HTML documents.

     must
                    Documents umlaut mark -->
<!ENTITY ccedil CDATA "&#231;" -- small c, cedilla -->
<!ENTITY eacute CDATA "&#233;" -- small e, acute accent -->
<!ENTITY ecirc  CDATA "&#234;" -- small e, circumflex accent -->
<!ENTITY egrave CDATA "&#232;" -- small e, grave accent -->
<!ENTITY eth    CDATA "&#240;" -- small eth, Icelandic -->
<!ENTITY euml   CDATA "&#235;" -- small e, dieresis or user agents in conflict with this
                    statement are not conforming.

     SGML document
                    A sequence of characters organized physically as a
                    set of entities and logically into a hierarchy of
                    elements. An SGML document consists of data
                    characters and markup; the markup describes the
                    structure of the information and an instance of
                    that structure.[SGML]

     shall
                    If a document umlaut mark -->
<!ENTITY iacute CDATA "&#237;" -- small i, acute accent -->
<!ENTITY icirc  CDATA "&#238;" -- small i, circumflex accent -->
<!ENTITY igrave CDATA "&#236;" -- small i, grave accent -->
<!ENTITY iuml   CDATA "&#239;" -- small i, dieresis or user agent conflicts with this
                    statement, it does not conform to this
                    specification.

     should
                    If a document umlaut mark -->
<!ENTITY ntilde CDATA "&#241;" -- small n, tilde -->
<!ENTITY oacute CDATA "&#243;" -- small o, acute accent -->
<!ENTITY ocirc  CDATA "&#244;" -- small o, circumflex accent -->
<!ENTITY ograve CDATA "&#242;" -- small o, grave accent -->
<!ENTITY oslash CDATA "&#248;" -- small o, slash -->
<!ENTITY otilde CDATA "&#245;" -- small o, tilde -->
<!ENTITY ouml   CDATA "&#246;" -- small o, dieresis or user agent conflicts with this
                    statement, undesirable results may occur in
                    practice even though it conforms to this
                    specification.

     start-tag
                    Descriptive markup that identifies the start of an
                    element and specifies its generic identifier and
                    attributes. [SGML]

     
     syntax-reference
     character set
                    A coded character set whose range includes all
                    characters used for markup; e.g. name characters
                    and delimiter characters.

     tag
                    Markup that delimits an element. A tag includes a
                    name which refers to an element declaration in the
                    DTD, and may include attributes.[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 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, acute accent -->
<!ENTITY ucirc  CDATA "&#251;" -- small u, circumflex accent -->
<!ENTITY ugrave CDATA "&#249;" -- small u, grave accent -->
<!ENTITY uuml   CDATA "&#252;" -- small u, dieresis or stored in a
                    file.[SGML]

     typical
                    Typical processing is described for many elements.
                    This is not a mandatory part of the specification
                    but is given as guidance for designers umlaut mark -->
<!ENTITY yacute CDATA "&#253;" -- small y, acute accent -->
<!ENTITY yuml   CDATA "&#255;" -- small y, dieresis or umlaut mark -->


10. Security Considerations

    Anchors, embedded images, and to help
                    explain the uses for which the all other elements were
                    intended.

     URI
                    A Universal Resource Identifier is a formatted
                    string that serves which contain
    URIs as an identifier for a
                    resource, typcally on parameters may cause the Internet. URIs are used
                    in HTML URI to identify the destination of hyperlinks.
                    URIs be dereferenced in common practice include Uniform Resource
                    Locators (URLs)[URL] and Relative URLs[RELURL].
    response to user agent
                    A component input. In this case, the security
    considerations of a distributed system that presents
                    an interface and processes [URL] apply.

    The widely deployed methods for submitting forms requests on behalf --
    HTTP and SMTP -- provide little assurance of a
                    user; for example, a www browser or a mail user
                    agent.

     WWW
                    The World-Wide Web is a hypertext-based,
                    distributed confidentiality.
    Information providers who request sensitive information system created via
    forms -- especially by
                    researchers at CERN in Switzerland. Users may
                    create, edit or browse hypertext documents.
                    `http://www.w3.org/'


10. Bibliography way of the `PASSWORD' type input field
    (see 8.1.2, "Input Field: INPUT") -- should be aware and make
    their users aware of the lack of confidentiality.

Berners-Lee, Connolly                                          [Page 63]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995



11. References

    [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:ftp://ds.internic.net/rfc/rfc1630.txt>

    [URL]
            T. Berners-Lee, L. Masinter, and M. McCahill. ``Uniform
            Resource Locators (URL).'' RFC 1738, CERN, Xerox PARC,
            University of Minnesota, October 1994.
            <URL:ftp://ds.internic.net/rfc/rfc1738.txt>

    [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),
            Progress, MIT, UC Irvine, CERN, March 1995.
            <URL:ftp://ds.internic.net/internet-drafts/draft-ietf-http-v10-spec-00.ps>

    [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.
            <URL:ftp://ds.internic.net/rfc/rfc1521.txt>

    [RELURL]
            R. T. Fielding. ``Relative Uniform Resource Locators.''
            Work in Progress
                    (draft-ietf-uri-relative-url-06.txt), Progress, UC Irvine, March 1995.
            <URL:ftp://ds.internic.net/internet-drafts/draft-ietf-uri-relative-url-06.txt>

    [GOLD90]
            C. F. Goldfarb. ``The SGML Handbook.'' Y. Rubinsky, Ed.,
            Oxford University Press, 1990. <URL:>

    [DEXTER]
            Frank Halasz and Mayer Schwartz, ``The Dexter Hypertext
            Reference Model'', ``Communications of the ACM'', pp.
            30-39, vol. 37 no. 2, Feb 1994, <URL:>

    [IMEDIA]
            J. Postel. ``Media Type Registration Procedure.''
                    RFC 1590, Procedure.'',
            USC/ISI, March 1994.
            <URL:ftp://ds.internic.net/rfc/rfc1590.txt>

    [IANA]
            J. Reynolds and J. Postel. ``Assigned Numbers.'' STD 2,
            RFC 1700, USC/ISI, October 1994.
            <URL:ftp://ds.internic.net/rfc/rfc1700.txt>


Berners-Lee, Connolly                                          [Page 64]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    [SQ91]
            SoftQuad. ``The SGML Primer.'' 3rd ed., SoftQuad Inc.,
            1991.

     [US-ASCII]
                    US-ASCII. <URL:http://www.sq.com/>

    [ISO-646]
            ISO/IEC 646:1991 Information technology -- ISO 7-bit
            coded character set for information interchange
            <URL:http://www.iso.ch/cate/d4777.html>

    [ISO-10646]
            ISO/IEC 10646-1:1993 Information technology -- Universal
            Multiple-Octet Coded Character Set - 7-Bit American
                    Standard Code for Information Interchange.
                    Standard ANSI X3.4-1986, ANSI, 1986. (UCS) -- Part 1:
            Architecture and Basic Multilingual Plane
            <URL:http://www.iso.ch/cate/d18741.html>

    [ISO-8859-1]
            ISO 8859. International Standard -- Information
            Processing -- 8-bit Single-Byte Coded Graphic Character
            Sets -- 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.
            <URL:http://www.iso.ch/cate/d16338.html>

    [SGML]
            ISO 8879. Information Processing - -- Text and Office
            Systems - Standard Generalized Markup Language (SGML),
            1986.


11. Appendices 

     These appendices are provided <URL:http://www.iso.ch/cate/d16387.html>


12. 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 active participants in the HTML
    working group, too numerous to list individually, without whom
    there would be no standards process and no standard. That this
    document approaches its objective of carefully converging a
    description of current practice and formalization of HTML's
    relationship to SGML is a tribute to their effort.


Berners-Lee, Connolly                                          [Page 65]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

12.1. Authors' Addresses

    Tim Berners-Lee

    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

    Research Technical Staff, W3 Consortium
    MIT Laboratory for informational reasons only
     - they do not form a part of the HTML specification.


11.1. 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/


13. The ANSI/ISO 8859-1 HTML Coded Character Set

    This list, sorted numerically, is derived from ANSI/ISO
     8859-1 8-bit single-byte list details the code positions and characters of the HTML
    document character set, specified in 9.5, "SGML Declaration for
    HTML". This coded graphic character set: set is based on [ISO-8859-1].

    REFERENCE       DESCRIPTION
    --------------  -----------
    &#00; - &#08;   Unused
    &#09;           Horizontal tab
    &#10;           Line feed
    &#11; - &#12;   Unused
    &#13;           Carriage Return
    &#14; - &#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

Berners-Lee, Connolly                                          [Page 66]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    &#58;           Colon
    &#59;           Semi-colon
    &#60;           Less than
    &#61;           Equals sign
    &#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 (underscore)
    &#96;           Acute accent
    &#97; - &#122;  Letters a-z
    &#123;          Left curly brace
    &#124;          Vertical bar
    &#125;          Right curly brace
    &#126;          Tilde
    &#127; - &#160; &#159; Unused
    &#160;          Non-breaking Space
    &#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
    &#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, grave accent
    &#193;          Capital A, acute accent

Berners-Lee, Connolly                                          [Page 67]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    &#194;          Capital A, circumflex accent
    &#195;          Capital A, tilde
    &#196;          Capital A, dieresis or umlaut mark
    &#197;          Capital A, ring
    &#198;          Capital AE dipthong (ligature)
    &#199;          Capital C, cedilla
    &#200;          Capital E, grave accent
    &#201;          Capital E, acute accent
    &#202;          Capital E, circumflex accent
    &#203;          Capital E, dieresis or umlaut mark
    &#204;          Capital I, grave accent
    &#205;          Capital I, acute accent
    &#206;          Capital I, circumflex accent
    &#207;          Capital I, dieresis or umlaut mark
    &#208;          Capital Eth, Icelandic
    &#209;          Capital N, tilde
    &#210;          Capital O, grave accent
    &#211;          Capital O, acute 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, grave accent
    &#218;          Capital U, acute 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, grave accent
    &#225;          Small a, acute 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, grave accent
    &#233;          Small e, acute accent
    &#234;          Small e, circumflex accent
    &#235;          Small e, dieresis or umlaut mark
    &#236;          Small i, grave accent
    &#237;          Small i, acute accent
    &#238;          Small i, circumflex accent
    &#239;          Small i, dieresis or umlaut mark
    &#240;          Small eth, Icelandic
    &#241;          Small n, tilde
    &#242;          Small o, grave accent
    &#243;          Small o, acute 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, 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


11.2. Obsolete Features 

     This section describes elements that are no longer part of
     HTML. Client implementors should implement these obsolete
     elements for compatibility with previous versions of the
     HTML specification.


11.2.1. Comment Element 

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


11.2.2. Highlighted Phrase Element 

     <HP>

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


11.2.3. Plain Text Element 

     <PLAINTEXT>

Berners-Lee, Connolly                                          [Page 68]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    &#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. Proposed Entities

    The Plain Text element is used to terminates the HTML DTD references the ``Added Latin 1'' entity
     and to indicate that what follows is not SGML set, which does not
     require parsing. Instead, an old 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 is line one of
    only supplies named entities for a long listing
     0002 file from <ANY@HOST.INC.COM> which is sent


11.2.4. Example and Listing Elements 

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

     The Example and Listing elements have been replaced by the
     Preformatted Text element (Section 10.2).

     These styles allow text subset of fixed-width the non-ASCII
    characters to be
     embedded absolutely as is into in [ISO-8859-1], namely the document. The syntax is:

     <LISTING> ... </LISTING>

     or

     <XMP> ... </XMP> accented characters. The text between these tags is typically rendered in a
     monospaced font
    following entities should be supported so that any formatting done by character
     spacing on successive lines will be maintained.

     Between the opening and closing tags:

          * The text may contain any ISO Latin-1 printable
          characters, except for the end-tag opener. The Example
          and Listing elements have historically used
          specifications which do not conform to SGML.
          Specifically, the text may contain all ISO Latin printable
          characters, including the tag opener, as long it they
          does not contain the 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 text 8859-1
    characters may only be referenced symbolically. The names for
    these entities are rendered as a
          move to taken from the beginning appendixes of the next line, except for [SGML].

    <!ENTITY nbsp   CDATA "&#160;" -- no-break space -->
    <!ENTITY iexcl  CDATA "&#161;" -- inverted exclamation mark -->
    <!ENTITY cent   CDATA "&#162;" -- cent sign -->
    <!ENTITY pound  CDATA "&#163;" -- pound sterling sign -->
    <!ENTITY curren CDATA "&#164;" -- general currency sign -->
    <!ENTITY yen    CDATA "&#165;" -- yen sign -->
    <!ENTITY brvbar CDATA "&#166;" -- broken (vertical) bar -->
    <!ENTITY sect   CDATA "&#167;" -- section sign -->
    <!ENTITY uml    CDATA "&#168;" -- umlaut (dieresis) -->
    <!ENTITY copy   CDATA "&#169;" -- copyright sign -->
    <!ENTITY ordf   CDATA "&#170;" -- ordinal indicator, feminine -->
    <!ENTITY laquo  CDATA "&#171;" -- angle quotation mark, left -->
    <!ENTITY not    CDATA "&#172;" -- not sign -->
    <!ENTITY shy    CDATA "&#173;" -- soft hyphen -->
    <!ENTITY reg    CDATA "&#174;" -- registered sign -->
    <!ENTITY macr   CDATA "&#175;" -- macron -->
    <!ENTITY deg    CDATA "&#176;" -- degree sign -->
    <!ENTITY plusmn CDATA "&#177;" -- plus-or-minus sign -->
    <!ENTITY sup2   CDATA "&#178;" -- superscript two -->
    <!ENTITY sup3   CDATA "&#179;" -- superscript three -->
    <!ENTITY acute  CDATA "&#180;" -- acute accent -->
    <!ENTITY micro  CDATA "&#181;" -- micro sign -->
    <!ENTITY para   CDATA "&#182;" -- pilcrow (paragraph sign) -->
    <!ENTITY middot CDATA "&#183;" -- middle dot -->
    <!ENTITY cedil  CDATA "&#184;" -- cedilla -->
    <!ENTITY sup1   CDATA "&#185;" -- superscript one
          immediately following a start-tag -->
    <!ENTITY ordm   CDATA "&#186;" -- ordinal indicator, masculine -->
    <!ENTITY raquo  CDATA "&#187;" -- angle quotation mark, right -->
    <!ENTITY frac14 CDATA "&#188;" -- fraction one-quarter -->
    <!ENTITY frac12 CDATA "&#189;" -- fraction one-half -->
    <!ENTITY frac34 CDATA "&#190;" -- fraction three-quarters -->
    <!ENTITY iquest CDATA "&#191;" -- inverted question mark -->
    <!ENTITY Agrave CDATA "&#192;" -- capital A, grave accent -->
    <!ENTITY Aacute CDATA "&#193;" -- capital A, acute accent -->
    <!ENTITY Acirc  CDATA "&#194;" -- capital A, circumflex accent -->

Berners-Lee, Connolly                                          [Page 69]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    <!ENTITY Atilde CDATA "&#195;" -- capital A, tilde -->
    <!ENTITY Auml   CDATA "&#196;" -- capital A, dieresis 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 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.


11.3. Proposed Features 

     This section describes proposed HTML elements and entities
     that are not currently supported under HTML Levels 1, umlaut mark -->
    <!ENTITY Aring  CDATA "&#197;" -- capital A, ring -->
    <!ENTITY AElig  CDATA "&#198;" -- capital AE diphthong (ligature) -->
    <!ENTITY Ccedil CDATA "&#199;" -- capital C, cedilla -->
    <!ENTITY Egrave CDATA "&#200;" -- capital E, grave accent -->
    <!ENTITY Eacute CDATA "&#201;" -- capital E, acute accent -->
    <!ENTITY Ecirc  CDATA "&#202;" -- capital E, circumflex accent -->
    <!ENTITY Euml   CDATA "&#203;" -- capital E, dieresis or umlaut mark -->
    <!ENTITY Igrave CDATA "&#204;" -- capital I, grave accent -->
    <!ENTITY Iacute CDATA "&#205;" -- capital I, acute accent -->
    <!ENTITY Icirc  CDATA "&#206;" -- capital I, circumflex accent -->
    <!ENTITY Iuml   CDATA "&#207;" -- capital I, dieresis or umlaut mark -->
    <!ENTITY ETH    CDATA "&#208;" -- capital Eth, Icelandic -->
    <!ENTITY Ntilde CDATA "&#209;" -- capital N, tilde -->
    <!ENTITY Ograve CDATA "&#210;" -- capital O, grave accent -->
    <!ENTITY Oacute CDATA "&#211;" -- capital O, acute accent -->
    <!ENTITY Ocirc  CDATA "&#212;" -- capital O, circumflex accent -->
    <!ENTITY Otilde CDATA "&#213;" -- capital O, tilde -->
    <!ENTITY Ouml   CDATA "&#214;" -- capital O, dieresis or 2,
     but may be supported in the future.


11.3.1. Additional Character Entities 

     To indicate special characters, HTML uses entity umlaut mark -->
    <!ENTITY times  CDATA "&#215;" -- multiply sign -->
    <!ENTITY Oslash CDATA "&#216;" -- capital O, slash -->
    <!ENTITY Ugrave CDATA "&#217;" -- capital U, grave accent -->
    <!ENTITY Uacute CDATA "&#218;" -- capital U, acute accent -->
    <!ENTITY Ucirc  CDATA "&#219;" -- capital U, circumflex accent -->
    <!ENTITY Uuml   CDATA "&#220;" -- capital U, dieresis or numeric
     representations. Additional character presentations are
     proposed:

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


11.3.2. Defining Instance Element 

     <DFN> ... </DFN>

     The Defining Instance element indicates the defining
     instance of a term. The typical rendering is bold umlaut mark -->
    <!ENTITY Yacute CDATA "&#221;" -- capital Y, acute accent -->
    <!ENTITY THORN  CDATA "&#222;" -- capital THORN, Icelandic -->
    <!ENTITY szlig  CDATA "&#223;" -- small sharp s, German (sz ligature) -->
    <!ENTITY agrave CDATA "&#224;" -- small a, grave accent -->
    <!ENTITY aacute CDATA "&#225;" -- small a, acute accent -->
    <!ENTITY acirc  CDATA "&#226;" -- small a, circumflex accent -->
    <!ENTITY atilde CDATA "&#227;" -- small a, tilde -->
    <!ENTITY auml   CDATA "&#228;" -- small a, dieresis or umlaut mark -->
    <!ENTITY aring  CDATA "&#229;" -- small a, ring -->
    <!ENTITY aelig  CDATA "&#230;" -- small ae diphthong (ligature) -->
    <!ENTITY ccedil CDATA "&#231;" -- small c, cedilla -->
    <!ENTITY egrave CDATA "&#232;" -- small e, grave accent -->
    <!ENTITY eacute CDATA "&#233;" -- small e, acute accent -->
    <!ENTITY ecirc  CDATA "&#234;" -- small e, circumflex accent -->
    <!ENTITY euml   CDATA "&#235;" -- small e, dieresis or bold
     italic. This element is not widely supported.


11.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 widely supported.


11.3.4. Underline Element 

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

     Example of use:

     The text <U>shown here</U> is rendered in the
     document as underlined.


12. 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 Marc Andreessen

     Tim Berners-Lee Paul Burchard

     James Clark Daniel W. umlaut mark -->
    <!ENTITY igrave CDATA "&#236;" -- small i, grave accent -->
    <!ENTITY iacute CDATA "&#237;" -- small i, acute accent -->
    <!ENTITY icirc  CDATA "&#238;" -- small i, circumflex accent -->
    <!ENTITY iuml   CDATA "&#239;" -- small i, dieresis or umlaut mark -->
    <!ENTITY eth    CDATA "&#240;" -- small eth, Icelandic -->
    <!ENTITY ntilde CDATA "&#241;" -- small n, tilde -->
    <!ENTITY ograve CDATA "&#242;" -- small o, grave accent -->
    <!ENTITY oacute CDATA "&#243;" -- small o, acute accent -->
    <!ENTITY ocirc  CDATA "&#244;" -- small o, circumflex accent -->
    <!ENTITY otilde CDATA "&#245;" -- small o, tilde -->
    <!ENTITY ouml   CDATA "&#246;" -- small o, dieresis or umlaut mark -->
    <!ENTITY divide CDATA "&#247;" -- divide sign -->
    <!ENTITY oslash CDATA "&#248;" -- small o, slash -->

Berners-Lee, Connolly

     Roy T. Fielding Peter Flynn

     Jay Glicksman Paul Grosso

     Eduardo Gutentag Bill Hefley

     Chung-Jen Ho Mike Knezovich

     Tom Magliery Murray Maloney

     Larry Masinter Karen Olson Muldrow

     Bill Perry Dave Raggett

     E. Corprew Reed Yuri Rubinsky

     Eric Schieler James L. Seidman

     Eric W. Sink Stuart Weibel

     Chris Wilson Francois Yergeau


12.1. Authors' Addresses 

     Tim Berners-Lee

     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.                                          [Page 70]

INTERNET-DRAFT      Hypertext Markup Language - 2.0        June 16, 1995

    <!ENTITY ugrave CDATA "&#249;" -- small u, grave accent -->
    <!ENTITY uacute CDATA "&#250;" -- small u, acute accent -->
    <!ENTITY ucirc  CDATA "&#251;" -- small u, circumflex accent -->
    <!ENTITY uuml   CDATA "&#252;" -- small u, dieresis or umlaut mark -->
    <!ENTITY yacute CDATA "&#253;" -- small y, acute accent -->
    <!ENTITY thorn  CDATA "&#254;" -- small thorn, Icelandic -->
    <!ENTITY yuml   CDATA "&#255;" -- small y, dieresis or umlaut mark -->
















































Berners-Lee, Connolly

     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/                                          [Page 71]




----