Editorial comments for latest 2.0 spec

Earl Hood <ehood@imagine.convex.com>
Date: Fri, 14 Oct 94 15:41:19 EDT
Message-id: <199410141936.OAA03214@imagine.convex.com>
Reply-To: ehood@imagine.convex.com
Originator: html-wg@oclc.org
Sender: html-wg@oclc.org
Precedence: bulk
From: Earl Hood <ehood@imagine.convex.com>
To: Multiple recipients of list <html-wg@oclc.org>
Subject: Editorial comments for latest 2.0 spec
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: HTML Working Group (Private)

(All references are to the HTML version of the spec)

Here is my $1.25 worth about the spec:

HTMLSPEC_3.html:  2. Overview of HTML Specification,
		  3.4.1 Understanding HTML Elements

    The following text exists:

	Start tags are delimited by < and >, and end tags are delimited
	by </ and >. For example:

	<H1>This is a Heading</H1>
	<P>This is a paragraph.

    The <P> example seems out of place in the context of the sentence
    preceding the example.

HTMLSPEC_4.html:  2.1 Introduction to HTML Elements

    Level conformance is mentioned without prior discussion about HTML
    level conformance.  Example:

	The Anchor element is a feature supported by HTML Level 1.

    As a reader, I'd be confused about this level reference if I was
    new to HTML.  I believe either a cross-reference should be present
    to the level conformance section (3.1), or levels should not even
    be mentioned in the introduction of elements.

HTMLSPEC_9.html:  3.3 Understanding HTML and SGML

    The following text exists in the first paragraph of section 3.3:

	The SGML declaration for HTML is given in SGML Declaration for HTML.

    I believe this is supposed to be a cross-reference (hyperlink), but
    no such anchor exists.

HTMLSPEC_10.html:  3.4.1 Understanding HTML Elements

    The 3rd paragraph of 3.4.1:

	NOTE: Technically, the start and end tags for HTML, HEAD, and
	BODY elements are omissible. However, this is not recommended
	since the HEAD/ BODY structure allows an implementation to
	determine certain properties of a document -- the TITLE, for
	example -- without parsing the entire document.

    I believe should be after the (last) paragraph in 3.4:

	HTML documents should also contain an <HTML> tag at the
	beginning of the file (after the prologue), and </HTML> at the
	end. Within those tags, an HTML document is organized as a HEAD
	and a BODY, much like memo or a mail message. Within the HEAD,
	you can specify the TITLE and other information about the
	document. Within the BODY, you can structure text into
	paragraphs and lists as well as highlighting phrases and
	creating links. You do this using HTML elements.

    And before the beginning of 3.4.1.

HTMLSPEC_14.html:  3.8.4 EM (Emphasis)

    2nd paragraph:

	While <EM> and <I> often give the same effect, use <EM> except
	eeein the case that ...


HTMLSPEC_15.html:  3.9.2 I (Italic)


	The <I> tag specifies that the text be displayed in italic font
	(or slanted if italic unavailable).

    The text:

	where available, otherwise alternative mapping is allowed.

    should be added, like in 3.9.1 B (Boldface).  Browsers like Lynx
    cannot do italics or slanted.

HTMLSPEC_17.html:  3.11.1 (DL) Definition List 

    6th paragraph:

	Unless you provide the compact attribute, HTML leaves white
    ----------------------------------------------^^^^ ^-----------------
	space between successive DT, DD pairs.  The COMPACT attribute may
	also reduce the width of the left-hand (DT) column.

    Should be replaced with "HTML viewer", "formatter", "client", or
    something similiar.  The second "^" mark represents that the
    word "may", or "typically", should be added.

HTMLSPEC_17.html:  3.11.1 (DL) Definition List 

    7th paragraph:

	The opening list tag must be DL COMPACT. It must be immediately
	followed by the first term (DT). For example:

    Awkward paragraph.  Seems better transition (structure) is needed.
    The paragraph asserts that the COMPACT attribute is always

HTMLSPEC_17.html:  3.11 Lists

    General:  The COMPACT attribute is not mentioned for OL and UL.
    Has the COMPACT attribute disappeared for these elements?  If
    not, it might be useful to give formatting/rendering tips for
    the elements when the COMPACT attribute is specified.


    I noticed some slight formatting errors in the HTML version of
    the spec.  I'm guessing it has to do with usage of WebMaker.


That's all folks.


    Earl Hood                |   CONVEX Computer Corporation
    ehood@convex.com         |   3000 Waterview Parkway
    Phone: (214) 497-4387    |   P.O. Box 833851
    FAX: (214) 497-4500      |   Richardson, TX  75083-3851