I tend to agree that inline HTML could raise some major problems, both
technical and legal. I prefer managing it somehow through the editing
process, rather than by server or browser, especially since there are a
*LOT* of servers and browsers that currently don't handle it, and a break
would create a serious deficiency in the ability to read a document.
For example, if your browser doesn't support superscript, you can still
read the text, albeit in a degraded display format. If your browser doesn't
support the inlined HTML code, you get *nothing*. Sort of like
non-implementation of the <BASE> element, or those folks who create web
pages solely of inline GIFs with no ALT or alternative links.
I've implemented a document #includes (or "inline HTML") feature in the
latest version of my freeware Mac-based HTML editor (sorry for the plug),
and I used an customizable SGML-like entity format for the included code.
When the document is exported from the editor, the included document is
inserted into the text at the point of the entity. But now I'm a little
curious: what _exactly_ would a document #includes look like in SGML (ie.,
what would the actual tag look like)?
An example someone? Where could I find a spec?
Thanks for any assistance.
BTW, before I get a load of email, HTML.edit 1.7 will be available by COB
today (May 22), info at:
Murray M. Altheim, Information Systems Analyst
National Technology Transfer Center, Wheeling, West Virginia