Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Root element specified by DTD ?

From: "VK" <schools_ring@-----.--->
To: NULL
Date: 6/3/2006 6:31:00 AM

Alan J. Flavell wrote:
> I'm saying that - no matter which specific HTML DTD were to be called
> out from the above DOCTYPE - the result could be an HTML fragment, but
> it would be unreasonable to claim it as an "HTML document".

You have no choice but claim it as "HTML document". It is served from
the served with "Content-Type: text/html", for local files it is served
as the same type by association .html,.htm... --> text/html.

So before any DTD you /have/ to explicetly declare what document you
are serving - this is the only way to make an application to react on
it. This way however you would twist around an HTML code, it is always
/HTML document/ for the recipient: correctly formatted or badly broken
is another issue. Out of curiosity you can serve a page from your
server such as:

Content-Type: text/html\n\n
!@#$%&*


P.S. I'm really glad to see that the discussion at
<http://groups.google.com/group/comp.infosystems.www.authoring.html/browse_frm/thread/4fd4218808cd53ce>

triggered your curiosity and the thinking process in whole.

Just try to not put your frustration on Mr.Kesselman - he has nothing
to do with it.



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent