\documentstyle[rfc,fancyheadings,times]{cernman}
\lhead[RFC XXX]{June 1993}
\chead{Hypertext Markup language}
\rhead[June 1993]{RFC XXXX}
\lfoot[\thepage]{Berners-Lee and Connolly}
\rfoot[Berners-Lee and Connolly]{\thepage}
\cfoot{}
\pagestyle{fancy}
\begin{document}
% First page special
\thispagestyle{plain}
\begin{tabular*}{\textwidth}{@{}l@{\extracolsep{\fill}}r@{}}
Hypertext Markup Language&Tim Berners-Lee, CERN\\
Internet Draft&Daniel Connolly, Atrium Technology Inc.\\
Expires 13 January 1994&13 July 1993\\[0.5cm]
\end{tabular*}

\begin{center}
\Large\bf\sf
Hypertext Markup Language\\[1cm]
\large A Representation of Textual Information and Metainformation\\
for Retrieval and Interchange\\[1cm]
\end{center}
% --------------------------------------------------------


\author{Generated from the Hypertext}\title{Hypertext Markup Language (HTML)} \maketitle \cleardoublepage \pagenumbering{roman} \setcounter{page}{1} \tableofcontents \cleardoublepage \pagenumbering{arabic} \setcounter{page}{1}



\chapter{Hypertext Markup Language (HTML)}
\subsection{An Application Conforming to International
Standard ISO 8879 $--$ Standard Generalized
Markup Language}
\section{About of this Document}This document describes the current
practice and current proposals for
future standardisation of HTML, as
a basis for review and enhancement.\par 
 The document is a draft form of
a standard for interchange of information
on the network which is proposed
to be registered as a MIME (RFC1521)
content type. \par 
Please send comments to connolly@hal.com
or the discussion list www-html@info.cern.ch.
\subsection{Version}This is version 2.0 of this document.
It introduces forms for user input
of information. This feature is known
as a level 2 feature of HTML.  All
other specified features are known
as level 1 features.  Features of
higher levels which are under discussion,
(such as tables, figures, and mathematical
formulae) where mentioned are described
as "proposed".\par 
The latest version of this document
is currently available in hypertext
on the World-Wide Web as http://info.cern.ch/hypertext/WWW/MarkUp/HTML.html
\section{Abstract}HyperText Markup Language (HTML)
can be used to represent
\begin{itemize}
\item Hypertext news, mail, online documentation,
and collaborative hypermedia;
\item Menus of options;
\item Database query results;
\item Simple structured documents with
inlined graphics.
\item Hypertext views of existing bodies
of information
\end{itemize}The World Wide Web (W3) initiative
links related information throughout
the globe. HTML provides one simple
format for providing linked information,
and all W3 compatible programs are
required to be capable of handling
HTML. W3 uses an Internet protocol
(Hypertext Transfer Protocol, HTTP),
which allows transfer representations
to be negotiated between client and
server, the result being returned
in an extended MIME message. HTML
is therefore just one, but an important
one, of the representations used
with W3.\par 
HTML is proposed as a MIME content
type.\par 
HTML refers to the URI specification
RFCxxxx.\par 
Implementations of HTML parsers and
generators can be found in the various
W3 servers and browsers, in the public
domain W3 code, and may also be built
using various public domain SGML
parsers such as \lbrack SGMLS\rbrack  . HTML documents
are SGML documents with fairly generic
semantics appropriate for representing
information from a wide range of
applications.
\begin{DL}{allow this much space}
\item[
\end{DL}








\subsection{Status of this memo}This document is an Internet Draft.
Internet Drafts are working documents
of the Internet Engineering Task
Force (IETF), its Areas, and its
Working Groups.  Note that other
groups may also distribute working
documents as Internet Drafts.  \par 
Internet Drafts are working documents
valid for a maximum of six months.
Internet Drafts may be updated, replaced,
or obsoleted by other documents at
any time.  It is not appropriate
to use Internet Drafts as reference
material or to cite them other than
as a "working draft" or "work in
progress".  \par 
Distribution of this document is
unlimited. 







\section{Vocabulary}This specification uses the words
below with the precise meaning given.

\begin{DL}{allow this much space}
\item[Representation 
]The encoding of information
for interchange. For example, HTML
is a representation of hypertext.
\item[Rendering 
]The form of presentation
to information to the human reader.
\end{DL}

\subsection{Imperatives}
\begin{DL}{allow this much space}
\item[may 
]The implementation is not obliged
to follow this in any way.
\item[must 
]If this is not followed, the
implementation does not conform to
this specification.
\item[shall 
]as "must" 
\item[should 
]If this is not followed, though
the implementation officially conforms
to the standard, undesirable results
may occur in practice.
\item[typical 
]Typical rendering is described
for many elements. This is not a
mandatory part of the standard but
is given as guidance for designers
and to help explain the uses for
which the elements were intended.
\end{DL}

\subsection{Notes}Sections marked "Note:" are not mandatory
parts of the specification but for
guidance only. 
\subsection{Status of features}
\begin{DL}{allow this much space}
\item[Mandatory 
]These features must be
implemented in the rendering. Features
are mandatory unless otherwise mentioned.

\item[Optional
] Standard HTML features which
may safely be ignored by parsers.
It is legal to ignore these, treat
the contents as though the tags were
not there. (e.g. EM, and processing
instructions) .  Authors should be
awarethat these features may be ignored
by some applications.
\item[Proposed
]The specification of these
features is not final. They should
not be regarded as part ofthe standard,
but indicate possible directions
for future versions.
\item[Obsolete 
]Not standard HTML. Parsers
should implement these features as
far as possible in order to preserve
back-compatibility with previous
versions of this specification.
\end{DL}








\chapter{HTML and MIME}The definition of the HTML content
subtype is 
\begin{DL}{allow this much space}
\item[MIME Type name 
]text 
\item[MIME subtype name:
] html 
\item[Required parameters: 
]none 
\item[Optional parameters:
] level, version,
charset 
\end{DL}

\section{Level}The level parameter specifies the
feature set which is used in the
document.  The level is an integer
number, implying that any features
of same or lower level may be present
in the document.  Levels are defined
by this specification.
\section{Version}In order to help avoid future compatibility
problems, the version parameter may
be used to give the version number
of this specification to which the
 document conforms.   The version
number appears at the front of this
document and within public identifier
for the SGML DTD.
\section{Character sets}The base character set (the SGML
BASESET) for HTML is ISO Latin-1.
This is the set referred to by any
numeric character references . The
actual character set used in the
representation of an HTML document
may be ISO Latin 1, or its 7-bit
subset which is ASCII. There is no
obligation for an HTML document to
contain any characters above decimal
127. It is possible that a transport
medium such as electronic mail imposes
constraints on the number of bits
in a representation of a document,
though the HTTP access protocol used
by W3 always allows 8 bit transfer.\par 
When an HTML document is encoded
using 7-bit characters, then the
mechanisms of character references
and entity references may be used
to encode characters in the upper
half of the ISO Latin-1 set. In this
way, documents may be prepared which
are suitable for mailing through
7-bit limited systems.
\subsection{Character set option (proposed)}The SGML declaration specified ISO
Latin 1 as the base character set.
The charset parameter is reserved
for future use. Its intended significance
is to override the base character
set of the SGML declaration. Support
of character sets other than ISO-Latin-1
is not a requirement for conformance
with this specification. 







\chapter{HTML and SGML}This section describes the relationship
between HTML and SGML, and guides
the newcomer through interpretation
of the DTD . (This is not a full
tutorial on SGML, and in the event
of any apparent conflict, the SGML
standard is definitive.)\par 
The HyperText Markup Language is
an application conforming to International
Standard ISO 8879 $--$ Standard Generalized
Markup Language \lbrack  SGML \rbrack . SGML is
a system for defining structured
document types, and markup languages
to represent instances of those document
types.\par 
Every SGML document has three parts:
\begin{itemize}
\item An SGML declaration, which binds
SGML processing quantities and syntax
token names to specific values. For
example, the SGML declaration in
the HTML DTD specifies that the string
that opens a tag is $<$/ and the maximum
length of a name is 34 characters.
\item A prologue including one or more
document type declarations, which
specifiy the element types, element
relationships and attributes, and
references that can be represented
by markup. The HTML DTD specifies,
for example, that the HEAD element
contains at most one TITLE element.
\item An instance, which contains the data
and markup of the document.
\end{itemize}We use the term HTML to mean both
the document type and the markup
language for representing instances
of that document type.\par 
The SGML declaration for HTML is
given in the appendix ``SGML Delcaration
for HTML.'' It is implicit among
WWW implementations.\par 
The prologue for an HTML document
should look like:
\begin{verbatim}
      <!DOCTYPE HTML PUBLIC "-//W3 Organization//DTD W3 HTML 2.0//EN">

\end{verbatim}

\begin{DL}{allow this much space}
\item[NOTE 2:
] Many extant HTML documents
do not contain a prologue. Implementations
are encouraged to infer the above
prologue if the document does not
begin with $<$! .
\end{DL}
.







\section{Structured Text}An HTML instance is like a text file,
except that some of the characters
are interpreted as markup. The markup
gives structure to the document.\par 
The instance represents a hierarchy
of elements. Each element has a name
, some attributes , and some content.
Most elements are represented in
the document as a start tag, which
gives the name and attributes, followed
by the content, followed by the end
tag. For example:
\begin{verbatim}
	<!DOCTYPE HTML PUBLIC
	 	"-//W3 Organization//DTD W3 HTML 2.0//EN">
	<HTML>
	  <HEAD>
	    <TITLE>
	      A sample HTML document
	    </TITLE>
	  </HEAD>

	  <BODY>
	    <H1>
	      An Example of Structure
	      <br>
	      In HTML
	    </H1>
	    <P>
	      Here's a typical paragraph.
	    <UL>
	      <LI>
	        Item one has an
	        <A NAME="anchor">
	          anchor
	        </A>
	      <LI>
	        Here's item two.
	    </UL>
	  </BODY>
	</HTML>


\end{verbatim}
Some elements (e.g. BR ) are empty.
They have no content. They show up
as just a start tag.\par 
For the rest of the elements, the
content is a sequence of data characters
and nested elements. Some things
such as forms and anchors cannot
be nested, in which case this is
mentioned in the text. Anchors and
character highlighting may be put
inside other constructs.
\subsection{Tags}Most elements start and end with
tags. Empty elements have no end
tag. Start tags are delimited by
$<$and $>$, and end tags are delimited
by $<$/ and $>$. For example:
\begin{verbatim}
	<h1> ... </H1>   <!-- uppercase = lowercase  -->
	<h1 > ... </h1 > <!-- spaces OK before > -->

\end{verbatim}
The following are not valid tags:
\begin{verbatim}
	< h1>             <!-- this is not a tag at all -->
	<H1/> <H=1>       <!-- these are markup errors -->
\end{verbatim}

\begin{DL}{allow this much space}
\item[NOTE:
] The SGML declaration for HTML
specifies SHORTTAG YES , which means
that there are some other valid syntaxes
for tags, e.g. NET tags: $<$em/.../
, empty start tags: $<$$>$ , empty end
tags: $<$/$>$ . Until such time as support
for these idioms is widely deployed,
their use is strongly discouraged.
\end{DL}
The start and end tags for the HTML,
HEAD, and BODY elements are omissable.
The end tags of some other elements
(e.g. P, LI, DT, DD) can be ommitted
(see the DTD for details). This does
not change the document structure
$--$ the following documents are equivalent:
\begin{verbatim}
	<!DOCTYPE HTML PUBLIC
	 	"-//W3 Organization//DTD W3 HTML 2.0//EN">
	  <TITLE>Structural Example</TITLE>
	  <H1>Structural Example</H1>
	  <P>A paragraph...

	<!DOCTYPE HTML PUBLIC
	 	"-//W3 Organization//DTD W3 HTML 2.0//EN">
	  <HTML><HEAD>
	  <TITLE>Structural Example</TITLE>
	  </HEAD>
	  <BODY>
	  <H1>Structural Example</H1>
	  <P>A paragraph...</P>
	  </BODY>

\end{verbatim}

\subsubsection{Names}The element name immediately follows
the tag open delimiter. Names consist
of a letter followed by up to 33
letters, digits, periods, or hyphens.
Names are not case sensitive. For
example:
\begin{verbatim}
	A H1 h1 another.name name-with-hyphens


\end{verbatim}

\subsubsection{Attributes}In a start tag, whitespace and attributes
are allowed between the element name
and the closing delimiter. An attribute
consists of a name, an equal sign,
and a value. Whitespace is allowed
around the equal sign.\par 
The value is either:
\begin{itemize}
\item A string literal, delimited by single
quotes or double quotes, or
\item A name token; that is, a sequence
of letters, digits, periods, or hyphens.
\end{itemize}For example:
\begin{verbatim}
	<A HREF="http://host/dir/file.html">
	<A HREF=foo.html >
	<IMG SRC="mrbill.gif" ALT="Mr. Bill says, &#34;Oh Noooo&#34;">

\end{verbatim}
The length of an attribute value
(after replacing entity and numeric
character referencees) is limited
to 1024 characters.
\begin{DL}{allow this much space}
\item[NOTE 1:
] Some implementations allowed
any character except space or '$>$'
in a name token, for example $<$A HREF=foo/bar.html$>$
. As a result, there are many documents
that contain attribute values that
should be quoted but are not. While
parser implementators are encouraged
to support this idiom, its use in
future documents is stictly prohibited.
\item[NOTE 2:
] Some implementations also
consider any occurence of the $>$ character
to signal the end of a tag. For compatibility
with such implementations, it may
be necessary to represent $>$ with
an entity or numeric character reference;
for example: $<$IMG SRC="eq1.ps" ALT="a
$>$ b"$>$
\end{DL}
Attributes with a delcared value
of NAME (e.g. ISMAP , COMPACT ) may
be written using a minimized syntax.
The markup:
\begin{verbatim}
	<UL COMPACT="COMPACT">

\end{verbatim}
can be written as
\begin{verbatim}
	<UL COMPACT>

\end{verbatim}

\subsection{Undefined tag and attribute names}It is a principle to be conservative
in that which one produces, and liberal
in that which one accepts.  HTML
parsers should be liberal except
when verifying code.  HTML generators
should generate strictly conforming
HTML.\par 
The behaviour of WWW applications
reading HTML documents and discovering
tag or attribute names which they
do not understand should be to behave
as though, in the case of a tag,
the whole tag had not been there
but its content had, or in the case
of an attribute, that the attribute
had not been present.
\subsection{Character Data }The charcters between the tags represent
text in the ISO-Latin-1 character
set, which is a superset of ASCII.
Because certain characters will be
interpreted as markup, they should
be "escaped"; that is, represented
by markup $--$ entity or numeric character
references. For example:
\begin{verbatim}
                When a&#60;b, we can show that...
                Brought to you by AT&amp;T

\end{verbatim}
The HTML DTD includes entities for
each of the non-ASCII characters
so that one may reference them by
name if it is inconvenient to enter
them directly:
\begin{verbatim}           Kurt G&ouml;del was a famous logician and mathematician.

\end{verbatim}

\begin{DL}{allow this much space}
\item[NOTE 1:
] To ensure that a string of
characters has no markup, it is sufficient
to represent all occurrences of $<$
, $>$ , and \& by character or entity
references. 
\item[NOTE 2:
] There are SGML features (
CDATA , RCDATA ) to allow most $<$
, $>$ , and \& characters to be entered
without the use of entity or character
references. Because these features
tend to be used and implemented inconsistently,
and because they require 8-bit characters
to represent non-ASCII characters,
they are not employed in this version
of the HTML DTD.   An earlier HTML
specification included an XMP element
whose syntax is not expressible in
SGML. Inside the XMP , no markup
was recognized except the $<$/XMP$>$
end tag. While implementations are
encouraged to support this idiom,
its use is obsolete. 
\end{DL}

\subsubsection{Comments}To include comments in an HTML document
that will be ignored by the parser,
surround them with $<$!$--$ and $--$$>$.
After the comment delimiter, all
text up to the next occurrence of
$--$ is ignored. Hence comments cannot
be nested. Whitespace is allowed
between the closing $--$ and $>$. (But
not between the opening $<$! and $--$.)\par 
For example:
\begin{verbatim}<HEAD>
<TITLE>HTML Guide: Recommended Usage</TITLE>
<!-- Id: Text.html,v 1.6 1994/04/25 17:33:48 connolly Exp -->
</HEAD>

\end{verbatim}

\begin{DL}{allow this much space}
\item[Note 3:
]Some historical implementations
incorrectly consider a $>$ sign to
terminate a comment.
\end{DL}
. 
\begin{verbatim} 

\end{verbatim}








\chapter{HTML Elements}This is a discussion of the elements
in the HTML language, and how they
interact to represent documents.

\section{The HTML Document Element}An HTML document is organized as
a HEAD and a BODY, much like memo
or a mail message: 
\begin{verbatim}
                                HTML
	                         |
	                         |_head
	                         |_body

\end{verbatim}
The HEAD element is an small unordered
collection of information about the
document, whereas the BODY is an
ordered sequence of information elements
of arbitrary length. This organization
allows an implementation to determine
certain properties of a document
$--$ the title, for example $--$ without
parsing the entire document. 
\section{Information in the HEAD Element}
\begin{DL}{allow this much space}
\item[TITLE 
]The title of the document 
\item[ISINDEX 
]Sent by a server in a searchable
document 
\item[NEXTID 
]A parameter used by editors
to generate unique identifiers 
\item[LINK 
]Relationship between this document
and another. See also the Anchor
element , Relationships . A document
may have many LINK elements. 
\item[BASE 
]A record of the URL of the document
when saved
\end{DL}

\subsection{Proposed head elements}
\begin{DL}{allow this much space}
\item[EXPIRES
]The date after which the document
is invalid. Semantics as in the HTTP
specification.
\end{DL}

\subsection{Obsolete head elements}
\begin{DL}{allow this much space}
\item[META
]A wrapper for an HTTP element
]
\end{DL}

