| See also: 6.2.3 "Implied SGML Declaration"
| ... the system can imply the SGML declaration ...
But 6.2.3 doesn't say that an application convention can be established
that the system *must* imply the SGML declaration.
| >It is not possible to override 4.283 in the HTML spec;
| It is possible, and we did it. It's called an application convention.
| Just like null end-tags and all that. I don't understand your point.
I disagree with your assertion of application conventions wrt null
end-tags, too. But the point is just what I wrote: "what 3.3 describes
as an "HTML document" is not an SGML document entity but rather that
portion of it which is to be served to a client." And I note that
6.2.3 says in part:
The [SGML] declaration must be present explicitly, however, if the
document is subsequently sent to another system.
One might well want to process an "HTML document" as an SGML document
entity in the course of preparing it. It would not be an error to
prepend an SGML declaration to it at that point.
-- Terry Allen (email@example.com), Online Books Editor, Songline Studios affiliated with O'Reilly & Associates, Inc. A Davenport Group sponsor. See http://www.ora.com/davenport/README.html "Laid across a map of the US, Indonesia would stretch from coast to coast."