Re: Anchored rendering of TABLE head/foot
Michael Kaelbling (mjk@sylt.zfe.siemens.de)
Mon, 19 Dec 94 10:48:52 EST
<!doctype HTML public "-//W30//DTD W3 HTML 2.0//EN">
Comments on HTML Spec - 2.0
Comments on Draft of HTML Spec. - 2.0
The comments in this letter are organized according to the sections
in the draft specification.
"1. Abstract"
-
Probable typo: "unlined"
"Simple structured documents with
unlined graphics" should probably read "inlined".
-
Terminology: "W3" vs. "WWW"
This document seems
intent on using the abbreviation "W3", but this preference over
"WWW" is not followed consistently throughtout the document.
Perhaps, "WWW" should be put in §8.
"2. HTML Specification Overview"
-
Implicit forward reference to "Level"
The use of
"level"s precedes the explanation of what levels are. It might be
good to introduce them briefly -- perhaps call them conformance
levels and point to the explanation on page 16.
-
Redundant entry: "Blockquote" and "Quoted Material"
The
<BLOCKQUOTE> element is given twice in §2.2. Perhaps
the second entry should be omitted or reduced to "see Blockquote."
-
Inappropriate reference to Mosaic?
In §2.4 there
is the comment "Not supported by Mosaic." The questions are: What
is Mosaic? Why should we care? What if Mosaic decides to conform
to Level 1?
-
Probable typo: /ul
The example in §2.8 contains "does/ul>" where it
should probably read "does<ul>".
"3. HTML Specification"
-
Inconsistent typeface for URL
Section 3. seems to be the only place a different typeface is used
for a URL.
-
Probable typo: Professionnnal
In §3.12.4 the word "Professionnnal" is a misspelling.
-
Incorrect radio input attributes?
The example in §3.13.1 contains two radio buttons of the
form:
<input name="male" type=radio>
<input name="female" type=radio>
but my feeling is that they should look something like
<input name="gender" value="male" type=radio>
<input name="gender" value="female" type=radio>
-
Missing quote marks?
Also in the example in
§3.13.1, the textarea element should probably have quotemarks
around the numbers in the cols and rows
attributes to be consistent with §3.4.3 and §3.4.2
-
Unsupported ALIGN attribute?
Also in the example in §3.13.1, the apparently nonstandard
ALIGN=CENTER attribute is shown in a P
element.
-
Terminology: "Numeric" vs. "Numerical"
Compare the titles of sections §3.14.3 and §3.15.3; and
check with Mr. Goldfarb, who may have a strong opinion on the choice
of adjective.
-
Missing # characters
There seem to be quite a few incorrectly formed numeric character
references in §3.15.3, i.e., with no # after the
initial & character.
"8. Terms"
-
URL, URN vs. URI
URI made the current list, but it's near relations didn't, when
perhaps they should.
-
Unhappy page break
There is a rather odd page break in the explanation of "W3".
Michael Kaelbling, mjk@zfe.siemens.de
@(#) 1.1