\section{Body Elements (level 1)}The order of the contents of the
BODY element should be preserved
when it is rendered on the output
device. 
\subsection{Hypertext Anchors}
\begin{DL}{allow this much space}
\item[Anchors
] Sections of text which form
the beginning and/or end of hypertext
links are called "anchors" and defined
by the A tag.
\end{DL}

\subsection{Block Elements}These elements typically stack vertically
in the rendered flow of text. Whitespace
between them is ignored. 
\begin{DL}{allow this much space}
\item[Headings 
]Several levels of heading
are supported. 
\item[Paragraph 
]The P element represents
a paragraph. 
\item[Horizontal Rule 
]A horizontal dividing
line 
\item[Address style 
]Used to represent authorship
or status of a document
\item[Blockquote style 
]A block of text
quoted from another source. 
\item[Lists 
]Bulleted lists, glossaries,
etc. 
\item[Preformatted text 
]Sections in fixed-width
font for preformatted text.
\end{DL}

\subsection{Inline Elements}These elements fall left to right
in the rendered flow of text. Whitespace
between them separates words, except
in the PRE element, where it has
its literal ASCII meaning. 
\begin{DL}{allow this much space}
\item[Special Phrases 
]Emphasis, typographic
distinctions, etc. 
\item[Line Breaks 
]Indicates a line break
in a flow of text. 
\item[IMG 
]The IMG tag allows inline graphics.
\end{DL}

\section{Body elements (level 2)}
\subsection{Elements for forms}The FORM element and various other
elements allowed only within it describe
forms which allow user input.
\begin{DL}{allow this much space}
\item[FORM elements
] FORM, INPUT, SELECT,
OPTION, TEXTAREA, etc
\end{DL}

\section{Obsolete elements}The other elements are obsolete but
should be recognised by parsers for
back-compatibility.

$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$


 



\section{HEAD}

