Structural changes
- Added a general index.
- Added an errata sheet (for future use).
- Added copyright notice
- File "convent.html" renamed "conform.html".
- Arnaud debugged html2ps (!) and his patches
have allowed us to suppress some page numbers
on links in the printed version. We have added
some page numbers to the element/attribute index
in the printed version.
Content changes
- Minor edits everywhere (to correct typos, making wording uniform,
etc.). For example, "document type definition" and "document
type declaration" clearly distinguished.
- URL -> URI throughout spec.
- Added section numbers in external references where appropriate
General
- Status section changed in preparation for REC status
- Addition of marble background.
- Added Copyright notice section.
- Updated list of acknowledgments, including thanks to WAI.
- Expanded list of WAI contributions.
- Added mini-section on start tag/end tag rules
(extracted from other parts of the spec and put here).
An end tag closes open start tags, etc.
Document conformance
- Added definition of authoring tool (under author).
- Removed comment about crufty CRLF relationship
with MIME.
- Added recommendation to authors to use the strict DTD
- Added recommendation to user agents to support HTML 2.0 and
HTML 3.2 in addition to HTML 4.0.
- Rewrote section on white space
to distinguish "input" white space sequences from "output" inter-word
space. Please review. Also adjusted section on line breaks.
-
- Integrated comments from David Abrahamson to the editors.
- Clarified COL/COLGROUP text to match DTD: either COL elements
OR COLGROUP elements at top level. This wasn't clear
in previous text.
- Removed statement about table reflow when
column calculation
is not consistent.
- "border" attribute on TABLE now %Pixel; type (not CDATA). Table
examples fixed accordingly.
Major rewrite please review. While this
section has changed allure significantly since the last
version, the substantive changes are few:
- The "get" method is no longer deprecated.
This may raise some eyebrows, but discussions with the Chair
led to the conclusion that "get" was appropriate for
some types of submission, even though it was not good
for internationalization. The spec now distinguishes
the two more clearly and emphasizes the use of "post"
for i18n. The text about get/post is largely from HTML 2.0.
- The spec now says that an object determines the value
that is submitted for it with a form. This was missing
before.
Note that the subsection numbers have changed because
the form control elements are no longer "under" the
FORM element section.
Ian edited this section to give a more abstract view of forms and
to provide a clearer understanding of (1) which controls are submitted
with a form (called "successful controls") (2) which controls are
"successful". Previous versions of this section only discussed this in
the negative (i.e., what was not submitted with the form.
In particular, please review sections 17.2 (new,
defines useful terms), 17.2.1 (new, lists available
control types whatever element is used to create them),
17.4.1 (cleaner, shorter), and 17.13.
Also added:
- Link to WAI Guidelines for ALT text.
- Edit to section about long description (attached to
frame, not contents).
Major rewrite please review. While this
section has changed allure significantly since the last
version, the substantive changes are few:
- The "get" method is no longer deprecated.
This may raise some eyebrows, but discussions with the Chair
led to the conclusion that "get" was appropriate for
some types of submission, even though it was not good
for internationalization. The spec now distinguishes
the two more clearly and emphasizes the use of "post"
for i18n. The text about get/post is largely from HTML 2.0.
- The spec now says that an object determines the value
that is submitted for it with a form. This was missing
before.
Note that the subsection numbers have changed because
the form control elements are no longer "under" the
FORM element section.
Ian edited this section to give a more abstract view of forms and
to provide a clearer understanding of (1) which controls are submitted
with a form (called "successful controls") (2) which controls are
"successful". Previous versions of this section only discussed this in
the negative (i.e., what was not submitted with the form.
In particular, please review sections 17.2 (new,
defines useful terms), 17.2.1 (new, lists available
control types whatever element is used to create them),
17.4.1 (cleaner, shorter), and 17.13.
- Added "accesskey" attribute to TEXTAREA
- Made "border" attribute on TABLE type %Pixels;.
- Added WAI link for section on alt text algorithm.
New, empty section.