', `

', and ` quote>' are equivalent, whereas `&' is different from `&'.

In a start tag, the element name must immediately follow the tag
open delimiter `<'.



Attributes In a start tag, white space and attributes are allowed
between the element name and the closing delimiter. An attribute typi-
cally consists of an attribute name, an equal sign, and a value, though
some attributes may be just a value. White space is allowed around the
equal sign.

The value of the attribute may be either:


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


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

In this example, img is the element name, `src' is the attribute
name, and `http://host/dir/file.gif' is the attribute value:







Some
-----------
The SGML declaration for HTML specifies SHORTTAG YES, which
means that there are other valid syntaxes for tags, such as
NET tags, `'; and empty
end tags, `'. Until support for these idioms is widely
deployed, their use is strongly discouraged.
Some historical implementations consider any occurrence of
the `>' character to signal the end of a tag. For ompati-



Berners-Lee, Connolly FORMFEED[Page 10]





INTERNET DRAFT May 1985


A useful technique for computing an attribute value literal for a
given string is to replace each quote and space character by an entity
reference or numeric character reference as follows:



ENTITY NUMERIC
CHARACTER REFERENCE CHAR REF CHARACTER DESCRIPTION
TAB Tab
LF Line Feed
CR Carriage Return
Space
" " " Quotation mark
& & & Ampersand



For example:







Some

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

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

-----------
bility with such implementations, when `>' appears in an
attribute value, it should be represented with a numeric
character reference, such as in: ` alt="a>b">'.
Some historical implementations allow any character except
space or `>' in a name token. Attributes values must be
quoted only if they don't satisfy the syntax for a name
token.



Berners-Lee, Connolly FORMFEED[Page 11]





INTERNET DRAFT May 1985


can be written using a minimized syntax:








Some



Comments To include comments in an HTML document that will be eliminated
in the mapping to terminals, surround them with `'. After the comment
delimiter, all text up to the next occurrence of `-->' is ignored.
Hence comments cannot be nested. White space is allowed between the
closing `--' and `>', but not between the opening `
For example:










Some



Example HTML Document









-----------
Some historical implementations only understand the mini-
mized syntax.
Some historical HTML implementations incorrectly consider
any `>' character to be the termination of a comment.



Berners-Lee, Connolly FORMFEED[Page 12]





INTERNET DRAFT May 1985




First Header




This is a paragraph in the example HTML file. Keep in mind
that the title does not appear in the document text, but that
the header (defined by H1) does.





1. First item in an ordered list.
   
2. Second item in an ordered list.
   
   
   
   • Note that lists can be nested;
     
   • Whitespace may be used to assist in reading the
     HTML source.
     
   
   
3. Third item in an ordered list.
   



This is an additional paragraph. Technically, end tags are
not required for paragraphs, although they are allowed. You can
include character highlighting in a paragraph. This sentence
of the paragraph is emphasized. Note that the </P>
end tag has been omitted.




Be sure to read these bold instructions.





























Berners-Lee, Connolly FORMFEED[Page 13]





INTERNET DRAFT May 1985


3. HTML as an Internet Media Type 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 docu-
ments. HTML user agents should be able to preserve all formatting dis-
tinctions represented in an HTML document, and be able to simultaneously
present resources referred to by IMG elements. (they may ignore some
formatting distinctions or IMG resources at the request of the user).
Conforming HTML user agents should support form entry and submission.



3.1. text/html media type

This specification defines the Internet Media Type[IMEDIA] (for-
merly referred to as the Content Type[MIME]) called `text/html'. The
following is to be registered with [IANA].


Media Type name
text


Media subtype name
html


Required parameters
none


Optional parameters
version, charset


Encoding considerations
any encoding is allowed


Security considerations
see `Security Considerations'



The optional parameters are defined as follows:


Version
To help avoid future compatibility problems, the version parameter



Berners-Lee, Connolly FORMFEED[Page 14]





INTERNET DRAFT May 1985


may be used to give the version number of the specification to
which the document conforms. The version number appears at the
front of this document and within the public identifier of the HTML
DTD. This specification defines version 2.0.


Charset
The charset parameter (as defined in section 7.1.1 of RFC
1521[MIME]) may be given to specify the character encoding scheme
used to represent the HTML document as a sequence of octets.





3.2. HTML Document Representation A message entity with a content type
of `text/html' represents an HTML document, consisting of a single text
entity. The `charset' parameter (whether implicit or explicit) identi-
fies a character encoding scheme. The text entity consists of the char-
acters determined by this character encoding and the octets of the body
of the message entity.

HTML user agents must support the ISO-8859-1 character encoding
scheme, and hence the US-ASCII character encoding scheme. HTML



Undeclared Markup Error Handling To facilitate experimentation and
interoperability between implementations of various versions of HTML,
the installed base of HTML user agents supports a superset of the HTML
2.0 language by reducing it to HTML 2.0: markup in the form of a start
tag or end tag whose generic identifier is not declared is mapped to
nothing during tokenization. Undeclared attributes are treated simi-
larly. The entire attribute specification of an unknown attribute
(i.e., the unknown attribute and its value, if any) should be ignored.
On the other hand, references to undeclared entities should be treated
as data characters.

For example:





foo

...


-----------
HTML user agents are encouraged to support ISO10646 as a
document character set, and Unicode-1-1-UTF-8 and Uni-
code-1-1-UCS-2 as character encoding schemes. Other encod-
ings schemes such as ISO-2022-JP may be supported as well.



Berners-Lee, Connolly FORMFEED[Page 15]





INTERNET DRAFT May 1985


=>

,"foo",

,

,"..."
xxx

yyy
=> "xxx ",

," yyy
Let α and β be finite sets.
=> "Let α and β be finite sets."



Support for notifying the user of such errors is encouraged.

Information providers should keep in mind that this convention is
not binding: unspecified behavior may result, as such markup is not
conforming to this specification.



Conventional Representation of Newlines SGML specifies that a text
entity is a sequence of records, each beginning with a record start
character and ending with a record end character (characters numbered 10
and 13 respectively). (@@cite a section)

MIME specifies that a body of type `text/*' is a sequence of lines,
each terminated by CRLF, that is octets 10, 13.

In practice, HTML documents are frequently represented and trans-
mitted using an end of line convention that depends on the conventions
of the source of the document; frequently, that representation consists
of CR only, LF only, or CR LF combination. Hence the decoding of the
octets will often result in a text entity with some missing record start
and record end characters.

Since there is no ambiguity, HTML user agents are encouraged to
infer the missing record start and end characters.

An HTML user agent should treat end of line in any of its varia-
tions as a word space in all contexts except preformatted text. Within
preformatted text, an HTML user agent should expect to treat any of the
three common representations of end-of-line as starting a new line.



3.3. Security Considerations Anchors, embedded images, and all other
elements which contain URIs as parameters may cause the URI to be deref-
erenced in response to user input. In this case, the security consider-
ations of the URI specification apply.

Documents may be constructed whose visible contents mislead the
reader to follow a link to unsuitable or offensive material.



Berners-Lee, Connolly FORMFEED[Page 16]





INTERNET DRAFT May 1985


>


















































Berners-Lee, Connolly FORMFEED[Page 17]





INTERNET DRAFT May 1985


4. Document Structure Elements

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







If

HTML user agents are required to support the above document type
declaration, the following document type declarations, and no others.








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



4.1. HTML Document Element ... Level 0

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

The <
-----------
If the body of a text/html body part does not begin with a
document type declaration, an HTML user agent should infer
the above document type declaration.
The start and end tags for HTML, Head, and Body elements are
omissible; however, this is not recommended since the
head/body structure allows an implementation to determine
certain properties of a document, such as the title, without
parsing the entire document.



Berners-Lee, Connolly FORMFEED[Page 18]





INTERNET DRAFT May 1985


4.2. Head ... Level 0

The head of an HTML document is an unordered collection of informa-
tion about the document. The Title element is required.











4.3. Body ... Level 0

The Body element identifies the body component of an HTML document.
Specifically, the body of a document may contain links, text, and for-
matting information within and tags.



4.4. Title Level 0

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

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

The





-----------
The length of a title is not limited; however, long titles
may be truncated in some applications. To minimize this
possibility, titles should be fewer than 64 characters.
Also keep in mind that a short title, such as Introduction,
may be meaningless out of context. An example of a meaning-
ful title might be ``Introduction to HTML Elements.''



Berners-Lee, Connolly FORMFEED[Page 19]





INTERNET DRAFT May 1985


4.5. Base Level 0

The Base element allows the URI of the document itself to be
recorded in situations in which the document may be read out of context.
URIs within the document may be in a ``partial'' form relative to this
base address[RELURL].

The Base element has one attribute, HREF, which identifies the
absolute base URI.



4.6. Isindex Level 0

The Isindex element tells the interpreter that the document is an
index. This means that the reader may request a keyword search on the
resource by adding a question mark to the end of the document address,
followed by a list of keywords separated by plus signs.

The Isindex element is usually generated by the network server from
which the document was obtained via a URI. The server must have a
search engine that supports this feature for the resource. If the docu-
ment URI is unknown to the interpreter, must be ignored.



4.7. Link Level 0

The Link element indicates a relationship between the document and
some other object. A document may have any number of Link elements.

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

Typical uses are to indicate authorship, related indexes and glos-
saries, older or more recent versions, etc. Links can indicate a static
tree structure in which the document was authored by pointing to a
``parent'' and ``next'' and ``previous'' document, for example.

Servers may also allow links to be added by those who do not have
the right to alter the body of a document.



4.8. Meta Level 0

The META element is used within the HEAD element to embed document
metainformation not defined by other HTML elements. META elements can



Berners-Lee, Connolly FORMFEED[Page 20]





INTERNET DRAFT May 1985


be extracted by servers and/or clients for use in identifying, indexing,
and cataloging specialized document metainformation.

Although it is generally preferable to use named elements which
have well-defined semantics for each type of metainformation (e.g.
TITLE), the META element is provided for situations where strict SGML
parsing is necessary and the local DTD is not extensible. HTML inter-
preters may use the META element's content if they recognize and under-
stand the semantics identified by the NAME or HTTP-EQUIV attributes, and
may treat the content as metainformation (and not render it) even when
they do not recognize the name.

In addition, HTTP servers may wish to read the content of the docu-
ment HEAD to generate header fields corresponding to any elements defin-
ing a value for the attribute HTTP-EQUIV. Note, however, that the
method by which the server extracts document metainformation is not part
of this specification, nor can it be assumed by authors that any given
server will be capable of extracting it. The META element only provides
an extensible mechanism for identifying and embedding document metain-
formation - how it may be used is up to the individual server implemen-
tation and the HTML interpreter.

Attributes of the META element:


HTTP-EQUIV
This attribute binds the element to an HTTP header field. It means
that if you know the semantics of the HTTP header field named by
this attribute, then you can process the contents based on a well-
defined syntactic mapping, whether or not your DTD tells you any-
thing about it. HTTP header field names are not case sensitive.
If not present, the attribute NAME should be used to identify this
metainformation and the content should not be used within an HTTP
response header.


NAME
Metainformation name. If the NAME attribute is not present, the
name can be assumed to be equal to the value of HTTP-EQUIV.


CONTENT
The metainformation content to be associated with the given name.
If multiple META elements are provided with the same name, their
combined contents-concatenated as a comma-separated list-is the
value associated with that name.





Berners-Lee, Connolly FORMFEED[Page 21]





INTERNET DRAFT May 1985


Examples

If the document contains:



      CONTENT="Tue, 04 Dec 1993 21:29:02 GMT">

      content="fielding@ics.uci.edu (Roy Fielding)">



then the server (if so configured) may include the following head-
ers:



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



as part of the HTTP response to a GET or HEAD request for that doc-
ument.

When the HTTP-EQUIV attribute is not present, the server should not
generate an HTTP response header for the metainformation; e.g.,







would never generate an HTTP response header, but would still allow
HTML interpreters to identify and make use of that metainformation.

The Meta element should never be used to define information that
should be associated with an existing HTML element. An example of an
inappropriate use of the Meta element is:







Berners-Lee, Connolly FORMFEED[Page 22]





INTERNET DRAFT May 1985




Do not name an HTTP-EQUIV equal to a response header that should
normally only be generated by the HTTP server. Example names that are
inappropriate include ``Server'', ``Date'', and ``Last-modified'' - the
exact list of inappropriate names is dependent on the particular server
implementation. We recommend that servers ignore any META elements
which specify HTTP-equivalents which are equal (case-insensitively) to
their own reserved response headers.



4.9. Nextid Level 0

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







When modifying a document, existing anchor identifiers should not
be reused, as these identifiers may be referenced by other documents.
Human writers of HTML usually use mnemonic alphabetical identifiers.

HTML interpreters may ignore the Nextid element. Support for the
Nextid element does not impact HTML interpreters in any way.




















Berners-Lee, Connolly FORMFEED[Page 23]





INTERNET DRAFT May 1985


5. Character Content An HTML user agent should present the body of an
HTML document as a collection of typeset paragraphs and preformatted
text. Except for the PRE element, each block structuring element is
regarded as a paragraph by taking the data characters in its content and
the content of its descendant elements, concatenating them, and split-
ting the result into words, separated by space, tab, or record end char-
acters (and perhaps hyphen characters). The sequence of words is type-
set as a paragraph by breaking it into lines.



5.1. The ISO Latin 1 Character Repertoire Conforming HTML user agents
are required to support the [US-ASCII] and [ISO-8859-1] character encod-
ings, and the Latin Alphabet Nr. 1 document character set as specified
in `SGML Declaration for HTML'.

The character repertoire shared by the two encodings and the docu-
ment character set is Latin Alphabet Nr. 1, or simply Latin-1. Latin-1
includes characters from most Western European languages, as well as a
number 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.

Use

In SGML applications, the use of control characters is limited in
order to maximize the chance of successful interchange over heteroge-
neous networks and operating systems. In HTML, only three control char-
acters are allowed: Horizontal Tab (HT, encoded as 9 decimal in US-
ASCII and ISO-8859-1), Carriage Return, and Line Feed.

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



Kurt Gödel was a famous logician and mathematician.



See `ISO Latin 1 Character Entity Set' for a table of the ``Added
Latin 1'' entities, and `The ISO-8859-1 Coded Character Set' for a table
of the code positionss of ISO-8859-1.
-----------
Use the non-breaking space and soft hyphen indicator charac-
ters is discouraged because support for them is not widely
deployed.



Berners-Lee, Connolly FORMFEED[Page 24]





INTERNET DRAFT May 1985


6. Data Elements


6.1. Line Break
Level 0

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

Example of use:





Pease porridge hot

Pease porridge cold

Pease porridge in the pot

Nine days old.





6.2. Horizontal Rule

---

Level 0

A Horizontal Rule element is a divider between sections of text
such as a full width horizontal rule or equivalent graphic.

Example of use:





---



February 8, 1995, CERN







6.3. Image Level 0

The Image element is used to incorporate in-line graphics (typi-
cally icons or small graphics) into an HTML document. This element can-
not be used for embedding other HTML text.

HTML interpreters that cannot render in-line images ignore the
Image element unless it contains the ALT attribute. Note that some HTML
interpreters can render linked graphics but not in-line graphics. If a



Berners-Lee, Connolly FORMFEED[Page 25]





INTERNET DRAFT May 1985


graphic is essential, you may want to create a link to it rather than to
put it in-line. If the graphic is not essential, then the Image element
is appropriate.

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


ALIGN
The ALIGN attribute accepts the values TOP or MIDDLE or BOTTOM,
which specifies if the following line of text is aligned with the
top, middle, or bottom of the graphic.


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



Be sure
to read these instructions.




ISMAP
The ISMAP (is map) attribute identifies an image as an image map.
Image maps are graphics in which certain regions are mapped to
URIs. By clicking on different regions, different resources can be
accessed from the same graphic. Example of use:










SRC The value of the SRC attribute is the URI of the document to be
embedded; only images can be embedded, not HTML text. Its syntax
is the same as that of the HREF attribute of the `' tag. SRC is
mandatory. Image elements are allowed within anchors.





Berners-Lee, Connolly FORMFEED[Page 26]





INTERNET DRAFT May 1985


Example of use:



Be sure to read these
instructions.













































Berners-Lee, Connolly FORMFEED[Page 27]





INTERNET DRAFT May 1985


7. Character Format Elements

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



This is emphasized text.



Character format tags may be ignored by minimal HTML applications.

Character format tags are interpreted from left to right as they
appear in the flow of text. Level 1 interpreters must render high-
lighted text 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.

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



plain bold italic may the rendered
the same as plain bold italic





7.1. Semantic Format Elements

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

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





Berners-Lee, Connolly FORMFEED[Page 28]





INTERNET DRAFT May 1985


Citation ... Level 1

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



Code ... Level 1

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



Emphasis ... Level 1

The Emphasis element indicates typographic emphasis, typically ren-
dered as italics.



Keyboard ... Level 1

The Keyboard element indicates text typed by a user, typically ren-
dered in a monospaced font. This is commonly used in instruction manu-
als.



Sample ... Level 1

The Sample element indicates a sequence of literal characters, typ-
ically rendered in a monospaced font.



Strong ... Level 1

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



Variable ... Level 1

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



Berners-Lee, Connolly FORMFEED[Page 29]





INTERNET DRAFT May 1985


7.2. Physical Format Elements

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



Bold ... Level 1

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



Italic ... Level 1

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



Teletype ... Level 1

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
























Berners-Lee, Connolly FORMFEED[Page 30]





INTERNET DRAFT May 1985


8. Hyperlink Elements


8.1. Anchor ... Level 0

An anchor is a marked section of text that is the start and/or des-
tination of a hypertext link. Anchor elements are defined by the `'
tag. The `' tag accepts several attributes; at least one of the
NAME and HREF attributes is required.

Attributes of the `' tag:



HREF

If the HREF attribute is present, the text between the opening and
closing anchor tags becomes hypertext. If this hypertext is selected by
readers, they are moved to another document, or to a different location
in the current document, whose network address is defined by the value
of the HREF attribute.

Example:



See HaL's
information for more details.



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

With the HREF attribute, the form HREF=``#identifier'' can refer to
another anchor in the same document.

Example:



The glossary defines
terms used in this document.







Berners-Lee, Connolly FORMFEED[Page 31]





INTERNET DRAFT May 1985


