> When the above conflicts with the SGML standard, the SGML standard
> may be ignored. Note, however, that not all HTML applications are
> capable of ignoring the SGML standard.
to which Gavin suggests the change
When the above conflicts with the SGML standard, the SGML standard
may be ignored. Note, however, that not all HTML applications are
capable of ignoring the SGML standard, and that strict conformance
may be required in the future.
The old language was:
2.5 Understanding HTML and SGML
HTML is an application of ISO Standard 8879:1986 -
Standard Generalized Markup Language (SGML). SGML is a
system for defining structured document types, and
markup languages to represent instances of those
document types. The SGML declaration for HTML is given
in Section 5.1. It is implicit among HTML user agents.
If the HTML specification and SGML standard conflict,
the SGML standard is definitive.
and that is the only approach I can support. HTML is defined as
an application of SGML; we cannot ignore the SGML standard when we
choose. It's that second para, saying that the SGML standard is
definitive, that is still needed. The wording about how some HTML
apps can't ignore HTML is kinda odd considering almost all of them do.
What's at issue here is how browsers are to do error recovery;
let's not say we're defining an SGML app and then saying the SGML
standard isn't normative for SGML apps.
Regards,
-- Terry Allen (terry@ora.com) O'Reilly & Associates, Inc. Editor, Digital Media Group 101 Morris St. Sebastopol, Calif., 95472 occasional column at: http://gnn.com/meta/imedia/webworks/allen/A Davenport Group sponsor. For information on the Davenport Group see ftp://ftp.ora.com/pub/davenport/README.html or http://www.ora.com/davenport/README.html