Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Root element specified by DTD ?

From: "Jukka K. Korpela" <jkorpela@--.---.-->
To: NULL
Date: 6/3/2006 10:43:00 PM

VK <schools_ring@y...> scripsit:

> 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".

Surely there's the option of being silent? And, in fact, saying that it is 
not an HTML document.

> It is served from
> the served with "Content-Type: text/html",

So what? Serving it as image/gif would not make it a GIF image. The Internet 
media type would be incorrectly declared. A Content-Type declaration does 
not magically _make_ the data conform to the specification of a specific 
media type.

> for local files it is
> served as the same type by association .html,.htm... --> text/html.

That's a rule that you just made up. Besides, nobody said the filename 
suffix is .html or .htm. For all that you can know, it can be .gif or .foo.

> So before any DTD you /have/ to explicetly declare what document you
> are serving

Nope. Nobody forces you to serve a document on the Internet, or using HTTP 
in particular.

-- 
Yucca, http://www.cs.tut.fi/~jkorpela/ 



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