In this example, selecting ``glossary'' takes the reader to another
anchor (i.e., Glossary) in the same document.
The NAME attribute is described below. If the anchor is in another doc-
ument, the HREF attribute may be relative to the document's address or
the specified base address (see `Base').



NAME

If present, the NAME attribute allows the anchor to be the target
of a link. The value of the NAME attribute is an identifier for the
anchor. Identifiers are arbitrary strings but must be unique within the
HTML document.

Example of use:



Coffee is an example of ...
... An example of this is coffee.



Another document can then make a reference explicitly to this
anchor by putting the identifier after the address, separated by a hash
sign:









TITLE

The TITLE attribute is informational only. If present, the TITLE
attribute should provide the title of the document whose address is
given by the HREF attribute. The TITLE attribute is useful for at least
two reasons. The HTML interpreter may display the title of the document
prior to retrieving it, for example, as a margin note or on a small box
while the mouse is over the anchor, or while the document is being
loaded. Another reason is that documents that are not marked up text,
such as graphics, plain text and Gopher menus, do not have titles. The
TITLE attribute can be used to provide a title to such documents. When
using the TITLE attribute, the title should be valid and unique for the



Berners-Lee, Connolly FORMFEED[Page 32]





INTERNET DRAFT May 1985


destination document.



REL

The REL attribute gives the relationship(s) described by the hyper-
text link from the anchor to the target. The value is a whitespace-
separated list of relationship names. Relationship names and their
semantics will be registered by the W3 Consortium. The default rela-
tionship is void. The REL attribute is only used when the HREF
attribute is present.



REV

The REV attribute is the same as the REL attribute, but the seman-
tics of the link type 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

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



METHODS

The METHODS attributes of anchors and links provide information
about the functions that the user may perform on an object. These are
more accurately given by the HTTP protocol when it is used, but it may,
for similar reasons as for the TITLE attribute, be useful to include the
information in advance in the link. For example, the HTML interpreter
may chose a different rendering as a function of the methods allowed;
for example, something that is searchable may get a different icon.

The value of the METHODS attribute is a whitespace-separated list
of HTTP methods supported by the object for public use.







Berners-Lee, Connolly FORMFEED[Page 33]





INTERNET DRAFT May 1985


9. Block Structuring Elements

The following elements may be included in the body of an HTML docu-
ment:



9.1. Paragraph

...

Level 0

The Paragraph element indicates a paragraph. The exact indenta-
tion, leading space, etc. of a paragraph is not defined and may be a
function of other tags, style sheets, etc.

Typically, paragraphs are surrounded by a vertical space of one
line or half a line. This is typically not the case within the Address
element and is never the case within the Preformatted Text element.
With some HTML interpreters, the first line in a paragraph is indented.

Example of use:





This Heading Precedes the Paragraph




This is the text of the first paragraph.


This is the text of the second paragraph. Although you do not
need to start paragraphs on new lines, maintaining this
convention facilitates document maintenance.




This is the text of a third paragraph.







9.2. Preformatted Text

 ...  

Level 0

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

The

 tag may be used with the optional WIDTH attribute.  The


WIDTH attribute specifies the maximum number of characters for a line


and allows the HTML interpreter to select a suitable font and indenta-


tion.  If the WIDTH attribute is not present, a width of 80 characters


is assumed.  Where the WIDTH attribute is supported, widths of 40, 80


and 132 characters should be presented optimally, with other widths


being rounded up.

















Berners-Lee, Connolly                                  FORMFEED[Page 34]

















INTERNET DRAFT                                                  May 1985








     Within preformatted text:








o    Line breaks within the text are rendered as a move to the beginning


     of the next line.








o    The 
 tag should not be used@@.  If found, it should be rendered


     as a move to the beginning of the next line.








o    Anchor elements and character highlighting elements may be used.








o    Elements that define paragraph formatting (headings, address, etc.)


     must not be used.








o    The horizontal tab character (encoded in US-ASCII and ISO-8859-1 as


     decimal 9) must be interpreted as the smallest positive nonzero


     number of spaces which will leave the number of characters so far


     on the line as a multiple of 8.  Its use is not recommended how-


     ever.





     References





     Example of use:











     


     This is an example line.


     











     Within








-----------


References to the ``beginning of a new line'' do not imply


that the renderer is forbidden from using a constant left


indent for rendering preformatted text.  The left indent may


be constrained by the width required.


Within a Preformatted Text element, the constraint that the


rendering must be on a fixed horizontal character pitch may


limit or prevent the ability of the HTML interpreter to


faithfully render character formatting elements.











Berners-Lee, Connolly                                  FORMFEED[Page 35]

















INTERNET DRAFT                                                  May 1985








9.3.  Address 
 ...  
 Level 0





     The Address element specifies such information as address, signa-


ture and authorship, often at the top or bottom of a document.





     Typically, an Address is rendered in an italic typeface and may be


indented.  The Address element implies a paragraph break before and


after.





     Example of use:











     



     Newsletter editor



     J.R. Brown



     JimquickPost News, Jumquick, CT 01234



     Tel (123) 456 7890


     

















9.4.  Blockquote 
 ...  
 Level 0





     The Blockquote element is used to contain text quoted from another


source.





     A typical rendering might be a slight extra left and right indent,


and/or italic font.  The Blockquote element causes a paragraph break,


and typically provides space above and below the quote.





     Single-font rendition may reflect the quotation style of Internet


mail by putting a vertical line of graphic characters, such as the


greater than symbol (>), in the left margin.





     Example of use:











     I think the poem ends


     



     
Soft you now, the fair Ophelia. Nymph, in thy orisons, be all


     my sins remembered.


     


     but I am not sure.














Berners-Lee, Connolly                                  FORMFEED[Page 36]

















INTERNET DRAFT                                                  May 1985




















9.5.  Headings 
 ...  
 through 
 ...  
 Level 0





     HTML defines six levels of heading.  A Heading element implies all


the font changes, paragraph breaks before and after, and white space


necessary to render the heading.





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





     Example of use:











     
This is a heading


     Here is some text


     
Second level heading


     Here is some more text.











     The rendering of headings is determined by the HTML interpreter,


but typical renderings are:








 ...  


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


     below.








 ...  


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


     below.








 ...  


     Italic, large font, slightly indented from the left margin.  One or


     two blank lines above and below.








 ...  


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


     below.




















Berners-Lee, Connolly                                  FORMFEED[Page 37]

















INTERNET DRAFT                                                  May 1985








 ...  


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








 ...  


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


     above.











     Although heading levels can be skipped (for example, from H1 to


H3), this practice is discouraged as skipping heading levels may produce


unpredictable results when generating other representations from HTML.











9.6.  List Elements





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











Definition List 
 ...  
 Level 0





     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 of use:











     



     
Term
This is the definition of the first term.


     
Term
This is the definition of the second term.


     











     If the DT term does not fit in the DT column (one third of the dis-


play area), it may be extended across the page with the DD section moved


to the next line, or it may be wrapped onto successive lines of the left


hand column.





     Single occurrences of a DT tag without a subsequent DD tag are


allowed, and have the same significance as if the DD tag had been pre-


sent with no text.














Berners-Lee, Connolly                                  FORMFEED[Page 38]

















INTERNET DRAFT                                                  May 1985








     The opening list tag must be DL and must be immediately followed by


the first term (DT).





     The definition list type can take the COMPACT attribute, which sug-


gests that a compact rendering be used, because the list items are small


and/or the entire list is large.





     Unless you provide the COMPACT attribute, the HTML interpreter may


leave white space between successive DT, DD pairs.  The COMPACT


attribute may also reduce the width of the left-hand (DT) column.





     If using the COMPACT attribute, the opening list tag must be DL


COMPACT, which must be immediately followed by the first DT tag:











     



     
Term
This is the first definition in compact format.


     
Term
This is the second definition in compact format.


     

















Directory List  ...   Level 0





     A Directory List element is used to present a list of items con-


taining up to 20 characters each.  Items in a directory list may be


arranged in columns, typically 24 characters wide.  If the HTML inter-


preter can optimize the column width as function of the widths of indi-


vidual elements, so much the better.





     A directory list must begin with the DIR tag which is immediately


followed by a LI (list item) tag:











     


     
A-H
I-M


     
M-R
S-Z


     





























Berners-Lee, Connolly                                  FORMFEED[Page 39]

















INTERNET DRAFT                                                  May 1985








Menu List  ...   Level 0





     A menu list is a list of items with typically one line per item.


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





     A menu list must begin with a MENU tag which is immediately fol-


lowed by a LI (list item) tag:











     


     
First item in the list.


     
Second item in the list.


     
Third item in the list.


     

















Ordered List 
 ...  
 Level 0





     The Ordered List element is used to present a numbered list of


items, sorted by sequence or order of importance.





     An ordered list must begin with the OL tag which is immediately


followed by a LI (list item) tag:











     



     
Click the Web button to open the Open the URI window.


     
Enter the URI number in the text field of the Open URI


     window. The Web document you specified is displayed.


     
Click highlighted text to move from one link to another.


     











     The Ordered List element can take the COMPACT attribute, which sug-


gests that a compact rendering be used.











Unordered List 
 ...  
 Level 0





     The Unordered List element is used to present a list of items which


is typically separated by white space and/or marked by bullets.











Berners-Lee, Connolly                                  FORMFEED[Page 40]

















INTERNET DRAFT                                                  May 1985








     An unordered list must begin with the UL tag which is immediately


followed by a LI (list item) tag:











     



     
First list item


     
Second list item


     
Third list item


     





























































































































Berners-Lee, Connolly                                  FORMFEED[Page 41]

















INTERNET DRAFT                                                  May 1985








10.  Form-based Input Elements





     Forms are created by placing input fields within paragraphs, pre-


formatted/literal text, and lists.  This gives considerable flexibility


in designing the layout of forms.





     The following elements are used to create forms:








FORM


     A form within a document.








INPUT


     One input field.








OPTION


     One option within a Select element.








SELECT


     A selection from a finite set of options.








TEXTAREA


     A multi-line input field.











     Each variable field is defined by an Input, Textarea, or Option


element and must have an NAME attribute to identify its value in the


data returned when the form is submitted.





     Example of use (a questionnaire form):











     
Sample Questionnaire


     
Please fill out this questionnaire:


     



     
Your name: 


     
Male 


     
Female 


     
Number in family: 


     
Cities in which you maintain a residence:


     



     
Kent 











Berners-Lee, Connolly                                  FORMFEED[Page 42]

















INTERNET DRAFT                                                  May 1985








     
Miami 


     
Other 


     


     Nickname: 


     
Thank you for responding to this questionnaire.


     
 


     











     In the example above, the P and UL tags have been used to lay out


the text and input fields.  The HTML interpreter is responsible for han-


dling which field will currently get keyboard input.





     Many platforms have existing conventions for forms, for example,


using Tab and Shift keys to move the keyboard focus forwards and back-


wards between fields, and using the Enter key to submit the form.  In


the example, the SUBMIT and RESET buttons are specified explicitly with


special purpose fields.  The SUBMIT button is used to e-mail the form or


send its contents to the server as specified by the ACTION attribute,


while RESET resets the fields to their initial values.  When the form


consists of a single text field, it may be appropriate to leave such


buttons out and rely on the Enter key.





     The Input element is used for a large variety of types of input


fields.





     To let users enter more than one line of text, use the Textarea


element.





     The radio button and checkbox types of input field can be used to


specify multiple choice forms in which every alternative is visible as


part of the form.  An alternative is to use the Select element which is


typically rendered in a more compact fashion as a pull down combo list.











10.1.  Form 
 ...  
 Level 2





     The Form element is used to delimit a data input form.  There can


be several forms in a single document, but the Form element can't be


nested.





     The ACTION attribute is a URI specifying the location to which the


contents of the form is submitted to elicit a response.  If the ACTION


attribute is missing, the URI of the document itself is assumed.  The


way data is submitted varies with the access protocol of the URI, and


with the values of the METHOD and ENCTYPE attributes.











Berners-Lee, Connolly                                  FORMFEED[Page 43]

















INTERNET DRAFT                                                  May 1985








     In general:








o    the METHOD attribute selects variations in the protocol.








o    the ENCTYPE attribute specifies the format of the submitted data in


     case the protocol does not impose a format itself.





     The Level 2 specification defines@@ and requires support for the


HTTP access protocol only.





     When the ACTION attribute is set to an HTTP URL, the METHOD


attribute must be set to an HTTP method [HTTP].  The default method is


GET, although for many applications the POST method is preferred.  With


the POST method, the ENCTYPE attribute is a media type specifying the


format of the posted data;  the default is ``application/x-www-form-


urlencoded''.





     The submitted contents of the form logically consist of name/value


pairs.  The names are usually equal to the NAME attributes of the vari-


ous interactive elements in the form.





     The











10.2.  Input  Level 2





     The Input element represents a field whose contents may be edited


by the user.





     Attributes of the Input element:








ALIGN


     Vertical alignment of the image.  For use only with TYPE=IMAGE.


     The possible values are exactly the same as for the ALIGN attribute


-----------


The names are not guaranteed to be unique keys, nor are the


names of form elements required to be distinct.  The values


encode the user's input to the corresponding interactive


elements.  Fields with null values may be omitted from the


returned list of name/value pairs, whereas those with non-


null values should be included (even if the value was not


altered by the user).  In particular, unselected radio but-


tons and checkboxes should be excluded from the contents


list.











Berners-Lee, Connolly                                  FORMFEED[Page 44]

















INTERNET DRAFT                                                  May 1985








     of the image element.








CHECKED


     Indicates that a checkbox or radio button is selected.  Unselected


     checkboxes and radio buttons do not return name/value pairs when


     the form is submitted.








MAXLENGTH


     Indicates the maximum number of characters that can be entered into


     a text field.  This can be greater than specified by the SIZE


     attribute, in which case the field will scroll appropriately.  The


     default number of characters is unlimited.








NAME


     Symbolic name used when transferring the form's contents.  The NAME


     attribute is required for most input types and is normally used to


     provide a unique identifier for a field, or for a logically related


     group of fields.








SIZE


     Specifies the size or precision of the field according to its type.


     For example, to specify a field with a visible width of 24 charac-


     ters:











          INPUT TYPE=text SIZE="24"














SRC  A URI specifying an image.  For use only with TYPE=IMAGE.








TYPE


     Defines the type of data the field accepts.  Defaults to free text.


     Several types of fields can be defined with the type attribute:








CHECKBOX


     Used for simple Boolean attributes, or for attributes that can take


     multiple values at the same time.  The latter is represented by a


     number of checkbox fields each of which has the same name.  Each


     selected checkbox generates a separate name/value pair in the











Berners-Lee, Connolly                                  FORMFEED[Page 45]

















INTERNET DRAFT                                                  May 1985








     submitted data, even if this results in duplicate names.  The


     default value for checkboxes is ``on''.








HIDDEN


     No field is presented to the user, but the content of the field is


     sent with the submitted form.  This value may be used to transmit


     state information about client/server interaction.








IMAGE


     An image field upon which you can click with a pointing device,


     causing the form to be immediately submitted.  The coordinates of


     the selected point are measured in pixel units from the upper-left


     corner of the image, and are returned (along with the other con-


     tents of the form) in two name/value pairs.  The x-coordinate is


     submitted under the name of the field with ``.x'' appended, and the


     y-coordinate is submitted under the name of the field with ``.y''


     appended.  Any VALUE attribute is ignored.  The image itself is


     specified by the SRC attribute, exactly as for the Image element.





     In








PASSWORD


     The same as the TEXT attribute, except that text is not displayed


     as it is entered.








RADIO


     Used for attributes that accept a single value from a set of alter-


     natives.  Each radio button field in the group should be given the


     same name.  Only the selected radio button in the group generates a


     name/value pair in the submitted data.  Radio buttons require an


     explicit VALUE attribute.








RESET


     A button that when pressed resets the form's fields to their speci-


     fied initial values.  The label to be displayed on the button may


     be specified just as for the SUBMIT button.








SUBMIT


     A button that when pressed submits the form.  You can use the VALUE


-----------


In a future version of the HTML specification, the IMAGE


functionality may be folded into an enhanced SUBMIT field.











Berners-Lee, Connolly                                  FORMFEED[Page 46]

















INTERNET DRAFT                                                  May 1985








     attribute to provide a non-editable label to be displayed on the


     button.  The default label is application-specific.  If a SUBMIT


     button is pressed in order to submit the form, and that button has


     a NAME attribute specified, then that button contributes a


     name/value pair to the submitted data.  Otherwise, a SUBMIT button


     makes no contribution to the submitted data.








TEXT


     Used for a single line text entry fields.  Use in conjunction with


     the SIZE and MAXLENGTH attributes.  Use the Textarea element for


     text fields which can accept multiple lines.








VALUE


     The initial displayed value of the field, if it displays a textual


     or numerical value;  or the value to be returned when the field is


     selected, if it displays a Boolean value.  This attribute is


     required for radio buttons.

















10.3.  Option  Level 2





     The Option element can only occur within a Select element.  It rep-


resents one choice, and can take these attributes:








SELECTED


     Indicates that this option is initially selected.








VALUE


     When present indicates the value to be returned if this option is


     chosen.  The returned value defaults to the contents of the Option


     element.











     The contents of the Option element is presented to the user to rep-


resent the option.  It is used as a returned value if the VALUE


attribute is not present.























Berners-Lee, Connolly                                  FORMFEED[Page 47]

















INTERNET DRAFT                                                  May 1985








10.4.  Select  ...   Level 2





     The Select element allows the user to chose one of a set of alter-


natives described by textual labels.  Every alternative is represented


by the Option element.  Attributes are:








MULTIPLE


     The MULTIPLE attribute is needed when users are allowed to make


     several selections, e.g.  SELECT MULTIPLE.








NAME


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








SIZE


     Specifies the number of visible items.  If this is greater than


     one, then the resulting form control will be a list.











     The Select element is typically rendered as a pull down or pop-up


list.  For example:











     


     Vanilla


     Strawberry


     Rum and Raisin


     Peach and Orange


     











     If no option is initially marked as selected, then the first item


listed is selected.











10.5.  Text Area  ...   Level 2





     The Textarea element lets users enter more than one line of text.


For example:




















Berners-Lee, Connolly                                  FORMFEED[Page 48]

















INTERNET DRAFT                                                  May 1985








     <br>
     HaL Computer Systems
<br>
     1315 Dell Avenue
<br>
     Campbell, California 95008
<br>
     











     The text up to the end tag () is used to initialize the


field's value.  This end tag is always required even if the field is


initially blank.  When submitting a form, lines in a TEXTAREA should be


terminated using CRLF.





     In a typical rendering, the ROWS and COLS attributes determine the


visible dimension of the field in characters.  The field is rendered in


a fixed-width font.  HTML interpreters should allow text to extend


beyond these limits by scrolling as needed.





     In

































































-----------


In the initial design for forms, multi-line text fields were


supported by the Input element with TYPE=TEXT.  Unfortu-


nately, this causes problems for fields with long text val-


ues.  SGML's default (Reference Quantity Set) limits the


length of attribute literals to only 240 characters.  The


HTML 2.0 SGML declaration increases the limit to 1024 char-


acters.











Berners-Lee, Connolly                                  FORMFEED[Page 49]

















INTERNET DRAFT                                                  May 1985








11.  HTML Public Text








11.1.  HTML DTD





     This is the Document Type Definition for the HyperText Markup Lan-


guage.











     


     
             "-//IETF//DTD HTML 2.0//EN"


             -- Typical usage:


                 


                 


                 ...


                 


             --


             >


     


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


     -->


     
             


     ]]>


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


     -->


     









Berners-Lee, Connolly                                  FORMFEED[Page 50]

















INTERNET DRAFT                                                  May 1985








     -- Use this feature test entity to validate that a


        document uses no highlighting tags, which may be


        ignored on minimal implementations.


     -->


     
             -- Use this feature test entity to validate that a document


                contains no forms, which may not be supported in minimal


                implementations


             -->


     


     
             -- meaning an internet media type


                (aka MIME content type, as per RFC1521)


             -->


     
             -- as per HTTP specification, in progress


             -->


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


             -->


     


     


     


     


     
       "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML">


     %ISOlat1;


     


     


     


     


     


     


     
       -- one to one mapping        -->


     
       -- context-sensitive mapping -->


     
       -- generated text prefix     -->


     
       -- generated text suffix     -->


     
       -- suspend transform process -->


     


     
     


     


     


     


     
             %SDAFORM; "Lit"


             >


     
             %SDAFORM; "B"


             >


     
             %SDAFORM; "It"


             >


     


     


     


     


     


     


     


     


     


     


     


     ]]>


     


     


     
             %SDAPREF; "&#RE;"


             >











Berners-Lee, Connolly                                  FORMFEED[Page 52]

















INTERNET DRAFT                                                  May 1985








     


     


     
             


     ]]>


     


     
             -- a list of these will be specified at a later date -->


     
             "REL %linkType #IMPLIED


             REV %linkType #IMPLIED


             URN CDATA #IMPLIED


             TITLE CDATA #IMPLIED


             METHODS NAMES #IMPLIED


             ">


     
             
             -- 
Heading


                     is preferred to


                
Heading


             -->


     ]]>


     


     


     
             HREF %URI #IMPLIED


             NAME %linkName #IMPLIED


             %linkExtraAttributes;


             %SDAPREF; ""


             >


     


     


     


     


     


     


     


     


     


     


     
             SRC %URI;  #REQUIRED


             ALT CDATA #IMPLIED


             ALIGN (top|middle|bottom) #IMPLIED


             ISMAP (ISMAP) #IMPLIED


             %SDAPREF; "#AttVal(Alt)"


             >


     











Berners-Lee, Connolly                                  FORMFEED[Page 53]

















INTERNET DRAFT                                                  May 1985








     


     


     


     


     


     


     
             %SDAFORM; "Para"


             >


     


     


     


     
             %SDAPREF; "&#RE;&#RE;"


             >


     


     


     
             %SDAFORM; "H1"


             >


     
             %SDAFORM; "H2"


             >


     
             %SDAFORM; "H3"


             >


     
             %SDAFORM; "H4"


             >


     
             %SDAFORM; "H5"


             >


     
             %SDAFORM; "H6"


             >


     


     


     


     


     


     


     


     
             


     ]]>


     


     
             











Berners-Lee, Connolly                                  FORMFEED[Page 54]

















INTERNET DRAFT                                                  May 1985








     ]]>


     


     
             | %preformatted


             | %block.forms">


     


     


     


     
             WIDTH NUMBER #implied


             %SDAFORM; "Lit"


             >


     


     


     
     
             -- historical, non-conforming parsing mode where


                the only markup signal is the end tag


                in full


             -->


     


     
             %SDAFORM; "Lit"


             %SDAPREF; "Example:&#RE;"


             >


     
             %SDAFORM; "Lit"


             %SDAPREF; "Listing:&#RE;"


             >


     


     


     


     


     
             %SDAFORM; "Lit"


             >


     ]]>


     


     


     
             COMPACT (COMPACT) #IMPLIED


             %SDAFORM; "List"


             %SDAPREF; "Definition List:"


             >


     


     
             %SDAFORM; "Term"


             >











Berners-Lee, Connolly                                  FORMFEED[Page 55]

















INTERNET DRAFT                                                  May 1985








     


     
             %SDAFORM; "LItem"


             >


     


     


     


     


     


     
             COMPACT (COMPACT) #IMPLIED


             %SDAFORM; "List"


             >


     
             COMPACT (COMPACT) #IMPLIED


             %SDAFORM; "List"


             >


     


     


     


     


     


     
             COMPACT (COMPACT) #IMPLIED


             %SDAFORM; "List"


             %SDAPREF; "Directory"


             >


     
             COMPACT (COMPACT) #IMPLIED


             %SDAFORM; "List"


             %SDAPREF; "Menu"


             >


     


     


     


     


     


     
             %SDAFORM; "LItem"


             >


     


     


     
     
     -- 
Heading


        
Text ...


     is preferred to


        
Heading











Berners-Lee, Connolly                                  FORMFEED[Page 56]

















INTERNET DRAFT                                                  May 1985








        Text ...


     -->


     ]]>


     
      HR | ADDRESS)*">


     


     


     


     
             %SDAFORM; "BQ"


             >


     


     


     
             %SDAFORM; "Lit"


             %SDAPREF; "Address:&#RE;"


             >


     


     


     
     


     
             ACTION %URI #IMPLIED


             METHOD (%HTTP-Method) GET


             ENCTYPE %Content-Type; "application/x-www-form-urlencoded"


             %SDAPREF; "Form:"


             %SDASUFF; "Form End."


             >


     


     


     


     


     
                             RADIO | SUBMIT | RESET |


                             IMAGE | HIDDEN )">


     


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


     >


     











Berners-Lee, Connolly                                  FORMFEED[Page 57]

















INTERNET DRAFT                                                  May 1985








     


     


     


     


     


     


     


     


     


     
             NAME CDATA #REQUIRED


             SIZE NUMBER #IMPLIED


             MULTIPLE (MULTIPLE) #IMPLIED


             %SDAFORM; "List"


             %SDAPREF;


             "Select #AttVal(Multiple)"


     >


     


     


     


     


     


     
             SELECTED (SELECTED) #IMPLIED


             VALUE CDATA #IMPLIED


             %SDAFORM; "LItem"


             %SDAPREF;


             "Option: #AttVal(Value) #AttVal(Selected)"


     >


     


     


     


     


     
             NAME CDATA #REQUIRED


             ROWS NUMBER #REQUIRED


             COLS NUMBER #REQUIRED


             %SDAFORM; "Para"


             %SDAPREF; "Input Text -- #AttVal(Name): "


             >


     


     


     


     


     ]]>


     


     
     











Berners-Lee, Connolly                                  FORMFEED[Page 58]

















INTERNET DRAFT                                                  May 1985








     ]]>


     


     
      (%head.extra)">


     


     


     


     
             %SDAFORM; "Ti"    >


     


     


     
             HREF %URI #REQUIRED


             %linkExtraAttributes;


             %SDAPREF; "Linked to : #AttVal (TITLE) (URN) (HREF)>"    >


     


     


     


     


     


     


     


     


     
             %SDAPREF;


        "[Document is indexed/searchable.]">


     


     


     
             HREF %URI; #REQUIRED     >


     


     


     


     
             N %linkName #REQUIRED     >


     


     


     


     
             HTTP-EQUIV  NAME    #IMPLIED


             NAME        NAME    #IMPLIED


             CONTENT     CDATA   #REQUIRED    >


     


     


     


     


     


     









Berners-Lee, Connolly                                  FORMFEED[Page 59]

















INTERNET DRAFT                                                  May 1985








             


     ]]>


     


     


     


     
             %version.attr;


             %SDAFORM; "Book"


             >


     

















11.2.  SGML Declaration for HTML





     This is the SGML Declaration for HyperText Markup Language (HTML)


as used by the World Wide Web (WWW) application:











     
     --


     SGML Declaration for HyperText Markup Language (HTML).


     --


     CHARSET


              BASESET  "ISO 646:1983//CHARSET


                        International Reference Version


                        (IRV)//ESC 2/5 4/0"


              DESCSET  0   9   UNUSED


                       9   2   9


                       11  2   UNUSED


                       13  1   13


                       14  18  UNUSED


                       32  95  32


                       127 1   UNUSED


          BASESET   "ISO Registration Number 100//CHARSET


                     ECMA-94 Right Part of


                     Latin Alphabet Nr. 1//ESC 2/13 4/1"


              DESCSET  128  32   UNUSED


                       160  96    32


     CAPACITY        SGMLREF


                     TOTALCAP        150000


                     GRPCAP          150000


     SCOPE    DOCUMENT


     SYNTAX


              SHUNCHAR CONTROLS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16











Berners-Lee, Connolly                                  FORMFEED[Page 60]

















INTERNET DRAFT                                                  May 1985








      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


         --


     >


     

















11.3.  Sample SGML Open Entity Catalog for HTML





     The SGML standard describes an ``entity manager'' as the portion or


component of an SGML system that maps SGML entities into the actual


storage model (e.g., the file system).  The standard itself does not


define a particular mapping methodology or notation.





     To assist the interoperability among various SGML tools and sys-


tems, the SGML Open consortium has passed a technical resolution that


defines a format for an application- independent entity catalog that


maps external identifiers and/or entity names to file names.





     Each entry in the catalog associates a storage object identifier


(such as a file name) with information about the external entity that


appears in the SGML document.  In addition to entries that associate


public identifiers, a catalog entry can associate an entity name with a


storage object indentifier.  For example, the following are possible


catalog entries:














     -- catalog: SGML Open style entity catalog for HTML --


     -- $Id: catalog,v 1.2 1994/11/30 23:45:18 connolly Exp $ --


     -- Ways to refer to Level 2: most general to most specific --


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











Berners-Lee, Connolly                                  FORMFEED[Page 62]

















INTERNET DRAFT                                                  May 1985








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

















11.4.  Character Entity Sets





     The following entity names are used in HTML, always prefixed by


ampersand (&) and followed by a semicolon@@ as shown.  They represent


particular graphic characters which have special meanings in places in


the markup, or may not be part of the character set available to the


writer.











Numeric and Special Graphic Entity Set





     The following table lists each of the supported characters speci-


fied in the Numeric and Special Graphic entity set, along with its name,


syntax for use, and description.  This list is derived from ISO Standard


8879:1986//ENTITIES Numeric and Special Graphic//EN.  However, HTML does


not provide support for the entire entity set - only the entities listed


below are supported.











     GLYPH   NAME      SYNTAX       DESCRIPTION


     <       lt    <       Less than sign


     >       gt    >       Greater than sign


     &       amp   &     Ampersand


     "       quot  "   Double quote sign

















ISO Latin 1 Character Entity Set





     The following public text lists each of the characters specified in


the Added Latin 1 entity set, along with its name, syntax for use, and











Berners-Lee, Connolly                                  FORMFEED[Page 63]

















INTERNET DRAFT                                                  May 1985








description.  This list is derived from ISO Standard 8879:1986//ENTITIES


Added Latin 1//EN.  HTML includes the entire entity set.











     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     











Berners-Lee, Connolly                                  FORMFEED[Page 64]

















INTERNET DRAFT                                                  May 1985








     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     


     






























































Berners-Lee, Connolly                                  FORMFEED[Page 65]

















INTERNET DRAFT                                                  May 1985








12.  Glossary








character


     An atom of information, for example a letter or a digit.  Graphic


     characters have associated glyphs, where as control characters have


     associated processing semantics.








character encoding scheme


     A function whose domain is the set of sequences of octets, and


     whose range is the set of sequences of characters from a character


     repertoire;  that is, a sequence of octets and a character encoding


     scheme determines a sequence of characters.








character repertoire


     A finite set of characters;  e.g.  the range of a coded character


     set.








code position


     An integer.  A coded character set and a code position from its


     domain determine a character.








coded character set


     A function whose domain is a subset of the integers and whose range


     is a character repertoire.  That is, for some set of integers (usu-


     ally of the form {0, 1, 2, ..., N} ), a coded character set and an


     integer in that set determine a character.  Conversely, a character


     and a character set determine the character's code position (or, in


     rare cases, a few code positions).








conforming HTML user agent


     A user agent that conforms to this specification in its processing


     of the Internet Media Type `text/html; version=2.0'.








data characters


     Characters other than markup, which make up the content of ele-


     ments.








DTD  document type definition.  @@ A collection of declarations (entity,


     element, attribute, link, map, etc.) in SGML syntax that defines


     the components and structures available for a class (type) of











Berners-Lee, Connolly                                  FORMFEED[Page 66]

















INTERNET DRAFT                                                  May 1985








     documents.  [SGML]








element


     @@A component of the hierarchical structure defined by the document


     type definition;  it is identified in a document instance by


     descriptive markup, usually a start-tag and an end- tag.  [SGML]








entity


     data with an associated notation or interpretation;  for example, a


     sequence of octets associated with an Internet Media Type.  [SGML]








HTML document


     An SGML document conforming to this document type definition.








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


     tions, and processing instructions.[SGML]








may  The implementation is not obliged to follow this in any way.








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 in its treatment


     of the Internet Media Type ``text/html;  level=0;  version=2.0''








must


     If this is not followed, the implementation does not conform to


     this specification.








SGML document


     A set of entities, including the document entity, which is a text


     entity that conforms to the grammar specified in the SGML stan-


     dard.[SGML]











Berners-Lee, Connolly                                  FORMFEED[Page 67]

















INTERNET DRAFT                                                  May 1985








shall


     If a document or user agent conflicts with this statement, it does


     not conform to this specification.








should


     If a document or user agent conflicts with this statement, undesir-


     able results may occur in practice even though the document or user


     agent conforms to this specification.








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


     ing, transmitted over the network or stored in a file.[SGML]








typical


     Typical rendering is described for many elements.  This is not a


     mandatory part of the specification but is given as guidance for


     designers and to help explain the uses for which the elements were


     intended.








URI  A Universal Resource Identifier is a formatted string that serves


     as an identifier for a resource, typcally on the Internet.  URIs


     are used in HTML to identify the destination of hypertext links,


     the source of in-line images, and the object of form actions.  URIs


     in common use include Uniform Resource Locators (URLs)[URL] and


     Relative URLs[RELURL].








user agent


     A component of a distributed system that presents an interface and


     processes requests on behalf of a user;  for example, a www browser


     or a mail user agent.








WWW  The World-Wide Web is a hypertext-based, distributed information


     system created by researchers at CERN in Switzerland.  Users may


     create, edit or browse hypertext documents.  `http://www.w3.org/'

















Berners-Lee, Connolly                                  FORMFEED[Page 68]

















INTERNET DRAFT                                                  May 1985








13.  Bibliography








[URI]


     T.  Berners-Lee.  ``Universal Resource Identifiers in WWW:  A Uni-


     fying Syntax for the Expression of Names and Addresses of Objects


     on the Network as used in the World- Wide Web.'' RFC 1630, CERN,


     June 1994.








[URL]


     T.  Berners-Lee, L.  Masinter, and M.  McCahill.  ``Uniform


     Resource Locators (URL).'' RFC 1738, CERN, Xerox PARC, University


     of Minnesota, October 1994.








[HTTP]


     T.  Berners-Lee, R.  T.  Fielding, and H.  Frystyk Nielsen.


     ``Hypertext Transfer Protocol - HTTP/1.0.'' Work in Progress


     (draft-ietf-http-v10-spec-00.ps), MIT, UC Irvine, CERN, March 1995.








[MIME]


     N.  Borenstein and N.  Freed.  ``MIME (Multipurpose Internet Mail


     Extensions) Part One:  Mechanisms for Specifying and Describing the


     Format of Internet Message Bodies.'' RFC 1521, Bellcore, Innosoft,


     September 1993.








[RELURL]


     R.  T.  Fielding.  ``Relative Uniform Resource Locators.''  Work in


     Progress (draft-ietf-uri- relative-url-06.txt), UC Irvine, March


     1995.








[GOLD90]


     C.  F.  Goldfarb.  ``The SGML Handbook.'' Y.  Rubinsky, Ed., Oxford


     University Press, 1990.








[IMEDIA]


     J.  Postel.  ``Media Type Registration Procedure.'' RFC 1590,


     USC/ISI, March 1994.








[IANA"]


     J.  Reynolds and J.  Postel.  ``Assigned Numbers.'' STD 2, RFC


     1700, USC/ISI, October 1994.











Berners-Lee, Connolly                                  FORMFEED[Page 69]

















INTERNET DRAFT                                                  May 1985








[SQ91]


     SoftQuad.  ``The SGML Primer.'' 3rd ed., SoftQuad Inc., 1991.








[US-ASCII]


     US-ASCII.  Coded Character Set - 7-Bit American Standard Code for


     Information Interchange.  Standard ANSI X3.4-1986, ANSI, 1986.








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








[SGML]


     ISO 8879.  Information Processing - Text and Office Systems - Stan-


     dard Generalized Markup Language (SGML), 1986.



















































































Berners-Lee, Connolly                                  FORMFEED[Page 70]

















INTERNET DRAFT                                                  May 1985








A.  Appendices These appendices are provided for informational reasons


only - they do not form a part of the HTML specification.











A.1.  The ISO-8859-1 Coded Character Set





     This list, sorted numerically, is derived from ISO-8859-1 8-bit


single-byte coded graphic character set:











     REFERENCE       DESCRIPTION


     � -    Unused


     	     Horizontal tab


     
     Line feed


      -    Unused


           Space


     !     Exclamation mark


     "     Quotation mark


     #     Number sign


     $     Dollar sign


     %     Percent sign


     &     Ampersand


     '     Apostrophe


     (     Left parenthesis


     )     Right parenthesis


     *     Asterisk


     +     Plus sign


     ,     Comma


     -     Hyphen


     .     Period (fullstop)


     /     Solidus (slash)


     0 - 9   Digits 0-9


     :     Colon


     ;     Semi-colon


     <     Less than


     =     Equals sign


     >     Greater than


     ?     Question mark


     @     Commercial at


     A - Z   Letters A-Z


     [     Left square bracket


     \     Reverse solidus (backslash)


     ]     Right square bracket


     ^     Caret


     _     Horizontal bar (underscore)


     `     Acute accent











Berners-Lee, Connolly                                  FORMFEED[Page 71]

















INTERNET DRAFT                                                  May 1985








     a - z  Letters a-z


     {   Left curly brace


     |   Vertical bar


     }   Right curly brace


     ~   Tilde


      -   Unused


     ¡   Inverted exclamation


     ¢   Cent sign


     £   Pound sterling


     ¤   General currency sign


     ¥   Yen sign


     ¦   Broken vertical bar


     §   Section sign


     ¨   Umlaut (dieresis)


     ©   Copyright


     ª   Feminine ordinal


     «   Left angle quote, guillemotleft


     ¬   Not sign


     ­   Soft hyphen


     ®   Registered trademark


     ¯   Macron accent


     °   Degree sign


     ±   Plus or minus


     ²   Superscript two


     ³   Superscript three


     ´   Acute accent


     µ   Micro sign


     ¶   Paragraph sign


     ·   Middle dot


     ¸   Cedilla


     ¹   Superscript one


     º   Masculine ordinal


     »   Right angle quote, guillemotright


     ¼   Fraction one-fourth


     ½   Fraction one-half


     ¾   Fraction three-fourths


     ¿   Inverted question mark


     À   Capital A, grave accent


     Á   Capital A, acute accent


     Â   Capital A, circumflex accent


     Ã   Capital A, tilde


     Ä   Capital A, dieresis or umlaut mark


     Å   Capital A, ring


     Æ   Capital AE dipthong (ligature)


     Ç   Capital C, cedilla


     È   Capital E, grave accent


     É   Capital E, acute accent


     Ê   Capital E, circumflex accent











Berners-Lee, Connolly                                  FORMFEED[Page 72]

















INTERNET DRAFT                                                  May 1985








     Ë   Capital E, dieresis or umlaut mark


     Ì   Capital I, grave accent


     Í   Capital I, acute accent


     Î   Capital I, circumflex accent


     Ï   Capital I, dieresis or umlaut mark


     Ð   Capital Eth, Icelandic


     Ñ   Capital N, tilde


     Ò   Capital O, grave accent


     Ó   Capital O, acute accent


     Ô   Capital O, circumflex accent


     Õ   Capital O, tilde


     Ö   Capital O, dieresis or umlaut mark


     ×   Multiply sign


     Ø   Capital O, slash


     Ù   Capital U, grave accent


     Ú   Capital U, acute accent


     Û   Capital U, circumflex accent


     Ü   Capital U, dieresis or umlaut mark


     Ý   Capital Y, acute accent


     Þ   Capital THORN, Icelandic


     ß   Small sharp s, German (sz ligature)


     à   Small a, grave accent


     á   Small a, acute accent


     â   Small a, circumflex accent


     ã   Small a, tilde


     ä   Small a, dieresis or umlaut mark


     å   Small a, ring


     æ   Small ae dipthong (ligature)


     ç   Small c, cedilla


     è   Small e, grave accent


     é   Small e, acute accent


     ê   Small e, circumflex accent


     ë   Small e, dieresis or umlaut mark


     ì   Small i, grave accent


     í   Small i, acute accent


     î   Small i, circumflex accent


     ï   Small i, dieresis or umlaut mark


     ð   Small eth, Icelandic


     ñ   Small n, tilde


     ò   Small o, grave accent


     ó   Small o, acute accent


     ô   Small o, circumflex accent


     õ   Small o, tilde


     ö   Small o, dieresis or umlaut mark


     ÷   Division sign


     ø   Small o, slash


     ù   Small u, grave accent


     ú   Small u, acute accent











Berners-Lee, Connolly                                  FORMFEED[Page 73]

















INTERNET DRAFT                                                  May 1985








     û   Small u, circumflex accent


     ü   Small u, dieresis or umlaut mark


     ý   Small y, acute accent


     þ   Small thorn, Icelandic


     ÿ   Small y, dieresis or umlaut mark

















A.2.  Obsolete Features





     This section describes elements that are no longer part of HTML.


Client implementors should implement these obsolete elements for compat-


ibility with previous versions of the HTML specification.











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











Highlighted Phrase Element 





     The Highlighted Phrase element should be ignored if not imple-


mented.  This element has been replaced by more meaningful elements (see


Section 8).





     Example of use:











     first highlighted phrasenon-


     highlighted textsecond highlighted phrase etc.

















Plain Text Element 
<br>

<br>
     The Plain Text element is used to terminates the HTML entity and to
<br>
indicate that what follows is not SGML which does not require parsing.
<br>

<br>

<br>

<br>
Berners-Lee, Connolly                                  FORMFEED[Page 74]
<br>

<br>

<br>

<br>

<br>

<br>
INTERNET DRAFT                                                  May 1985
<br>

<br>

<br>
Instead, an old HTTP convention specified that what followed was an
<br>
ASCII (MIME ``text/plain'') body.  Its presence is an optimization.
<br>
There is no closing tag.
<br>

<br>
     Example of use:
<br>

<br>

<br>

<br>
     <PLAINTEXT>
<br>
     0001 This is line one of a long listing
<br>
     0002 file from <ANY@HOST.INC.COM> which is sent
<br>

<br>

<br>

<br>

<br>

<br>
Example and Listing Elements <XMP> ...  </XMP> and <LISTING> ...
<br>
</LISTING>
<br>

<br>
     The Example and Listing elements have been replaced by the Prefor-
<br>
matted Text element (Section 10.2).
<br>

<br>
     These styles allow text of fixed-width characters to be embedded
<br>
absolutely as is into the document.  The syntax is:
<br>

<br>

<br>

<br>
     <LISTING> ... </LISTING>
<br>

<br>

<br>

<br>
     or
<br>

<br>

<br>

<br>
     <XMP> ... </XMP>
<br>

<br>

<br>

<br>
     The text between these tags is typically rendered in a monospaced
<br>
font so that any formatting done by character spacing on successive
<br>
lines will be maintained.
<br>

<br>
     Between the opening and closing tags:
<br>

<br>

<br>
o    The text may contain any ISO Latin-1 printable characters, expect
<br>
     for the end tag opener.  The Example and Listing elements have
<br>

<br>

<br>

<br>
Berners-Lee, Connolly                                  FORMFEED[Page 75]
<br>

<br>

<br>

<br>

<br>

<br>
INTERNET DRAFT                                                  May 1985
<br>

<br>

<br>
     historically used specifications which do not conform to SGML.
<br>
     Specifically, the text may contain ISO Latin printable characters,
<br>
     including the tag opener, as long it they does not contain the
<br>
     closing tag in full.
<br>

<br>

<br>
o    SGML does not support this form.  HTML interpreters may vary on how
<br>
     they interpret other tags within Example and Listing elements.
<br>

<br>

<br>
o    Line boundaries within the text are rendered as a move to the
<br>
     beginning of the next line, except for one immediately following a
<br>
     start tag or immediately preceding an end tag.
<br>

<br>

<br>
o    The horizontal tab character must be interpreted as the smallest
<br>
     positive nonzero number of spaces which will leave the number of
<br>
     characters so far on the line as a multiple of 8.  Its use is not
<br>
     recommended.
<br>

<br>
     The Listing element is rendered so that at least 132 characters fit
<br>
on a line.  The Example element is rendered to that at least 80 charac-
<br>
ters fit on a line but is otherwise identical to the Listing element.
<br>

<br>

<br>

<br>
A.3.  Proposed Features
<br>

<br>
     This section describes proposed HTML elements and entities that are
<br>
not currently supported under HTML Levels 0, 1, or 2@@, but may be sup-
<br>
ported in the future.
<br>

<br>

<br>

<br>
Additional Character Entities
<br>

<br>
     To indicate special characters, HTML uses entity or numeric repre-
<br>
sentations.  Additional character presentations are proposed:
<br>

<br>

<br>

<br>
     CHARACTER                  REPRESENTATION
<br>
     Non-breaking space           &nbsp;
<br>
     Soft-hyphen            &shy;
<br>
     Registered               &reg;
<br>
     Copyright                  &copy;
<br>

<br>

<br>

<br>

<br>

<br>
Berners-Lee, Connolly                                  FORMFEED[Page 76]
<br>

<br>

<br>

<br>

<br>

<br>
INTERNET DRAFT                                                  May 1985
<br>

<br>

<br>
Defining Instance Element <DFN> ...  </DFN>
<br>

<br>
     The Defining Instance element indicates the defining instance of a
<br>
term.  The typical rendering is bold or bold italic.  This element is
<br>
not widely supported.
<br>

<br>

<br>

<br>
Strike Element <STRIKE> ...  </STRIKE>
<br>

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

<br>

<br>

<br>
Underline Element <U> ...  </U>
<br>

<br>
     The Underline element is proposed to indicate that the text should
<br>
be rendered as underlined.  This proposed tag is not supported by all
<br>
HTML interpreters.
<br>

<br>
     Example of use:
<br>

<br>

<br>

<br>
     The text <U>shown here</U> is rendered in the
<br>
     document as underlined.
<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>
Berners-Lee, Connolly                                  FORMFEED[Page 77]
<br>

<br>

<br>

<br>

<br>

<br>
INTERNET DRAFT                                                  May 1985
<br>

<br>

<br>
B.  Acknowledgments
<br>

<br>
     The HTML document type was designed by Tim Berners-Lee at CERN as
<br>
part of the 1990 World Wide Web project.  In 1992, Dan Connolly wrote
<br>
the HTML Document Type Definition (DTD) and a brief HTML specification.
<br>

<br>
     Since 1993, a wide variety of Internet participants have con-
<br>
tributed to the evolution of HTML, which has included the addition of
<br>
in-line images introduced by the NCSA Mosaic software for WWW.  Dave
<br>
Raggett played an important role in deriving the FORMS material from the
<br>
HTML+ specification.
<br>

<br>
     Dan Connolly and Karen Olson Muldrow rewrote the HTML Specification
<br>
in 1994.  The document was then edited by the HTML working group as a
<br>
whole, with updates being made by Eric Schieler, Mike Knezovich, and
<br>
Eric W.  Sink at Spyglass, Inc.  Finally, Roy Fielding restructured the
<br>
entire draft into its current form.
<br>

<br>
     Special thanks to the many people who have contributed to this
<br>
specification:
<br>

<br>
     Terry Allen Marc Andreessen
<br>

<br>
     Tim Berners-Lee Paul Burchard
<br>

<br>
     James Clark Daniel W.  Connolly
<br>

<br>
     Roy T.  Fielding Peter Flynn
<br>

<br>
     Jay Glicksman Paul Grosso
<br>

<br>
     Eduardo Gutentag Bill Hefley
<br>

<br>
     Chung-Jen Ho Mike Knezovich
<br>

<br>
     Tom Magliery Murray Maloney
<br>

<br>
     Larry Masinter Karen Olson Muldrow
<br>

<br>
     Bill Perry Dave Raggett
<br>

<br>
     E.  Corprew Reed Yuri Rubinsky
<br>

<br>
     Eric Schieler James L.  Seidman
<br>

<br>
     Eric W.  Sink Stuart Weibel
<br>

<br>

<br>

<br>

<br>

<br>
Berners-Lee, Connolly                                  FORMFEED[Page 78]
<br>

<br>

<br>

<br>

<br>

<br>
INTERNET DRAFT                                                  May 1985
<br>

<br>

<br>
     Chris Wilson Francois Yergeau
<br>

<br>

<br>

<br>
B.1.  Authors' Addresses
<br>

<br>

<br>
Tim Berners-Lee
<br>

<br>

<br>

<br>
          Director, W3 Consortium
<br>
          MIT Laboratory for Computer Science
<br>
          545 Technology Square
<br>
          Cambridge, MA 02139, U.S.A.
<br>
          Tel: +1 (617) 253 9670
<br>
          Fax: +1 (617) 258 8682
<br>
          Email: timbl@w3.org
<br>

<br>

<br>

<br>

<br>
Daniel W.  Connolly
<br>

<br>

<br>

<br>
          Research Technical Staff, W3 Consortium
<br>
          MIT Laboratory for Computer Science
<br>
          545 Technology Square
<br>
          Cambridge, MA 02139, U.S.A.
<br>
          Fax: +1 (617) 258 8682
<br>
          Email: connolly@w3.org
<br>
          URI: http://www.w3.org/hypertext/WWW/People/Connolly/
<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>
Berners-Lee, Connolly                                   FORMFEED[Page 0]
<br>

<br>

<br>

<br>

<br>

<br>
INTERNET DRAFT                                                  May 1985
<br>

<br>

<br>
                           Table of Contents
<br>

<br>

<br>

<br>
1    Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .   3
<br>

<br>
1.1      Scope . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
<br>

<br>
1.2      Conformance . . . . . . . . . . . . . . . . . . . . . . . .   3
<br>

<br>
Documents  . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
<br>

<br>
User Agents  . . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
<br>

<br>
2    HTML as an Application of SGML  . . . . . . . . . . . . . . . .   6
<br>

<br>
2.1      SGML Documents  . . . . . . . . . . . . . . . . . . . . . .   6
<br>

<br>
2.2      HTML Lexical Syntax . . . . . . . . . . . . . . . . . . . .   8
<br>

<br>
Data Characters  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
<br>

<br>
Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   9
<br>

<br>
Names  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  10
<br>

<br>
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  10
<br>

<br>
Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  12
<br>

<br>
Example HTML Document  . . . . . . . . . . . . . . . . . . . . . . .  12
<br>

<br>
3    HTML as an Internet Media Type  . . . . . . . . . . . . . . . .  14
<br>

<br>
3.1      text/html media type  . . . . . . . . . . . . . . . . . . .  14
<br>

<br>
3.2      HTML Document Representation  . . . . . . . . . . . . . . .  15
<br>

<br>
Undeclared Markup Error Handling . . . . . . . . . . . . . . . . . .  15
<br>

<br>
Conventional Representation of Newlines  . . . . . . . . . . . . . .  16
<br>

<br>
3.3      Security Considerations . . . . . . . . . . . . . . . . . .  16
<br>

<br>
4    Document Structure Elements . . . . . . . . . . . . . . . . . .  18
<br>

<br>
4.1      HTML Document Element . . . . . . . . . . . . . . . . . . .  18
<br>

<br>

<br>

<br>

<br>
Berners-Lee, Connolly                                   FORMFEED[Page i]
<br>

<br>

<br>

<br>

<br>

<br>
INTERNET DRAFT                                                  May 1985
<br>

<br>

<br>
4.2      Head  . . . . . . . . . . . . . . . . . . . . . . . . . . .  19
<br>

<br>
4.3      Body  . . . . . . . . . . . . . . . . . . . . . . . . . . .  19
<br>

<br>
4.4      Title . . . . . . . . . . . . . . . . . . . . . . . . . . .  19
<br>

<br>
4.5      Base  . . . . . . . . . . . . . . . . . . . . . . . . . . .  20
<br>

<br>
4.6      Isindex . . . . . . . . . . . . . . . . . . . . . . . . . .  20
<br>

<br>
4.7      Link  . . . . . . . . . . . . . . . . . . . . . . . . . . .  20
<br>

<br>
4.8      Meta  . . . . . . . . . . . . . . . . . . . . . . . . . . .  20
<br>

<br>
4.9      Nextid  . . . . . . . . . . . . . . . . . . . . . . . . . .  23
<br>

<br>
5    Character Content . . . . . . . . . . . . . . . . . . . . . . .  24
<br>

<br>
5.1      The ISO Latin 1 Character Repertoire  . . . . . . . . . . .  24
<br>

<br>
6    Data Elements . . . . . . . . . . . . . . . . . . . . . . . . .  25
<br>

<br>
6.1      Line Break  . . . . . . . . . . . . . . . . . . . . . . . .  25
<br>

<br>
6.2      Horizontal Rule . . . . . . . . . . . . . . . . . . . . . .  25
<br>

<br>
6.3      Image . . . . . . . . . . . . . . . . . . . . . . . . . . .  25
<br>

<br>
7    Character Format Elements . . . . . . . . . . . . . . . . . . .  28
<br>

<br>
7.1      Semantic Format Elements  . . . . . . . . . . . . . . . . .  28
<br>

<br>
Citation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  29
<br>

<br>
Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  29
<br>

<br>
Emphasis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  29
<br>

<br>
Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  29
<br>

<br>
Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  29
<br>

<br>
Strong . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  29
<br>

<br>
Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  29
<br>

<br>
7.2      Physical Format Elements  . . . . . . . . . . . . . . . . .  30
<br>

<br>

<br>

<br>

<br>
Berners-Lee, Connolly                                  FORMFEED[Page ii]
<br>

<br>

<br>

<br>

<br>

<br>
=1 .if 0 .tl 'INTERNET DRAFT''May 1985'
<br>

<br>

<br>
Bold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  30
<br>

<br>
Italic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  30
<br>

<br>
Teletype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  30
<br>

<br>
8    Hyperlink Elements  . . . . . . . . . . . . . . . . . . . . . .  31
<br>

<br>
8.1      Anchor  . . . . . . . . . . . . . . . . . . . . . . . . . .  31
<br>

<br>
HREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  31
<br>

<br>
NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  32
<br>

<br>
TITLE  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  32
<br>

<br>
REL  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  33
<br>

<br>
REV  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  33
<br>

<br>
URN  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  33
<br>

<br>
METHODS  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  33
<br>

<br>
9    Block Structuring Elements  . . . . . . . . . . . . . . . . . .  34
<br>

<br>
9.1      Paragraph . . . . . . . . . . . . . . . . . . . . . . . . .  34
<br>

<br>
9.2      Preformatted Text . . . . . . . . . . . . . . . . . . . . .  34
<br>

<br>
9.3      Address . . . . . . . . . . . . . . . . . . . . . . . . . .  36
<br>

<br>
9.4      Blockquote  . . . . . . . . . . . . . . . . . . . . . . . .  36
<br>

<br>
9.5      Headings  . . . . . . . . . . . . . . . . . . . . . . . . .  37
<br>

<br>
9.6      List Elements . . . . . . . . . . . . . . . . . . . . . . .  38
<br>

<br>
Definition List  . . . . . . . . . . . . . . . . . . . . . . . . . .  38
<br>

<br>
Directory List . . . . . . . . . . . . . . . . . . . . . . . . . . .  39
<br>

<br>
Menu List  . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  39
<br>

<br>
Ordered List . . . . . . . . . . . . . . . . . . . . . . . . . . . .  40
<br>

<br>
Unordered List . . . . . . . . . . . . . . . . . . . . . . . . . . .  40
<br>

<br>

<br>

<br>

<br>
Berners-Lee, Connolly                                 FORMFEED[Page iii]
<br>

<br>

<br>

<br>

<br>

<br>
INTERNET DRAFT                                                  May 1985
<br>

<br>

<br>
10   Form-based Input Elements . . . . . . . . . . . . . . . . . . .  42
<br>

<br>
10.1      Form . . . . . . . . . . . . . . . . . . . . . . . . . . .  43
<br>

<br>
10.2      Input  . . . . . . . . . . . . . . . . . . . . . . . . . .  44
<br>

<br>
10.3      Option . . . . . . . . . . . . . . . . . . . . . . . . . .  47
<br>

<br>
10.4      Select . . . . . . . . . . . . . . . . . . . . . . . . . .  48
<br>

<br>
10.5      Text Area  . . . . . . . . . . . . . . . . . . . . . . . .  48
<br>

<br>
11   HTML Public Text  . . . . . . . . . . . . . . . . . . . . . . .  50
<br>

<br>
11.1      HTML DTD . . . . . . . . . . . . . . . . . . . . . . . . .  50
<br>

<br>
11.2      SGML Declaration for HTML  . . . . . . . . . . . . . . . .  60
<br>

<br>
11.3      Sample SGML Open Entity Catalog for HTML . . . . . . . . .  62
<br>

<br>
11.4      Character Entity Sets  . . . . . . . . . . . . . . . . . .  63
<br>

<br>
Numeric and Special Graphic Entity Set . . . . . . . . . . . . . . .  63
<br>

<br>
ISO Latin 1 Character Entity Set . . . . . . . . . . . . . . . . . .  63
<br>

<br>
12   Glossary  . . . . . . . . . . . . . . . . . . . . . . . . . . .  66
<br>

<br>
13   Bibliography  . . . . . . . . . . . . . . . . . . . . . . . . .  69
<br>

<br>
A    Appendices  . . . . . . . . . . . . . . . . . . . . . . . . . .  71
<br>

<br>
A.1      The ISO-8859-1 Coded Character Set  . . . . . . . . . . . .  71
<br>

<br>
A.2      Obsolete Features . . . . . . . . . . . . . . . . . . . . .  74
<br>

<br>
Comment Element  . . . . . . . . . . . . . . . . . . . . . . . . . .  74
<br>

<br>
Highlighted Phrase Element . . . . . . . . . . . . . . . . . . . . .  74
<br>

<br>
Plain Text Element . . . . . . . . . . . . . . . . . . . . . . . . .  74
<br>

<br>
Example and Listing Elements . . . . . . . . . . . . . . . . . . . .  75
<br>

<br>
A.3      Proposed Features . . . . . . . . . . . . . . . . . . . . .  76
<br>

<br>
Additional Character Entities  . . . . . . . . . . . . . . . . . . .  76
<br>

<br>

<br>

<br>

<br>
Berners-Lee, Connolly                                  FORMFEED[Page iv]
<br>

<br>

<br>

<br>

<br>

<br>
INTERNET DRAFT                                                  May 1985
<br>

<br>

<br>
Defining Instance Element  . . . . . . . . . . . . . . . . . . . . .  77
<br>

<br>
Strike Element . . . . . . . . . . . . . . . . . . . . . . . . . . .  77
<br>

<br>
Underline Element  . . . . . . . . . . . . . . . . . . . . . . . . .  77
<br>

<br>
B    Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . .  78
<br>

<br>
B.1      Authors' Addresses  . . . . . . . . . . . . . . . . . . . .  79
<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>
Berners-Lee, Connolly                                   FORMFEED[Page v]
<br>

<br>

<br>