XHTML needs to stand for Extensible Hypertext Markup Language . It's a combination of XML and HTML. It is a simpler, more structured version of HTML.
XHTML is more formal and stricter edition of HTML. i.e.
That's the explanation behind their HTML preferences; most web pages have Bad HTML.
The explanations that explain why XHTML is better than HTML follow:
XHTML validation is a method for validating XHTML documents using a validator from W3C.
XHTML isn't that distinct from HTML 4.01, and it's easy to adopt. You can continue using lowercase letters to compose your HTML code.
In XHTML elements cannot be overlapped.
Let's take an illustration to show that each attribute must have a meaning in XHTML.
Example in HTML:
<ol compact> <input type="radio" name="title" value="decline" checked>Radio Button</input>
Same example in XHTML:
<ol compact="compact" > <input type="radio" name="title" value="decline" checked="checked">Radio Button</input>
XHTML's decomposition into a collection of modules abstract to have modularity is defined as XHTML modularizing.
The XHTML modules are used in the language for interpretation of the XML document type.
XHTML modularization defines a well-defined collection of XHTML compilable and adjustable components. This supports a specific system by the usage of common build blocks and standard techniques for the use of build blocks.
For XHTML three types of DTD are used.
On top of XHTML document you will use all of the DTD.
The Hello World page of XHTML looks like this:
<?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xml:lang="en" lang="en" xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Hello Phptpoint</title> </head> <body> <p>This is My First paragraph.</p> </body> </html>
Modular DTD allows new deployments quick to deploy. A single application supports XHTML subset only. For eg, only a subset of XHTML is needed for a mobile phone, Internet TV, etc.