\par The HEAD element contains all information about the document
in general. It does not contain any text which is part of the
document: this is in the $<$A HREF="BODY.html"
NAME="z2"$>$BODY. Within the head element,
only certain elements
are allowed.



$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$


 



\section{BODY}

\par The BODY element contains all the information which is part
of the document, as opposed information about the document which
is in the HEAD .

\par The elements within the BODY element are in the order in which
they should be presented to the reader.

\par See the list of things
which are allowed within a BODY element .

$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$



 



\section{Anchors}

\par An anchor is a piece of text which marks the beginning and/or
the end of a hypertext link.

\par The text between the opening tag and the closing tag is either
the start or destination (or both) of a link.
Attributes of the anchor tag are as follows.

\begin{DL}{allow this much space}

\item[HREF

]OPTIONAL. If the HREF attribute is present,
the anchor is sensitive text: the start of a link.
If the reader selects this text, (s)he should be presented with
another document whose network address is defined by the value
of the HREF attribute . The format of the network address is
specified $<$A
HREF="../../Addressing/Addressing.html"
NAME="z10"$>$elsewhere . This allows for the form HREF="\#identifier"
to refer to another anchor in the same document.
If the anchor is in another document, the attribute is a relative name
, relative to the documents address (or specified base address if any).
\begin{DL}{allow this much space}

\item[{\bf @@NOTE:}

]{\em This refers to the URI specification,
which does not cover relative addresses.
There is no specification of how to distinguish relative addresses
from absolute addresses. \/}

\end{DL}


\item[NAME

]OPTIONAL. If present, the attribute NAME allows the anchor
to be the destination of a link. The value of the attribute is
an identifier for the anchor. Identifiers are arbitrary strings
but must be unique within the HTML document.
Another document can then make a reference explicitly to this
anchor by putting the identifier after the address,
separated by a hash sign
.
\begin{DL}{allow this much space}

\item[{\bf @@NOTE:}

]{\em This feature is representable in SGML as an ID attribute,
if we restrict the identifiers to be SGML names.
\/}

\end{DL}


\item[REL

]OPTIONAL. An attribute REL may give the relationship (s)
described by the hypertext link. The value is a comma-separated
list of relationship values. Values and their semantics will
be registered by the HTML registration
authority . The default relationship if none other is given
is void. REL should not be present unless HREF is present.
See Relationship values
, REV .

\item[REV

]OPTIONAL. The same as $<$A HREF="\#21"
NAME="z38"$>$REL , but the semantics 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.

\item[URN

]OPTIONAL. If present, this specifies a uniform resource number
for the document. See $<$A HREF="../URN.html"
NAME="z29"$>$note .

\item[TITLE

]OPTIONAL. This is informational only.
If present the value of this field should equal the value of
the TITLE of the document whose address is given by the HREF
attribute. See$<$A HREF="LinkTitle.html"
NAME="z31"$>$ note .

\item[METHODS

]OPTIONAL. The value of this field is a string which if present
must be a comma separated list of HTTP METHODS supported by the
object for public use. See note .
\end{DL}

\par All attributes are optional, although one of NAME and HREF
is necessary for the anchor to be useful.
See also: LINK .

\subsection{Example of use:}

\begin{verbatim}	See <A HREF="../HTML.dtd.html#z24"
NAME="z34"><A HREF="http://info.cern.ch/">CERN</A>'s information for
	more details.

	A <A NAME=serious>serious</A> crime is one which is associated
	with imprisonment. 
			...
	The Organization may refuse employment to anyone convicted
	of a <a href="#serious">serious</A> crime.


\end{verbatim}



$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$


 



\section{Address}

\par This element is for address information,
signatures, authorship, etc, often at the top or bottom of a
document.

\subsection{Typical rendering}

\par Typically, an address element is italic and/or right justified
or indented. The address element implies a paragraph break.
Paragraph marks within the address element do not cause extra
white space to be inserted.

\subsection{Examples of use:}

\begin{verbatim}		<ADDRESS><A HREF="Author.html">A.N.Other</A></ADDRESS>


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


\end{verbatim}


$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$


 



\section{BASE}

\par This element allows the URL of the document itself to be recorded
in situations in which the document may be read out of context.
URLs within the document may be in a "partial" form relative
to this base address.

\par Where the base address is not specified,
the reader will use the URL it used to access the document to
resolve any relative URLs.

\par The one attribute is:

\begin{DL}{allow this much space}

\item[HREF

]the URL
\end{DL}

$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$



 



\section{Line Break}

\par The line break element marks that a new line must be started
at the given point.

\subsection{Typical rendering}

\par A new line with indent the same as that of line-wrapped text.

\subsection{Examples}

\begin{verbatim}		<ADDRESS>Tim Berners-Lee<BR>
		World Wide Web project<BR>
		CERN<BR>1211 Geneva 23<BR>Switzerland
		</ADDRESS>

		I think that I shall never see<BR>
		A hoarding lovely as a tree<BR>
		In fact, unless the hoardings fall<BR>
		I'll never see a tree at all.<P>



\end{verbatim}


\subsection{See also:}
Paragraph marks

$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$


 



\section{BLOCKQUOTE}

\par The BLOCKQUOTE element allows text quoted from another source
to be rendered specially.

\subsection{Typical rendering}

\par A typical rendering might be a slight extra left and right
indent, and/or italic font. BLOCKQUOTE causes a paragraph break,
and typically a line or so of white space will be allowed between
it and any text before or after it.

\par Single-font rendition may for example put a vertical line
of "$>$" characters down the left margin to indicate quotation
in the Internet mail style.

\subsection{Example}

\begin{verbatim}I think it ends
<BLOCKQUOTE>Soft you now, the fair Ophelia. Nymph, in thy orisons, 
be all my sins remembered.
</BLOCKQUOTE>
but I am not sure.
\end{verbatim}








