Re: XHTML 1.0 Strict MIME types (was: Re: CSS and Netscape)

>> You're missing an important point in the note.  The
>> note clearly states that if the HTML Compatibility
>> Guidelines of the XHTML 1.0 spec are met, then
>> XHTML 1.0 may be served as text/html:
> 
> No I was not something missing, but I made the difference between XHTML
> 1.0 strict and XHTML 1.0 transitional/frames
> .
> I wrote only about XHTML 1.0 strict, as in this specs e.g in the img
> element vspace and hspace are not allowed.
> In XHTML 1.0 transitional these vspace  and hspace attributes are
> allowed as in HTML.

vspace and hspace were not allowed in HTML 4.0 Strict either, only in HTML 4.0 
Transitional.

> I also should  serve for that reason XHTML 1.0 transitional as text/html
> but not XHTML 1.0 strict.

That certain old elements or attributes from HTML 4.0 are not included in XHTML 1.0 
Strict is irrelevant; a valid XHTML 1.0 Strict document can still be compatible with HTML 
4.0.

> As you know is XHTML 1.0 not existing ( XHTML 1.0 has 3 DTDs: strict,
> frames and transitional), while only XHTML 1.1 exists. The text in the
> note is something confusing I think (it speaks only  about XHTML 1.0 as
> you do) .

If the note says "XHTML 1.0", it obviously refers to all three variants.

> That makes the difference in my eyes. XHTML 1.0 strict is not
> totally compatible with HTML as XHTML 1.0 transitional is.

XHTML 1.0 Strict is not, but an XHTML 1.0 Strict _document_ can be.

> The differences between XHTML 1.0 strict and XHTML 1.1 are very little.
> Only the lang attribute has been removed from all elements  (is replaced
> by xml:lang) and the name attribute is replaced in some elements  as in
> <a> by only id.

And that is what makes XHTML 1.1 incompatible with HTML 4.0. For certain functionality, 
such as named anchors, you must add the name attribute to be HTML 4 compatible. You could 
do that in XHTML 1.0 Strict, but not in XHTML 1.1.

/Jonas

Received on Sunday, 1 September 2002 05:56:37 UTC