< draft-ietf-html-spec-04.txt   draft-ietf-html-spec-05.txt >
HTML Working Group T. Berners-Lee HTML Working Group T. Berners-Lee
INTERNET-DRAFT MIT/W3C INTERNET-DRAFT MIT/W3C
<draft-ietf-html-spec-04.txt> D. Connolly <draft-ietf-html-spec-05.txt> D. Connolly
Expires: In six months June 16, 1995 Expires: In six months August 8, 1995
Hypertext Markup Language - 2.0 Hypertext Markup Language - 2.0
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
skipping to change at page 2, line 34 skipping to change at page 2, line 34
5.5 Block Structuring Elements ........................... 23 5.5 Block Structuring Elements ........................... 23
5.6 List Elements ........................................ 25 5.6 List Elements ........................................ 25
5.7 Phrase Markup ........................................ 28 5.7 Phrase Markup ........................................ 28
5.8 Line Break: BR ....................................... 31 5.8 Line Break: BR ....................................... 31
5.9 Horizontal Rule: HR .................................. 31 5.9 Horizontal Rule: HR .................................. 31
5.10 Image: IMG ........................................... 31 5.10 Image: IMG ........................................... 31
6 Characters, Words, and Paragraphs .................... 33 6 Characters, Words, and Paragraphs .................... 33
6.1 The HTML Document Character Set ...................... 33 6.1 The HTML Document Character Set ...................... 33
7 Hyperlinks ........................................... 34 7 Hyperlinks ........................................... 34
7.1 Accessing Resources .................................. 34 7.1 Accessing Resources .................................. 34
7.2 Activation of Hyperlinks ............................. 34 7.2 Activation of Hyperlinks ............................. 35
7.3 Simultaneous Presentation of Image Resources ......... 35 7.3 Simultaneous Presentation of Image Resources ......... 35
7.4 Fragment Identifiers ................................. 35 7.4 Fragment Identifiers ................................. 36
7.5 Queries and Indexes .................................. 35 7.5 Queries and Indexes .................................. 36
7.6 Image Maps ........................................... 36 7.6 Image Maps ........................................... 37
8 Forms ................................................ 36 8 Forms ................................................ 37
8.1 Form Elements ........................................ 37 8.1 Form Elements ........................................ 37
8.2 Form Submission ...................................... 42 8.2 Form Submission ...................................... 42
9 HTML Public Text ..................................... 45 9 HTML Public Text ..................................... 45
9.1 HTML DTD ............................................. 45 9.1 HTML DTD ............................................. 46
9.2 Strict HTML DTD ...................................... 56 9.2 Strict HTML DTD ...................................... 57
9.3 Level 1 HTML DTD ..................................... 57 9.3 Level 1 HTML DTD ..................................... 57
9.4 Strict Level 1 HTML DTD .............................. 58 9.4 Strict Level 1 HTML DTD .............................. 58
9.5 SGML Declaration for HTML ............................ 58 9.5 SGML Declaration for HTML ............................ 59
9.6 Sample SGML Open Entity Catalog for HTML ............. 60 9.6 Sample SGML Open Entity Catalog for HTML ............. 61
9.7 Character Entity Sets ................................ 61 9.7 Character Entity Sets ................................ 62
10 Security Considerations .............................. 63 10 Security Considerations .............................. 64
11 References ........................................... 64 11 References ........................................... 64
12 Acknowledgments ...................................... 65 12 Acknowledgments ...................................... 66
12.1 Authors' Addresses ................................... 66 12.1 Authors' Addresses ................................... 66
13 The HTML Coded Character Set ......................... 66 13 The HTML Coded Character Set ......................... 66
14 Proposed Entities .................................... 69 14 Proposed Entities .................................... 69
1. Introduction 1. Introduction
The HyperText Markup Language (HTML) is a simple data format The HyperText Markup Language (HTML) is a simple data format
used to create hypertext documents that are portable from one used to create hypertext documents that are portable from one
platform to another. HTML documents are SGML documents with platform to another. HTML documents are SGML documents with
generic semantics that are appropriate for representing generic semantics that are appropriate for representing
skipping to change at page 5, line 44 skipping to change at page 5, line 44
An HTML user agent is a level 2 user agent if, additionally: An HTML user agent is a level 2 user agent if, additionally:
* It allows the user to express all form field values * It allows the user to express all form field values
specified in an HTML document and to (attempt to) submit the specified in an HTML document and to (attempt to) submit the
values as requests to information services. values as requests to information services.
2. Terms 2. Terms
absolute URI absolute URI
a URI in absolute form, as per [URL] a URI in absolute form; for example, as per [URL]
anchor anchor
one of two ends of a hyperlink; typically, a phrase one of two ends of a hyperlink; typically, a phrase
marked as an <A> element. marked as an <A> element.
base URI base URI
URI used as the base of an HTML document for the purpose an absolute URI used in combination with a relative URI
of resolving hyperlink destinations. to determine another absolute URI.
character character
An atom of information, for example a letter or a digit. An atom of information, for example a letter or a digit.
Graphic characters have associated glyphs, where as Graphic characters have associated glyphs, where as
control characters have associated processing semantics. control characters have associated processing semantics.
character encoding character encoding
scheme scheme
A function whose domain is the set of sequences of A function whose domain is the set of sequences of
octets, and whose range is the set of sequences of octets, and whose range is the set of sequences of
skipping to change at page 8, line 55 skipping to change at page 8, line 55
associated character encoding scheme, transmitted over associated character encoding scheme, transmitted over
the network or stored in a file. [SGML] the network or stored in a file. [SGML]
typical typical
Typical processing is described for many elements. This Typical processing is described for many elements. This
is not a mandatory part of the specification but is is not a mandatory part of the specification but is
given as guidance for designers and to help explain the given as guidance for designers and to help explain the
uses for which the elements were intended. uses for which the elements were intended.
URI URI
A Universal Resource Identifier is a formatted string A Uniform Resource Identifier is a formatted string that
that serves as an identifier for a resource, typically serves as an identifier for a resource, typically on the
on the Internet. URIs are used in HTML to identify the Internet. URIs are used in HTML to identify the anchors
destination of hyperlinks. URIs in common practice of hyperlinks. URIs in common practice include Uniform
include Uniform Resource Locators (URLs)[URL] and Resource Locators (URLs)[URL] and Relative URLs
Relative URLs [RELURL]. [RELURL].
user agent user agent
A component of a distributed system that presents an A component of a distributed system that presents an
interface and processes requests on behalf of a user; interface and processes requests on behalf of a user;
for example, a www browser or a mail user agent. for example, a www browser or a mail user agent.
WWW WWW
The World-Wide Web is a hypertext-based, distributed The World-Wide Web is a hypertext-based, distributed
information system created by researchers at CERN in information system created by researchers at CERN in
Switzerland. <URL:http://www.w3.org/> Switzerland. <URL:http://www.w3.org/>
skipping to change at page 15, line 20 skipping to change at page 15, line 20
<!-- Id: html-sgml.sgm,v 1.5 1995/05/26 21:29:50 connolly Exp --> <!-- Id: html-sgml.sgm,v 1.5 1995/05/26 21:29:50 connolly Exp -->
<!-- another -- -- comment --> <!-- another -- -- comment -->
<!> <!>
</HEAD> </HEAD>
<BODY> <BODY>
<p> <!- not a comment, just regular old data characters -> <p> <!- not a comment, just regular old data characters ->
3.3. HTML Public Text Identifiers 3.3. HTML Public Text Identifiers
To identify information as an HTML document conforming to this To identify information as an HTML document conforming to this
specification, each document should start with one of the specification, each document must start with one of the
following document type declarations. following document type declarations.
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
This document type declaration refers to the HTML DTD in 9.1, This document type declaration refers to the HTML DTD in 9.1,
"HTML DTD". "HTML DTD".
NOTE - If the body of a `text/html' message entity does NOTE - If the body of a `text/html' message entity does
not begin with a document type declaration, an HTML user not begin with a document type declaration, an HTML user
agent should infer the above document type declaration. agent should infer the above document type declaration.
skipping to change at page 19, line 45 skipping to change at page 19, line 45
minimize this possibility, titles should be fewer than minimize this possibility, titles should be fewer than
64 characters. 64 characters.
A user agent may display the title of a document in a history A user agent may display the title of a document in a history
list or as a label for the window displaying the document. This list or as a label for the window displaying the document. This
differs from headings (5.4, "Headings: H1 ... H6"), which are differs from headings (5.4, "Headings: H1 ... H6"), which are
typically displayed within the body text flow. typically displayed within the body text flow.
5.2.2. Base Address: BASE 5.2.2. Base Address: BASE
The optional <BASE> element specifies the base address for The optional <BASE> element allows the address of a document to
resolving relative links from the document, overriding any be recorded in situations in which the document may be read out
context otherwise known to the user agent. The required HREF of context. The required HREF attribute specifies the base URI
attribute specifies the URI for navigating the document (see 7, (see 7, "Hyperlinks") for navigating the document, overriding
"Hyperlinks"). The value of the HREF attribute must be an any context otherwise known to the user agent. The value of the
absolute URI. HREF attribute must be an absolute URI.
5.2.3. Keyword Index: ISINDEX 5.2.3. Keyword Index: ISINDEX
The <ISINDEX> element indicates that the user agent should allow The <ISINDEX> element indicates that the user agent should allow
the user to search an index by giving keywords. See 7.5, the user to search an index by giving keywords. See 7.5,
"Queries and Indexes" for details. "Queries and Indexes" for details.
5.2.4. Link: LINK 5.2.4. Link: LINK
The <LINK> element represents a hyperlink (see 7, "Hyperlinks"). The <LINK> element represents a hyperlink (see 7, "Hyperlinks").
skipping to change at page 34, line 8 skipping to change at page 34, line 8
Kurt G&ouml;del was a famous logician and mathematician. Kurt G&ouml;del was a famous logician and mathematician.
See 9.7.2, "ISO Latin 1 Character Entity Set" for a table of the See 9.7.2, "ISO Latin 1 Character Entity Set" for a table of the
``Added Latin 1'' entities, and 13, "The HTML Coded Character ``Added Latin 1'' entities, and 13, "The HTML Coded Character
Set" for a table of the code positions of [ISO 8859-1] and the Set" for a table of the code positions of [ISO 8859-1] and the
control characters in the HTML document character set. control characters in the HTML document character set.
7. Hyperlinks 7. Hyperlinks
In addition to general purpose elements such as paragraphs and In addition to general purpose elements such as paragraphs and
lists, HTML documents can express hyperlinks. A hyperlink is a lists, HTML documents can express hyperlinks. An HTML user agent
relationship between two anchors, called the head and the tail allows the user to navigate these hyperlinks.
of the hyperlink[DEXTER]. An anchor is a resource such as an
HTML document, or some fragment of, i.e. view on or portion of a
resource. Typically, the user activates a link by indicating the
tail of the link; the head of the link is presented as a result.
Anchors are addressed by Uniform Resource Identifiers (URI). A hyperlink is a relationship between two anchors, called the
URIs either refer directly to an anchor in absolute form for head and the tail of the hyperlink[DEXTER]. Each anchor is
example as in [URL], or they refer to an anchor relative to a addressed, or uniquely identified, by an absolute Uniform
base URI which is absolute, as in [RELURL]. Resource Identifier (URI), optionally followed by a '#' and a
sequence of characters called a fragment identifier, as per
[RELURL]. For example:
http://www.w3.org/hypertext/WWW/TheProject.html
http://www.w3.org/hypertext/WWW/TheProject.html#z31
In an anchor address, the URI refers to a resource; it may be
used in a variety of information retrieval protocols to obtain
an entity that represents the resource, such as an HTML
document. The fragment identifier, if present, refers to some
view on, or portion of the resource.
An HTML user agent begins navigation with an absolute URI,
called the base URI, and an HTML document that is a
representation of the resource identified by the base URI.
Each of the following markup constructs indicates the tail Each of the following markup constructs indicates the tail
anchor of a hyperlink or set of hyperlinks: anchor of a hyperlink or set of hyperlinks:
* <A> elements with HREF present. * <A> elements with HREF present.
* <LINK> elements. * <LINK> elements.
* <IMG> elements. * <IMG> elements.
* <INPUT> elements with the SRC attribute present. * <INPUT> elements with the SRC attribute present.
* <ISINDEX> elements. * <ISINDEX> elements.
* <FORM> elements with `METHOD=GET'. * <FORM> elements with `METHOD=GET'.
These markup constructs refer to head anchors either directly by
means of an absolute URI, or indirectly by means of a relative
URI, which must be combined with the base URI as in [RELURL] to
determine the address of the head anchor. The markup may also
include fragment identifiers, separated from the URI by a '#'
character.
7.1. Accessing Resources 7.1. Accessing Resources
To access the head anchor of a hyperlink, the user agent Once the address of the head anchor is determined, the user
determines its URI from the URI given in the tail anchor, using agent may obtain a representation of the resource, for example
the base URI of the document containing the tail anchor if as in [URL].
necessary. Any fragment identifier is discarded, and the result
is used to access a resource, for example as in [URL].
For example, if a document identified as `http://host/x/y.html' For example, if the base URI is `http://host/x/y.html' and the
contains: document contains:
<img src="../icons/abc.gif"> <img src="../icons/abc.gif">
then the user agent must use the URI `http://host/icons/abc.gif' then the user agent uses the URI `http://host/icons/abc.gif' to
to access the resource linked from the <IMG> element. access the resource linked from the <IMG> element.
If the URI in the address of the head anchor is the same as the
base URI, then the base document is sufficient as a
representation of the resource. A user agent must _not_, for
example, use any network information retrieval protocols to
obtain a new representation of the resourse.
For example, if the base uri is
`http:'/www.w3.org/hypertext/WWW/TheProject.html/, then each of
the following markup constructs indicates a link whose head and
tail anchors have the same URI in their address:
<a href="#xyz">
<a href="../WWW/TheProject.html">
<a href="./TheProject.html">
<a href="TheProject.html">
<a href="TheProject.html#z21">
<a href="../../hypertext/WWW/TheProject.html">
<a href="http://www.w3.org/hypertext/WWW/TheProject.html">
7.2. Activation of Hyperlinks 7.2. Activation of Hyperlinks
An HTML user agent allows the user to navigate the content of An HTML user agent allows the user to navigate the content of
the document and request activation of <A> element hyperlinks. A the document and request activation of hyperlinks denoted by <A>
request to activate a link is essentially a request to process elements. HTML user agents should also allow activation of
the resource indicated by the head anchor of the link, for <LINK> element hyperlinks.
example to display the indicated HTML document. HTML user agents
should also allow activation of <LINK> element hyperlinks.
The base URI for navigating the head anchor may be different To activate a link, the user agent obtains a representation of
from the URI used to access it. For example, it may be replaced the resource identified in the address of the head anchor. If
by a <BASE> tag in the destination document or by an HTTP the representation is another HTML document, navigation may
begin again with this new document. The base URI for navigation
is taken from the head anchor by default; however, any <BASE>
tag in the destination document overrides this default. The
process of obtaining the destination document may also override
the base URI, as in the case of an HTTP `URI:' header or
redirection transaction. redirection transaction.
7.3. Simultaneous Presentation of Image Resources 7.3. Simultaneous Presentation of Image Resources
An HTML user agent may activate hyperlinks indicated by <IMG> An HTML user agent may activate hyperlinks indicated by <IMG>
and <INPUT> elements concurrently with processing the document; and <INPUT> elements concurrently with processing the document;
that is, image hyperlinks may be processed without explicit that is, image hyperlinks may be processed without explicit
request by the user. Image resources should be embedded in the request by the user. Image resources should be embedded in the
presentation at the point of the tail anchor, that is the <IMG> presentation at the point of the tail anchor, that is the <IMG>
or <INPUT> element. or <INPUT> element.
<LINK> hyperlinks may also be processed without explicit user <LINK> hyperlinks may also be processed without explicit user
request; for example, style sheet resources may be processed request; for example, style sheet resources may be processed
before or during the processing of the document. before or during the processing of the document.
7.4. Fragment Identifiers 7.4. Fragment Identifiers
Any characters following a `#' character in a URI constitute a Any characters following a `#' character in a hypertext address
fragment identifier. As a degenerate case, a URI of the form constitute a fragment identifier. In particular, an address of
`#fragment' refers to an anchor in the same document. the form `#fragment' refers to an anchor in the same document.
The meaning of fragment identifiers depends on the media type of The meaning of fragment identifiers depends on the media type of
the resource containing the head anchor. For `text/html' the representation of the anchor's resource. For `text/html'
resources, it refers to the <A> element with a NAME attribute representations, it refers to the <A> element with a NAME
whose value is the same as the fragment identifier. The matching attribute whose value is the same as the fragment identifier.
is case sensitive. The document should have exactly one such The matching is case sensitive. The document should have exactly
element. The user agent should indicate the anchor element, for one such element. The user agent should indicate the anchor
example by scrolling to and/or highlighting the phrase. element, for example by scrolling to and/or highlighting the
phrase.
For example, if a user agent was processing a document For example, if the base URI is `http://host/x/y.html' and the
identified as `http://host/x/y.html' and the user indicated the user activated the link denoted by the following markup:
following anchor:
<p> See: <a href="app1.html#bananas">appendix 1</a> <p> See: <a href="app1.html#bananas">appendix 1</a>
for more detail on bananas. for more detail on bananas.
then the user agent URI must access the resource Then the user agent accesses the resource identified by
`http://host/x/app1.html'. Assuming the resource is represented `http://host/x/app1.html'. Assuming the resource is represented
using the `text/html' media type, the user agent must locate the using the `text/html' media type, the user agent must locate the
anchor named `bananas' and begin navigation there. <A> element whose NAME attribute is `bananas' and begin
navigation there.
7.5. Queries and Indexes 7.5. Queries and Indexes
The <ISINDEX> element represents a set of hyperlinks. The user The <ISINDEX> element represents a set of hyperlinks. The user
can choose from the set by providing keywords to the user agent. can choose from the set by providing keywords to the user agent.
The user agent computes the head URI by appending `?' and the The user agent computes the head URI by appending `?' and the
keywords to the base URI. The keywords are escaped according to keywords to the base URI. The keywords are escaped according to
[URL] and joined by `+'. For example, if a document contains: [URL] and joined by `+'. For example, if a document contains:
<BASE HREF="http://host/index"> <BASE HREF="http://host/index">
<ISINDEX> <ISINDEX>
and the user provides the keywords `apple' and `berry', then the and the user provides the keywords `apple' and `berry', then the
user agent must access the resource user agent must access the resource
`http://host/index?apple+berry'. `http://host/index?apple+berry'.
skipping to change at page 43, line 8 skipping to change at page 43, line 43
data, but hidden fields with VALUE attributes present data, but hidden fields with VALUE attributes present
should. should.
NOTE - The URI from a query form submission can be NOTE - The URI from a query form submission can be
used in a normal anchor style hyperlink. used in a normal anchor style hyperlink.
Unfortunately, the use of the `&' character to Unfortunately, the use of the `&' character to
separate form fields interacts with its use in SGML separate form fields interacts with its use in SGML
attribute values as an entity reference delimiter. attribute values as an entity reference delimiter.
For example, the URI `http://host/?x=1&y=2' must be For example, the URI `http://host/?x=1&y=2' must be
written `<a href="http://host/?x=1&#38;y=2"' or `<a written `<a href="http://host/?x=1&#38;y=2"' or `<a
href="http://host/?x=1&#amp;y=2">'. href="http://host/?x=1&amp;y=2">'.
HTTP server implementors, and in particular, CGI HTTP server implementors, and in particular, CGI
implementors are encouraged to support the use of implementors are encouraged to support the use of
`;' in place of `&' to save users the trouble of `;' in place of `&' to save users the trouble of
escaping `&' characters this way. escaping `&' characters this way.
8.2.2. Query Forms: METHOD=GET 8.2.2. Query Forms: METHOD=GET
If the processing of a form is idempotent (i.e. it has no If the processing of a form is idempotent (i.e. it has no
lasting observable effect on the state of the world), then the lasting observable effect on the state of the world), then the
skipping to change at page 44, line 54 skipping to change at page 45, line 36
name name
``John Doe'' ``John Doe''
gender gender
``male'' ``male''
family family
``5'' ``5''
city city
``kent,miami'' ``kent''
city
``miami''
other other
``abc\ndef'' ``abc\ndef''
nickname nickname
``J&D'' ``J&D''
The user agent then conducts an HTTP POST transaction using the The user agent then conducts an HTTP POST transaction using the
URI `http://www.w3.org/sample'. The message body would be URI `http://www.w3.org/sample'. The message body would be
(ignore the line break): (ignore the line break):
name=John+Doe&gender=male&family=5&city=kent%2Cmiami& name=John+Doe&gender=male&family=5&city=kent&city=miami&
other=abc%0D%0Adef&nickname=J%26D other=abc%0D%0Adef&nickname=J%26D
9. HTML Public Text 9. HTML Public Text
9.1. HTML DTD 9.1. HTML DTD
This is the Document Type Definition for the HyperText Markup This is the Document Type Definition for the HyperText Markup
Language, level 2. Language, level 2.
<!-- html.dtd <!-- html.dtd
Document Type Definition for the HyperText Markup Language Document Type Definition for the HyperText Markup Language
(HTML DTD) (HTML DTD)
$Id: html.dtd,v 1.28 1995/06/16 18:54:22 connolly Exp $ $Id: html.dtd,v 1.29 1995/08/04 17:50:22 connolly Exp $
Author: Daniel W. Connolly <connolly@w3.org> Author: Daniel W. Connolly <connolly@w3.org>
See Also: html.decl, html-1.dtd See Also: html.decl, html-1.dtd
http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html
- --> - -->
<!ENTITY % HTML.Version <!ENTITY % HTML.Version
"-//IETF//DTD HTML 2.0//EN" "-//IETF//DTD HTML 2.0//EN"
-- Typical usage: -- Typical usage:
skipping to change at page 46, line 43 skipping to change at page 47, line 28
<!ENTITY % Content-Type "CDATA" <!ENTITY % Content-Type "CDATA"
-- meaning an internet media type -- meaning an internet media type
(aka MIME content type, as per RFC1521) (aka MIME content type, as per RFC1521)
--> -->
<!ENTITY % HTTP-Method "GET | POST" <!ENTITY % HTTP-Method "GET | POST"
-- as per HTTP specification, in progress -- as per HTTP specification, in progress
--> -->
<!ENTITY % URI "CDATA"
-- The term URI means a CDATA attribute
whose value is a Uniform Resource Identifier,
as defined by
"Universal Resource Identifiers" by Tim Berners-Lee
aka RFC 1630
Note that CDATA attributes are limited by the LITLEN
capacity (1024 in the current version of html.decl),
so that URIs in HTML have a bounded length.
-->
<!--========= DTD "Macros" =====================--> <!--========= DTD "Macros" =====================-->
<!ENTITY % heading "H1|H2|H3|H4|H5|H6"> <!ENTITY % heading "H1|H2|H3|H4|H5|H6">
<!ENTITY % list " UL | OL | DIR | MENU " > <!ENTITY % list " UL | OL | DIR | MENU " >
<!--======= Character mnemonic entities =================--> <!--======= Character mnemonic entities =================-->
<!ENTITY % ISOlat1 PUBLIC <!ENTITY % ISOlat1 PUBLIC
"ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML"> "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML">
%ISOlat1; %ISOlat1;
skipping to change at page 48, line 32 skipping to change at page 49, line 4
<!-- <STRONG> Strong emphais --> <!-- <STRONG> Strong emphais -->
<!-- <CODE> Source code phrase --> <!-- <CODE> Source code phrase -->
<!-- <SAMP> Sample text or characters --> <!-- <SAMP> Sample text or characters -->
<!-- <KBD> Keyboard phrase, e.g. user input --> <!-- <KBD> Keyboard phrase, e.g. user input -->
<!-- <VAR> Variable phrase or substituable --> <!-- <VAR> Variable phrase or substituable -->
<!-- <CITE> Name or title of cited work --> <!-- <CITE> Name or title of cited work -->
<!ENTITY % pre.content "#PCDATA | A | HR | BR | %font | %phrase"> <!ENTITY % pre.content "#PCDATA | A | HR | BR | %font | %phrase">
]]> ]]>
<!ENTITY % text "#PCDATA | A | IMG | BR"> <!ENTITY % text "#PCDATA | A | IMG | BR">
<!ELEMENT BR - O EMPTY> <!ELEMENT BR - O EMPTY>
<!ATTLIST BR <!ATTLIST BR
%SDAPREF; "&#RE;" %SDAPREF; "&#RE;"
> >
<!-- <BR> Line break --> <!-- <BR> Line break -->
<!--========= Link Markup ======================--> <!--========= Link Markup ======================-->
<!ENTITY % linkType "NAME"> <!ENTITY % linkType "NAMES">
<!ENTITY % linkExtraAttributes <!ENTITY % linkExtraAttributes
"REL %linkType #IMPLIED "REL %linkType #IMPLIED
REV %linkType #IMPLIED REV %linkType #IMPLIED
URN CDATA #IMPLIED URN CDATA #IMPLIED
TITLE CDATA #IMPLIED TITLE CDATA #IMPLIED
METHODS NAMES #IMPLIED METHODS NAMES #IMPLIED
"> ">
<![ %HTML.Recommended [ <![ %HTML.Recommended [
skipping to change at page 49, line 14 skipping to change at page 49, line 37
-- <H1><a name="xxx">Heading</a></H1> -- <H1><a name="xxx">Heading</a></H1>
is preferred to is preferred to
<a name="xxx"><H1>Heading</H1></a> <a name="xxx"><H1>Heading</H1></a>
--> -->
]]> ]]>
<!ENTITY % A.content "(%heading|%text)*"> <!ENTITY % A.content "(%heading|%text)*">
<!ELEMENT A - - %A.content -(A)> <!ELEMENT A - - %A.content -(A)>
<!ATTLIST A <!ATTLIST A
HREF %URI #IMPLIED HREF CDATA #IMPLIED
NAME CDATA #IMPLIED NAME CDATA #IMPLIED
%linkExtraAttributes; %linkExtraAttributes;
%SDAPREF; "<Anchor: #AttList>" %SDAPREF; "<Anchor: #AttList>"
> >
<!-- <A> Anchor; source/destination of link --> <!-- <A> Anchor; source/destination of link -->
<!-- <A NAME="..."> Name of this anchor --> <!-- <A NAME="..."> Name of this anchor -->
<!-- <A HREF="..."> Address of link destination --> <!-- <A HREF="..."> Address of link destination -->
<!-- <A URN="..."> Permanent address of destination --> <!-- <A URN="..."> Permanent address of destination -->
<!-- <A REL=...> Relationship to destination --> <!-- <A REL=...> Relationship to destination -->
<!-- <A REV=...> Relationship of destination to this --> <!-- <A REV=...> Relationship of destination to this -->
<!-- <A TITLE="..."> Title of destination (advisory) --> <!-- <A TITLE="..."> Title of destination (advisory) -->
<!-- <A METHODS="..."> Operations on destination (advisory) --> <!-- <A METHODS="..."> Operations on destination (advisory) -->
<!--========== Images ==========================--> <!--========== Images ==========================-->
<!ELEMENT IMG - O EMPTY> <!ELEMENT IMG - O EMPTY>
<!ATTLIST IMG <!ATTLIST IMG
SRC %URI; #REQUIRED SRC CDATA #REQUIRED
ALT CDATA #IMPLIED ALT CDATA #IMPLIED
ALIGN (top|middle|bottom) #IMPLIED ALIGN (top|middle|bottom) #IMPLIED
ISMAP (ISMAP) #IMPLIED ISMAP (ISMAP) #IMPLIED
%SDAPREF; "<Fig><?SDATrans Img: #AttList>#AttVal(Alt)</Fig>" %SDAPREF; "<Fig><?SDATrans Img: #AttList>#AttVal(Alt)</Fig>"
> >
<!-- <IMG> Image; icon, glyph or illustration --> <!-- <IMG> Image; icon, glyph or illustration -->
<!-- <IMG SRC="..."> Address of image object --> <!-- <IMG SRC="..."> Address of image object -->
<!-- <IMG ALT="..."> Textual alternative --> <!-- <IMG ALT="..."> Textual alternative -->
<!-- <IMG ALIGN=...> Position relative to text --> <!-- <IMG ALIGN=...> Position relative to text -->
skipping to change at page 53, line 33 skipping to change at page 54, line 4
<!-- <BLOCKQUOTE> Quoted passage --> <!-- <BLOCKQUOTE> Quoted passage -->
<!ELEMENT ADDRESS - - (%text|P)*> <!ELEMENT ADDRESS - - (%text|P)*>
<!ATTLIST ADDRESS <!ATTLIST ADDRESS
%SDAFORM; "Lit" %SDAFORM; "Lit"
%SDAPREF; "Address:&#RE;" %SDAPREF; "Address:&#RE;"
> >
<!-- <ADDRESS> Address, signature, or byline --> <!-- <ADDRESS> Address, signature, or byline -->
<!--======= Forms ====================--> <!--======= Forms ====================-->
<![ %HTML.Forms [ <![ %HTML.Forms [
<!ELEMENT FORM - - %body.content -(FORM) +(INPUT|SELECT|TEXTAREA)> <!ELEMENT FORM - - %body.content -(FORM) +(INPUT|SELECT|TEXTAREA)>
<!ATTLIST FORM <!ATTLIST FORM
ACTION %URI #IMPLIED ACTION CDATA #IMPLIED
METHOD (%HTTP-Method) GET METHOD (%HTTP-Method) GET
ENCTYPE %Content-Type; "application/x-www-form-urlencoded" ENCTYPE %Content-Type; "application/x-www-form-urlencoded"
%SDAPREF; "<Para>Form:</Para>" %SDAPREF; "<Para>Form:</Para>"
%SDASUFF; "<Para>Form End.</Para>" %SDASUFF; "<Para>Form End.</Para>"
> >
<!-- <FORM> Fill-out or data-entry form --> <!-- <FORM> Fill-out or data-entry form -->
<!-- <FORM ACTION="..."> Address for completed form --> <!-- <FORM ACTION="..."> Address for completed form -->
<!-- <FORM METHOD=...> Method of submitting form --> <!-- <FORM METHOD=...> Method of submitting form -->
<!-- <FORM ENCTYPE="..."> Representation of form data --> <!-- <FORM ENCTYPE="..."> Representation of form data -->
<!ENTITY % InputType "(TEXT | PASSWORD | CHECKBOX | <!ENTITY % InputType "(TEXT | PASSWORD | CHECKBOX |
RADIO | SUBMIT | RESET | RADIO | SUBMIT | RESET |
IMAGE | HIDDEN )"> IMAGE | HIDDEN )">
<!ELEMENT INPUT - O EMPTY> <!ELEMENT INPUT - O EMPTY>
<!ATTLIST INPUT <!ATTLIST INPUT
TYPE %InputType TEXT TYPE %InputType TEXT
NAME CDATA #IMPLIED NAME CDATA #IMPLIED
VALUE CDATA #IMPLIED VALUE CDATA #IMPLIED
SRC %URI #IMPLIED SRC CDATA #IMPLIED
CHECKED (CHECKED) #IMPLIED CHECKED (CHECKED) #IMPLIED
SIZE CDATA #IMPLIED SIZE CDATA #IMPLIED
MAXLENGTH NUMBER #IMPLIED MAXLENGTH NUMBER #IMPLIED
ALIGN (top|middle|bottom) #IMPLIED ALIGN (top|middle|bottom) #IMPLIED
%SDAPREF; "Input: " %SDAPREF; "Input: "
> >
<!-- <INPUT> Form input datum --> <!-- <INPUT> Form input datum -->
<!-- <INPUT TYPE=...> Type of input interaction --> <!-- <INPUT TYPE=...> Type of input interaction -->
<!-- <INPUT NAME=...> Name of form datum --> <!-- <INPUT NAME=...> Name of form datum -->
skipping to change at page 55, line 36 skipping to change at page 56, line 9
<!-- <HEAD> Document head --> <!-- <HEAD> Document head -->
<!ELEMENT TITLE - - (#PCDATA)*> <!ELEMENT TITLE - - (#PCDATA)*>
<!ATTLIST TITLE <!ATTLIST TITLE
%SDAFORM; "Ti" > %SDAFORM; "Ti" >
<!-- <TITLE> Title of document --> <!-- <TITLE> Title of document -->
<!ELEMENT LINK - O EMPTY> <!ELEMENT LINK - O EMPTY>
<!ATTLIST LINK <!ATTLIST LINK
HREF %URI #REQUIRED HREF CDATA #REQUIRED
%linkExtraAttributes; %linkExtraAttributes;
%SDAPREF; "Linked to : #AttVal (TITLE) (URN) (HREF)>" > %SDAPREF; "Linked to : #AttVal (TITLE) (URN) (HREF)>" >
<!-- <LINK> Link from this document --> <!-- <LINK> Link from this document -->
<!-- <LINK HREF="..."> Address of link destination --> <!-- <LINK HREF="..."> Address of link destination -->
<!-- <LINK URN="..."> Lasting name of destination --> <!-- <LINK URN="..."> Lasting name of destination -->
<!-- <LINK REL=...> Relationship to destination --> <!-- <LINK REL=...> Relationship to destination -->
<!-- <LINK REV=...> Relationship of destination to this --> <!-- <LINK REV=...> Relationship of destination to this -->
<!-- <LINK TITLE="..."> Title of destination (advisory) --> <!-- <LINK TITLE="..."> Title of destination (advisory) -->
<!-- <LINK METHODS="..."> Operations allowed (advisory) --> <!-- <LINK METHODS="..."> Operations allowed (advisory) -->
<!ELEMENT ISINDEX - O EMPTY> <!ELEMENT ISINDEX - O EMPTY>
<!ATTLIST ISINDEX <!ATTLIST ISINDEX
%SDAPREF; %SDAPREF;
"<Para>[Document is indexed/searchable.]</Para>"> "<Para>[Document is indexed/searchable.]</Para>">
<!-- <ISINDEX> Document is a searchable index --> <!-- <ISINDEX> Document is a searchable index -->
<!ELEMENT BASE - O EMPTY> <!ELEMENT BASE - O EMPTY>
<!ATTLIST BASE <!ATTLIST BASE
HREF %URI; #REQUIRED > HREF CDATA #REQUIRED >
<!-- <BASE> Base context document --> <!-- <BASE> Base context document -->
<!-- <BASE HREF="..."> Address for this document --> <!-- <BASE HREF="..."> Address for this document -->
<!ELEMENT NEXTID - O EMPTY> <!ELEMENT NEXTID - O EMPTY>
<!ATTLIST NEXTID <!ATTLIST NEXTID
N CDATA #REQUIRED > N CDATA #REQUIRED >
<!-- <NEXTID> Next ID to use for link name --> <!-- <NEXTID> Next ID to use for link name -->
<!-- <NEXTID N=...> Next ID to use for link name --> <!-- <NEXTID N=...> Next ID to use for link name -->
skipping to change at page 64, line 34 skipping to change at page 65, line 6
<URL:ftp://ds.internic.net/internet-drafts/draft-ietf-http-v10-spec-00.ps> <URL:ftp://ds.internic.net/internet-drafts/draft-ietf-http-v10-spec-00.ps>
[MIME] [MIME]
N. Borenstein and N. Freed. ``MIME (Multipurpose N. Borenstein and N. Freed. ``MIME (Multipurpose
Internet Mail Extensions) Part One: Mechanisms for Internet Mail Extensions) Part One: Mechanisms for
Specifying and Describing the Format of Internet Message Specifying and Describing the Format of Internet Message
Bodies.'' RFC 1521, Bellcore, Innosoft, September 1993. Bodies.'' RFC 1521, Bellcore, Innosoft, September 1993.
<URL:ftp://ds.internic.net/rfc/rfc1521.txt> <URL:ftp://ds.internic.net/rfc/rfc1521.txt>
[RELURL] [RELURL]
R. T. Fielding. ``Relative Uniform Resource Locators.'' R. Fielding. ``Relative Uniform Resource Locators.'' RFC
Work in Progress, UC Irvine, March 1995. 1808, June 1995
<URL:ftp://ds.internic.net/internet-drafts/draft-ietf-uri-relative-url-06.txt> <URL:ftp://ds.internic.net/rfc/rfc1808.txt>
[GOLD90] [GOLD90]
C. F. Goldfarb. ``The SGML Handbook.'' Y. Rubinsky, Ed., C. F. Goldfarb. ``The SGML Handbook.'' Y. Rubinsky, Ed.,
Oxford University Press, 1990. <URL:> Oxford University Press, 1990. <URL:>
[DEXTER] [DEXTER]
Frank Halasz and Mayer Schwartz, ``The Dexter Hypertext Frank Halasz and Mayer Schwartz, ``The Dexter Hypertext
Reference Model'', ``Communications of the ACM'', pp. Reference Model'', ``Communications of the ACM'', pp.
30-39, vol. 37 no. 2, Feb 1994, <URL:> 30-39, vol. 37 no. 2, Feb 1994, <URL:>
 End of changes. 42 change blocks. 
102 lines changed or deleted 128 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/