\section{Fill-out Forms and Input fields}Forms are composed by placing input
fields within paragraphs, preformatted/literal
text, lists and tables. This gives
considerable scope in designing the
layout of forms.  The form features
use the following elements which
are all known as HTML level 2 elements.
\begin{DL}{allow this much space}
\item[FORM
]a form within a document. 
\item[INPUT
]one input field
\item[TEXTAREA
]a multline input field
\item[SELECT
]A selection from a finite set
of options
\item[OPTION
]one option within a SELECT
\end{DL}
Each field is defined by an INPUT
element and must have an NAME attribute
which uniquely names the field in
the document. Additional optional
attributes can be used to specify
the type of the field (defaults to
free text), its size/precision, its
initial value and whether the field
is currently disabled or in error:
\begin{verbatim}
<FORM ACTION="mailto:www_admin@info.cern.ch">
<MH HIDDEN>Subject: WWW Questionaire</MH>
Please help up to improve the World Wide Web by filling in the
following questionaire:
<P>Your organization? <INPUT NAME="org" SIZE="48">
<P>Commercial? <INPUT NAME="commerce" TYPE=checkbox>
How many users? <INPUT NAME="users" TYPE=int>
<P>Which browsers do you use?
<UL>
<LI>X Mosaic <INPUT NAME="browsers" TYPE=checkbox VALUE="xmosaic">
<LI>Cello <INPUT NAME="browsers" TYPE=checkbox VALUE="cello">
<LI>Others <TEXTAREA NAME="others" COLS=48 ROWS=4></TEXTAREA>
</UL>
A contact point for your site: <INPUT NAME="contact" SIZE="42">
<P>Many thanks on behalf of the WWW central support team.
<P ALIGN=CENTER><INPUT TYPE=submit> <INPUT TYPE=reset>
</FORM>
\end{verbatim}
This fictitious example is a questionnaire
that will be emailed to www\_admin@info.cern.ch
. The FORM element is used to delimit
the form. There can be several forms
in a single document, but the FORM
element can't be nested. The ACTION
attribute specifies a URL that designates
an HTTP server or an email address.
If missing, the URL for the document
itself will be assumed. The effect
of the action can be modified by
including a method prefix, e.g. ACTION="POST
http://...." . This prefix is used
to select the HTTP method when sending
the form's contents to an HTTP server.
Would it be cleaner to use a separate
attribute, e.g. METHOD ?\par 
Servers can disable forms by sending
an appropriate header or by an attribute
on the optional HTMLPLUS element
at the very start of the document,
e.g. $<$htmlplus forms=off$>$ .\par 
Here, the $<$P$>$ and $<$UL$>$ elements have
been used to lay out the text (and
input fields. The browser has changed
the background color within the FORM
element to distinguish the form from
other parts of the document. The
browser is responsible for handling
the input focus, i.e. which field
will currently get keyboard input.\par 
For many platforms there will be
existing conventions for forms, e.g.
and shift- keys to move the keyboard
focus forwards and backwards between
fields, while an  key submits the
form. In the example, the  and  buttons
are specified explicitly with special
purpose fields. The  button is used
to email the form or send its contents
to the server as specified by the
ACTION attribute, while the  button
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  key.\par 
The INPUT element is used for a large
variety of typed of input fields.\par 
When you need to let users enter
more than one line of text, you should
use the TEXTAREA element.\par 
The RADIO 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 generally
rendered in a more compact fashion
as a pull down combo list. 







\subsection{FORM}The FORM element is used to delimit
the form. There can be several forms
in a single document, but the FORM
element can't be nested. \par 
The ACTION attribute specifies a
URL that designates an HTTP server
or an email address. If missing,
the URL for the document itself will
be assumed.  The effect of the action
can be modified by including a method
prefix, e.g. ACTION="POST http://...."
. This prefix is used to select the
HTTP method when sending the form's
contents to an HTTP server. Would
it be cleaner to use a separate attribute,
e.g. METHOD ?







\subsection{INPUT}The INPUT element represents a field
whose contents may be edited by the
user.  It has the following attributes.
\begin{DL}{allow this much space}
\item[NAME
] Symbolic name used when transferring
the form's contents. This attribute
is always needed and should uniquely
identify this field.
\item[TYPE
] Defines the type of data the
field accepts. Defaults to free text.
\item[SIZE
] Specifies the size or precision
of the field according to its type.
\item[MAXLENGTH
] The maximum number of characters
that will be accepted as input. This
can be greater that specified by
SIZE , in which case the field will
scroll appropriately. The default
is unlimited.
\item[VALUE
] The initial value for the field,
or the value when checked for checkboxes
and radio buttons. This attribute
is required for radio buttons.
\item[SRC
] A URL or URN specifying an image
- for use only with TYPE=IMAGEMAP.
\item[ALIGN
] Vertical alignment of the image
- for use only with TYPE=IMAGEMAP.
\end{DL}

\paragraph{Propsed }
\begin{DL}{allow this much space}
\item[CHECKED
] When present indicates that
a checkbox or radio button is selected.
\item[DISABLED
] When present indicates that
this field is temporarily disabled.
Browsers should show this by "greying
it" out in some manner.
\item[ERROR
] When present indicates that
the field's initial value is in error
in some way, e.g. because it is inconsistent
with the values of other fields.
Servers should include an explanatory
error message with the form's text.
\end{DL}

\subsubsection{Types}The following types of fields can
be defined with the TYPE attribute
:
\begin{DL}{allow this much space}
\item[TEXT
] Single line text entry fields.
Use the SIZE attribute to specify
the visible width in characters,
e.g. SIZE="24" for a 24 character
field. The MAX attribute can be used
to specify an upper limit to the
number of characters that can be
entered into a text field, e.g. MAX=72
. Use the TEXTAREA element for text
fields which can accept multiple
lines (see below).
\item[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.
\item[CHECKBOX
] Used for simple Boolean
attributes, or for attributes which
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 .
\item[RADIO
] For attributes which can take
a single value from a set of alternatives.
Each radio button field in the group
should be given the same NAME .
\item[SUBMIT
] This is a button that when
pressed submits the form. It offers
authors control over the location
of this button. You can use an image
as a submit button by specifying
a URL with the SRC attribute.
\item[RESET
] This is a button that when
pressed resets the form's fields
to their initial values as specified
by the VALUE attribute. You can use
an image as a reeset button by specifying
a URL with the SRC attribute. 
\end{DL}

\paragraph{Proposed types}
\begin{DL}{allow this much space}
\item[RANGE
] This allows you to specify
an integer range with the MIN and
MAX attributes, e.g. MIN=1 MAX=100
. Users can select any value in this
range.
\item[INT
] For entering integer numbers,
the maximum number of digits can
be specified with the SIZE attribute
(excluding the sign character), e.g.
size=3 for a three digit number.
\item[FLOAT
] For fields which can accept
floating point numbers.
\item[SCRIBBLE
] A field upon which you can
write with a pen or mouse. The size
of the field in millimeters is given
as SIZE= width , height. The units
are absolute as they relate to the
dimensions of the human hand, rather
than pixels of varying resolution.
The scribble may involve time and
pressure data in addition to the
basic ink data. You can use scribble
for signatures or sketches. The field
can be initialised by setting the
SRC attribute to a URL which contains
the ink *2 . The VALUE attribute
is ignored.
\item[AUDIO
] This provides a way of entering
spoken messages into a form. Browsers
might show an icon which when clicked
pops-up a set of tape controls that
you can use to record and replay
messages. The initial message can
be set by specifying a URL with the
SRC attribute. The VALUE attribute
is ignored.
\end{DL}

\paragraph{Obsolete types}DATE	 Fields which can accept a recognized
date format.\par 
URL	 For fields which expect document
references as URLs or URNs.
\begin{DL}{allow this much space}
\item[IMAGE
] This allows you to specify
an image field upon which you can
click with a pointing device. The
SRC and ALIGN attributes are exactly
the same as for the IMG and IMAGE
elements. The symbolic names for
the x and y coordinates of the click
event are specified with .x and .y
for the  given with the NAME attribute.
The VALUE attribute is ignored.
\end{DL}
When you need to let users enter
more than one line of text, you should
use the TEXTAREA element.







\subsection{OPTION}The OPTION element can take the following
attributes:
\begin{DL}{allow this much space}
\item[SELECTED
] Indicates that this option
is initially selected.
\item[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.
\end{DL}

\paragraph{Proposed attributes}
\begin{DL}{allow this much space}
\item[DISABLED
] When present indicates that
this option is temporarily disabled.
Browsers should show this by "greying
it"
\end{DL}
The contents of the OPTION element
is presented to the user to represent
the option.  It is used as a returned
value if the VALUE attribute is not
present.







\subsection{SELECT}The SELECT element allows the user
to chose one of a set of alternatives
described by textual labels, Every
alternative is represented by the
OPTION element.
\subsubsection{Attributes}
\begin{DL}{allow this much space}
\item[MULTIPLE
]The MULTIPLE attribute is
needed when users are allowed to
make several selections, e.g. $<$SELECT
MULTIPLE$>$ .
\end{DL}

\paragraph{Proposed attributes}
\begin{DL}{allow this much space}
\item[ERROR
]The ERROR attribute can be used
to indicate that the initial selection
is in error in some way, e.g. because
it is inconsistent with the values
of other fields.
\end{DL}

\subsubsection{Typical rendering}SELECT is typically as a pull down
or pop-up list. 
\subsubsection{Example}e.g.
\begin{verbatim}<SELECT NAME="flavor">
<OPTION>Vanilla
<OPTION>Strawberry
<OPTION>Rum and Raisin
<OPTION>Peach and Orange
</SELECT>

\end{verbatim}

\begin{DL}{allow this much space}
\item[out in some manner.
\end{DL}








\subsection{TEXTAREA}When you need to let users enter
more than one line of text, you should
use the TEXTAREA element, e.g.
\begin{verbatim}<TEXTAREA NAME="address" ROWS=64 COLS=6>
Hewlett Packard Laboratories
1501 Page Mill Road
Palo Alto, California 94304-1126
</TEXTAREA>

\end{verbatim}
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.
The ROWS and COLS attributes determine
the visible dimension of the field
in characters. Browsers are recommended
to allow text to grow beyond these
limits by scrolling as needed. In
the initial design for forms, multi-line
text fields were supported by the
INPUT element with TYPE=TEXT . Unfortunately,
this causes problems for fields with
long text values as SGML limits the
length of attribute literals. The
HTML+ DTD allows for up to 1024 characters
(the SGML default is only 240 characters!).

$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$



 



\section{Headings}







\par Six levels of heading are supported. (Note that a hypertext
node within a hypertext work tends to need fewer levels of heading
than a work whose only structure is given by the nesting of headings.)

\par A heading element implies all the font changes,
paragraph breaks before and after, and white space (for example)
necessary to render the heading. Further character emphasis or
paragraph marks are not required in HTML.

\par H1 is the highest level of heading, and is recommended for
the start of a hypertext node. It is suggested that the the text
of the first heading be suitable for a reader who is already
browsing in related information, in contrast to the title tag which should
identify the node in a wider context.

\par The heading elements are

\begin{verbatim}		<H1>, <H2>, <H3>, <H4>, <H5>, <H6>

\end{verbatim}


\par It is not normal practice to jump from one header to a header
level more than one below, for example for follow an H1 with
an H3. Although this is legal, it is discouraged,
as it may produce strange results for example when generating
other representations from the HTML.

\subsection{Example:}

\begin{verbatim}		<H1>This is a heading</H1>
		Here is some text
		<H2>Second level heading</H2>
		Here is some more text.

\end{verbatim}


\subsection{Parser Note:}

\par Parsers should not require any specific order to heading elements,
even if the heading level increases by more than one between
successive headings.

\subsection{Typical Rendering}

\begin{DL}{allow this much space}

\item[H1

]Bold very large font, centered. One or two lines clear space
between this and anything following. If printed on paper,
start new page.

\item[H2

]Bold, large font,, flush left against left margin,
no indent. One or two clear lines above and below.

\item[H3

]Italic, large font, slightly indented from the left margin.
One or two clear lines above and below.

\item[H4

]Bold, normal font, indented more than H3.
One clear line above and below.

\item[H5

]Italic, normal font, indented as H4.
One clear line above.

\item[H6

]Bold, indented same as normal text, more than H5.
One clear line above.
\end{DL}

\par These typical values are just an indication,
and it is up to the designer of the presentation software to
define the styles. The reader may have options to customize these.
When writing documents, you should assume that whatever is done
it is designed to have the same sort of effect as the styles
above.

\par The rendering software is responsible for generating suitable
vertical white space between elements, so it is NOT normal or
required to follow a heading element with a paragraph mark.


$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$



 



\section{Horizontal Rule}

\subsection{Typical Rendering}

\par Some sort of divider between sections of text such as a full
width horizontal rule or equivalent graphic.

\subsection{Example}

\par The horizontal rule is typically used for separating heading
information (when more than just a heading) from content,
etc.

\begin{verbatim}		<H1>The Albatross</H1>
		<Address>The Bumstead Monthly, 1948</Address>
		The following information is culled from
		this and suvccessive issues of the magazine.
		Thanks are due to the editor-in-chief,
		A.R. Bunstead, for her help and advice.
		<H2>Copyright IQR Inc.</h2>
		This recording may not be sold, resold,
		hired out, used, or talked about in too great
		a depth without the publisher's written or
		videotaped consent.
		<HR>
		The Albatross, most fabled and infamous of ..


\end{verbatim}



$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$



 



\section{IMG: Embedded Images}

\par Status: $<$A HREF="../StatusMeanings.html\#z5"
NAME="z7"$>$Extra

\par The IMG element allows another document to be inserted inline.
The document is normally an icon or small graphic,
etc. This element is NOT intended for embedding other HTML text.

\par Browsers which are not able to display inline images ignore
IMG elements. Authors should note that some browsers will be
able to display (or print) linked graphics but not inline graphics.
If the graphic is essential, it may be wiser to make a link to
it rather than to put it inline. If the graphic is essentially
decorative, then IMG is appropriate.

\par The IMG element is empty: it has no closing tag.
It has two attributes:

\begin{DL}{allow this much space}

\item[SRC

]The value of this attribute is the URL of the document to
be embedded. Its syntax is the same as that of the HREF attribute of the A tag.
SRC is mandatory.

\item[ALIGN

]Take values TOP or MIDDLE or BOTTOM,
defining whether the tops or middles of bottoms of the graphics
and text should be aligned vertically.

\item[ALT

]Optional alternative text as an alternative to the graphics
for display in text-only environments.
\end{DL}

\par Note that IMG elements are allowed within anchors.

\subsection{Example}

\begin{verbatim}	Warning: < IMG SRC ="triangle.gif" ALT="Warning:"> This must be done by a
	qualified technician.

	< A HREF="Go.html">< IMG SRC ="Button.ps" ALT="GO"></A>






\end{verbatim}



$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$


 



\section{ISINDEX}

\par This element informs the reader that the document is an index
document. As well as reading it, the reader may use a keyword
search.

\par The node may be queried with a keyword search by suffixing
the node address with a question mark, followed by a list of
keywords separated by plus signs. See the network address
format .

\par Note that this tag is normally generated automatically by
a server. If it is added by hand to an HTML document,
then the client will assume that the server can handle a search
on the document. Obviously the server must have this capability
for it to work: simply adding $<$ISINDEX$>$ in the document
is not enough to make searches happen if the server does not
have a search engine!

\par Status: standard.

\subsection{Example of use:}

\begin{verbatim}		<ISINDEX>

\end{verbatim}


$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$


 



\section{LINK}

\par The LINK element occurs within the HEAD element of an HTML document.
It is used to indicate a relationship between the document and
some other object. A document may have any number of LINK elements.

\par The LINK element is empty, but takes the same attributes as
the anchor element .

\par Typical uses are to indicate authorship,
related indexes and glossaries, 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.

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

$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$



 



\section{Forms of list in HTML}

\par These lists may be nested

\subsection{Glossaries}

\par A glossary (or definition list) is a list of paragraphs each
of which has a short title alongside it.
Apart from glossaries, this element is useful for presenting
a set of named elements to the reader. The elements within a
glossary follow are introduced by these elements:

\begin{DL}{allow this much space}

\item[DT

]The "term", typically placed in a wide left indent

\item[DD

]The "definition", which may wrap onto many lines
\end{DL}

\par These elements must appear in pairs. Single occurrences of
DT without a following DD are allowed, and have the same significance
as if the DD had been present with no text..
The one attribute which DL can take is

\begin{DL}{allow this much space}

\item[COMPACT

]suggests that a compact rendering be used,
because the enclosed elements are individually small,
or the whole glossary is rather large, or both.
\end{DL}

\subsubsection{Typical rendering}

\par The definition list DT, DD pairs are arranged vertically.
For each pair, the DT element is on the left,
in a column of about a third of the display area,
and the DD element is in the right hand two thirds of the display
area. The DT term is normally small enough to fit on one line
within the left-hand column. If it is longer,
it will either extend across the page, in which case the DD section
is moved down to separate them, or it is wrapped onto successive
lines of the left hand column.

\par This is sometimes implemented with the use of a large negative
first line indent.

\par White space is typically left between successive DT,DD pairs
unless the COMPACT attribute is given. The COMPACT attribute
is appropriate for lists which are long and/or have DT,DD pairs
which each take only a line or two. It is of course possible
for the rendering software to discover these cases itself and
make its own decisions, and this is to be encouraged.

\par The COMPACT attribute may also reduce the width of the left-hand
(DT) column.

\subsubsection{Examples of use}

\begin{verbatim}	<DL>
	<DT>Term the first<DD>definition paragraph is reasonably
	long but is still displayed clearly
	<DT>Term2 follows<DD>Definition of term2
	</DL>

	<DL COMPACT>
	<DT>Term<DD>definition paragraph
	<DT>Term2<DD>Definition of term2
	</DL>




\end{verbatim}


\subsection{Lists}

\par A list is a sequence of paragraphs,
each of which may be preceded by a special mark or sequence number.
The syntax is: 


\begin{verbatim}
		<UL>
		<LI> list element
		<LI> another list element ...
		</UL>

\end{verbatim}


\par The opening list tag may be any of UL, OL,
MENU or DIR. It must be immediately followed by
the first list element.

\subsubsection{Typical rendering}

\par The representation of the list is not defined here,
but a bulleted list for unordered lists,
and a sequence of numbered paragraphs for an ordered list would
be quite appropriate. Other possibilities for interactive display
include embedded scrollable browse panels.

\par List elements with typical rendering are:

\begin{DL}{allow this much space}

\item[UL

]A list of multi-line paragraphs, typically separated by some
white space and/or marked by bullets, etc.

\item[OL

]As UL, but the paragraphs are typically numbered in some
way to indicate the order as significant.

\item[MENU

]A list of smaller paragraphs. Typically one line per item,
with a style more compact than UL.

\item[DIR

]A list of short elements, typically less than 20 characters.
These may be arranged in columns across the page,
typically 24 character in width. If the rendering software is
able to optimize the column width as function of the widths of
individual elements, so much the better.
\end{DL}

\subsubsection{Example of use}

\begin{verbatim}		<OL>
		<LI> When you get to the station, leave
		by the southern exit, on platform one.
		<LI>Turn left to face toward the mountain
		<LI>Walk for a mile or so until you reach the
		"Asquith Arms" then 
		<LI>Wait and see...
		</OL>

		< MENU >
		<LI>The oranges should be pressed fresh
		<LI>The nuts may come from a packet
		<LI>The gin must be good quality
		</MENU>

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




\end{verbatim}



$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$


 



\section{Next ID}

\par This tag takes a single attribute which is the number of the
next document-wide numeric identifier to be allocated of the
form z123.

\par When modifying a document, old anchor ids should not be reused,
as there may be references stored elsewhere which point to them.
This is read and generated by hypertext editors.
Human writers of HTML usually use mnemonic alphabetical identifiers.
Browser software may ignore this tag.

\subsection{Example of use:}

\begin{verbatim}		<NEXTID N=z27>


\end{verbatim}


$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$



 



\section{P: Paragraph}

\par The empty P element represents a paragraph.
The exact rendering of this (indentation,
leading, etc) is not defined here, and may be a function of other
tags, style sheets etc.

\par You do NOT need to use $<$P$>$ to put white space around
heading, list, address or blockquote elements.
It is the responsibility of the rendering software to generate
that white space. An empty paragraph has undefined effect and
should be avoided.

\subsection{Typical rendering}

\par Typically, paragraphs are surrounded by a small vertical space
(of a line or half a line). This is not the case (typically)
within ADDRESS or (ever) within PRE elements.
With some implementations, normal paragraphs may have a small
extra left indent on the first line.

\subsection{Examples of use}

\begin{verbatim}	<h1>What to do</h1>
	<p>This is a one paragraph.<P>This is a second.
	<P>
	This is a third.

\end{verbatim}


\subsection{Bad example}

\begin{verbatim}        <h1><P>What not to do</h1>
	<address><p>I found that on my XYZ browser it looked prettier to
	me if I put some paragraph tags</address>
	<p>
	<ul><p><li>Around lists, and
	<li>Inside headings.
	</ul>
	<p>
	<h2>None of the paragraph tags in this example should
	be there.</h2>

\end{verbatim}


\subsection{See also}

\par Line Break


$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$



 



\section{PRE: Preformatted text}

\par Preformatted elements in HTML are displayed with
text in a fixed width font, and so are suitable for text which
has been formatted for a teletype by some existing formatting
system.

\begin{verbatim}

\end{verbatim}


\par The optional attribute is:

\begin{DL}{allow this much space}

\item[WIDTH

]This attribute gives the maximum number of characters which
will occur on a line. It allows the presentation system to select
a suitable font and indentation. Where the WIDTH attribute is
not recognized, it is recommended that a width of 80 be assumed.
Where WIDTH is supported, it is recommended that at least widths
of 40, 80 and 132 characters be presented optimally,
with other widths being rounded up.
\end{DL}

\par Within a PRE element,

\begin{itemize}

\item Line boundaries within the text are rendered as a move to
the beginning of the next line, except for one immediately following
or immediately preceding a tag.

\item The $<$p$>$ tag should not be used.
If found, it should be rendered as a move to the beginning of
the next line.

\item Anchor elements and character highlighting elements may be
used.

\item Elements which define paragraph formatting (Headings,
Address, etc) must not be used.

\item The ASCII Horizontal Tab (HT) character must be interpreted
as the smallest positive nonzero number of spaces which will
leave the number of characters so far on the line as a multiple
of 8. Its use is not recommended however.
\end{itemize}

\subsubsection{Example of use}

\begin{verbatim}			<A HREF="../HTML.dtd.html#z34"
NAME="z33"><PRE WIDTH="80">
			This is an example line
			</PRE>

\end{verbatim}


\subsubsection{Note: Highlighting}

\par Within a preformatted element, the constraint that the rendering
must be on a fixed horizontal character pitch may limit or prevent
the ability of the renderer to render highlighting elements specially.

\subsubsection{Note: Margins}

\par The above references to the "beginning of a new line" must
not be taken as implying that the renderer is forbidden from
using a (constant) left indent for rendering preformatted text.
The left indent may of course be constrained by the width required.


$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$



 



\section{TITLE}

\par The title of a document is specified by the TITLE element.
The TITLE element must occur in the HEAD of the document.

\par There may only be one title in any document.
It should identify the content of the document in a fairly wide
context.

\par It may not contain anchors, paragraph marks,
or highlighting. The title may be used to identify the node in
a history list, to label the window displaying the node,
etc. It is not normally displayed in the text of a document itself.
Contrast titles with headings .
The title should ideally be less than 64 characters in length.
That is, many applications will display document titles in window
titles, menus, etc where there is only limited room.
Whilst there is no limit on the length of a title (as it may
be automatically generated from other data),
information providers are warned that it may be truncated if
long.

\subsubsection{Examples of use}

\par Appropriate titles might be

\begin{verbatim}		<TITLE>Rivest and Neuman. 1989(b)</TITLE>
\end{verbatim}


\par or

\begin{verbatim}		<TITLE>A Recipe for Maple Syrup Flap-Jack</TITLE>

\end{verbatim}


\par or

\begin{verbatim}		<TITLE>Introduction -- AFS user's Guide</TITLE>

\end{verbatim}


\par Examples of inappropriate titles are those which are only
meaningful within context,

\begin{verbatim}		<TITLE>Introduction</TITLE>

\end{verbatim}


\par or too long,

\begin{verbatim}	<TITLE>Remarks on the Quantum-Gravity effects of "Bean
	Pole" diversification in Mononucleosis patients in Developing
	Countries under Economic Conditions Prevalent during
	the Second half of the Twentieth Century, and Related Papers:
	a Summary</TITLE>





\end{verbatim}



$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$



 



\section{Character highlighting}

\par Status: $<$A HREF="StatusMeanings.html\#z5"
NAME="z3"$>$Extra

\par These elements allow sections of text to be formatted in a
particular way, to provide emphasis, etc.
The tags do NOT cause a paragraph break,
and may be used on sections of text within paragraphs.

\par Where not supported by implementations,
like all tags, these tags should be ignored but the content rendered.

\par All these tags have related closing tags,
as in

\begin{verbatim}		This is <EM>emphasized</EM> text.

\end{verbatim}


\par Some of these styles are more explicit than others about how
they should be physically represented. The logical styles should
be used wherever possible, unless for example it is necessary
to refer to the formatting in the text. (Eg,
"The italic parts are mandatory".)

\subsubsection{Note:}

\par Browsers unable to display a specified style may render it
in some alternative, or the default, style,
with some loss of quality for the reader.
Some implementations may ignore these tags altogether,
so information providers should attempt not to rely on them as
essential to the information content.

\par These element names are derived from TeXInfo macro names.

\subsection{Physical styles}

\begin{DL}{allow this much space}

\item[TT

]Fixed-width typewriter font.

\item[B

]Boldface, where available, otherwise alternative mapping
allowed.

\item[I

]Italic font (or slanted if italic unavailable).

\item[U

]Underline.
\end{DL}

\subsection{Logical styles}

\begin{DL}{allow this much space}

\item[EM

]Emphasis, typically italic.

\item[STRONG

]Stronger emphasis, typically bold.

\item[CODE

]Example of code. typically monospaced font.
(Do not confuse with $<$A HREF="Elements/PRE.html"
NAME="z4"$>$PRE )

\item[SAMP

]A sequence of literal characters.

\item[KBD

]in an instruction manual, Text typed by a user.

\item[VAR

]A variable name.

\item[DFN

]The defining instance of a term. Typically bold or bold italic.

\item[CITE

]A citation. Typically italic.
\end{DL}

\subsection{Examples of use}

\begin{verbatim}	This text contains an <em>emphasized</em> word.
	<strong>Don't assume</strong> that it will be italic!
	It was made using the <CODE>EM</CODE> element. A citation is
	typically italic and has no formal necessary structure:
	<cite>Moby Dick</cite> is a book title.
\end{verbatim}



$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$



 



\section{Obsolete elements}

\par The following elements of HTML
are obsolete. It is recommended that client implementors implement
the obsolete forms for compatibility with old servers.

\subsubsection{Plaintext}

\par Status: $<$A HREF="StatusMeanings.html\#z8"
NAME="z59"$>$Obsolete .

\par The empty PLAINTEXT tag terminates the HTML entity.
What follows is not SGML. In stead, there's an old HTTP convention
that what follows is an ASCII (MIME "text/plain") body.

\par An example if its use is:

\begin{verbatim}			<PLAINTEXT>
			0001 This is line one of a ling listing
			0002 file from <any@host.inc.com> which is sent

\end{verbatim}


\par This tag allows the rest of a file to be read efficiently
without parsing. Its presence is an optimization.
There is no closing tag. The rest of the data is not in SGML.

\subsubsection{XMP and LISTING: Example sections}

\par Status: $<$A HREF="StatusMeanings.html\#z8"
NAME="z60"$>$Obsolete . This are in use and should be recognized
by browsers. New servers should use $<$PRE$>$ instead.

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

\begin{verbatim}			<LISTING>
				...
			</LISTING>

\end{verbatim}


\par or

\begin{verbatim}			<XMP>
				...
			</XMP>

\end{verbatim}


\par The text between these tags is to be portrayed in a fixed
width font, so that any formatting done by character spacing
on successive lines will be maintained. Between the opening and
closing tags:

\begin{itemize}

\item The text may contain any ISO Latin printable characters,
but not the end tag opener. (See Historical note )

\item Line boundaries are significant, except any occurring immediately
after the opening tag or before the closing tag.
and are to be rendered as a move to the start of a new line.

\item The ASCII Horizontal Tab (HT) character must be interpreted
as the smallest positive nonzero number of spaces which will
leave the number of characters so far on the line as a multiple
of 8. Its use is not recommended however.
\end{itemize}

\par The LISTING element is portrayed so that
at least 132 characters will fit on a line.
The XMP 
elementis portrayed in a font so that at least 80 characters
will fit on a line but is otherwise identical to LISTING.

\subsubsection{Highlighted Phrase HP1 etc}

\par Status: $<$A HREF="StatusMeanings.html\#z4"
NAME="z52"$>$Obsolete . These tags like all others should be
ignored if not implemented. Replaced will more meaningful elements
$--$ see character highlighting
.

\paragraph{Examples of use:}

\begin{verbatim}		<HP1>...</HP1>   <HP2>... </HP2> etc.

\end{verbatim}


\subsubsection{Comment element}

\par Status: $<$A HREF="StatusMeanings.html\#z8"
NAME="z58"$>$Obsolete

\par A comment element used for bracketing off unneed text and
comment has been introduced in some browsers but will be replaced
by the SGML command feature in new implementations.


$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$



 



\subsection{Historical Note: XMP and LISTING}

\par The XMP and LISTING
elements used historically to have non SGML conforming specifications,
in that the text could contain any ISO Latin printable characters,
including the tag opener, so long as it does not contain the
closing tag in full.

\par This form is not supported by SGML and so is not the specified
HTML interpretation. Providers should be warned that implementations
may vary on how they interpret end tags apparently within these
elements


$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$



 



\chapter{Entities}

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

\begin{DL}{allow this much space}

\item[$<$

]The less than sign $<$

\item[$>$

]The "greater than" sign $>$

\item[\&amp;

]The ampersand sign \&itself.

\item[\&quot;

]The double quote sign "

\item[\&nbsp;

]A non-breaking space
\end{DL}

\par Also allowed are references to any of the ISO Latin-1 alphabet,
using the entity names in the following table.


$<$!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML Date 1994/04/19 17:24:06 //EN"$>$






\section{ISO Latin 1 character entities}

\par This list is derived from "ISO 8879:1986//ENTITIES Added Latin
1//EN".

\begin{DL}{allow this much space}

\item[\&AElig;

]capital AE diphthong (ligature)

\item[\&Aacute;

]capital A, acute accent

\item[\&Acirc;

]capital A, circumflex accent

\item[\&Agrave;

]capital A, grave accent

\item[\&Aring;

]capital A, ring

\item[\&Atilde;

]capital A, tilde

\item[\&Auml;

]capital A, dieresis or umlaut mark

\item[\&Ccedil;

]capital C, cedilla

\item[\&ETH;

]capital Eth, Icelandic

\item[\&Eacute;

]capital E, acute accent

\item[\&Ecirc;

]capital E, circumflex accent

\item[\&Egrave;

]capital E, grave accent

\item[\&Euml;

]capital E, dieresis or umlaut mark

\item[\&Iacute;

]capital I, acute accent

\item[\&Icirc;

]capital I, circumflex accent

\item[\&Igrave;

]capital I, grave accent

\item[\&Iuml;

]capital I, dieresis or umlaut mark

\item[\&Ntilde;

]capital N, tilde

\item[\&Oacute;

]capital O, acute accent

\item[\&Ocirc;

]capital O, circumflex accent

\item[\&Ograve;

]capital O, grave accent

\item[\&Oslash;

]capital O, slash

\item[\&Otilde;

]capital O, tilde

\item[\&Ouml;

]capital O, dieresis or umlaut mark

\item[\&THORN;

]capital THORN, Icelandic

\item[\&Uacute;

]capital U, acute accent

\item[\&Ucirc;

]capital U, circumflex accent

\item[\&Ugrave;

]capital U, grave accent

\item[\&Uuml;

]capital U, dieresis or umlaut mark

\item[\&Yacute;

]capital Y, acute accent

\item[\&aacute;

]small a, acute accent

\item[\&acirc;

]small a, circumflex accent

\item[\&aelig;

]small ae diphthong (ligature)

\item[\&agrave;

]small a, grave accent

\item[\&aring;

]small a, ring

\item[\&atilde;

]small a, tilde

\item[\&auml;

]small a, dieresis or umlaut mark

\item[\&ccedil;

]small c, cedilla

\item[\&eacute;

]small e, acute accent

\item[\&ecirc;

]small e, circumflex accent

\item[\&egrave;

]small e, grave accent

\item[\&eth;

]small eth, Icelandic

\item[\&euml;

]small e, dieresis or umlaut mark

\item[\&iacute;

]small i, acute accent

\item[\&icirc;

]small i, circumflex accent

\item[\&igrave;

]small i, grave accent

\item[\&iuml;

]small i, dieresis or umlaut mark

\item[\&ntilde;

]small n, tilde

\item[\&oacute;

]small o, acute accent

\item[\&ocirc;

]small o, circumflex accent

\item[\&ograve;

]small o, grave accent

\item[\&oslash;

]small o, slash

\item[\&otilde;

]small o, tilde

\item[\&ouml;

]small o, dieresis or umlaut mark

\item[\&szlig;

]small sharp s, German (sz ligature)

\item[\&thorn;

]small thorn, Icelandic

\item[\&uacute;

]small u, acute accent

\item[\&ucirc;

]small u, circumflex accent

\item[\&ugrave;

]small u, grave accent

\item[\&uuml;

]small u, dieresis or umlaut mark

\item[\&yacute;

]small y, acute accent

\item[\&yuml;

]small y, dieresis or umlaut mark
\end{DL}






\chapter{The HTML DTD}The SGML declaration of HTML follows . Its relationship
to the content of an SGML document
is explained in the section "HTML
and SGML" .
\begin{verbatim}
<!SGML  "ISO 8879:1986"
--
	SGML Declaration for HyperText Markup Language (HTML)
	as used by the World-Wide Web (WWW) application.

--

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 95 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 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
              --  SPACE       32
                  TAB SEPCHAR  9
                  LF  SEPCHAR 10
                  FF  SEPCHAR 12
                  CR  SEPCHAR 13 --

	-- The above is an accurate description of the usage of FUNCTION --
	-- characters in HTML implementations; that is, there is no      --
	-- Record Start or Record End character, and no occurences of    --
	-- character 10 or 13 are "ignored" by the parser.               --
	-- But because few SGML implementations support this concrete    --
	-- sytax, we include the one below.                              --

	-- Note that in order to get correct behaviour w.r.t. newline    --
	-- processing, you will have to play some tricks in construcing  --
	-- the document entity for parsing in order to keep the parser   --
	-- from ignoring newlines in surpirsing ways                     --

		  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
                  NAMELEN  34
                  TAGLVL   100
                  LITLEN   1024
                  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    NONE
>
<!-- 
	$Id: html.decl,v 1.6 1994/05/18 17:23:34 connolly Exp $

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

	See also: http://www.hal.com/%7Econnolly/html-spec/HTML.html
		  http://info.cern.ch/hypertext/WWW/MarkUp/MarkUp.html
 -->
\end{verbatim}






\chapter{The HTML DTD}The HTML DTD follows . Its relationship
to the content of an SGML document
is explained in the section "HTML
and SGML" .
\begin{verbatim}
<!--	html.dtd

        Document Type Definition for the HyperText Markup Language
        as used by the World Wide Web (HTML DTD).

	$Id: html.dtd,v 1.13 1994/05/18 17:23:29 connolly Exp $

	Author: Daniel W. Connolly <connolly@hal.com>
	See Also: http://www.hal.com/%7Econnolly/html-spec/HTML.html
		  http://info.cern.ch/hypertext/WWW/MarkUp/MarkUp.html
-->

<!ENTITY HTML.Version
	"-//connolly hal.com//DTD WWW HTML $Date 1994/04/19 17:24:06 $//EN"
	-- public identifier for "current pracitice" version             -- 
	-- actually, take the $'s out to get the real public identifer,  --
	-- since $ is illegal in public identifier. When DTD stabilizes, --
	-- we'll need to stop using RCS keywords to version the pub id   --

        -- Typical usage:

            <!DOCTYPE HTML PUBLIC "-//connolly hal.com//DTD WWW HTML
						$Date: 1994/05/18 17:23:29 $//EN">
	    <html>
	    ...
	    </html>
	--
	>


<!-- Feature Test Entities -->

<!-- To use these, write your document like:
	<!DOCTYPE HTML [
	<!ENTITY % HTML.Optional "INCLUDE">
	<!ENTITY % html PUBLIC "-//connolly hal.com//DTD WWW HTML 1.8//EN">
	%html;
	]>
	<TITLE>Here's my doc</TITLE>
	<p>It uses lots of optional features

 In practice, if you're using sgmls to validate your docs,
 you can stick the <!DOCTYPE [...]> in a separate file and
 validate with:
	sgmls -s doctype.sgml foo.html
 -->

<!ENTITY % HTML.Minimal  "IGNORE">
<!ENTITY % HTML.Obsolete "IGNORE">
<!ENTITY % HTML.Prescriptive "IGNORE">

<![ %HTML.Minimal [
	<!ENTITY % HTML.linkRelationships "IGNORE">
	<!ENTITY % HTML.linkMethods "IGNORE">
	<!ENTITY % HTML.linkRedundantInfo "IGNORE">
	<!ENTITY % HTML.forms "IGNORE">
	<!-- @@ nested lists -->
	<!-- @@ phrases -->
	<!-- @@ headers inside A -->
	<!-- @@ nested phrases, fonts -->
	]]>
	
<![ %HTML.Obsolete [
	<!ENTITY % HTML.titleCDATA "INCLUDE">
	<!ENTITY % HTML.litCDATA "INCLUDE">
	<!ENTITY % HTML.pSeparator "INCLUDE">
	]]>

<![ %HTML.Prescriptive [
	<!--
	This feature test entity prescribes that certain
	idioms detract from the structural integrity of an
	HTML document, and are therefore disallowed.
	-->
	<!ENTITY % HTML.font-phrase "IGNORE">
	<!ENTITY % HTML.anchorNameCDATA "IGNORE">
	<!ENTITY % HTML.PLAINTEXT "IGNORE">
	<!ENTITY % HTML.bodyBlockOnly "INCLUDE">
	]]>

<!ENTITY % HTML.bodyBlockOnly "IGNORE"
	-- only allow block elements in the BODY element
	This means all paragraphs need to start with a <P> tag.
	-->

<!ENTITY % HTML.pSeparator "IGNORE"
	-- use P element as paragraph separator, rather	that container.
	-->

<!ENTITY % HTML.linkRelationships "INCLUDE"
	-- Adding markup to links to show the relationship between
	ends of a link
	see http://info.cern.ch/hypertext/WWW/MarkUp/Relationships.html
	-->

<!ENTITY % HTML.linkMethods "INCLUDE"
	-- Adding markup to links to show the methods supported
	by the referent object
	see http://info.cern.ch/hypertext/WWW/MarkUp/Elements/A.html
	-->

<!ENTITY % HTML.linkRedundantInfo "INCLUDE"
	-- Adding markup to links to give redundant information
	like URN, content type, title...
	-->

<!ENTITY % HTML.anchorNameCDATA "INCLUDE"
	-- Anchor names should be distinct. SGML parser can validate
	this if the NAME attribute of the A element is declared as ID.
	But that restricts the syntax of an anchor name to an SGML name,
	i.e. a letter followed by letters, numbers, periods and dashes,
	up to NAMELEN (34) characters long.
	-->

<!ENTITY % HTML.PLAINTEXT "INCLUDE"
	-- Support for the <PLAINTEXT> tag as a sign of the
	end of th HTML data stream and the beginning of a stream
	of text/plain data
	-->

<!ENTITY % HTML.titleCDATA "IGNORE"
	-- Is the TITLE element #PCDATA, RCDATA, or CDATA content?
	On Mosaic, it's #PCDATA, but in the linemode browser,
	it's more like CDATA, but not quite.
	-->

<!ENTITY % HTML.NEXTID "INCLUDE"
	-- Used by the NeXT implementation to keep track of the
	next anchor id to use
	-->

<!ENTITY % HTML.font-phrase "INCLUDE"
	-- allow B, I, TT, U outside PRE,
	CITE, VAR, etc. inside PRE
	-->

<!ENTITY % HTML.KEY "IGNORE"
	-- There was once a KEY element, for keyboard keys, menu items,
	buttons, etc. but it's not supported or widely documented
	-->

<!ENTITY % HTML.U "IGNORE"
	-- There was also a U element, but since it clashes with
	the common pracitce of underlining hypertext links, it is
	not widely supported
	-->

<!ENTITY % HTML.litCDATA "IGNORE"
	-- treat XMP, LISTING as CDATA, as per linemodeWWW
	-->

<!ENTITY % HTML.forms "INCLUDE"
	-- Support for forms as per
http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/Docs/fill-out-forms/overview.html
	-->

<!-- DTD definitions -->

<!ENTITY % heading "H1|H2|H3|H4|H5|H6" >
<!ENTITY % list " UL | OL | DIR | MENU ">
<!ENTITY % literal " XMP | LISTING ">

<!ENTITY % URI "CDATA"
        -- The term URI means a CDATA attribute
           whose value is a Uniform Resource Identifier,
           as defined by 
	"Universal Resource Identifiers" by Tim Berners-Lee
	aka http://info.cern.ch/hypertext/WWW/Addressing/URL/URI_Overview.html

	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.

	@@ Need to discuss relative addresses.
        -->

<!ENTITY % Content-Type "CDATA"
	-- meaning a MIME content type, as per RFC1521
	-->

<![ %HTML.anchorNameCDATA [ <!ENTITY % anchor-name "CDATA"> ]]>
<!ENTITY % anchor-name "ID">

<![ %HTML.linkRelationships [ <!ENTITY % linkRelAttrs "
        REL CDATA #IMPLIED -- forward relationship type --
        REV CDATA #IMPLIED -- reversed relationship type
                              to referent data:

                                PARENT CHILD, SIBLING, NEXT, TOP,
                                DEFINITION, UPDATE, ORIGINAL etc. --
	"> ]]>
<!ENTITY % linkRelAttrs "">

<![ %HTML.linkRedundantInfo [ <!ENTITY % linkRedundantAttrs "
        URN CDATA #IMPLIED -- universal resource number --

        TITLE CDATA #IMPLIED -- advisory only --
	"> ]]>
<!ENTITY % linkRedundantAttrs "">

<![ %HTML.linkMethods [ <!ENTITY % linkMethodAttrs "
        METHODS NAMES #IMPLIED -- supported public methods of the object:
                                        TEXTSEARCH, GET, HEAD, ... --
	"> ]]>
<!ENTITY % linkMethodAttrs "">

<!ENTITY % linkattributes
        "NAME %anchor-name #IMPLIED
        HREF %URI;  #IMPLIED
	%linkRelAttrs;
	%linkRedundantAttrs;
	%linkMethodAttrs;
        ">


<!-- Document Element -->


<![ %HTML.PLAINTEXT [ <!ENTITY % obsolete-plaintext ", PLAINTEXT?"> ]]>
<!ENTITY % obsolete-plaintext "">

<!ENTITY % html-content "HEAD, BODY %obsolete-plaintext;">
<!ELEMENT HTML O O  (%html-content)>

<![ %HTML.NEXTID [  <!ENTITY % head-content "TITLE? & ISINDEX? & LINK* & BASE?
			& NEXTID?"> ]]>
<!ENTITY % head-content "TITLE & ISINDEX? & LINK* & BASE?">
<!ELEMENT HEAD O O  (%head-content)>

<![ %HTML.titleCDATA [ <!ENTITY % title-content "CDATA"> ]]>
<!ENTITY % title-content "(#PCDATA)">
<!ELEMENT TITLE - -  %title-content
          -- The TITLE element is not considered part of the flow of text.
             It should be displayed, for example as the page header or
             window title.
          -->

<!ELEMENT ISINDEX - O EMPTY
          -- WWW clients should offer the option to perform a search on
             documents containing ISINDEX.
          -->

<!ELEMENT NEXTID - O EMPTY>
<!ATTLIST NEXTID N %anchor-name #REQUIRED
          -- The number should be a name suitable for use
             for the ID of a new element. When used, the value
             has its numeric part incremented. EG Z67 becomes Z68
          -->
<!ELEMENT LINK - O EMPTY>
<!ATTLIST LINK
        %linkattributes>
        
<!ELEMENT BASE - O EMPTY    -- Reference context for URIs -->
<!ATTLIST BASE

        HREF %URI; #REQUIRED

        >

<![ %HTML.KEY [
	<!ENTITY % key-emph "| KEY">
	]]>
<!ENTITY % key-emph "">

<![ %HTML.U [
	<!ENTITY % u-font "| U">
	]]>
<!ENTITY % u-font "">

<!ENTITY % font "TT | B | I %u-font">
<!ENTITY % phrase "EM | STRONG | CODE | SAMP | KBD | VAR | DFN | CITE
	 | STRIKE %key-emph">


<![ %HTML.font-phrase [
	<!ENTITY % obsolete-font "| %font">
	<!ENTITY % obsolete-phrase "| %phrase">
	]]>
<!ENTITY % obsolete-font "">
<!ENTITY % obsolete-phrase "">
<![ %HTML.pSeparator [
	<!ENTITY % obsolete-p "| P">
	]]>
<!ENTITY % obsolete-p "">

<!ENTITY % inline "%phrase %obsolete-font">
<!ENTITY % pre-inline "%font %obsolete-phrase %obsolete-p">

<!ENTITY % text "#PCDATA | IMG | %inline | BR %obsolete-p">

<!ENTITY % htext "A | %text"    -- Plus links, no structure -->

<![ %HTML.font-phrase [ <!ENTITY % font-content "(%htext)+"> ]]>
<!ENTITY % font-content "#PCDATA">
<!ELEMENT (%font;) - - (%font-content;)>

<!ELEMENT (%phrase;) - - (%htext)+>

<!ENTITY % pre "PRE | XMP | LISTING">

<![ %HTML.forms [ <!ENTITY % block-form "| FORM | ISINDEX"> ]]>
<!ENTITY % block-form "">

<![ %HTML.pSeparator [
	<!ENTITY % obsolete-htext "| %htext">
	<!ENTITY % block-p "">
	]]>
<!ENTITY % obsolete-htext "| A">
<!ENTITY % block-p "| P ">

<!ENTITY % block "HR | %list | DL
		| %pre | BLOCKQUOTE | ADDRESS 
		%block-form %block-p">


<![ %HTML.bodyBlockOnly [
	<!ENTITY % current-htext "">
	]]>
<!ENTITY % current-htext "| %htext">

<!ENTITY % body-content "%heading | %block %current-htext">
<!ELEMENT BODY O O  (%body-content)*>


<!ELEMENT A     - - (%heading|%block|%text)+ -(A)
	-- @# Technically, this allows silliness like:
		<H2><A>xyz<H1>h1</H1></A></H2>
	The right way to do anchors outside of %htext is more like:
		<as id=z1><H2>lkjlkj</h2><ae start=z1>
	-->
<!ATTLIST A
        %linkattributes;
        >

<!ELEMENT IMG    - O EMPTY --  Embedded image -->
<!ATTLIST IMG
        SRC %URI;  #IMPLIED     -- URI of document to embed --
	ALT CDATA #IMPLIED
	ALIGN (top|middle|bottom) #IMPLIED
	ISMAP (ISMAP) #IMPLIED
        >


<![ %HTML.pSeparator [ <!ENTITY % p-content "EMPTY"> ]]>
<!ENTITY % p-content "(%htext)+">
<!ELEMENT P     - O %p-content>
<!ELEMENT HR    - O EMPTY -- horizontal rule -->
<!ELEMENT BR    - O EMPTY -- @# BR -> &br; -->

<!ELEMENT ( %heading )  - -  (%htext;)+>

<!ELEMENT DL    - -  (DT*, DD?)+>
<!ATTLIST DL
	COMPACT (COMPACT) #IMPLIED>

<!ELEMENT DT    - O (%htext)+>
<!ELEMENT DD    - O (%htext|%block)+>

<!ELEMENT (%list) - -  (LI)+>

<!ELEMENT LI    - O (%htext|%block)+>

<!ELEMENT BLOCKQUOTE - - (%htext|%block)+ -- @# Hmm... --
        -- for quoting some other source -->

<!ELEMENT ADDRESS - - (%htext;|%block)+>

<!ELEMENT PRE - - (#PCDATA|%pre-inline|A)+>
<!ATTLIST PRE
        WIDTH NUMBER #implied
        >

<!-- Mnemonic character entities. -->

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

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

<!-- Processing Entities -->

<!ENTITY nbsp "<? nonbreaking-space>">
<!-- @# should add entites for processing instructions
	for line break, centering, etc. -->


<!-- Forms  -->
<![ %HTML.forms [

<!ENTITY % HTTP-Method "(GET | POST)">
<!ELEMENT FORM - - (%body-content)* -(FORM) +(INPUT|SELECT|TEXTAREA)>
<!ATTLIST FORM
	ACTION %URI #REQUIRED
	METHOD %HTTP-Method #IMPLIED -- @# MAILTO? --
	ENCTYPE %Content-Type; #IMPLIED
	>

<!ENTITY % InputType "(TEXT | PASSWORD | CHECKBOX |
			RADIO | SUBMIT | RESET |
			IMAGE | HIDDEN )">
<!ELEMENT INPUT - O EMPTY>
<!ATTLIST INPUT
	TYPE %InputType #IMPLIED -- @# defaults to TEXT?? --
	NAME CDATA #IMPLIED -- required for all but submit and reset --
	VALUE CDATA #IMPLIED
	SRC %URI #IMPLIED -- for image inputs -- 
	CHECKED (CHECKED) #IMPLIED
	SIZE CDATA #IMPLIED -- @# should be NUMBERS: delimit with space, not comma --
	MAXLENGTH NUMBER #IMPLIED
	ALIGN (top|middle|bottom|left|center|right) #IMPLIED --@#supported?--
	>

<!ELEMENT SELECT - - (OPTION+)>
<!ATTLIST SELECT
	NAME CDATA #REQUIRED
	SIZE NUMBER #IMPLIED
	MULTIPLE (MULTIPLE) #IMPLIED
	>

<!ELEMENT OPTION - O (#PCDATA)>
<!ATTLIST OPTION
	SELECTED (SELECTED) #IMPLIED
	VALUE CDATA #IMPLIED
	>

<!ELEMENT TEXTAREA - - (#PCDATA)>
<!ATTLIST TEXTAREA
	NAME CDATA #REQUIRED
	ROWS NUMBER #REQUIRED -- @#implied? --
	COLS NUMBER #REQUIRED
	>
]]>

<!-- Obsolete Elements  -->

<![ %HTML.litCDATA [ <!ENTITY % lit-content "CDATA"> ]]>
<!ENTITY % lit-content "RCDATA">
<!ELEMENT (%literal) - -  %lit-content>

<![ %HTML.PLAINTEXT [
<!ELEMENT PLAINTEXT - O EMPTY>
]]>
\end{verbatim}







\chapter{Security Considerations}Anchors, embedded images, and all
other elements which contain URls
as parameters may cause the URI to
be dereferenced, in which case the
security considerations of the URI
specification apply.\par 
Documents may be constructed whose
visible contents mislead one to follow
a link by  to unsuitable or offensive
material.







\chapter{Acknowledgements}The HTML document type was designed
initially at CERN in 1990 for the
World-Wide Web project. The DTD was
written, and the specification tightened
up, by Dan Connolly. After much discussion
on the network and some enhancement
in particular the addition of inline
images introduced by the NCSA "Mosaic"
software for WWW.   The FORMS material
is derived from the HTML+ specification
with the help of Dave Raggett.This document is the work of many
contributors. Many thanks to Erik
Naggum and James Clark for making
SGML technology available, and toTerry
Allen, Dave Raggett, Marc Andressen,
William Perry, and the rest of the
WWW community.

$<$/ADDRESS$>$







\chapter{References}
\begin{DL}{allow this much space}
\item[SGML
] ISO 8879:1986, Information Processing
Text and Office Systems Standard
Generalized Markup Language (SGML).
\item[sgmls
] an SGML parser by James Clark
$<$jjc@jclark.com$>$ derived from the
ARCSGML parser materials which were
written by Charles F. Goldfarb. The
source is available on the ifi.uio.no
FTP server in the directory /pub/SGML/SGMLS
.
\item[W3
] The World-Wide Web , a global
information initiative. For bootstrap
information, telnet info.cern.ch
or find documents by ftp://info.cern.ch/pub/www/doc
\item[URI
] Universal Resource Identifiers.
RFCxxx. Currently available by anonymous
FTP from info.cern.ch in /pub/www/doc/url*.\{ps,txt\}
\end{DL}








\chapter{Author's addresses}
\begin{verbatim}
				Daniel W. Connolly
		Affiliation:	HaL Software Systems
				Austin, TX
				USA
		email:		connolly@hal.com


				Tim Berners-Lee
		Address		CERN
				1211 Geneva 23
				Switzerland
		Telephone: 	+41(22)767 3755
		Fax:       	+41(22)767 7155
		email:	   	timbl@info.cern.ch


\end{verbatim}


\end{document}
