shamkabir
06-03-2008, 06:36 AM
XHTML 1.0 is a reformulation of HTML 4.01 as an application of XML.
XHTML 1.1 is a reformulation of XHTML 1.0 Strict using Modularization of XHTML.
XHTML 1.0 is just an application of XML which uses the same set of element names and attributes (i.e., semantics) as HTML 4.01. It comes in three different DTDs (Strict, Transitional, Frameset) just like HTML 4.01.
XHTML 1.1 uses a concept called Modularization of XHTML, which means that the definition is split into a number of modules, which you can combine in any combination. There's something called XHTML Basic, for instance, which comprises just the essential modules for simple documents. XHTML 1.1 uses all modules (including a module for Ruby annotations that isn't part of any XHTML 1.0 DTD).
For most webpages, the logical choice is still HTML 4.01 Strict.
Why HTML? Because a large majority of users still use Internet Explorer, which does not support XHTML at all. Although you may use XHTML markup and serve it as text/html so that IE will accept the document, it's pointless since you cannot use any advantage that XHTML may have over HTML.
Why Strict? Because the Strict DTD enforces the separation of structure and presentation more than the Transitional DTD (which is mean to be used during a transitional phase when you convert old pre-HTML4 documents to a modern form).
If you absolutely have to write a few scattered '/' characters in your markup to feel manly (or whatever), or if you belong to the .0001% of Web authors who really need XHTML and can afford to ignore IE users, you should probably stick to XHTML 1.0 Strict.
If you serve the document as text/html, don't even think about using XHTML 1.1. It is not backwards-compatible with HTML and should not be served as text/html.
Source : Internet
XHTML 1.1 is a reformulation of XHTML 1.0 Strict using Modularization of XHTML.
XHTML 1.0 is just an application of XML which uses the same set of element names and attributes (i.e., semantics) as HTML 4.01. It comes in three different DTDs (Strict, Transitional, Frameset) just like HTML 4.01.
XHTML 1.1 uses a concept called Modularization of XHTML, which means that the definition is split into a number of modules, which you can combine in any combination. There's something called XHTML Basic, for instance, which comprises just the essential modules for simple documents. XHTML 1.1 uses all modules (including a module for Ruby annotations that isn't part of any XHTML 1.0 DTD).
For most webpages, the logical choice is still HTML 4.01 Strict.
Why HTML? Because a large majority of users still use Internet Explorer, which does not support XHTML at all. Although you may use XHTML markup and serve it as text/html so that IE will accept the document, it's pointless since you cannot use any advantage that XHTML may have over HTML.
Why Strict? Because the Strict DTD enforces the separation of structure and presentation more than the Transitional DTD (which is mean to be used during a transitional phase when you convert old pre-HTML4 documents to a modern form).
If you absolutely have to write a few scattered '/' characters in your markup to feel manly (or whatever), or if you belong to the .0001% of Web authors who really need XHTML and can afford to ignore IE users, you should probably stick to XHTML 1.0 Strict.
If you serve the document as text/html, don't even think about using XHTML 1.1. It is not backwards-compatible with HTML and should not be served as text/html.
Source : Internet