- Section 13.6.1
- Image map examples using "poly" have been fixed
to form a closed polygon. Also, the last pair of coordinates
is the same as the first to close the polygon.
- Section 14.4.1
- In the final example, the STYLE
element is missing the attribute assignment "media=screen, print".
- Section 15.2.1
- In the example with "mypar", the CSS rule should read
P#mypar {font-style: italic; color: blue}
In CSS, "#" refers to an ID name while the
"." refers to a class name. This example is dealing with
the "id" attribute.
- Section 16.2.2
- Values for marginwidth and
marginheight
must be 0 pixels or more, not 1 pixel or more.
- Section 16.2.2
- The FRAME
element does not take the target
attribute.
- Section 16.5
- The IFRAME
element does not take the target
attribute.
- Section 17.2.1
- In the description of "checkboxes", change "selected"
to "checked" in "when the control element's selected
attribute is set."
- Section 17.6.1
- In the "Attributes defined elsewhere" section for the
OPTGROUP element, the
attributes onfocus,
onblur, and onchange
should not be there.
- Section 18.2.3
- To the list of elements that take onfocus
and onblur, add A
and AREA.
- Section 20
- The SGML Declaration for HTML 4.0 must be modified slightly
to support hexadecimal numeric character references.
The lines:
DELIM
GENERAL SGMLREF
SHORTREF SGMLREF
must be changed to:
DELIM
GENERAL SGMLREF
HCRO "&#x" -- 38 is the number for ampersand --
SHORTREF SGMLREF
And the initial <!SGML "ISO 8879:1986" must be changed
to <!SGML "ISO 8879:1986 (WWW)".
- Section 21
- The HR element should
also take the lang
and dir attributes. These are
noted as being defined elsewhere at the element's definition,
but were left out of the DTDs.
- Section 21
- The OBJECT element's
archive attribute is defined
in the DTD as taking a value of type %URI". This is
incorrect: the value may be a space-separated list
of URIs (as indicated in the definition of the
attribute and in the DTDs comment).
- Section 21
- The FORM element's
DTD fragment should include a definition for the
accept attribute, which is
listed in the element's definition. The definition
should be the following:
accept %ContentTypes; #IMPLIED -- list of MIME types for file upload --
Also, the archive attribute
for the OBJECT element is defined
in the DTD as taking a value of type %URI". This is
incorrect: the value may be a space-separated list
of URIs (as indicated in the definition of the
attribute and in the DTD comment).
- Section B.4.1
- At the end of the section, the following sentences are incorrect:
"The list of terms in the content is ALL, INDEX, NOFOLLOW,
NOINDEX. The name and the content attribute values are
case-insensitive." In fact, the META
definition specifies that values for the name and content
attributes are case-sensitive.
- Section B.4.1.1
- The specification reads, "Blank lines are not permitted."
Blank lines are permitted in the robots.txt file, just not within
a single "record". Note that the specification doesn't define
record.
Further down the page, the specification reads, "There must
be exactly one "User-agent" field per record."
In fact, there can be more than one User-Agent field
in the robots.txt file, just not more than one per record.
For information about search robots, please consult, for example:
- References
-
- The [URI] reference
should be updated to RFC 2396 as of August 1998.
"Uniform Resource Identifiers (URI): Generic Syntax",
T. Berners-Lee, R. Fielding, L. Masinter, August 1998.
This RFC is available at
http://ds.internic.net/rfc/rfc2396.txt.
RFC 2396 updates
[RFC1738] and [RFC1808].